Privacy Policy
Last Updated: April 5, 2026
Listen, we built freesalaries because we believe salary transparency shouldn't come at the cost of your personal privacy.
1. The Core Philosophy
Unlike traditional job platforms that demand your resume, phone number, and inbox just to show you a salary range, we want absolutely none of that. You shouldn’t have to dox yourself just to find out if you’re underpaid. We operate on a model of strictly anonymous, aggregate data.
2. Data We Actually Collect
When you submit your compensation, we literally only save the numbers and categories you select: your job title, years of experience, country, and the salary itself. We don't ask for your name. We don't ask for your email. Because we don't even have a user registration system, there is no account tying this data back to your real-world identity.
3. What About IP Addresses?
By default, web servers log IP addresses to prevent DDoS attacks and stop malicious bots. However, we hash and drop these addresses immediately after caching rate limits. Your raw IP is never stored in our primary database directly linked to your individual salary submission.
4. Cookies and Tracking
We use strictly essential cookies to remember your language preference and your UI theme (like dark mode). We also use lightweight, privacy-focused analytics just to see how many people visit the site. You won’t find invasive tracking pixels from social media giants chasing you around the internet after you leave.
5. Who We Share Data With
The entire point of this platform is to share aggregated salary data publicly with everyone. That's the product. We will never quietly sell a hidden, backend profile of you to advertisers or recruiters—mostly because we couldn't even if we wanted to. We simply don’t possess that kind of data.
6. Your Rights
Under normal circumstances (like GDPR or CCPA), you'd have the 'right to be forgotten'. But because our submissions are 100% anonymous, we literally cannot mathematically prove which record belongs to you if you asked us to delete it. Therefore, once a salary is submitted, it becomes a permanent part of the aggregated public dataset.