Data handling

Know where your data goes.

How the website, your SEED account and Gmail permission fit together.

This website

Reading a guide does not connect an account or import records. The guides link to the provider’s own export process. A guide is not a claim that SEED can import that service.

If you join the product updates list, we store your email address, consent and signup date, then synchronize the contact to a dedicated list in Resend. The form does not collect archive contents or create a beta account.

Your beta archive

A SEED account has its own archive. Google sign-in requests basic account identity. Gmail import has a separate permission step and uses read-only access: it cannot send, edit or delete messages in Gmail. Google’s permission covers reading the mailbox; the date range you select limits what SEED imports.

The service stores selected messages, their attachments and metadata on its hosted infrastructure. Files are encrypted on the server; the keys are also held there. Email previews show text and do not load remote images. Automated AI processing and sharing with external agents are not included in this beta.

Service providers

Azure provides hosting, Cloudflare provides traffic delivery and protection, and Resend handles product-list contacts and account emails. Google provides sign-in and Gmail access when you choose to connect it. See the privacy notice for data use, retention and contact information.

The next chapter

Begin with what you would hate to lose.

Keep the original and the story behind it. Your history deserves a home.

Join the waitlist