Before a project goes public: the privacy policy

What may accompany a private project conversation?

The information involved may include details you choose to share, plus basic technical data generated by using the website.

A message may contain your name, business contact details, organization, project description, communications or attached materials. For a marketing discussion, that might mean public project links, objectives, preferred channels or launch details. A website visit may also make technical information available, such as browser or device details, requested pages and basic connection data. The information visible can vary with your browser settings and the tools used to operate the site.

Please do not include account passwords, private keys, wallet recovery phrases or other credentials in an initial inquiry. They are not needed to understand a request. If a document may contain personal or confidential details, ask before sending it. You can begin with a summary, then decide whether further material is necessary.

Use follows the reason for contact

Discreet handling begins with a simple distinction: what is needed for your request, and what is not.

Information may be used to respond to an inquiry, understand a project, prepare or administer requested work, communicate about it and maintain appropriate business records. A general website visit and a discussion about a potential engagement do not call for identical details. We aim to use information relevant to the purpose rather than request material without a practical reason.

Details may also support website operation, protection, technical troubleshooting and the detection of misuse. If you share project materials, they may be consulted to assess the work requested and communicate about it. You may identify project details as confidential and state the handling expectations you would like discussed. The How we work page offers context on working arrangements; the specific engagement may clarify what information is needed.

A narrow path for sharing

Information may be shared when that is relevant to its original purpose, website operation, or a legitimate business or legal need. The people involved and the details disclosed depend on the circumstance; an inquiry is not treated as permission to circulate its contents broadly.

A practical check before sharing is to identify the recipient and the information involved. For example:

• Website or engagement support may receive details relevant to their task.
• A legal obligation may require disclosure of particular records.
• A platform or publisher may need information to carry out a specific requested placement.
• A party you ask us to coordinate with should be identified, along with the information you authorize us to share.

You may ask about a proposed disclosure before materials are sent. A considered sign-off means naming the party and the information you authorize, rather than sending an open-ended approval. The Terms of service provide additional context for service arrangements.

The record, the people involved and your approval

The handling of a record depends on its purpose and the people involved. This table describes the points you can clarify; it does not create a fixed retention period or an approval process beyond the information you choose to provide.

Nothing in this summary asks you to provide credentials. If a particular disclosure is under discussion, you can ask what information is needed before authorizing it. For a general inquiry, a short description may be enough to establish the context.

Retention and protection in context

Information is kept while it remains useful for its purpose, for managing an engagement, or for addressing relevant business and legal needs. The appropriate period can differ by record and circumstance, so this policy does not assign one fixed period to every message, project file or technical record.

Access is limited to information relevant to the work or business task. We take care in handling records, while recognizing that online transmission and storage cannot be described as risk-free. Share only what is needed, and use reasonable care when sending sensitive material.

A conversation that does not proceed, or an engagement that ends, may still leave records held for a relevant operational or legal purpose. You can ask whether particular information remains held and request correction or deletion. The request will be considered in light of the record, its circumstances and applicable obligations. A private summary can often establish the question without attaching the original material again.

A discreet route for questions and changes

You may ask what information you provided, request a correction, or ask whether deletion is possible. The options available can depend on where you live, the information involved and any relevant business or legal reason to retain it.

Use the contact page and describe the record or conversation in question. If comfortable, include 1 identifying detail, such as the email address or project reference associated with the inquiry. State the action you are requesting, and do not include passwords or secret credentials. A follow-up may be needed to understand the request or verify it; if you are acting for another person or organization, explain your authority.

The policy may change as the website or practices change. For a question about a particular project, identify it so the response can address that context. Which email address or project reference should help locate the record? The contact point can then ask for a focused clarification if needed; no 2-working-day response deadline is stated here.