Privacy Policy
What Fletcher reads, what we keep, who else sees it, and how to get it deleted.
Who we are
Not Quite My Tempo (notmytempo.dev, "Fletcher", "we") is a code review service run by Parshva Shah, an individual based in India. We decide how the data described here is used. Questions, requests, and complaints go to support@notmytempo.dev.
What we collect
Your GitHub account
You sign in with GitHub; we don't have passwords. From GitHub we keep your numeric user ID and username, the organizations and repositories you can reach through the Fletcher GitHub App, and your role in each organization. Your avatar is loaded directly from GitHub. We also keep the GitHub access token from sign-in, encrypted, and use it only to re-check that access every 10 minutes while you're signed in. Sessions end after an hour.
Installations and repositories
For each account that installs the App: the account name, ID, and type, and the names, IDs, and default branches of the repositories it gives Fletcher, plus which of them have reviews turned on.
Pull requests and code
To review a pull request, Fletcher fetches its title, description, diff,
and the repository's .fletcher.json file, if there is one.
For context it also fetches the full content of the changed files, the
repository's contribution guidelines (such as AGENTS.md or
CONTRIBUTING.md), its dependency manifests (such as
package.json), and the list of file paths in the
repository. It sends all of this except the file list to the AI model
provider your workspace uses (see below). We don't keep your source
files. While a review runs, its title, description, and diff are held in
the state of its Cloudflare Workflow, which Cloudflare deletes within 30
days of the review finishing. We do keep what the review produced: the
verdict, summary, and each finding (file path, line, severity, and
message, which can quote short pieces of your code). We also keep the
commit SHA, the pull request number, timing, errors, and token counts.
Reviews are also posted as comments on the pull request in GitHub.
Your own API keys
If an admin saves a workspace's own Gemini or Vertex AI key, we check it with Google, then store it encrypted (AES-256-GCM). After that, only its last 4 characters are shown. We record who saved it and when, and which model the workspace chose.
Billing
Polar sells the paid plan as merchant of record. Polar collects your name, email, billing address, tax details, and payment method under its own privacy policy. We never see card details. We keep only the Polar customer and subscription IDs, the subscription's status, when the current period starts and ends, and how many review credits each review used.
Activity and operations
We keep an audit log of role, key, and settings changes in each workspace (who, what, and when). Our operational logs record event names, internal and GitHub IDs, repository names, and error details, but not your code. Cloudflare, which hosts the service, processes request data such as IP addresses to deliver and protect it.
Cookies and tracking
We set one session cookie when you sign in, plus short-lived cookies that protect the GitHub sign-in itself. These are strictly necessary, so there's no cookie banner. We don't use analytics, advertising, or tracking scripts. Pages load fonts from Google Fonts, so your browser sends its IP address to Google when fetching them.
How we use it
- To review pull requests and show the results in your dashboard.
- To decide who can see and change what, based on your GitHub access.
- To run the free trial and the paid plan.
- To keep the service secure and reliable, for example with the daily review limit.
- To answer you when you contact us.
We don't sell your data, we don't use it for advertising, and we don't use your code to train AI models. Our legal bases are performing our contract with you and our legitimate interest in running a secure service.
AI processing
Reviews are generated by Google's Gemini models, through the Gemini API or Vertex AI. Free trial and paid-plan reviews use our Gemini key, which is on Google's paid API service and doesn't let Google use prompts or responses to train its models. If your workspace uses its own key, your account's terms with Google apply instead. Note that on the unpaid tier of Google AI Studio, Google may use content to improve its products, so use a paid key for private code.
Who we share it with
We use these service providers, and only for running Fletcher:
- GitHub: sign-in, repository access, and posting reviews.
- Google: Gemini API or Vertex AI for reviews, and Google Fonts.
- Cloudflare: hosting, database, and network.
- Polar: checkout, subscriptions, invoices, and tax. Polar uses Stripe for payments.
These providers may process data in the United States and other countries. We'll also disclose data if the law requires it.
How long we keep it
- Your account: until you delete it on your Account page, which also deletes your sessions and roles and revokes Fletcher's access to your GitHub account.
- Workspace and review history: until an owner deletes the workspace's data in its settings, which also uninstalls Fletcher. Uninstalling the App on GitHub stops new reviews but keeps past history. After a deletion we keep only the GitHub account's name and ID, its billing references, how many free reviews it used, and the plan credits it used this billing period, so neither can be reset.
- API keys: until an admin removes or replaces the key in workspace settings.
- Sessions: one hour, or until you sign out.
- Billing records: Polar keeps these for as long as tax and accounting law requires.
Your choices and rights
You can delete your account yourself on your Account page, and an owner can delete a workspace's data in its settings. You can also ask us to access, correct, export, or delete your personal data, or object to how we use it. Email support@notmytempo.dev, and we'll respond within 30 days. You can stop Fletcher at any time by uninstalling the GitHub App or revoking its authorization in your GitHub settings. If you're in the EU or UK, you can also complain to your data protection authority. If you're in India, the contact above is our grievance contact under the Digital Personal Data Protection Act, 2023.
Security
Tokens and keys are encrypted at rest. Session cookies hold only random tokens, which we store as keyed hashes. Webhooks from GitHub and Polar are signature-checked. No system is perfectly secure; if a breach affects you, we'll tell you and the relevant authorities as the law requires.
Age
Fletcher is not for anyone under 16, and we don't knowingly collect their data.
Changes
We'll post changes here and update the effective date. For material changes, we'll also give notice in the app before they take effect.