A privacy policy for your first conversation

What happens after you send us a message?

This privacy policy covers details you choose to send when you ask us about work or raise a privacy question. It explains how we use those details to reply, consider a possible project, and coordinate agreed work. It does not describe every technical record a website may create.

If cookies, device logs, or similar details matter to you, ask us before sharing project information. For a first note, a name, a reply route, a project name, and a short question are usually enough. That gives us context without asking you to expose more than needed. Please leave out anything that could let someone enter an account or control a wallet. If more context would help, we can explain what to share before you send it. You can also read the terms of service for the rules that apply when using this site.

When a group detail enters a project message

Imagine a volunteer who runs a fan group and spots that its pinned message is out of date. They contact us while considering a refresh, sharing the group name, a way to reply, and a brief description of what they want to discuss. That is enough for us to understand the question and respond.

We would use those details to follow the conversation and discuss whether our work fits what the volunteer has in mind. If the volunteer later shares a draft message, we would use it to discuss that requested work. They do not need to send group members’ personal details just to explain the issue. Nor should they include passwords, wallet recovery phrases, or private keys. If another organizer needs to join the conversation, the volunteer can tell us which project details may be discussed with that person. A small note about who may see the information helps keep the conversation clear.

Keep the first message easy to handle

A useful first message gives us enough to understand your question without exposing extra personal or project information. You can start with a few simple details and add more only if the conversation needs them.

• Tell us what you are asking about, in plain words.
• Include the project or organization name only if it helps explain your question.
• Give one preferred way for us to reply.
• Leave out account access details, private keys, and wallet seed phrases.

Say you want to ask whether a project discussion might be useful. A short note describing the project and the question is a better start than a folder of internal documents. If sensitive information becomes relevant, ask us first how to provide it. We can tell you what context would help us respond. For a general picture of the team and its work, visit About us. You can also begin with How we work if you want to understand how conversations about an engagement are handled.

A clear route for questions and changes

For a question about a message, a correction, or a request to review whether information is still needed, give us enough detail to find the right conversation. Use this 3-part guide:

1. Name the email address or communication channel used in the original exchange.
2. Describe the message or information you mean, as closely as you can.
3. State what action you want us to consider, such as correcting a detail.

You do not need to attach sensitive documents or repeat private information to make the request. We may ask a follow-up question if we cannot tell which conversation you mean. If you are writing for someone else, explain your authority and share only what helps us assess the request.

For example, if a contact detail in an earlier note is wrong, identify the channel and the detail to review. We can then consider the request and explain the next step. We do not set a fixed deletion schedule on this page, and it does not name particular communication tools, data locations, or technical safeguards. Ask us about those details before sharing sensitive material.

Before you press send

We keep submitted information for as long as it remains useful for answering your request, coordinating relevant work, or keeping a record of decisions. The appropriate period can vary with the conversation and any ongoing obligations. If you have a question about a particular message or record, tell us which conversation you mean.

Please consider both the information and the channel before sending anything sensitive. This page does not describe specific technical protections or establish that a communication method is risk-free. Never send account credentials, recovery phrases, or private keys. If you already sent something that should not have been included, tell us what it was and where you sent it, without repeating the secret itself.

For a privacy question or request, use the contact page and label your message as a privacy matter. Include the channel, a brief description, and the action you want us to consider. We will review the request and reply with the next appropriate step. You can also ask us which details are needed before sending project information.