Your resume, our responsibility

• Encrypted at rest. Your data is encrypted at rest with AES-256 on our managed database (MongoDB Atlas) and file storage (Cloudflare R2). Encryption is provider-managed.
• Encrypted in transit. All traffic is encrypted using TLS 1.2 or higher (HTTPS), with HSTS and a strict security-header set (Content-Security-Policy, X-Frame-Options, nosniff). Plain HTTP is redirected to HTTPS.
• Signed in and scoped to you. Sign-in is handled by Clerk; we never store your password. Every request is verified against your signed session token, and your data is scoped to your account — another user’s account is designed to be unable to read it (cross-user access is rejected, HTTP 403).
• What AI sees. The AI that scores your fit and tailors your resume and cover letters is used under no-training API terms — your content is never used to train any third-party model. Where a provider offers zero data retention, we use it. Our AI providers today are OpenRouter (primary) and Anthropic (fallback).
• Only the fields you approved. When we apply for you, we transmit only the application fields you approved for that specific job — nothing more.

Auto-Apply is the feature where Jobeezy, at your explicit per-job direction and as your agent, submits an application you have reviewed. Here is exactly how the boundaries work:

• You approve each job. We apply only when you say yes to that specific posting. You can review and cancel before we submit. There is no mass-apply and no background batch you didn’t approve.
• We submit through the employer’s own system. Applications go into the employer’s careers page or applicant-tracking system (ATS) — their real hiring channel, not a side door.
• It runs on a managed cloud browser, not your phone. We drive an isolated, per-run cloud browser through Browserbase, a managed cloud-browser provider. Each session is isolated and torn down after the application is submitted.
• We do not use your personal logins. For most employer systems we apply as a guest, with no account. The one exception is Workday: because Workday requires an account, we create a candidate account on your behalf, securely store the password we generate, and use a Jobeezy-managed email alias — we never use your personal LinkedIn, Indeed, or email passwords, and we never post under your name on job boards.
• Withdrawal. You can ask us to withdraw where the employer supports it, but an application that has already been submitted to an employer cannot be recalled.

Read more in the Security details and the Terms of Service.

Jobeezy’s Fit Score (a 0–100 rating of how well a job posting matches your stated preferences and qualifications) and our document tailoring are advisory tools for you, the job seeker. They are advice to you about a job — not a report about you sent to an employer.

• The Fit Score is guidance, not a gate. It helps you decide where to focus. It does not block you from applying — you may apply to any eligible or “stretch” job you choose.
• Jobeezy is not the employer. We make no hiring decision about you. The employer decides. A human — you — approves every application before it is submitted.
• We are not an employer-side decision tool. Jobeezy is not an automated employment decision tool acting for an employer. This is why we position ourselves clearly against laws such as NYC Local Law 144, Colorado’s SB 205, Illinois AI-hiring rules, and the EU AI Act — the human stays in the loop, and the score is help for you, not a verdict on you.

For the full plain-language explanation of how our AI works, see our AI transparency notice.

Two different kinds of sensitive information are handled two different ways. This is the most important accuracy point on this page, so we state it plainly:

• Your EEO answers are isolated. Your voluntary equal-opportunity answers — race, ethnicity, sex, veteran status, and disability self-ID — are stored in an isolated collection that is never joined into matching, scoring, or Auto-Apply — by design, not just policy. They reach an employer only if you explicitly approve sharing them, and they are erased immediately when you delete your account.
• Fair-chance and background information is used to help you. Fair-chance, criminal-record, justice-impacted, and health-gap information that you choose to add is treated as sensitive, but it is not isolated the way EEO answers are. We use it to help tailor your applications and match you to jobs, and it feeds the fairness dimension of your Fit Score. We never sell it, and it goes to an employer only as you direct.

We are not a consumer reporting agency. We do not run background checks, and we do not obtain your record from one — anything we hold is what you chose to give us.

• Sell your resume, email, or any personal data — not to brokers, not to recruiters, not to anyone.
• Use advertising pixels or advertising cookies; the mobile app blocks the advertising ID.
• Let a third-party AI model train on your content.
• Run a mass-apply or apply to a job you didn’t approve.
• Use your personal LinkedIn, Indeed, or email logins, or post under your name on job boards.
• Use your EEO answers to score, match, or tailor — ever.

