Insight
How Salary Freedom protects your anonymity
No name, no email, no IP — and a 5-person floor on every public number. Here is exactly what we collect and what we do not.
Salary data is sensitive. People share theirs willingly when they trust the receiver — and stop sharing the moment trust breaks. We built Salary Freedom around two non-negotiables: collect nothing that identifies the submitter, and never let a query result single anyone out.
What we collect
When you submit a salary, the form asks for role, city, industry, years of experience, base salary, optional bonus, and optional equity. That is the entire submission. There is no name field, no email field, no phone field. We do not log your IP and we do not write a device fingerprint.
The submission is verified by Firebase App Check, which proves the request came from a real browser. App Check tokens are checked once and discarded — never stored alongside the salary record.
The k = 5 floor
Every public number on Salary Freedom is backed by at least five anonymous submissions. If your search matches fewer than five records, we return "insufficient data" — never a count, a min, a max, or a percentile. Below the floor, even the count is identifying.
Histograms apply the same rule per bar: any bucket with fewer than five records collapses into a neighbor before display. You will never see a single-record bar.
What about company names?
The submission may collect company for moderation purposes, but the public search and the API do not expose company as a filter. The intersection of company + role + city is the easiest way to re-identify a person, and we will only expose it as a filter once the dataset is large enough to honor k = 5 at that intersection.