Privacy Policy

• Profile data — name, email, phone, work history, education, and saved screening answers you provide. Used solely to fill job applications on your behalf.
• Voluntary self-identification— optional EEO details you may add in Settings (gender, pronouns, race/ethnicity, veteran and disability status). Provided entirely at your discretion and used only to fill the corresponding voluntary questions on application forms so you don’t re-enter them each time. Any field you leave blank is skipped. We never sell this data, use it for advertising, or use it to target you, and it is never inferred — only what you explicitly enter is stored.
• Résumé files — PDFs you upload. Stored encrypted at rest; transmitted over TLS to fill file-input fields in the browser extension when you apply.
• Job queue & application outcomes — which roles you queued and whether they were submitted, skipped, or paused. Used to show you your pipeline and improve answer grounding.
• Pairing tokens — short-lived tokens that bind your web session to the browser extension. Expire after use; never stored in plaintext.
• Application-page content — when you run a fill, the extension reads the fields, labels, and questions on the job-application page you are viewing so it can match them to your profile. This reading happens locally in your browser. The job description and relevant screening questions may be sent to our server to generate grounded answers; we do not collect or store the surrounding page content beyond what is needed for that request.
• Job-board page data — on LinkedIn, Indeed, and Glassdoor job pages, the extension reads the public posting details (title, company, location) so you can add roles to your queue and see hiring intel. It is read-only and never posts, messages, or acts on your behalf on those sites.
• Usage analytics — page views and error counts (no personally identifiable information), and, for signed-in users, which jobs your feed showed you and which you queued, tailored, or declined, along with the match scores we assigned them. We use this to improve how the feed ranks and matches jobs to your profile. It records job identifiers, scores, and your action — never the contents of your résumé, answers, or messages.

• Your profile and saved answers (synced from the web app via a Bearer token).
• Your current batch queue and run state.
• Workday employer credentials — AES-256-GCM encrypted, key derived from a random secret stored only on your device. We never receive these passwords.
• A local activity log — a capped history of which fields were filled, the source of each value (your profile, your saved answers, or AI), and every consent checkbox decision. It contains no page URLs with query strings and no résumé contents, stays on your device, and you can clear it at any time.

• To fill job application forms in the Chrome extension on your instruction.
• To generate and ground screening answers using your saved profile.
• To tailor résumés to specific job descriptions (Pro / Max plans).
• To send transactional emails (account, billing, feature updates).
• We do not sell your data. We do not use it to train AI models.

• Anthropic Claude — generates screening answers and résumé tailoring. Your profile excerpt and the job description are sent per request; not retained by Anthropic for training under our API agreement.
• Stripe — handles subscription payments. We store only your Stripe customer ID; card numbers never touch our servers.
• Vercel / Render — host the web app and API. Data remains in US regions.

Henriquez Holdings LLC