Privacy
Rails Radar stores what it needs for job discovery, candidate matching and private application tracking. Below we describe only what the service actually does — no promises beyond the state of the system. Polska wersja.
What we store
- Account identity: your Google or GitHub identifier, verified e-mail, name and avatar.
- CV documents, the candidate facts extracted from them, and your manual corrections.
- Your application statuses, private notes and status history.
- The technical minimum: the sign-in session cookie, temporary OAuth data and workspace preferences such as board filters.
Candidate facts and recruitment notes are never published on public company pages. Signing in contacts your identity provider. Opening an external posting takes you to a source site with its own privacy policy.
Deleting your data
- Delete CV data in your profile removes the CV records and extracted facts from the live profile. Manual corrections stay until you clear or reset them. File deletion is attempted immediately.
- Delete a note removes that note from the workspace. Removing tracking does not erase the separate status-history records.
- Whole-account deletion is self-service: delete your account once signed in. It is irreversible — it removes the account, profile, CV, statuses, notes, history and match decisions, then signs you out and clears the session data. Before you delete anything you can export your data (JSON).
Export and corrections
Open your candidate profile export (JSON) when signed in. It contains candidate facts, provenance, the profile version and CV summaries — not your notes or application history. You can correct candidate facts in your profile; for anything else write to us.
Database snapshots
The backup job keeps the 7 most recent successful database snapshots, taken daily. That is a count, not a guaranteed number of days: a failed or stopped backup can leave older snapshots in place. Removing a live record does not rewrite existing snapshots; they expire through the rotation and are not used in the meantime. This page does not promise a verified encryption configuration or a fixed infrastructure retention period.
Technical files
We use only the technically necessary browser storage: keeping the session, security (request verification) and remembering your settings. We run no analytics and no marketing tracking, which is why there is no consent banner. Signing in requires no mandatory acceptance checkbox — this is information, not consent.
Data controller
Gotar, Strzelców 50/44, 81-586 Gdynia, Poland — NIP PL9581496348.
Legal bases for processing
- Article 6(1)(b) — contract. Running the account, signing you in, processing your CV and the facts extracted from it, matching you against listings, your application statuses, notes and match decisions. The service cannot work without this.
- Article 6(1)(f) — legitimate interests. Service security (technical logs that contain numeric identifiers only) and browsing public listings while remembering your view preferences, such as board filters.
- We do not rely on consent (Article 6(1)(a)): we run no marketing and no analytics, so there is no consent to collect or withdraw.
Recipients
- Google and GitHub — signing in only; nothing is left with them beyond the identity handshake.
- Laya — the decision model running on our own infrastructure. Both decision backends receive the same extract of state: the listing description and the facts derived from your CV.
- Cloudflare (Workers AI) — part of the hard questions is sent to this external provider, which receives that same extract of state.
In every case a recipient receives only the data needed to answer the questions about the listing and the match.
Retention periods
- Live records (account, profile, CV, statuses, notes, decisions): until you delete the account or that CV.
- CV files: deleted immediately when you delete them. Failed deletions and detached files are collected every minute and at the latest after 24 h.
- Finished queue jobs: cleared every hour. Background jobs keep their place in a separate database, so a job already queued when you delete your account keeps only your numeric account number until it runs and is cleared — never your CV or note text.
- The sign-in session cookie: until you close the browser.
- Technical logs: retention depends on the host — ask us, quoting your account number and without attaching your CV.
Your rights and contact
[email protected] for access, correction, export and deletion requests. Do not include your CV or sensitive notes in the first e-mail.