Docs · Account
Privacy and security
We track reading, not readers. The extension measures one number per file, and the code that does it is public. This page is the practical summary; the policies live at /privacy and /security.
What we store
- Time spent on each file of each pull request, per reviewer.
- Your GitHub identity (id, login, avatar), to show who read what.
- The changed-file list of each watched PR: paths and added/deleted line counts.
- Workspace-level billing metadata.
What we never store
- Source code. The extension never reads or transmits the diff body, and the GitHub App does not request code contents.
- Keystrokes, scroll positions inside files, mouse movement, or screenshots.
- Anything from outside github.com pull request pages.
- Third-party analytics or trackers, on the marketing site or in the dashboard.
How measurement stays honest
Dwell time counts only while the tab is focused and a file's rendered diff is on screen. Collapsed diffs, background tabs, and excluded files earn nothing. The full mechanics are in How it works, and the extension source is public for verification.
Retention
- Per-file reading state clears when a PR closes or merges.
- Aggregate reviewer history is kept 90 days, then deleted. Business and Enterprise workspaces can opt into longer audit retention.
Access and tokens
- Extension tokens are bearer tokens scoped to reading endpoints. Each reviewer can list and revoke theirs at dashboard settings; disconnecting from the popup revokes server-side too.
- Workspace data is visible only to workspace members, scoped by role.
- The GitHub App asks for the minimum: check runs, pull request metadata, and repository metadata.
Deleting your data
- Uninstall the GitHub App from the org. The workspace is suspended immediately and webhook ingestion stops.
- Email privacy@readpr.dev to permanently delete the workspace and all reading history. Requests are actioned within seven days.