Privacy Policy

The extension collects data only when you ask it to save a posting — by clicking the “Save to Tracker” button it adds to a supported job board, or by opening the extension’s popup on a page and clicking save. It does not run in the background, and it collects nothing on pages where you do not click.

When you save a posting, the extension reads and sends to 1centraal.com:

• the page’s address (URL) and its title;
• the visible text of the posting — what you would get by selecting the page and copying it. Hidden elements, scripts and markup are not included.
• a short report of how the save went — whether it worked, why it did not if it failed, which of the supported job boards it was, which button you used, the extension’s version and how long it took. This one is sent even when the save fails, which is the point of it: otherwise a save that never reaches us is invisible to us. It contains no address, no page title and no page text.

It does not read your browsing history, cookies, passwords, form contents, or any page you have not asked it to save.

• LinkedIn, Indeed, Greenhouse, Lever, Ashby — to place the save button on postings and read the posting text when you click it.
• The current tab, on your click — so the popup can save a posting from a job board not in the list above. This access lasts for that one action and does not persist.
• Local storage — to hold your account token, the titles of your ten most recent saves so the popup can show them, and any save reports that could not be sent yet.
• 1centraal.com — the tracker itself, where saved postings go.

One access token; the job title, company and date of your ten most recent saves; and up to twenty save reports that could not be sent — if a save fails because the tracker is unreachable, its report cannot be sent either, so it waits here and goes with the next one. All three live in the extension’s own local storage. Signing out from the popup, or removing the extension, deletes all of them. The token is never exposed to the pages you visit — it is held by the extension’s background service worker, not by the script that reads the posting.

Your account (email address, and your name if you signed in with Google), the postings you have saved including their original text, and the tracking you add yourself: status, notes, contacts, follow-up dates and checklist items. Access tokens are stored only as a hash, so the token itself cannot be recovered from the database.

If you import a CV, the file's text is stored along with the profile read out of it — your roles, education, achievements and skills — and any edits you make to that profile by hand. The assessment of a job against your profile is stored with the job.

Counts of extraction requests are recorded — how many were made and how many tokens they used — to monitor usage and enforce per-account limits. These records hold no posting content.

The extension reports what happens when you click Save: whether it worked, why it did not if it failed, which of the supported job boards it was (or “other”), which button you used, the extension’s version, and how long the save took. It is the only way we can see that saving is broken for someone — the save happens inside the extension and, until it reaches us, nothing about a failure leaves your browser. These reports contain no web address, no page title and no page text — nothing about a page you did not save, and nothing about the pages you browse. They go to 1centraal.com and nowhere else.

Three things are sent to Anthropic (the Claude API). The text of a saved posting, to extract the title, company, salary and other fields from it. The text of a CV you import, to read your roles, education, achievements and skills out of it. And, when a saved job is assessed against your profile, the posting's text together with that profile — the roles, skills, education, achievements and career goals it holds.

Anthropic does not train models on API data. Your name and email address are never sent with any of it, but note that a CV normally contains both, and it is sent as written.

The weekly email is delivered by Resend, which receives your email address and the contents of that email — the titles and companies of the jobs it lists. It is sent only if you are subscribed, and every one carries a one-click unsubscribe link. You can also turn it off at any time in your account settings.

Resend also delivers sign-in links, so it receives your email address when you ask for one. That happens whether or not you are subscribed to anything — it is how signing in without a password works.

The service also relies on Vercel for hosting, Neon for the database (hosted in the EU), and Google for sign-in. Each of these processes data only to provide that function.

Your data is not sold, not shared with advertisers, not used to build a profile of you, and not used for any purpose other than running the tracker. There are no third-party trackers or advertising scripts in the extension.

Saved postings are kept until you delete them. Deleting a saved posting removes its stored text along with it.

You can delete your whole account yourself, from the Account page — no request, no waiting. Everything attached to it goes at the same time: postings and their stored text, notes, contacts, checklists, any CV you imported and the profile read from it, the assessments of jobs against that profile, extension tokens, and the extraction and save records described above. It happens immediately and cannot be undone; nothing is retained in a separate copy, and there is no backup we can restore you from. If you also joined the waitlist with that address, that entry is removed too.

Questions, or a request to see or delete your data: support@1centraal.com.