Privacy

HeyArden operates this site and the Arden app, and is the party responsible for the personal information described here. Post: Address to be confirmed, Ontario, Canada. Email: hello@heyarden.app.

Arden is built in Canada, so the Personal Information Protection and Electronic Documents Act applies. If you are in the United Kingdom or the European Economic Area, the UK GDPR and the GDPR apply to you and the rights below are yours by law rather than by our goodwill. If you are in California, the CCPA rights below are yours.

This page covers heyarden.app, the marketing site you are reading, and the Arden iPhone app.

The site itself collects almost nothing. The app is where the real data is, and the rest of this page is about that.

If you join the list we store your email address, the time you signed up, the page that referred you, and your browser’s user-agent string. If you answered the optional name, company and role questions while the site asked them, we store those answers too. That is everything kept about a signup.

We use it to email you about early access and for nothing else. Every email we send has a working unsubscribe link, and unsubscribing removes you from the list.

The site also counts page views, so we can tell whether anyone is reading it. That is Vercel Web Analytics, and it sets no cookies. A visitor is identified by a hash of the incoming request rather than by anything saved on your device, and that hash is thrown away after 24 hours. What gets recorded is the page, the page that sent you there, an approximate location worked out from your IP address, and your browser, operating system and device type.

There are no advertising cookies, no tracking pixels, and nothing on this site follows you anywhere else.

With your permission, Arden connects to your Google Calendar directly through Google, and to your Gmail through Nylas, a mail infrastructure provider. Both are separate, later choices, and signing in grants neither. Arden reads mail and calendar to do what you asked, and writes calendar events and email drafts only after you approve them.

It stores what you capture. Notes, tasks, commitments, open loops, and what it learns about the people you work with, so that it can bring things back to you later. That memory is the product.

Voice you record is transcribed so it can be understood. You can delete any capture, and its transcript goes with it.

Arden requests the narrowest permissions that let it do what you asked, and the calendar and mail connections work differently, so here is each one plainly.

Your calendar (calendar.events) is a direct Google permission. Arden uses it to know when a meeting is coming and who is attending, and to create an event when you ask for one out loud. Any event Arden creates or changes is shown to you first and only happens after you confirm it. The tokens for this connection are encrypted and held by Arden.

Your mail is connected through Nylas, not through a Gmail permission that Arden itself holds. When you connect your mailbox, the Google consent screen names Nylas, because the connection runs through their infrastructure; Arden never receives your Gmail password or your Google mail tokens. Through that connection Arden reads recent correspondence with the people you are about to meet, and checks whether something you said you would send actually went out. Sending is separate: a draft is written, shown to you, and sent only after you approve that specific message. Arden never sends email on its own.

Arden’s use and transfer to any other app of information received from Google APIs will adhere to Google API Services User Data Policy, including the Limited Use requirements.

We do not sell your data. We do not share it with advertisers or data brokers. We do not use your email, calendar or captures to train models.

Sending an email always requires your confirmation. Arden never sends on your behalf without you approving the specific message.

Email and calendar content Arden has synced is kept for as long as your account exists. There is no automatic expiry today. Disconnecting an account removes what came from it, and deleting your account removes everything.

A scheduled clear-out of older mail is planned, and this page will describe it once it runs. We would rather tell you what happens now than describe a rule that has nothing behind it yet.

The record of actions Arden took on your behalf is kept for as long as your account exists.

Tasks, open loops, notes, memories and the people Arden knows about are kept until you delete them or delete your account.

Voice is transcribed on your iPhone and the audio is never uploaded. Only the resulting text reaches Arden.

Everything Arden remembers is readable, editable and deletable inside the app. Every read and write Arden makes is recorded with a timestamp; the in-app screen that shows you that record is still being built, and until it ships you can request the record by email.

Deleting your account deletes your data, and revokes the calendar connection with Google and the mail connection with Nylas. You can also disconnect either one at any time, in Arden or from your Google account settings, which stops all further access immediately.

If you are in the EU or the UK, you have the right to access, correct, export and erase your data, and to object to processing. Email hello@heyarden.app and we will do it.

Arden is operated from Ontario, Canada. Your data is stored and processed on managed cloud infrastructure that may be located outside Canada.

Five companies process data on Arden’s behalf, and no others. Supabase stores the database, where every table is isolated per user at the database level. Railway runs the server. Anthropic processes the text of what you say or write, in order to produce the answer you asked for, and it is not used to train their models. Voyage AI converts your notes and memories into numerical form so Arden can search them by meaning. Nylas operates the mail connection: it holds the grant that links your mailbox, refreshes the Google credentials itself, and holds a copy of message content on its US-hosted infrastructure in order to serve it to Arden.

Your Google Calendar tokens are encrypted with AES-256-GCM before they are stored, with the encryption key held outside the database, and they never reach your iPhone. Arden stores no mail credentials at all. That is what Nylas holds.

Error reports contain no message content, no email content and no personal data.

Your Google Calendar connection is encrypted with AES-256-GCM before it is stored. GCM authenticates as well as encrypts, so tampered data fails to open rather than quietly decrypting into something wrong. The key is never in the database: it lives in the server environment, which means a stolen copy of the database opens nothing. It never reaches your iPhone either, because the app holds no third-party keys at all.

Arden never stores your mailbox password or token. Mail runs through Nylas, which holds the connection; Arden holds an identifier for it and nothing more. The safest credential is the one that does not exist on our side.

Every table is isolated per user at the database level. That isolation is enforced by Postgres itself rather than by trusting application code to filter correctly, which is the difference between a rule and a hope.

The database runs on Supabase, which states that all customer data is encrypted at rest with AES-256 and in transit via TLS.

What none of that means: Arden is not end-to-end encrypted, and it is not zero-knowledge. Email subjects and bodies, notes, memories and tasks are ordinary database rows, because Arden reads them on the server to rank your mail and assemble your prep. Any assistant that reads your mail for you is in the same position, and we would rather say so than use a phrase that sounds stronger and is not true.

If this policy changes in a way that matters, we will tell waitlist members and users by email rather than quietly editing this page.

Questions about any of it: hello@heyarden.app.