Your resume, and what we do with it

When you paste your resume and a job post, the text is sent to a model provider to produce your tailoring pass and the result is stored in our database against your account so you can open it again later. That is the whole journey.

The text is transmitted over TLS 1.2 or better and stored encrypted at rest by our database provider (Neon, running on AWS). It is never posted anywhere public, never shared with another user, and never sent to any third party other than the model provider that produces your tailoring.

Beacon routes across providers. In this deployment the live provider is OpenAI, and the routing table on the How the AI works page shows which model handles which step.

We use these providers under their business API terms, which prohibit training on API traffic. We do not fine-tune any model on your resume data, we do not use your applications to improve prompts without asking, and we do not sell or license customer text to anyone for any purpose.

Access to the production database is limited to the engineers who operate it, and it is used to fix things, not to browse. We do not read customer resumes for product research.

If you open a support ticket about a specific application and send us the link, we may open that one application to answer your question. If you would rather we did not, say so in the ticket and we will work from your description instead.

• Tailored applications and the resume text stored with them: until you delete them, or until 30 days after you delete your account, whichever is sooner.
• Account records: for as long as the account is open, then 30 days.
• Form submissions from the contact, help, and careers forms: 24 months.
• Server logs, which record request paths and timings but not resume text: 30 days.
• Backups: rolling 7 days, after which deleted data is gone from backups too.

Delete any single application from your dashboard, which removes the resume text and the tailored output with it. Delete your whole account from Settings, which removes every application, the stored text, and the account record.

Both are immediate and neither needs a support ticket. If you want written confirmation for your own records, email us and we will send it.

• Passwords are hashed with scrypt and a per-user salt. We never store or log a password, and nobody at Beacon can see one.
• Sessions are httpOnly, sameSite cookies signed with a server-side secret, and they expire after 30 days.
• Google sign-in is supported so you do not have to keep another password at all.
• Every request for a tailored application checks that the application belongs to the account asking for it, in the database query itself rather than in the page.

• Two-factor authentication is required on every service Beacon uses, with no exceptions and no shared logins.
• Production access is limited to the engineering team and reviewed quarterly.
• Dependencies are updated on a weekly cadence and security advisories are actioned within 72 hours for anything reachable from production.
• We do not yet hold a SOC 2 report. We are a pre-seed company and would rather tell you that than imply otherwise. If you need a completed security questionnaire for procurement, email us and we will fill it in honestly.

Email security@beaconly.org. We acknowledge within two business days, we will not threaten you for reporting in good faith, and we will tell you when it is fixed. If you want to be credited, say so and we will.