Privacy Policy

1. What we collect

Account details you give us: your name, email address and the community details you provide during onboarding.

Content and memories: what you write to the co-founder, the drafts it produces, and the facts it records about your community and your voice.

Connection data: the tokens and page identifiers needed to publish to a destination you connected, stored encrypted.

Operational data: logs, error traces and basic usage events needed to run the service and investigate problems.

Waitlist data: if you join the beta waitlist, your name and email address, and nothing else.

2. Why we use it

To run the service for you: to ground drafts in what you have told us, to publish what you approve, and to report how a post performed.

To keep it safe: to screen generated content, to enforce spend caps, and to investigate abuse.

To talk to you: to send sign-in links, invites and service notices. We do not send marketing email to beta participants without asking first.

3. What we do not do

We do not sell your data. We do not use your content or memories to train shared models. We do not pool one community's material with another's. Each community's memory is isolated, and that isolation is a property of the system rather than a policy applied on top of it.

4. Memory, and deleting it

You can see everything the system remembers about you in the memory panel, in plain language, and export it as a file.

Deleting a memory removes it from what the model can reach. It is not archived out of sight or merely hidden in the interface. After deletion it does not come back in answers.

Deleting your account removes your content and memories from our production systems. Backups age out on their normal cycle, and we do not restore deleted material from them.

5. Who we share it with

Service providers who process data on our behalf under contract: our cloud host, our database and storage providers, our email provider, and the model providers behind drafting and image generation.

Destinations you connect: when you approve a post, its content goes to the platform you chose. That platform's own privacy policy then applies to it.

Legal requests: where we are legally required to disclose, and where we may lawfully tell you, we will.

6. Where data is held

Data is processed in the United States. If you are in the UK, EEA or Switzerland, transfers rely on Standard Contractual Clauses or another lawful transfer mechanism.

7. How long we keep it

Account and content data is kept while your account is active. Waitlist entries are kept until the beta closes or you ask us to remove yours. Operational logs are kept for a limited period and then discarded.

Records of approval and consent are kept for as long as we are required to, because their purpose is to show who agreed to what.

8. Your rights

Depending on where you live you may have the right to access, correct, delete, restrict or object to our use of your data, and to receive a copy in a portable format.

Write to the address below and we will action it. We will not charge you for exercising a right and we will not treat you differently for having done so.

9. Security

Connection tokens are encrypted at rest. Access to production data is limited to the people who need it, and administrative actions are logged.

No system is perfect. If we discover a breach affecting your data we will tell you and the relevant regulators within the time the law requires.

10. Children

Ge·on is not for anyone under 18. We do not knowingly collect data from children, and we will delete it if we find we have.

11. Changes

We will post any update here with a new date, and will email beta participants where a change is material.