Privacy
No Varnish holds very little about anyone. There is no builder account, no CV, no application data and no profile. Applying happens on the employer’s own site, so the part of a job hunt that carries the most personal data never touches us at all. That small footprint is the strongest privacy control here, and it is deliberate.
What we store
| Data | Who it is about | Why |
|---|---|---|
| Email address | Job alert subscribers | To send the digest you asked for |
| Email address and company | Employers | To run your listing and let you sign in |
| Session cookie | Employers | To keep you signed in |
| Visitor hash | Visitors | To count views without identifying you |
| Reporter hash | People who report a listing | To show you that you already reported it |
| IP address | Visitors | Rate limiting only. Never written to a table |
Analytics without tracking
We count page views and apply clicks so employers can see whether their listing is working. The identifier behind those counts is a hash of your IP address, your browser’s user agent and a salt that rotates every day. Because the salt changes daily, yesterday’s hash cannot be matched to today’s, so there is no way to follow a person across days.
No analytics cookie is set and no identifier is stored on your device. This is why you are not being asked to dismiss a consent banner.
Cookies and local storage
One cookie exists: the employer session. It is strictly necessary and needs no consent. Two values may be kept in your browser’s local storage — a draft of the post form, and the timestamp of your last visit so the feed can mark what is new. Neither leaves your device and neither identifies you.
How long we keep things
| Data | Kept for |
|---|---|
| Unconfirmed alert signups | 7 days, then deleted |
| Raw view and click events | 90 days |
| Reporter hash | 12 months |
| Sessions | 30 days, rolling |
| Rate limiting keys | The length of the window only |
| Do-not-contact records | Permanently, on purpose |
| Listings, companies, and daily totals | Indefinitely |
A do-not-contact record outlives everything else because deleting it would let us contact you again, which is the opposite of what it records.
Your rights
- Subscribers. Every digest has an unsubscribe link that removes your saved search, its matches and your address immediately. It takes one click and asks for no confirmation — asking you to confirm by email before deleting your email would be circular.
- Employers. Write to us and we will expire any live listings and anonymise your account.
- Anyone emailed about a sourced listing. One click removes you and your whole domain, permanently. See the sourcing policy.
- Access or correction. Ask, and we will assemble it by hand. There is little enough that this is realistic.
Who else processes this
Hosting, database, email delivery, payments, bot protection, image storage, error reporting and background job execution are run by third parties. The database is provisioned in the EU. Currency rates are fetched from a public source that receives no personal data.
This is a demonstration project. Treat this page as a description of how the system is built, not as legal advice or a finished policy.