Privacy Policy

Repo Notify is run by Quexo Limited, a company registered in England and Wales (company number 16313649), whose registered address is 3rd Floor 86-90 Paul Street, London, United Kingdom, EC2A 4NE. We are the controller of your personal data under the UK GDPR and the Data Protection Act 2018. Contact us about privacy at [email protected].

• Account details: your name, email address and password (stored only as a one-way hash), and your workspace and team memberships.
• Security data: your two-factor secret and recovery codes (encrypted), the public keys of any passkeys you register, and, if you sign in with GitHub, Google, Facebook or LinkedIn, the account id and basic profile that provider shares with us.
• GitHub connections: when you install our GitHub App, we store the installation id, the name, type and avatar of the account or organisation it is installed on, and the name, visibility and default branch of each repository you let it see. To confirm the installation is yours, GitHub tells us which installations your GitHub user can access; we use that once and don't keep the access token.
• Pull request details: when we build a digest we fetch titles, numbers, authors, reviewers, labels, review states and dates of pull requests from GitHub, put them in the email, and then discard them. We never read your code. We keep a record of each digest sent: when, to how many people, how many pull requests it listed, and any error.
• Digests: the settings you choose for each digest, such as its name, schedule, timezone, repositories and recipients.
• Outside recipients: when a workspace member asks us to send a digest to someone without an account, we store that email address, who added it, and whether and when the person confirmed or unsubscribed. We email them once to ask, and send nothing more unless they say yes.
• Billing: if you buy a paid plan, Paddle gives us your customer id, subscription status, plan and country. We never see or store your card details.
• Technical data: your IP address, browser and device type, kept with your sign-in sessions and in short-lived server logs, to keep accounts secure and fix problems.

• To provide Repo Notify (performing our contract with you): reading the repositories you connect, building and sending digests, running your account and providing paid plans.
• To keep it safe (legitimate interests): preventing abuse and account takeover.
• To talk to you (contract and legitimate interests): your digests, team invitations, alerts when a digest can't be sent, security alerts, receipts, and important changes to the service or these policies. We will only send marketing email if you opt in, and you can opt out at any time.
• To meet legal duties (legal obligation): for example keeping records required for tax.

We don't sell your personal data or share it for advertising. The members of your workspace see its connections and digests, and the people a digest is sent to see what it lists. Beyond that, we share data only with providers who help us run Repo Notify, under contracts that require them to protect it:

• GitHub, which we ask for repository and pull request details through the GitHub App you install. Your GitHub data is also covered by GitHub's privacy statement.
• Paddle.com, our reseller and Merchant of Record, which processes payments, tax and invoices. Paddle is an independent controller of the data you give it at checkout; see Paddle's privacy notice.
• Resend, which delivers our emails: digests, invitations, sign-in and verification messages.
• Cloudflare, which sits in front of the site to protect it from attacks and sees the traffic passing through.
• DigitalOcean, which hosts the service.
• Google, Facebook or LinkedIn, only if you choose to sign in with them.

We may also disclose data if the law requires it, or to protect people from harm.

Some of our providers process data outside the UK. When they do, we rely on UK adequacy regulations or the UK International Data Transfer Agreement (or Addendum to the EU Standard Contractual Clauses) to keep it protected.

• GitHub connections: until you disconnect them, uninstall the GitHub App, or delete the workspace. Uninstalling on GitHub removes the connection's repositories straight away.
• Pull request details: only while a digest is being built and sent.
• Digest history: the record of each digest sent is kept for 180 days.
• Outside recipients: until the digest is deleted or a member removes the address. If you unsubscribe or say no, we keep the address with that choice so you're not invited to that digest again.
• Accounts: while your account is open. When you delete it, we delete your personal data within 30 days, except for backups (overwritten within a further 30 days) and records we must keep by law, such as billing records, which are kept for up to 7 years.

We only use cookies that Repo Notify needs to work, so we don't ask for consent to them:

• a session cookie and a security token, to keep you signed in and protect forms;
• an optional "remember me" cookie, if you tick it when signing in;
• preference cookies for light/dark mode and the sidebar.

Paddle's checkout, which loads only when you choose to buy something, sets its own cookies for payment and fraud prevention.

You can ask to access, correct, delete or export your data, and to object to or restrict how we use it. You can change most details, leave a team, disconnect GitHub, or delete your account yourself from Settings. If you get a digest without an account, use the unsubscribe link in any of them. If you no longer want a team's digests, ask its owner to remove you or email us. For anything else email [email protected]; we will reply within one month.

If you are unhappy with how we handle your data, you can complain to the UK Information Commissioner's Office at ico.org.uk, or to your local data protection authority.

Every account is protected by two-factor authentication or a passkey. Passwords are hashed, secrets are encrypted, the GitHub App's access is read-only and short-lived, and all traffic uses HTTPS. If a breach affects your data, we will tell you and the ICO as the law requires.

Accounts are not for anyone under 16. If you believe a child has created an account, contact us and we will delete it.

If we change this policy in a way that matters, we will email account holders before the change takes effect. The date at the top shows when it was last updated.