1. The website waitlist
When you leave your email on our site, we store it on our account server (hosted on Railway) so we can let you know when HVNTR launches; we use it only to contact you about HVNTR's launch. We do not sell it, share it, or add you to any marketing list. Ask us at the contact email above and we will delete it.
2. The extension is local-first
HVNTR fills job-application forms with profile information you enter in the extension's settings. That profile is stored in Chrome's local extension storage on your own device. It is not sent to our servers. Form filling happens on your device; your answers go to the job portals you choose, not to us.
Optional self-identification. The extension's settings include optional voluntary self-identification fields: gender, race, Hispanic or Latino, veteran status, disability status, sexual orientation, transgender status, and pronouns. Each one is set to "Decline to answer" (pronouns are left blank) until you change it. Whatever you choose is stored only in Chrome's local extension storage on your device and is used only to answer the matching voluntary self-identification questions on an employer's application form. These fields are never sent to our servers or to an AI provider.
3. License checks
Customer builds verify an active subscription with our server before a run can start. We record your account email, subscription status, and billing history. Passwords are never stored by the extension. HVNTR keeps working for up to 72 hours if our server is unreachable, then pauses until the license can be confirmed.
4. Payments
Payments are processed by Stripe. We never see or store your card number — Stripe handles card data under its own privacy policy. We receive subscription status and billing events from Stripe.
5. Diagnostics
HVNTR can export a support bundle (Settings → Diagnostics) that you choose to send us when something breaks. The export is redacted by design — error and failure information, not your profile data. We only ever receive a bundle you explicitly send.
6. What we do not do
- We do not sell your data.
- We do not use your data for advertising or ad targeting.
- We do not transmit your profile answers to our servers.
- We do not run analytics or tracking in the extension.
7. Third parties
- Job portals (LinkedIn, Indeed, Dice, Greenhouse, Lever, and others): when HVNTR submits an application, your answers go to that employer's site, governed by that site's privacy policy and terms.
- Stripe: payment processing. Railway: hosting our account and license server.
- AI provider (optional, your choice): HVNTR can use an AI model to answer application questions that its rules and your saved answers don't cover. By default it points to Ollama on your own computer (localhost), so this data stays on your machine. If you instead choose a hosted OpenAI-compatible provider in the extension's AI settings and enter your own API key, HVNTR sends that provider the question text, the job's title, company and description, your resume text, and a profile summary (name, city and state, current title and company, years of experience, skills, education, summary, languages, workplace preferences, notice period, and willingness to relocate). What the provider does with it is governed by that provider's privacy policy and terms. Sensitive questions (work authorization, sponsorship, citizenship, security clearance, criminal history, self-identification, and salary) are never sent to an AI provider. You can set the AI provider to None at any time.
8. Data retention
Account and billing records are kept while your account is active and as required for tax and accounting. Local extension data is yours — uninstalling the extension removes the data stored on your device.
9. Your rights
You may request access to, correction of, or deletion of the account data we hold about you at the contact email above. California residents: we do not sell personal information as defined by the CCPA/CPRA.
10. Children
HVNTR is a job-application tool and is not directed at children under 16.
11. Changes
If this policy changes, we will post the updated version here and update the effective date. Material changes will be announced in the extension's release notes.