Privacy Policy

What this privacy policy covers

This policy covers privacy questions connected with visiting this website and contacting our team about marketing work. It gives you a practical starting point for deciding what to share and how to ask about information connected with your conversation.

The available policy details do not identify particular analytics tools, hosting providers, retention periods, or legal bases for processing. Rather than guess about those arrangements, ask for clarification before providing information that needs specific handling. This is especially useful when your request involves confidential launch plans, unpublished token details, or personal information about team members.

Use this page alongside the terms of service for the rules that apply to use of the site and any agreed work. For questions about a particular information request, send a note through Contact and describe the issue without including sensitive credentials. We can then identify what clarification you need before you share more.

What information might you share when contacting us?

You control what you include in an initial inquiry. A message may contain contact details, your project name, a description of the work you are considering, and context that helps explain your goals. If you attach a brief or other project material, check it for personal information and confidential details before sending it.

Keep the first message focused. A useful privacy-conscious checklist is:

• Give a work contact method and a short description of your request.
• Remove personal information that is not needed to understand the project.
• Label material that is confidential and explain any handling limits before sharing it.
• Never include passwords, private keys, seed phrases, or wallet recovery information.

This checklist is guidance for what to send, not a statement that the site requests every listed item or uses a particular form. If you are unsure whether a document is appropriate to share, ask first through the contact page. You can explain the type of document without attaching it.

How should you handle project and campaign information?

Treat project materials as information you choose to disclose, and share only what is needed for the conversation at hand. For an early discussion, a summary of the project, intended audience, and requested support is usually a more careful starting point than a full folder of internal files.

Before sending a document, check whether it contains personal contact details, unpublished announcements, access credentials, investor information, or third-party material you are not authorized to disclose. If confidentiality terms or a specific transfer method matter to your team, raise that point before sending files. Do not assume that a message channel or attachment has special protections unless those protections have been confirmed.

When a request concerns work already discussed, identify the project and the relevant conversation in your message, but omit secrets and credentials. This gives the team a clear way to understand your question without exposing information that is not needed. If your project has handling requirements, state them plainly at the start so they can be reviewed before additional materials are shared.

How do you ask about your information or reduce exposure?

You can ask what information is associated with a particular inquiry, request clarification about its handling, or explain a concern by contacting the team. Include enough context to identify the conversation, such as the email address you used and the project name, but do not send identity documents or account credentials unless a specific, appropriate process has been confirmed.

For a practical first step, send a short message that states:

• The contact method or project conversation involved.
• Whether you are asking for clarification, access, correction, or deletion.
• Any specific information you believe should not have been included.

The information available for this policy does not specify a response deadline, retention schedule, or technical security controls. Ask for those details directly if they are important to your decision. To reduce exposure while you wait, avoid forwarding sensitive attachments and remove unnecessary details from any follow-up. Keep a copy of your request so you can refer to it if you need to continue the conversation.

What if this privacy policy changes?

Review this page again before sharing information if your project has new confidentiality requirements or if you return after a significant gap. A revised policy may clarify how information is handled, so do not rely on assumptions based on an earlier conversation when the details matter to your team.

The current available details do not set out a notice method, update schedule, or effective date. If you need to know whether a particular version applies to a conversation, ask and identify the policy text you reviewed. For the service relationship itself, review the terms of service; for a general introduction to the team and its work, start at Home.

Before contacting us, prepare a short description of the work and flag any information that must remain confidential. Send that outline through the contact page without credentials or sensitive attachments. The team can clarify the privacy questions first, then you can decide what material is appropriate to share.