Last updated September 16, 2026
Privacy at Beam
This page describes the data flows implemented in Beam today. It is a plain-language production draft and still requires review by Beam's owner and legal counsel before general availability.
Information Beam processes
- Account information supplied through email sign-in or Google, including your name, email address, provider identifier, and avatar when available.
- The PDF resume you choose to upload, its extracted text and links, and the structured profile content created from it.
- Profile content, presentation choices, username, and images you choose to save.
- Session, IP address, user-agent, rate-limit, and operational log data needed to secure and run the service.
How resume data is handled
Beam reads the PDF on the server, extracts its text and embedded links, and sends that extracted content to Google Gemini to structure it. The original PDF is not saved to Beam's database or object storage. If you are not signed in, the structured import is held in the database behind a one-time token that expires after 15 minutes. The structured profile is saved only after authentication succeeds.
Service providers
The current application code uses Vercel for hosting, Neon for Postgres, Google Gemini for resume structuring, Resend for sign-in email, and S3-compatible object storage for profile images. Google also processes authentication information when you choose Google sign-in. Better Auth runs inside Beam and manages sessions and authentication records in Beam's database.
Retention and deletion
Temporary resume-import tokens expire after 15 minutes, although expired database rows may be removed during later cleanup. Saved account, profile, and media records remain until they are replaced or deleted. Beam does not yet provide self-service account deletion or a confirmed public support inbox. See the account and data page for the current limitation.
Public profiles and search indexing
Beam currently distinguishes published and unpublished profiles. A published profile can be opened by anyone who knows its URL; an unpublished profile is available only to its owner. Beam does not yet provide separate public, link-only, and private visibility controls. Search indexing is disabled for profiles while those controls are being completed.
Analytics and operational logs
Beam's application code does not currently initialize PostHog, Vercel Analytics, or another product analytics SDK. Hosting, authentication, database, email, AI, and storage providers may retain security and delivery logs under their own policies. The operator must confirm any dashboard-level analytics and provider retention settings before this notice is treated as final.
Contact
A monitored privacy and support contact has not yet been published. This must be resolved before Beam is offered for general use. The contact page will identify the official channel once configured.