What we hold, and what you can take back.

It depends on how far along you are.

• If you only read the site. Nothing that identifies you. If you open Dahlia, the guide on the public pages, the site sets one cookie holding a random value so your conversation can continue on the next page. We store a one-way hash of that value, never the value itself, and never your name or email.
• If you ask the founders for a conversation. What you type into the form: your name, your email, the organization if you give one, and your message. If you were talking with Dahlia first, you see the note before it goes anywhere and you can edit it.
• If you apply. Your name, your email, the project you want to bring, whether you confirmed the meeting times, and whether you ticked the box to hear about future cohorts. Applying is by invitation after a conversation, so your application is linked to the invitation that was issued to you.
• If you join a cohort. Your account email, your display name, your time zone, your reminder preferences, and then the work itself: your project, your goals, your promises and their dates, your check-ins, files you upload, work you share with the crew, feedback you give and receive, and your conversations with Dahlia.

Your conversations with Dahlia and everything she remembers about you belong to your account alone. The database itself refuses to hand them to anyone else, including the founders. That rule is written into the data, not into a screen, so no setting or mistake in the interface can open them.

Sharing is always an act you take. When you want the crew or a founder to see something, you pick it, preview exactly what they will see, and send it. Nothing from a private conversation moves into the pipeline, the meeting notes, the founders' reports or anyone else's workspace on its own.

Sessions are recorded or transcribed only after a notice for that specific session and each person's own agreement. Founders control access to any recording, and nothing is shared publicly without separate permission. Accepting the pilot agreement is not consent to be recorded. Otherwise, what survives a meeting is typed notes, and the actions in them become tasks only after a founder approves them and the person they belong to accepts them.

Program email goes to one person at a time. Your address is never shown to another participant and we do not use mailing lists that expose it.

Reminders are yours to control in your workspace settings: which kinds you get, the hours you do not want to be disturbed, and turning them off. We keep a record of each message we attempted and what the mail provider reported back, so we can tell a delivered message from a bounced one and never resend blindly. Ticking the box about future cohorts is separate from program email, and you can withdraw it.

Card details never reach The Pit. Payment runs on a payment provider's own checkout page. What comes back to us is the record: which offer, the amount, the currency, the provider's receipt identifier, and whether it succeeded, failed or was refunded. We use that to hold your seat and to reconcile the books.

Dahlia is software, not a person. When you ask her something, your message and the parts of your own workspace she is allowed to read are sent to a model provider, which generates the reply. She is given your work and nothing belonging to another member.

She cannot take money, grant access, accept anyone into a cohort or send a message to anyone. When she proposes something, it is a proposal: you confirm it before it is saved.

Private voice notes are recorded only when you choose and consent. Founders cannot hear the audio or read the transcript. Transcription uses the Lovable AI gateway. Raw audio stays private until the pilot ends on December 6, 2026. It is deleted on December 7. Your transcript stays until you delete it.

Separate live spoken conversation is off. Before it is turned on, the retention setting on the voice provider's account has to be confirmed and stated here, because that provider, not us, decides how long it holds audio.

There are no advertising trackers and no third-party analytics on this site. The cookies in use are the one that keeps you signed in and the random one described above for the public Dahlia conversation. Our hosting records ordinary server logs, including the address your request came from, which is how a site defends itself against abuse.

The founders see your application, the work you submit, the check-ins you choose to send, your attendance and your payment records. They do not have a way to read your private conversations with Dahlia or her memory of you.

The operations screens the founders use show status, not content: whether a message was attempted, whether a job is waiting, whether a payment needs reconciling. Every sensitive action is written to an audit record with who did it and when.

• See everything Dahlia remembers about you, edit it, or delete an item. Deleted memory is excluded from what she can read.
• Download your own data as a file from your settings. It includes your work, your promises, your files list and your conversations.
• Ask for your account and its data to be deleted. The request is recorded and you get confirmation when it is done.
• Change or stop reminders, and set quiet hours.
• Unshare work you previously shared, so it stops being visible to the crew.

Program records stay while you are a member and afterwards as the business record of a program you took part in: your enrollment, payments, attendance and the work you submitted. Private conversations and memory stay until you delete them or your account is deleted.

An inquiry that never becomes anything is removed on request, and removing it takes out that request and the unshared pipeline entry it created, nothing else.

When this page changes in a way that matters, the date at the top changes with it and members are told in the workspace.

To ask a question about your data, to ask for a copy or to ask for deletion, use the form on the contact page if you are not a member, or your settings page if you are.