Privacy policy
Template. Every value in
[BRACKETS]is a placeholder the operator must fill in before launch, and the text should be reviewed by a lawyer for the operator's jurisdiction.
Last updated: [EFFECTIVE DATE]
This policy covers the hosted service at repodar.dev. If you run your own copy of Repodar (self-hosting), you are the controller of that instance and this policy does not apply to it.
Who is responsible
The controller is [COMPANY NAME], [ADDRESS], [COUNTRY/JURISDICTION]. Contact for anything about your data: [CONTACT EMAIL].
What Repodar processes
Repodar is a read-only radar. It reads a few files from the repositories you choose, keeps what it derives from them and throws the files away. In detail:
| Data | Where it comes from | Why | Legal basis (GDPR Art. 6) |
|---|---|---|---|
| GitHub account: numeric id, login, display name, avatar URL, verified email address | GitHub sign-in | Your account and sign-in | Contract (b) |
| Sessions: a session token, its expiry, the IP address and browser user agent at sign-in | Your browser | Keeping you signed in, spotting misuse | Contract (b), legitimate interest (f) |
| GitHub OAuth access token (encrypted) | GitHub sign-in | Reading repositories you added by URL | Contract (b) |
| Repository metadata: name, id, default branch, archived flag, last push time | GitHub App | Listing your repositories | Contract (b) |
| Derived manifests: runtimes and versions, frameworks, deploy target, dependency names and versions, findings with dates | Parsing manifests and lockfiles in memory | The dashboard and the digest | Contract (b) |
| Provider tokens you paste (Forge, Cloudflare, Vercel, DigitalOcean, a GitHub fine-grained token), encrypted | You, in Settings | Reading where your projects are deployed | Contract (b) |
| What those providers report: site or project names, linked repository, runtime version, last deploy time | The provider APIs | Correcting the declared runtime and deploy target | Contract (b) |
| Digest email address and a record of each digest sent | Your GitHub account | Sending the digest email | Contract (b) |
| Rate-limit counters keyed by IP address | Your requests | Protecting the service | Legitimate interest (f) |
Consent cookie rd_consent |
Your choice in the cookie banner | Remembering that choice | Legal obligation (c) |
| Product analytics (only if enabled and only after you agree) | Your browser and the app | Learning which pages and features help | Consent (a) |
File contents, source code, commits and diffs are never stored. Repodar never writes to your repositories.
How long it is kept
- Account, sessions and repositories: for as long as your account exists. Sessions expire after 7 days of inactivity.
- Scan history: the last 20 scans per repository; older ones are deleted automatically.
- Digest records: the last 90 per account.
- Findings: while the repository is tracked; resolved findings stay visible with their date.
- Rate-limit counters: minutes (they expire with their time window).
- Provider tokens: until you remove them in Settings or delete your account.
- Product analytics: at most [ANALYTICS RETENTION, e.g. 24 months].
- When you ask us to delete your account, everything is deleted within 30 days, except what the law requires us to keep (for example invoices, if billing is ever enabled).
Who helps process it
| Processor | Purpose | Location |
|---|---|---|
| Cloudflare, Inc. | Hosting (Workers, D1, KV, Queues), optional cookieless Web Analytics | Global network; data processing addendum with SCCs |
| GitHub, Inc. | Sign-in and repository access (you connect it yourself) | United States; SCCs |
| Lettr | Sending the digest email | [LETTR LOCATION] |
| Stripe, Inc. (only if paid plans are enabled) | Payments | United States / EU; SCCs |
| PostHog, Inc. (only if analytics is enabled and you agree) | Product analytics, EU-hosted | European Union |
Provider APIs you connect (Laravel Forge, Cloudflare, Vercel, DigitalOcean) receive requests made with your own token; Repodar only reads from them.
Cookies
| Cookie | Purpose | Lifetime | Needs consent |
|---|---|---|---|
better-auth.session_token (__Secure- prefix over https) |
Keeps you signed in | 7 days | No (strictly necessary) |
| Better Auth state cookies during sign-in | Protects the GitHub sign-in against forgery | Minutes | No (strictly necessary) |
rd_consent |
Remembers your analytics choice (granted or denied) |
1 year | No (stores the choice itself) |
ph_<project key>_posthog |
PostHog product analytics, only if enabled | 1 year | Yes, set only after you agree |
Cloudflare Web Analytics, when enabled, is cookieless and stores nothing on your device. When analytics is enabled, a "Cookie settings" link appears in the footer and lets you change your choice at any time. When it is not enabled, there is no banner, no link and nothing to choose.
Your rights
Under the GDPR you can ask for access to your data, correction, deletion, restriction, a portable copy, and object to processing based on legitimate interest. Where processing is based on consent you can withdraw it at any time, without affecting what happened before. Write to [CONTACT EMAIL]; we answer within one month. You can also complain to your data protection authority, or to the authority of [COUNTRY/JURISDICTION].
Changes
We will announce material changes on this page and, if you have an account, by email before they take effect.