Privacy Policy
Effective date: 29 October 2026 ยท Version 2026-10-29
1. The short version
We collect the minimum needed to run a job feed: your account details, the broadcasts posted, and first-party usage events. We run no third-party trackers, no advertising SDKs and no external analytics. Contact details in job posts are visible to signed-in members only.
2. What we store
- Account: email, display name, password hash (bcrypt), company (HR only), role.
- Posts: the broadcast text and its parsed fields, poster identity, status and timestamps.
- Actions: upvotes, and first-party events such as feed views and WhatsApp taps.
- Security logs: login attempts (as a keyed hash, not your raw email), session metadata with a hashed session id, IP and user agent for abuse detection.
- Consent: which policy version you accepted and when.
3. What we never collect
- Your CV or any uploaded documents (we have no upload feature);
- Payment details - the service is free and we will never ask for money;
- Location, camera, microphone, or advertising identifiers (all blocked by browser policy too).
4. Why we process it
To provide the service (account, feed, moderation), to keep it secure (rate limiting, brute-force protection, audit trails), and to understand aggregate usage (first-party event counts).
5. Sharing
We do not sell data. Recruiters see your interaction with their posts only in aggregate. We disclose data when compelled by law, or to investigate abuse of the service.
6. Retention
- Accounts: until deletion is requested.
- Posts: 30 days from going live, then removed from the feed; audit metadata may persist.
- Security logs: up to 90 days.
- Events: aggregated or deleted after 12 months.
7. Your rights
Ask for a copy of your data, correction, or full deletion via the contact form. Deletion removes your account and disassociates your posts; anonymised aggregate counts may remain.
8. Cookies & storage
One session cookie (HttpOnly, SameSite) and local storage for theme and saved jobs. Details in the Cookie Policy.
9. Security
Prepared statements everywhere, nonce-based Content Security Policy, CSRF tokens on every
state-changing request, rate limiting, hardened sessions and least-privilege roles. See
SECURITY.md in our repository for the full posture.
10. Children
The service is not directed at anyone under 18.