Privacy

Privacy

Last updated: 2026-08-11

PayEvidence is built to need as little personal data as possible. The dataset is about jobs and employers, not people.

01

The dataset contains no personal data

We collect employer-published job postings from public ATS endpoints: titles, locations, departments and stated pay. No candidate profiles, no names, no tracking of individuals.

02

Access requests

If you submit the access form we store what you typed (name, email, company, use case) in our own database, solely to respond. No resale, no enrichment, no advertising.

03

Accounts are just an email

If you create an account we store exactly one personal field: your email address. There are no passwords (sign-in links are single-use and expire in 15 minutes), no profiles, and no tracking. Deleting your account deletes the address.

04

Cookies

One functional cookie remembers your language choice. No analytics or advertising cookies. Server-side we keep only cookieless daily aggregates (path, referrer domain, country, and a boolean crawler flag derived at request time). The user-agent is classified then discarded — no IP addresses, no user agents stored, no identifiers of any kind.

05

Retention

Access requests are kept while commercially relevant and deleted on request. Panel data contains no personal records to delete.

06

Your rights

For access, correction or deletion of anything you submitted, email [email protected].

This page describes actual system behavior in plain language. It is not formal legal advice; a production deployment should have counsel review its final privacy notice.
Before production: the operator must configure the real data-controller identity, contact address and applicable jurisdiction here. Placeholders must not ship to production.