Privacy

Last updated 13 September 2026

Who we are

Eden is an independent project operated from Seattle, Washington, currently in a closed beta. “Eve” is the personal agent Eden gives each person. Questions about anything on this page go to privacy@evebyeden.ai.

What Eden stores

Your account

Sign-in is handled by Clerk. Eden itself keeps a display name, a timezone, and the identifier Clerk gives your account. Your password never reaches Eden, and neither does a passkey’s private key — that stays on your device.

What you tell Eve

Memories, reminders, shared lists, polls, and messages in spaces you join. Each is marked personal or belonging to one space, and that marking is enforced when context is assembled, not merely when it is displayed.

Connector tokens

The token that lets Eve read a connected account is sealed with AES-256-GCM before it touches the database. It is never written to a log, never placed in a prompt, and never put in a background job — jobs carry identifiers only.

Suggestions found in your email

When you connect Gmail, Eden records what it concluded — a short title, a kind (bill, RSVP, appointment, deadline, renewal, task), a due date, an amount, a confidence score — along with Gmail’s identifier for the message, which is how Eve can point back at an email without keeping one. Suggestions are inert until you confirm them.

An audit record

Every action an agent takes writes a row recording that it happened, in the same database transaction as the action itself. These rows hold identifiers and the kind of action, and they are what makes it possible to answer “what did my agent do?” honestly.

Device tokens

A push token per device, so notifications can reach your phone.

What Eden does not store

• Email bodies. A message is read in memory while obligations are extracted from it and is discarded when that finishes. No copy is written to the database.
• Calendar event titles, attendees, locations, and descriptions. Availability is reduced to a list of start-and-end pairs at the boundary where it enters Eden. The type the rest of the system receives has two fields and nowhere to put a title, so no later code can leak one even by mistake.
• Your passwords for connected accounts. Connections go through Google’s OAuth flow; Eden never sees the password.
• Payment details. Eden takes no payments.
• Screen contents, keystrokes, location, or audio. Eden does not collect any of them.

What your agent shares, and with whom

Inside a space, agents exchange structured conclusions only: an availability verdict for a date, a stated preference, or a poll tally. There is no channel for one agent to send another free text. Anything written in sentences is posted into the space itself, where every human member can read it.

Personal memories and email suggestions never enter a run whose output is destined for a space. That is a filter in code, applied when context is assembled.

Who else processes your data

• Clerk — accounts and sign-in.
• Supabase — the Postgres database Eden stores everything in.
• Railway — where Eden’s API and background worker run.
• Anthropic — the model provider Eve runs on. Prompts are sent through its API, whose terms do not permit training on API inputs. A separate provider may compute the numeric embeddings used to search your memories.
• Google — only if you connect a Google account, and only for the read-only scopes listed below.
• Apple and Expo — delivery of push notifications to your device.

Google user data

Eden requests only these scopes, both read-only:

• https://www.googleapis.com/auth/calendar.readonly — used solely to compute the times you are busy.
• https://www.googleapis.com/auth/gmail.readonly — used solely to find obligations with dates and surface them to you.

Eden has no write access to either. It cannot send mail, cannot create or change a calendar event, and cannot delete anything in your Google account.

Limited Use. Eden’s use and transfer of information received from Google APIs to any other app will adhere to the Google API Services User Data Policy, including the Limited Use requirements. Google user data is used only to provide the features described here, is never sold, is never used for advertising, and is never used to train a model. It is read by a person only when you ask us for support, when it is necessary for security, or when the law requires it.

We do not train on your data

Nothing you write, connect, or store in Eden is used to train a model — not ours, not a provider’s. Eden does not grant itself a licence to your content in order to do so, and does not sell or rent your information to anyone.

Keeping it, and getting rid of it

• Disconnecting an account deletes the sealed token for it. Eve loses access at that moment — there is no cached copy that keeps working afterwards.
• Deleting your account removes your memories, reminders, suggestions, connections and device tokens. Write to privacy@evebyeden.ai and it will be done within 30 days.
• Audit rows are kept after the content they refer to is gone. They record that an action happened, not what was said, and they are the record that makes the rest of this page checkable.
• Content in a shared space — a poll, a list, a message — stays visible to that space’s members, the same way a sent message does.

Where your data lives

Eden’s database and servers are in the United States. If you use Eden from elsewhere, your information is processed there.

Children

Eden is not for people under 16, and we do not knowingly collect their information.

Changes

If this page changes in a way that affects what Eden does with your information, we will say so in the app before the change takes effect, not only by editing this page.