Protect the archive and its access
The beta requires a signed-in account and keeps each account’s archive separate. Email and password accounts verify their email address; Google sign-in uses Google’s account identity. The service uses encrypted transport, server-encrypted archive files and restricted operational access.
Server encryption does not mean the service is unable to read your records. The server holds the encryption keys. SEED is not described as end-to-end encrypted, zero knowledge or independently certified.
A small, explicit connection
Gmail access is read-only and separate from Google sign-in. You choose a date range for each import. Email previews use text without loading remote tracking images. The beta does not offer AI conversations or send your archive to an external agent.
Report a concern
Send the affected page and a description of what happened to [email protected]. Please leave private records, passwords and access tokens out of the report. We do not promise that any system is invulnerable.