Privacy Policy

Last updated: July 11, 2026

Draft: pending legal review. This policy was drafted from how the product actually works, but it is not final. Passages marked [VERIFY: …] are assertions we still need to confirm against our systems and with counsel before we rely on them. Don't treat those as settled until the marker is gone.

This policy covers Zelume: the resume builder and job-tracking web app at https://www.zelume.io, and the zelume-lint command-line tool and its Agent Bridge. It explains what we collect, why, how long we keep it, who else processes it, and how to get it back or delete it.

1. What we collect

Account data: your email and name (via AWS Cognito), and optional profile fields like university, graduation year, and target job title.
Resume & cover-letter content: everything you put into a resume or cover letter: work history, education, skills, contact details, and any resume you import or push from the CLI.
Job-application data: the jobs you save and track, including the job descriptions and any notes you add.
Auto-apply answer bank: if you use it, the answers you save for applications, which can include sensitive fields you choose to enter (e.g. work authorization, and voluntary EEO/demographic answers). You decide what goes in it.
Billing data: handled by Stripe. We store your plan status and a Stripe customer reference; we never see or store full card numbers.
Usage & diagnostics: analytics about how you use the app (pages, feature clicks) and error reports. This is behavioral, not your resume content. [VERIFY: confirm analytics captures no resume/PII field values, only event names and page paths]

2. Why we use it

To run the app: build, store, and render your resumes and cover letters.
To provide AI features (tailoring, rewriting, grammar, cover-letter generation); see section 3.
To process payments and manage your subscription (Stripe).
To send transactional email: verification, password reset, billing (via AWS / Amazon SES).
To measure and improve the product, and to diagnose errors.
For advertising measurement: we use Google Ads conversion tracking to understand which ads lead to sign-ups. [VERIFY: confirm this is limited to conversion measurement and is gated behind consent before launch (see section 9)]

For EU/EEA users, our legal bases are performance of the contract (running the service you signed up for) and legitimate interest (improving and securing it). [VERIFY: legal bases: confirm with counsel, especially for AI processing and advertising]

3. AI processing of your content

When you use an AI feature, the relevant resume or cover-letter text and the job description are sent to Amazon Bedrock, AWS's managed AI service, to generate the result. Bedrock runs inside the same AWS account and region as the rest of the app; your content is not sent to a separate third-party AI vendor.

The models we invoke are Anthropic Claude models hosted on Bedrock: Claude Sonnet 4 (us.anthropic.claude-sonnet-4) and Claude Haiku 4.5 (us.anthropic.claude-haiku-4-5).

Content is processed to produce your result and sent over encrypted (TLS) connections.
[VERIFY: Amazon Bedrock does not store inference inputs/outputs or use them to train models; confirm this holds for these SPECIFIC model inference profiles (Sonnet 4 and Haiku 4.5), since guarantees can vary by model provider within Bedrock]
The free zelume-lint CLI runs entirely on your own machine and sends nothing to us or to any AI provider. Only the web app and the account-linked Agent Bridge features use Bedrock.

4. Who else processes your data (sub-processors)

We rely on these providers to run the service:

Amazon Web Services (AWS): hosting, database (DynamoDB), file storage (S3), authentication (Cognito), AI (Bedrock), and email (SES). US region.
Stripe: payment processing and subscriptions.
Google: Google Analytics (usage analytics), Google Ads (conversion measurement), and optional Google sign-in if you choose it.
Sentry: error and performance monitoring. Error reports can incidentally include limited technical context. [VERIFY: confirm Sentry is configured to scrub PII / not capture resume content in error payloads]
Cloudflare Turnstile: bot protection on sign-up.

For EU/EEA and UK users, using these US-based providers involves an international data transfer. [VERIFY: state the transfer mechanism (Standard Contractual Clauses and/or the EU-US Data Privacy Framework) and confirm each provider is covered]

5. How long we keep it

Account, resumes, cover letters, applications: kept until you delete the item or your account. Deleting your account removes them right away (section 7).
Rendered PDF cache: the service caches generated PDFs to avoid re-rendering; these expire automatically after 7 days.
Analytics: retained by Google Analytics per our configured retention window. [VERIFY: state the exact GA4 retention setting (e.g. 2 or 14 months) and Sentry's retention]
Billing records: Stripe retains transaction records under its own retention and legal obligations even after you delete your Zelume account.
Backups / logs: [VERIFY: state any DynamoDB point-in-time-recovery / backup window and CloudWatch/log retention during which residual copies may persist after deletion]

6. Storage & security

Data is stored in AWS (US region) in DynamoDB and S3, encrypted at rest.
All traffic is encrypted in transit (TLS 1.2+).
Authentication is handled by AWS Cognito.
Web-app session tokens are stored in tab-scoped sessionStorage (cleared when the tab closes), never in localStorage.
CLI access tokens live only on your own machine, and you can revoke them from your account settings or by logging out of the CLI.

7. Your rights: access, export, correction, deletion

Export: download all your data as JSON at any time from your account.
Correct: edit your profile and content whenever you like.
Delete: deleting your account immediately removes your profile, resumes, cover letters, applications, and stored files, revokes any CLI access tokens, and deletes your login identity. Some records held by our providers persist under their own retention: Stripe keeps billing records, and residual copies may remain briefly in backups/logs (section 5).

EU/EEA and UK users also have the rights to object, restrict processing, and lodge a complaint with a data protection authority. California residents: see section 8.

8. California (CCPA/CPRA)

California residents can request access to and deletion of their personal information, and can opt out of any "sale" or "sharing" of it. [VERIFY: "we don't sell your personal information": confirm as a legal conclusion. Under CPRA, using Google Ads conversion tracking may count as "sharing" for cross-context behavioral advertising; confirm whether we must offer a Do-Not-Sell-or-Share control and honor the Global Privacy Control (GPC) signal]

9. Cookies & analytics

Zelume uses essential cookies/tokens for signing in, and, subject to your consent, Google Analytics and Google Ads conversion tracking, which set analytics/advertising cookies. Sentry is used for error monitoring.

[VERIFY: consent mechanism not yet live. Before launch we're adding a cookie-consent banner using Google Consent Mode (basic): analytics and ads storage default to DENIED until you accept, the Global Privacy Control signal is honored automatically, and opt-outs are confirmed. Until that ships, describe the current state honestly and do not publish this section as final]

10. Children

Zelume isn't intended for anyone under 16, and we don't knowingly collect data from them. [VERIFY: confirm the age threshold per jurisdiction (13 under COPPA in the US; 16 default under GDPR, varies 13–16 by member state)]

11. Changes & contact

We'll update this policy as the product changes and note the date at the top; material changes will be announced. [VERIFY: confirm how material changes are communicated (email vs. in-app notice)] For any privacy question or to exercise a right, email privacy@zelume.io. [VERIFY: confirm this inbox is monitored, and name the legal entity/controller and its address]