BETA REQUEST PRIVACY · NOVEMBER 2026

A little information.
A clear purpose.

What we collect

If you request beta access, we collect your name, email, optional use-case description, permission to contact you, and the request's status and timestamps. Please do not include client details, health information, passwords or documents.

Why we use it

Sealform's beta administrators use this information to review your request, record an approval or decline, and contact you about beta access. A request does not create an account or subscribe you to marketing. Approval sends a private, single-use invitation to register one workspace.

Where it is processed

The public website and request API run on Vercel. Beta requests are stored in a separate Neon PostgreSQL database. Resend handles beta request notifications, decision emails and mail to info@sealform.io. The request database is separate from the encrypted forms application; beta request details are not end-to-end encrypted.

Access and retention

Request details are private to administrators and our service providers. Private review and workspace-invitation links expire after seven days. Administrator sign-in links are single-use and expire after 15 minutes; administrator sessions last up to eight hours. We retain request details while processing beta access and preparing invitations. You can ask us to remove your request or withdraw permission to contact you by emailing info@sealform.io. Operational logs and provider backups may persist separately under their retention policies.

Website and abuse protection

This website does not use analytics, advertising scripts or tracking cookies. Signed-in beta administrators use a secure, HttpOnly session cookie to manage requests. The request service uses a keyed hash of network address and email to limit abuse; raw network addresses are not stored in the beta request database. Hosting and email providers may retain operational metadata. The website does not accept form documents or customer submissions.