Our revenue comes from subscriptions, not from your data.

• Global Privacy Control. We honor the Global Privacy Control (GPC) as an opt-out of sharing for cross-context behavioral advertising. There is no agreed “Do Not Track” standard, so we honor GPC instead.
• Delete in one tap. You can delete your account from the app. A checkpointed sweep removes your resume, profile, and application history across our data stores, usually within 30 days of a verified request; if a step fails it resumes from that point. We keep only what the law requires (for example, basic payment records held by the app stores), and we don’t hold data “just in case.” See the delete-account page.
• Access, correction, portability. You can ask us to access, correct, or export your data by emailing privacy@jobeezy.com. We acknowledge requests within 10 business days and respond within 45 days (with up to a 45-day extension for complex requests). An export is delivered to you as a JSON file inside a ZIP email attachment.
• Where your data is processed. Your data is processed in the United States (Render, US; MongoDB Atlas on AWS us-east-1; Cloudflare R2 on US + global edge). For users in the EEA, UK, and Switzerland, transfers rely on the EU Standard Contractual Clauses, the UK IDTA, and the Swiss addendum, as described in our Data Processing Addendum.
• Your privacy choices. We do not sell or share your personal information; you can review and manage your choices from the Your Privacy Choices control.

The full detail lives in our Privacy Policy and California Privacy Notice.

• Secrets. Credentials live in our hosting platform’s protected environment settings, never in our code or config files. Secrets can be rotated with versioned rollback, and are rotated on credential change or suspected compromise.
• Internal endpoints. Internal and scheduled endpoints require a separate internal key (constant-time verified, fail-closed) and are not reachable with a normal user session.
• Audit logging. We keep structured audit logs of admin actions and sensitive data-access events, with per-request correlation IDs; errors and performance are monitored via Sentry.
• Vulnerability scanning. Automated static-analysis (CodeQL), dependency, secret, and license scanning run in our CI pipeline plus a nightly scan; production dependencies are version-pinned.
• Supporting controls. HMAC-signed webhooks; prompt-injection hardening for untrusted text (resumes, scraped postings, ATS pages); per-IP and per-user rate limiting.
• Analytics minimization. By policy, we do not send your name, email, or resume text to our product-analytics tools; analytics events use pseudonymous IDs, and we redact identifiers from AI cache keys.
• Payments. We never receive or store your full card number. Subscriptions are billed by Apple or Google and managed through RevenueCat.

Full technical depth is on our Security page. No app, website, or company can promise information is ever 100% secure, and we don’t make that promise — we describe the practices we actually run.

We use a defined set of vetted service providers (“sub-processors”) that process data on our behalf under our instructions — for hosting, storage, AI, applying on your behalf, email, analytics, and error monitoring. Key names include Render (hosting), MongoDB Atlas (database), Cloudflare R2 (file storage), Clerk (sign-in), OpenRouter and Anthropic (AI), Browserbase (the managed cloud browser that submits applications), RevenueCat (subscriptions), and Resend (email).

Your EEO answers are excluded from every AI, analytics, and automation provider. We publish the complete, current list — with each vendor’s purpose, the data shared, and its role — on our Sub-processors page. We give at least 30 days’ advance notice before a new or replacement sub-processor takes effect, via our changelog and email to DPA customers, and you may object as described in our DPA.

We monitor our services and post current health on our Status page. To date, we have had no security incidents.

If a security breach affects your personal information in a way that is likely to put you at risk, we will notify affected users without undue delay and as required by applicable law, and tell you what happened and what to do. For EEA/UK/Swiss users, where the law requires it we will also notify the competent supervisory authority without undue delay and, where feasible, within 72 hours. See our Privacy Policy for details.

Email security@jobeezy.com. We acknowledge good-faith security reports within 5 business days and aim to remediate critical or high-severity issues within 30 days and medium or low issues within 90 days. These are good-faith targets, not guarantees.

Safe harbor. If you make a good-faith effort to comply with our published policy during your security research, we will consider your research authorized, work with you to resolve the issue quickly, and will not recommend or pursue legal action against you. Please do not trigger live application submissions to real employers — request a sandbox from us first.

Read the full policy at our responsible-disclosure policy and security.txt.