gitfor
Sign inSign up

Privacy Policy

How gitfor collects, uses and shares personal data, and the choices and rights you have.

Last updated October 13, 2026

1. Controller

Taigrr LLC, [LEGAL_ADDRESS], is the controller of personal data processed to run gitfor. Contact us at support@gitfor.dev. For repositories owned by an organization, the organization decides what is stored there and may act as a controller for its members' data.

2. What we collect

  • Account data. Username, email addresses (primary and added), password hash (PBKDF2; we never store the password), display name, bio, website, avatar, two-factor and passkey public credentials, and, if you sign in with GitHub, your GitHub user id, login and verified email.
  • Content. Repositories and their history, LFS objects, issues, pull requests, reviews, comments, discussions, reactions, releases and attachments, wikis, projects, CI workflow files, logs and artifacts, Sites files, and secrets you store (encrypted at rest).
  • Credentials metadata. Personal access tokens, deploy tokens, agent tokens and OAuth grants: we keep a hash, name, scopes, creation, expiry and last-use times, never the plaintext after it is shown to you once.
  • Security and request data. IP address and user agent on sessions and sign-in notices, a coarse IP bucket for rate limiting, Turnstile challenge results on signup and sign-in, and short-lived request logs kept by Cloudflare for operating and securing the service.
  • Usage and billing. Metered usage (storage, CI and editor minutes, AI tokens, bandwidth) recorded per account in Cloudflare D1 and Analytics Engine, your plan, and the Stripe customer and subscription ids. Card details go directly to Stripe and never reach us.
  • Email. Notification and security emails we send, delivery outcomes, and replies you send to notification emails (which become comments).
  • Product analytics (optional). If the operator enables PostHog, page views and product events are collected with a first-party analytics cookie and local storage on this site (a random visitor and session id), with private repository names scrubbed. PostHog may also record sessions (clicks, scrolling and page layout) to help fix bugs. Recordings mask every input and all page text except on public repository pages, never run on sign-in, settings or admin pages or on private repositories, and are kept for 30 days. Signed-in events are tied to your opaque account id, and to your email only if the operator turns that on. Nothing is collected when your browser sends Do Not Track or Global Privacy Control, and you can opt out in Settings.

Public repositories, profiles and the comments you post on them are visible to anyone, including search engines. Git commits carry the name and email you configured in Git; that metadata is part of the repository and is visible wherever the repository is.

3. Why we use it

  • Provide the service you asked for: host and serve your repositories, run CI jobs, editors and builds, publish your sites, and send the notifications you subscribed to (contract).
  • Keep accounts and the platform secure: authentication, rate limiting, abuse and fraud prevention, malware and phishing takedowns, and investigating incidents (legitimate interests).
  • Bill paid plans and credits and keep the records tax law requires (contract and legal obligation).
  • Understand and improve the product, and find and fix bugs, through aggregate usage and, where enabled, first-party analytics and masked session recordings (legitimate interests; you can opt out).
  • Comply with law and respond to valid legal requests (legal obligation).

We do not sell personal data, share it for cross-context behavioural advertising, or use it to train AI models.

4. AI features

When you use an AI feature, the code, diffs, issue text and prompts it needs are sent to Cloudflare Workers AI or to the provider of a key you configured. Workers AI does not use your inputs to train models. Your own provider's handling is governed by your agreement with it.

5. Processors and subprocessors

  • Cloudflare, Inc.. Hosting and infrastructure: Workers (application), D1 (database), R2 (object storage), KV (caches and short-lived tokens), Artifacts (Git storage), Containers (CI runners and editors), Workers AI (built-in AI features), Email Service (outbound and inbound email), Turnstile (bot checks), Analytics Engine (usage metering), Queues, Durable Objects, logs and observability.
  • Stripe, Inc.. Payments, subscriptions, invoices and tax for paid plans and credits.
  • GitHub, Inc.. Only if you use it: sign in with GitHub, repository import, mirroring and the GitHub app.
  • Your AI provider. Only if you configure your own key (for example OpenAI, Anthropic or a Cloudflare AI Gateway): the code and text an AI feature needs are sent to that provider under your agreement with it.
  • PostHog, Inc. (United States). Only if the operator enables analytics: product analytics and masked session recordings, using a first-party cookie on this site.
  • Integrations you enable. Services you connect (for example Linear, or webhook URLs you configure) receive the events you choose to send them.

We will update this list before adding a new subprocessor that handles account data.

6. International transfers

Cloudflare runs the service on its global network, so data may be processed in the United States and other countries. Transfers out of the EEA, UK and Switzerland rely on the EU–US Data Privacy Framework where the recipient is certified, and otherwise on Standard Contractual Clauses.

7. Cookies

We use strictly necessary cookies (your sign-in session and short-lived sign-in state) and, where analytics is enabled, one first-party analytics cookie. There are no advertising or third-party cookies. See the Cookie Policy.

8. Retention

  • Account data: for as long as your account exists. Deleting your account removes it, except as listed below.
  • Unverified accounts with no repositories, organizations or activity: deleted automatically shortly after signup.
  • Sessions: up to 30 days, and ended after 14 days without use. Sign-in tokens, reset and verification links expire within 24 hours.
  • Repositories and their CI data, sites and secrets: until you or an organization owner deletes them. Caches expire on their own within 30 days.
  • Comments, issues, pull requests and reviews on other people's repositories: kept after you delete your account so conversations stay intact, but attributed to “ghost” (Deleted user).
  • Webhook and integration delivery logs: 30 days.
  • Data exports: available for download for 24 hours, then deleted.
  • Billing and payment records: as long as tax and accounting law requires (typically up to 10 years), including after account deletion.
  • Abuse reports and enforcement records: as long as needed to handle the report and prevent repeat abuse.
  • Backups and Cloudflare infrastructure logs: rotated on Cloudflare's schedules.

9. Deleting your account

You can delete your account in Settings. We cancel any subscription, sign you out everywhere, revoke your tokens and keys, delete your repositories, sites, runners, stars, follows and notification settings, and retire your username so nobody can impersonate you with it. Content you contributed to other people's repositories stays but is shown as “ghost”. You must transfer or delete organizations you are the only owner of first.

10. Your rights

Depending on where you live, including under the GDPR, UK GDPR and the CCPA/CPRA, you have the right to:

  • access your data and get a copy (Settings → Export your data gives you a JSON archive);
  • correct inaccurate data (most of it is editable in Settings);
  • delete your data (Settings → Delete account);
  • object to or restrict processing based on legitimate interests, and opt out of analytics;
  • data portability (your repositories can always be cloned with Git);
  • withdraw consent where we rely on it, without affecting earlier processing;
  • not be discriminated against for exercising these rights.

We do not sell or share personal information as the CCPA defines those terms. To exercise a right, email support@gitfor.dev; we may need to verify that the request comes from the account holder, and an authorized agent may act for you with proof of authority. We answer within one month (45 days under the CCPA). You may also complain to your local data protection authority.

11. Security

Data is encrypted in transit, secrets and AI keys are encrypted at rest, passwords are hashed, and access to production is restricted. See the security policy to report a vulnerability.

12. Children

The service is not directed to children under 13 (16 in the EEA and UK without parental consent), and we do not knowingly collect their data. If you believe a child has an account, contact us and we will delete it.

13. Changes

We will post changes here and update the date above; for material changes we will also email account holders before they take effect.