Privacy

What RepoGates sends

What	When, and why
Repository name owner/repo	When you view a repository page (pre-check, so the verdict is ready before you click Download — you can turn this off in Options) and when a download starts.
Your account	A session token identifying the account you registered, so your checks can be counted against your plan. See Registration below.
Agent-provenance flag	If you arrived from a known AI surface, the request carries prov=agent and that surface's hostname (e.g. claude.ai). The hostname only — never the page URL, never any content.
A command line, with the Claude Code plugin only	If you install the RepoGates plugin for Claude Code, its hook sends the shell command line Claude Code is about to run — with URL credentials and NAME=value assignment values removed first — to the verdict service, which parses it for repository names, never executes it, and does not store or log it; the log carries the decision and the repository names only. A package named on the line (npm install express, pip install flask) is looked up by the verdict service on the public npm or PyPI registry to find the repository it declares — the lookup carries the package name and nothing about you. Nothing is sent for a line that names neither a GitHub repository nor an npm or PyPI package. The extension never sends command lines.
Device registration id	A random identifier minted per installation, so a plan can be limited to a number of machines. It is not a fingerprint: no hardware identifiers, no canvas hashing, nothing derived from the machine itself.

Registration

RepoGates requires an account. You sign in with Google or Microsoft; we never see a password, and we request only your email address.

We store the provider's stable identifier for you, your email address, when you registered, which distinct repositories your free trial was spent on (their owner/repo names and when), your plan, and your device registrations. The count lives on our server rather than in your browser because that is the only way a free allowance can mean anything. It is a record of the repositories your allowance was spent on — at most ten — and nothing else about your browsing.

Sign-in is handled by Google or Microsoft under their own privacy policies. Their sign-in pages may set cookies; RepoGates does not.

Who else handles your data

RepoGates does not sell data, and does not share it for advertising. Three named processors act on our instructions, for no purpose of their own, and only for what is described below:

• Google or Microsoft — sign-in only. We never see your password; they set their own sign-in cookies, not RepoGates.
• Polar, our merchant of record, handles checkout and billing for a paid plan: your email address and the payment details you give it directly (RepoGates never sees or stores a card number), so it can charge you and remit tax. Polar's own privacy policy governs that payment, not this one.
• Google Cloud Platform hosts the verdict service and the account data described on this page — the infrastructure the data lives on, not an independent user of it.

What RepoGates never sends

• No page contents, no repository contents, no code.
• No full URLs — never paths, queries, or fragments beyond owner/repo.
• No browsing history. Sites other than github.com and the enumerated AI surfaces are invisible to RepoGates by design — it holds no permission to see them.
• No telemetry, analytics, or advertising identifiers. No data is sold or shared beyond the named processors above.

What stays on your device

• The audit log — blocks, warnings, and your proceed or override decisions — is stored locally and shown in Options. It never leaves your machine on the personal tier.
• Cached verdicts, so repeat downloads need no network request.
• Your settings live in Chrome sync storage, subject to your own Chrome sync configuration.

Server-side handling

The verdict service receives owner/repo, computes a trust verdict from public GitHub metadata, caches that verdict briefly, and logs requests per-IP for rate limiting. Verdicts describe repositories, not people.

It also keeps a timeline per repository — the date of each answer, the verdict, the score and which checks fired, by number — for 180 days from the last time that answer was confirmed, so a repository's page can show what changed since the previous look. A timeline row records nothing about who asked: no account, device or address, and never the finding text.

This website (repogates.com) keeps standard access logs — path, referrer, user agent, IP address — for 30 days, for security and to count visits. No cookies, no advertising or analytics identifiers, and no client-side tracking script of any kind.

Your data, your call

Ask us to export or delete your account and everything attached to it — email, the repositories your trial was spent on, device registrations — at support@repogates.com. Deletion is permanent and takes effect within 30 days. You do not need a reason.

Managed (organisation) deployments

Not currently offered. The organisation tier was withdrawn in August 2026 and no managed deployments are sold today, so nothing in this section applies to any current customer. It is kept rather than deleted because the extension still contains the managed-storage mechanism, and a privacy notice should describe what the software can do, not only what we are selling this month.

If your organisation force-installs RepoGates, policy — block and warn rules, allowlist, fail mode — is set by your administrator through managed storage, and the extension marks which settings are organisation-controlled. Organisation deployments may report blocks and overrides to that organisation's console; where they do, reporting is pseudonymised and re-identification requires two administrators. The organisation tier ships with its own addendum and a DPIA template.

Limited use disclosure

RepoGates' use of the information described on this page adheres to the Chrome Web Store User Data Policy's Limited Use requirements:

• We use the data described above only to provide or improve RepoGates' single purpose — assessing a repository or model before you download it — and the user-facing features built on that: your plan, deep scans, the audit log.
• We transfer it only as described in Who else handles your data above: to a processor that needs it to provide that same function (Polar for billing, Google Cloud Platform for hosting), to comply with the law, for security purposes, or as part of a merger, acquisition or asset sale.
• We never use or transfer it to serve you personalised, retargeted, or interest-based advertising.
• We do not let a human read it, except: with your consent (for example, when you email support and we look at your account to help you); for security purposes; to comply with the law; or as part of merger, acquisition or similar review, in each case only for the duration and purpose reasonably needed.

---

Contact

Questions, complaints, or a data request: support@repogates.com.