Legal

Privacy policy

Last updated 10 November 2026

Nudge (nudgepr.dev) is run by Nudge PR (“we”). This policy explains what personal data we collect, why, and your rights. Questions go to admin@nudgepr.dev.

Who is responsible

  • For people who sign in to Nudge, we decide how your data is used: we’re the controller.
  • For your team’s reviewers and pull request authors, whom a workspace brings in from GitHub, Gitea or Slack, we act on the workspace’s behalf: we’re its processor, and the workspace’s owner is the controller. If that’s you, ask your workspace admin first; we’ll help them answer.

What we collect and why

DataWhy
Account detailsYour name, email address and sign-in id, from the sign-in provider. We never see your password.To run your account
Workspace membershipYour workspaces, role, access settings and invitations.To let teams share a workspace
Git activityGit usernames, display names and public emails; pull request titles, authors, labels, reviewers, reviews, comment activity and CI status. Never file contents.To assign and chase reviews, and show Insights
Messaging detailsSlack user ids, names, emails and time zones, and the channels you choose.To message the right person at a sensible time
Billing detailsBilling contact, plan, seat count and invoices. Card details are held by Stripe, not us.To take payment
Product analyticsWhich features are used, as ids and counts, not names or emails. On the website, only after you accept cookies.To improve Nudge
Error reportsTechnical details of errors, without names or emails.To find and fix problems

We rely on our contract with you to run your account, workspace and billing; on legitimate interests for product analytics and error reports; on your consent for cookies on the website; and on legal obligations to keep tax records. We don’t read or store your source code, sell personal data, or use it for advertising.

Cookies

The dashboard uses one essential cookie to keep you signed in. The website runs analytics without cookies until you accept them in the cookie banner; Cookie settings in the footer changes your answer at any time.

Who we share it with

Only the service providers that help us run Nudge, listed on Sub-processors, and the services your workspace connects (GitHub, Gitea, Slack). Where data leaves the UK or EU, it’s protected by the UK International Data Transfer Addendum or the EU Standard Contractual Clauses.

How long we keep it

  • Account and workspace data: while your account or workspace exists.
  • Raw event data from your git host: 30 days, for fixing problems.
  • Expired sign-in sessions: deleted automatically.
  • Billing records: as long as tax law requires, usually six years.
  • When a workspace lapses, its data stays so you can pick up again, until you delete it.

Your rights

You can ask to see, correct, export or delete your data, or object to how it’s used. In the dashboard, Account lets you:

  • Download my data: everything about you, as a file.
  • Delete my account: removes your account straight away. If you’re a workspace’s only member, the workspace and its data go too, its subscription is cancelled, and Nudge is disconnected from GitHub, Gitea and Slack.

If you’re a reviewer or pull request author in someone else’s workspace, its admins can erase you from it. Owners can also delete a whole workspace. For anything else, email admin@nudgepr.dev. We answer within a month. If you’re unhappy with our answer, you can complain to the UK Information Commissioner’s Office (ico.org.uk) or your local data protection authority.

Security

Data is encrypted in transit and at rest. Access tokens for your git host and Slack are stored encrypted, and sessions are stored only as hashes.

Children

Nudge is a tool for work and isn’t meant for anyone under 16.

Changes

We’ll update the date at the top when this policy changes, and email workspace owners about significant changes before they take effect.