Privacy policy
Effective 4 November 2026. Last changed 9 November 2026.
This policy says what personal data gitring keeps, why, who else handles it, how long we keep it, and what you can ask us to do. It covers the hosted service at gitring.tech and app.gitring.tech, and the waitlist of gitring's first version. It does not cover copies of gitring that other people run themselves.
1. Who we are
gitring is run by Mirza Anwaarullah Baig, an individual in India ("we"). For the personal data in this policy we are the controller (under the EU and UK GDPR) and the Data Fiduciary (under India's Digital Personal Data Protection Act 2023, the "DPDP Act").
When a business uses gitring for its code, that business decides what goes into its projects. For that content we act as its processor, under our Data Processing Agreement, which business customers can ask us for.
Contact: hello+privacy@gitring.tech. Grievance Officer for India: Mirza Anwaarullah Baig, at hello+grievance@gitring.tech.
2. What we keep and why
| What | Where it comes from | Why we keep it | Legal basis (GDPR) |
|---|---|---|---|
| Account: your GitHub account's id and login, name, email address and profile picture address. The email address is the primary address GitHub has verified for you (or, failing that, the public one on your profile), read again each time you sign in. If you sign in with Google: Google's fixed id for your account, your name and your email address as Google gives them; we do not keep your Google profile picture, and we never use your Google account for anything but signing you in. | GitHub, when you sign in with GitHub | To sign you in, show who did what, give you access to your projects, and send you the emails in section 6 | Contract (Art. 6(1)(b)) |
| Emails we send you: a welcome when you make your account; up to two getting-started emails in your first week, each only for a step you have not done, chosen from whether your account has an agent token or a program you connected, and whether an intent was declared in your projects; emails about your account and its security (a program you connected, a way to sign in added to your account, a project that now bills to you, a payment for your plan refunded or a chargeback on it lost); reminders (a decision that waits for you, a trial that ends); product news now and then, until you turn it off (every product-news email has an off link, and so does Settings); and, when our email provider reports that mail to your address bounced, that fact, so we stop sending to it. Each email's text and content are kept until it is sent (section 6); your address is read from your account when it goes. | Your account and what you do in gitring; our email provider, for a bounce | To tell you about your account, what waits for you and how to start; product news, which you can turn off | Contract (Art. 6(1)(b)) for account, security and reminder emails and the welcome; legitimate interest (Art. 6(1)(f)) for getting-started emails, which you can turn off when you sign up, in Settings, Email, or by the link in each; consent (Art. 6(1)(a)) for product news, which is off unless you turn it on and has a link to turn it off in each |
| Session data: a hash of your session cookie, which lasts 14 days; two short-lived cookies during sign-in, and a third when the link you came by has campaign tags (below) | Your browser | To keep you signed in safely | Contract; legitimate interest in security (Art. 6(1)(f)) |
| Command-line and agent sign-in requests: the network address and program that asked for a command-line sign-in code, and the network address that asked to connect a program | Your terminal, your browser and your agents | To let you approve a sign-in or a connection, and to limit abuse | Legitimate interest in security |
| GitHub token, encrypted | GitHub, when you sign in | To list and import your repositories and to mirror merged code to the GitHub repository you link | Contract |
| API keys, agent tokens and agent connections: a hash of each token, its name, its kind, the projects it covers and when it was made, last used and revoked; and when each of your agents first connected, and how (by address, with a token, or as git's helper). For a program you connect by its address: the name the program gives itself (we cannot check it), the addresses it returns you to, your approval, and when it was last used | You, when you create them or approve an agent; the program, when it registers | To let your agents act for you | Contract |
| Your content: code, intents (goal, plan, files and functions in scope), conflict checks, test output once test runs return, comments, approvals and the decision log; for a GitHub repository you link, the pull requests (title and description) and the outside check results GitHub sends us | You, your team, your agents, and GitHub for a repository you link | To provide the service | Contract (or, for a business customer, its instructions under the DPA) |
| Invitations: the GitHub login or the email address of a person invited to a project. An address is kept only while its invitation is open, and deleted when it is accepted, declined, revoked or expires. To show you an invitation sent to your address, we read the addresses GitHub has verified for you with your GitHub token; we keep which addresses they are in the server's memory for up to a minute, never in our database | The person who invites | To let the invited person join | Contract; legitimate interest in letting teams add people |
| Usage counts: checks per project, and who declared intents and made decisions | The service | To apply plan limits | Contract |
How you found gitring: the campaign tags of the link you came by when you signed up (utm_source, utm_medium, utm_campaign and utm_content, for example "news.ycombinator.com" or "gitring.tech"), kept with your account. Only short codes are kept: never search terms, the page you came from, or your address | The link you followed into gitring | To count sign-ups by where they came from, and to see which of our links help | Legitimate interest in knowing which of our links work |
| Billing: the plan you bought, monthly or yearly, the number of people it is for, when it renews or ends, and the ids Dodo Payments gives your customer record and your subscription | You, when you buy; Dodo Payments, which tells us the subscription's status | To give you the plan you paid for, and to keep business records | Contract; legal obligation (Art. 6(1)(c)) |
| Technical logs: request times, routes, error traces, trace ids | Your browser and agents | To run, secure and debug the service | Legitimate interest in security and reliability |
| Settings kept in your browser: in the web app, your theme, the last project you opened, when you last left a page, the last choice in a project's ask box, and an invitation link while you accept it (for that tab only). They stay in your browser and are not sent to us | Your browser | To show the app as you left it | Legitimate interest in a working app |
| Waitlist of gitring's first version: see section 5 | You, when you joined it | To tell you once that gitring is open | Consent (Art. 6(1)(a)) |
| Visits to gitring.tech: how you use the page (clicks, scrolling, mouse movement, the parts of the page you see), your device, browser and approximate location, recorded by Microsoft Clarity with one id per page view and no cookie | Your browser, on gitring.tech only (not the gitring app) | To see which parts of the page help people and which confuse them | Legitimate interest in improving the site (Art. 6(1)(f)) |
We do not use advertising or tracking cookies. We do not sell personal data. We do not show advertising. gitring.tech uses Microsoft Clarity with cookies turned off: it does not follow you from one page or visit to the next. The film on gitring.tech is hosted by YouTube (Google) and loads only when you press play: until then nothing is sent to YouTube. Played on the page, it runs in YouTube's privacy-enhanced mode; opened in a new tab, or without JavaScript, it plays on youtube.com. Either way Google's privacy policy applies to it. gitring.tech also shows Product Hunt's badge for gitring's launch, whose image your browser loads from Product Hunt (api.producthunt.com): Product Hunt receives your IP address and the details your browser sends with any request, under its own privacy policy.
We do not see your card number. Paid plans are sold by Dodo Payments (section 4) as merchant of record: Dodo Payments is the seller to you, takes the payment, works out and collects tax, sends the invoice and keeps card data, as a controller of its own under its own privacy policy, not as our processor. When you start buying, we send it your name, your email address and your gitring account id; it tells us whether your subscription is active, and nothing about your card. When you come back from its payment page, its address carries your email; the gitring app removes it from your browser's address bar at once.
3. AI processing
gitring uses AI models for two things: to judge conflicts between intents, and, when you choose it, to answer an ask you give gitring's agent. This section says what goes to which model.
What is sent to judge a conflict. When an agent declares or changes an intent, gitring first applies fixed rules. Only when the rules cannot decide does gitring send a model the minimum it needs: the two intents being compared (title, goal, plan summary, steps and checks, the files and functions in scope and the signatures they change, size, state, priority, when each was declared, and whether one depends on the other) and the facts gitring found about how they overlap. gitring adds no code of yours. A plan is text an agent writes, and it is sent as the agent wrote it, so it holds code only if the agent put code in it. No account data, such as names, logins or email addresses, is sent. The model chooses among outcomes gitring wrote and gives how sure it is; when it is sure enough, its choice settles the pair, unless the project chose to have a person settle such pairs. A person can settle the pair again while it is open.
What is sent when you ask gitring's agent. Only for an ask you give gitring's agent, and only while gitring runs it: your ask, the project's name, the titles of its intents, its file paths (up to 2,000), the items in your inbox, and, when the agent needs them, the goals and plans of up to three intents. File contents are not sent. No email address or login is sent. Its answer is a reply or a proposed intent; it decides nothing, and a person gives every proposed intent to an agent.
Where it goes.
| Model | Used for | Provider and hosting |
|---|---|---|
| Microsoft-Decision-1 | Judging conflicts | A Microsoft model hosted by Microsoft in Azure, through Microsoft Foundry, under Microsoft's data processing terms. It writes no text: it only scores the outcomes gitring offers. |
| DeepSeek V4 Flash | gitring's agent | A DeepSeek model sold and hosted by Microsoft in Azure, through Microsoft Foundry, under Microsoft's data processing terms. DeepSeek does not receive your content. |
| GPT-5.6 Luna | Nothing | An OpenAI model sold and hosted by Microsoft in Azure, through Microsoft Foundry. It is deployed but gitring does not call it. |
We send your content to no other model provider. If that changes, we change this section first (section 11).
No training on your code. gitring does not train or fine-tune any model on your code, intents or other content. Microsoft's terms for these models say that inputs and outputs are not available to the models' makers, are not used to improve their models, and are not used to train any foundation model without our permission. Microsoft checks inputs and outputs for abuse of its service: content its systems flag may be reviewed by automated means or by authorised Microsoft employees, and is stored for that review in the geography of our Microsoft Foundry resource.
Your agents are yours. The coding agents you connect (for example Claude Code or Codex) run under your own accounts with their providers. What they send to their providers is governed by your agreements with those providers, not by this policy.
People decide. A model may advise that two intents conflict. Every approval of a plan or a merge is a person's, and a project can require one before every merge. An agent can never approve.
4. Who else handles your data
We use these service providers (sub-processors).
| Provider | What they do for us | Location |
|---|---|---|
| Microsoft Azure | Hosting of the service, its database, file storage, secrets and logs; the gitring.tech site, the web app's files and the DNS | Singapore (Azure Southeast Asia), with backup copies in Hong Kong (Azure East Asia); the site and the web app's files are served from Hong Kong and Microsoft's global network |
| Microsoft Foundry | AI models (section 3) | The Foundry resource is in Singapore; Microsoft may process each request in any region where the model runs |
| Microsoft Azure (Azure Communication Services) | The emails we send you: account and security notices, the welcome, getting-started emails, reminders, product news until you turn it off, and invitations. It processes the address and the message to deliver it, tells us when mail to an address bounced, and keeps addresses that bounced hard for a while to prevent abuse. No open or click tracking. | Asia Pacific (Microsoft's geography that includes Singapore and Hong Kong; Microsoft chooses the data centre and may process in transit elsewhere) |
| Sign-in with Google (we receive your Google account's id, name and email address) | United States | |
| GitHub | Sign-in; repository import; mirror of merged code to the repository you link; the pull requests and outside checks of a repository you link | United States |
| Microsoft Clarity | Recordings of visits to gitring.tech, without cookies (section 2) | United States |
| Dodo Payments | Merchant of record for paid plans: it sells the plan to you and handles payment, tax and invoices as a controller of its own (section 2); we send it your name, email address and gitring account id | As its own privacy policy states |
| The hosting provider of gitring's first version | Keeps that version's records, its waitlist among them, until we delete them (section 5) | Outside Azure |
We may also disclose data if the law requires it, to protect people from harm, or as part of a sale or merger of the business (we will tell you first).
5. The waitlist
gitring's first version. Before this service, gitring's first version had a waitlist: people signed in to it and chose the plan they would want. Its records include, for each person who signed in, the name and email address the sign-in gave and how they signed in; for each person on its waitlist, also the plan they chose and an optional note. Those records were never copied into this service. They stay with the hosting provider of that first version (section 4). We use them only to write to the people on the waitlist once, to say that gitring is open, and then we delete them all, by 31 December 2026 at the latest. Legal basis: the consent you gave when you joined (GDPR Art. 6(1)(a)). To be removed sooner, write to hello+privacy@gitring.tech and we delete your records within 30 days.
This service. This service has no waitlist. People start with GitHub in the app.
6. How long we keep data
| Data | How long |
|---|---|
| Account and tokens | While your account is open. Deleted when you delete your account, with the tags of the link you signed up by and when your agents first connected. |
| Your content | While the project exists. When a project is deleted, its repository and its records are erased at once, and its backup copy is deleted at once too, apart from the copy our storage provider keeps for 7 days to recover from mistakes. A record that the project was deleted, and its usage counts, stay. A copy mirrored to a GitHub repository you linked is yours on GitHub, and stays there. |
| Backups | The database's backups and the repositories' recovery copies expire within 7 days. Deleted data stays in them for that time. |
| Technical logs | 30 days. |
| Command-line sign-in requests | A code lasts 10 minutes. It is deleted, with the network address and program that asked for it, a day after it expires, whether you approved it or not. |
| A sign-in waiting for your choice | When the address of a new GitHub or Google sign-in is the address of a gitring account that signs in the other way, gitring asks before it makes a second account. While you choose, it keeps what GitHub or Google said about that sign-in (and GitHub's token, encrypted) for 10 minutes, and deletes it within minutes after that, or at once when you choose. |
| Agent connection requests | Deleted an hour after they expire. A program you connect by its address keeps the network address it registered from for an hour; the program's record stays while an approval names it, and one nobody approved is deleted after a day. |
| Invitations | Until the project is deleted. One not yet accepted is deleted when the invited person deletes their gitring account. |
| Model inputs | We store the result of each check with its intent, as part of your content. Microsoft keeps inputs only as section 3 says. |
| Billing records | As long as tax law requires. |
| Settings kept in your browser | Until you clear your browser's storage for app.gitring.tech; the invitation link, until you close the tab. |
| Waitlist of the first version | See section 5. |
| Emails gitring sends you | The message waits until it is sent, or is dropped when it is no longer true (a decision already made, a trial already over, a project deleted, a getting-started step already done) or no longer timely (a reminder or a welcome after a day, a getting-started email two days after it was due, a notice after 7 days). A record that it was sent, skipped or failed is deleted 30 days later. Your address is never stored with it. When our email provider reports that mail to your address bounced, that mark is kept 30 days, until you sign in with another address, or until you delete your account, whichever is first. |
7. Your rights
Everyone. You can see and delete most of your data yourself in the app (Account settings and project settings). Your code is yours to copy at any time with git clone, and your records can be read through gitring's API; there is no export button. For a copy of your other data, write to us. Your name, email address and picture come from GitHub: to correct them, change them on GitHub and sign in again. To delete your account, use Settings, Delete your account: your sign-ins and tokens end, and your name, login, email address, avatar and GitHub link are removed. Projects only you are in are deleted with it. In projects other people use, the work you did stays and shows "deleted account": intents, plans, change requests, lines and tags, including projects you had left before. You delete your account from the web app, signed in with GitHub in the last 10 minutes, so that nobody who only has your laptop or a token can do it for you.
What stays after you delete your account, and why:
- Decisions and events. The record of each decision you made in a project that goes on (approved, sent back, settled) keeps the name you had when you made it. These records cannot be changed, by design, because the project's people rely on who decided what.
- Commits. The project's git history keeps the author names in its commits, including the merge commits gitring made for your intents, and any copy mirrored to GitHub keeps them too. Git history cannot be changed without rewriting the project, which is its people's to decide.
- A keyed fingerprint of your GitHub or Google account. We keep a one-way keyed hash of your GitHub account's number or Google's id for you, not the number or id itself, so that signing up again with the same GitHub account does not start a second free trial. It cannot be turned back into your account.
- Billing records, as section 6 says.
For anything else, write to hello+privacy@gitring.tech. We answer within 30 days.
Under the GDPR (EU and UK). You have the right to access, correct, erase, restrict, port and object to the processing of your personal data, and to withdraw consent at any time. You can complain to the data protection authority where you live.
Under India's DPDP Act 2023. As a Data Principal you have the right to a summary of your personal data and how it is processed; to correct, complete, update and erase it; to have a grievance answered; and to nominate someone to act for you if you die or cannot act. Write to our Grievance Officer first, at hello+grievance@gitring.tech. If you are not satisfied, you may complain to the Data Protection Board of India. Where we rely on your consent, you can withdraw it as easily as you gave it.
8. International transfers
We store data in Singapore, with backup copies in Hong Kong, and our emails are processed in Microsoft's Asia Pacific geography. GitHub, Google and Microsoft Clarity are in the United States (section 4), and Microsoft may process a model request in another region (section 3). If you are in the EU, the UK, India or the United States, your data is transferred to these places. For EU and UK data we rely on the Standard Contractual Clauses in our providers' data protection terms.
9. Security
In short: encryption in transit and at rest; GitHub tokens encrypted with AES-GCM; no passwords; API keys, agent tokens and session cookies stored only as hashes; secrets kept in Azure Key Vault; access to production limited to the people who run it. If a breach affects you, we will tell you and the authorities as the law requires.
10. Children
gitring is not for anyone under 18. We do not knowingly collect data from children. If you think a child has signed up, tell us and we will delete the account.
11. Changes
We will post changes here and change the date at the top. If a change matters, we will post it here and email account holders at least 30 days before it applies.