Who is responsible
Sesame runs the desktop app and the website at usesesame.app. For the optional website account, Sesame is the data controller. Send privacy requests to privacy@usesesame.app. The public beta is open to download, and we will publish the operator identity and postal address before the beta ends.
What we process
The desktop app keeps your vault entries, unlock material, imported exports, 2FA seeds, backup codes, and recovery notes on your device. The website and the account service are not built to receive them. If you turn on Sync, the desktop app sends an encrypted copy of your vault to the sync server you choose. That is a server you run, because hosted Sync is not available yet. The copy is encrypted on your device, so the server holds data it cannot read.
If you create a website account, the account service handles this data:
- Your email address, whether it is verified, a salted password hash, and the Terms and Privacy Policy versions you accepted.
- Your licence records and the identifiers of your connected desktops.
- Session, CSRF, and passkey tokens, session times, and short-lived rate-limit data derived from network information.
- A record of account security events, such as sign-ins and changes.
- The text you send through the support form, which takes no attachments and rejects likely secrets before sending.
Sesame has no advertising, behavioural analytics, profiling, session replay, or third-party trackers, and it does not sell or rent personal data.
The browser extension
The browser extension has no server and no account. It asks the desktop app for the value you want, and the desktop app answers only after you approve. To do this, the extension reads the structure of the form on the active tab and writes the approved value into it.
If you choose Save this login after Sesame filled a sign-up form, the extension reads the new username and password from that form and sends them to the desktop app for your approval. A password the extension generates in the change password flow stays in memory until you save it, close the tab, leave the site, or ten minutes pass. Other credential values stay in memory only while a request or an approval is open.
The extension writes none of these values to browser storage, logs, or any server. Its browser storage holds only the sites where you paused the inline button and whether onboarding was shown. It sends nothing to Sesame or to anyone else.
Why we process it
For users in the EEA and the UK, the account service relies on contract to provide the account, licences, sessions, desktop connections, and recovery. It relies on legitimate interests to prevent abuse, protect the service, and answer support requests.
You must agree to the Terms to create an account. Acknowledging this policy does not give permission for marketing or tracking. The desktop vault does not need a website account.
Retention and recipients
Account records stay until you ask for deletion or the beta closes. Website sessions last up to 30 days unless you sign out or revoke them sooner. Account security events are kept for 180 days. The CSRF token lasts up to one hour, and a passkey token lasts up to ten minutes. Support requests have no automatic expiry in this beta, so keep sensitive information out of them and ask for deletion by email when you no longer need them.
Two processors run the service, and there are no others:
- Hetzner Online GmbH in Falkenstein, Germany, hosts the server, the account database, and the mail relay that sends account email. All account data is stored there, inside the EU.
- Cloudflare, Inc. in the United States provides DNS for the domain and forwards mail sent to published contact addresses, such as the privacy address, to an operator mailbox.
Account email goes out through Sesame's own mail relay on the Hetzner server, so Sesame uses no outside outgoing mail service for verification, recovery, or email change messages.
International transfers
Account records, the database, and outgoing account email stay in Germany, inside the EEA, so they need no transfer safeguard.
Cloudflare is established in the United States. A message you send to a published contact address passes through Cloudflare, which is a processor outside the EEA. That transfer relies on Cloudflare's data processing terms, including the European Commission's standard contractual clauses. If you prefer not to use that route, contact us through the support form, which does not use Cloudflare mail routing.
Your rights
Under applicable law you can ask for access to your data, correction, deletion, restriction, and a portable copy, and you can object to processing based on legitimate interests. Email privacy@usesesame.app to use these rights. You can also complain to your local data protection authority. Where the GDPR applies, we aim to reply within one month.
Contact and changes
Send privacy questions and requests to privacy@usesesame.app or use the support page. Before a material change applies to existing accounts, we will publish the new version and highlight what changed.