Legal
Privacy Policy
Last updated: October 2026 · GDPR-compliant · EU servers
JobHiker is built on one core belief: your career data is yours. This document explains what we collect, why, and what we do to protect it.
What we collect
We collect the email address you use to register, the CV file you upload and the text we read out of it, and — if you fill it in — the applicant profile that our browser extension uses on application forms for you: name, phone, address, and — only if you choose to fill them in — your answers to the questions forms commonly ask, such as language level, whether you are allowed to work in Switzerland, availability and preferred workload. We never store your nationality, permit category, date of birth or gender. We also collect minimal usage data (jobs saved, notification settings) to power your account dashboard. If you subscribe, payment is handled by Stripe — the payment form is theirs and no card details ever reach our servers. We store only your subscription's status, its trial and billing period dates, and the provider's own subscription and product identifiers.
How we use it
Your CV text is sent to our AI providers to score jobs against your profile and, when you explicitly request a cover-letter draft, to generate that draft from your CV and the posting. Draft generation is optional and never submits an application. The CV file itself is never sent to an AI provider: it is kept so that, when you ask the browser extension to fill an application form, it can attach your CV to that form — on the job board's page, in your browser, for you to review before you send anything. If you ask the browser extension to try a form it has no rule for, that form's field descriptions — never what is typed into them — are sent to our AI provider to work out which of your details go where. We do not use your CV for advertising or to train AI models. Email is used for authentication, transactional emails, and the optional match notifications (which you can disable at any time); if you subscribe, it is also passed to our payment provider so the subscription can be matched to your account.
Storage and security
CV data is stored encrypted at rest (AES-256) on servers in the EU, and is decrypted server-side for scoring and cover-letter generation. The CV file itself is encrypted on our servers before it is stored, in Cloudflare R2 within its EU jurisdiction: Cloudflare holds only the encrypted file, never the key. Generated letters are also encrypted at rest; they are included in your data export and deleted with your account. When the extension fills an application form, or you mark a job as applied, we keep a record of what it contained — the cover letter you sent, which CV it was and the details you had filled in — so that weeks later you can still see what you told an employer. If you replace that CV afterwards, we keep the file that went out for as long as the record exists, so you can download exactly what you sent. The record is written once, never changed by later edits, included in your data export, and deleted when you remove that job from your board or delete your account. All traffic is protected with TLS in transit. The only documents we keep are the CVs you upload: the current file and its text, and an earlier file only while an application record still names it — all encrypted, all in your data export, all deleted with your account.
Browser extension
The JobHiker Chrome extension fills a job board's application form with your own details, on your click. It has no access to any web page until you click its button on that page, and then only to the tab you clicked on, to type your details into the form and read them back. If you choose “Allow on job boards”, it can also read the address of the page you are on at the supported job boards while its side panel is open, to follow you from tab to tab and look the posting up; it never fills a form or attaches your CV from that alone. It talks only to our API, signed with a key created in your browser when you pair it — no password is ever entered into it. It fetches your applicant profile, CV file and cover-letter draft for the posting you are on. To know which posting that is, it sends our API the address of the page you clicked it on, or, with that permission, the page you are on at a supported job board: on a job board, the posting's id from that address; on an employer's own application site, the whole address, which we match against the link the job board sent you on. That address is used to find the posting and is not stored with your account. It reports what it did as counts only: how many fields it filled or could not, never their values, never the page's text, never the letter. If you press “Report this form”, it sends the board's name and the page's address, and, if you write one, your short note about what went wrong — before it is stored we remove any e-mail address or phone number from it. We keep that address, without anything after its “?”, and the note with your account so we can fix the form; it is in your data export and deleted with your account. One thing goes further, and only when you press it: on a form it has no rule for, the extension offers “Try to fill this form anyway”, and pressing it sends that form's field descriptions — each field's name, label, type and placeholder, whether it is required, and up to eight of a list's options — to our API, which asks our AI provider where your details go. Never what you or anyone typed, never the page's text or HTML, and nothing about you. We keep the site's address, those field descriptions, the suggested field mapping and, each time it is used, which fields it then filled — never what was filled in — with your account; they are in your data export and deleted with your account. When you answer an employer's own choice question yourself — a dropdown or a set of options, such as whether you would relocate — the extension remembers the question and the option you chose, so that it can offer the same answer when another form asks the same question; it chooses it only when you press it. Text you type and checkboxes are never remembered. These answers stay in your browser and are never sent to us. If Chrome sync is turned on, Chrome keeps a copy with your Google account and brings it to your other computers where you are signed in, under Google's terms. “Forget my saved answers” in the extension deletes them, in this browser and in Chrome sync. It never submits an application. You can disconnect a paired browser at any time from your dashboard, and deleting your account revokes every pairing.
Applying from your phone
On a phone, where the extension cannot run, a posting's “Apply from your phone” shows your applicant profile as buttons that copy each detail to your phone's clipboard; the copying happens on your phone and nothing copied is sent to us. “Save my CV to this phone” downloads the CV file we keep for you to your phone. “Finish on my computer” sends an email with the posting to your account's address. We count how often each of these is used — copying a detail, copying all, copying your cover letter, saving your CV, finishing on a computer — with the posting it was used on, to decide what to build for phones next. We never record which detail you copied or what it said. These counts are in your data export and deleted with your account.
Notifications on your devices
If you turn on notifications on a device, your browser gives us an address at its push service (Apple's, Google's or Mozilla's) and two keys to encrypt messages with. We keep those with your account and use them only to send your matches: the job title, the company and how many more there are, never anything from your CV. Turning it off on the device, or the push service telling us the address is gone, deletes them, and so does deleting your account.
Self-hosted users
If you run the self-hosted version of JobHiker, none of your data ever reaches our servers. You are responsible for securing your own deployment. The self-hosted version is AGPL-licensed and auditable.
Data retention
Your account data is retained for as long as your account is active. You can delete your account at any time from your account menu, which immediately purges all personal data including CV text, and cancels any paid subscription so you are not charged again. So that the trial is once per person, we keep a keyed one-way fingerprint of your email address, and of your CV's text and the phone number and application email in your applicant profile if you fill them in. A fingerprint cannot be turned back into the address, CV or number; it can only tell whether the same one is seen again. While your account exists they are stored with it, and we note whether another account had the same one first. One thing is kept after deletion: those fingerprints, with no link to the deleted account, recording only that they have had a free trial. Backups are purged within 30 days.
Cookies
We use session cookies for authentication. Optional PostHog analytics cookies are used only after you allow them. Google Analytics is disabled.
Product analytics
Optional analytics runs on PostHog, hosted in the EU, and starts only after you opt in. We ask after onboarding, on your dashboard. You can decline without affecting any product features, or change your choice in Account under Data & privacy on this browser. We measure page visits, traffic sources and aggregate interactions. We never send your CV, applicant profile, email address or account identifier to PostHog. Analytics uses a random browser identifier; automatic click collection and session recording are disabled. URL parameters are filtered to campaign tags and referrer data is limited to the referring domain. Google Analytics is disabled.
Your rights (GDPR)
You have the right to access, correct, export, or delete your personal data at any time. To exercise these rights, email hello@jobhiker.com or delete your account from your account menu. We will respond within 72 hours.
Contact
Questions or complaints: hello@jobhiker.com. For GDPR-specific requests, add 'GDPR Request' in the subject line.