The policies describe g1t as it is: it runs no agents of its own. The Terms of Service no longer promise g1t agents that write code, review and land changes when an issue is assigned, nor bill agents as compute; section 6 now covers the coding agents you connect (acting with your credentials, your token's scopes and the workspace's rules) and Ask g1t, which answers with your workspace's own AI provider under your agreement with it. The Privacy Policy's sessions are the ones your connected agents record, the conversation with @g1t is said to be kept, and an AI provider is among the services you connect. Subprocessors' sandboxes run checks, workflows and builds, and your workspace's AI provider is listed among the integrations you choose. Refunds no longer list agents among what costs money. The policies' history has the change, dated 2026-10-13. Checked: the site's typecheck, its tests and a production build.
5 files+24−210/5 viewed
| 1 | − | This policy explains what information g1t collects, why, where it goes, how long we keep it, and what you can do about it. It covers g1t.sh, api.g1t.sh, mcp.g1t.sh, docs.g1t.sh, g1t.page and the agents and sandboxes g1t runs. g1t is run by Flagon, Inc. ("Flagon", "we"), which is responsible for your information. | |
| 1 | + | This policy explains what information g1t collects, why, where it goes, how long we keep it, and what you can do about it. It covers g1t.sh, api.g1t.sh, mcp.g1t.sh, docs.g1t.sh, g1t.page and the sandboxes g1t runs. g1t is run by Flagon, Inc. ("Flagon", "we"), which is responsible for your information. | |
| 2 | 2 | ||
| 3 | 3 | The short version: we collect what we need to run a git platform for you and your agents, we don't sell it, we don't advertise, we don't use your private content to train AI models, and the only analytics on g1t.sh counts how pages are used without reading what is in your workspaces. | |
| 4 | 4 | ||
| ⋯ | |||
| 25 | 25 | ||
| 26 | 26 | ### What agents do | |
| 27 | 27 | ||
| 28 | − | When an agent runs, we keep a **session**: what it was asked, the steps it took, the tools it called, what it wrote, which model it used, what it cost, and how the run ended. Run credentials and model keys are removed from what is recorded. A session is as visible as its project: **on a public project, anyone can read it**. Workflow and check logs are kept the same way. | |
| 28 | + | When a coding agent you connect records its work on g1t, we keep a **session**: what it was asked, the steps and tools it reports, what it wrote, which model it says it used, and how it ended. Credentials are removed from what is recorded. When you ask g1t a question, the conversation is kept with your direct message with @g1t. A session is as visible as its project: **on a public project, anyone can read it**. Workflow and check logs are kept the same way. | |
| 29 | 29 | ||
| 30 | 30 | To catch cryptocurrency mining, every sandbox samples its own CPU use, disk and network activity, and the command lines of the processes it runs. These measurements are used only for abuse detection. | |
| 31 | 31 | ||
| ⋯ | |||
| 84 | 84 | ||
| 85 | 85 | We use your information to: | |
| 86 | 86 | ||
| 87 | − | - run g1t: sign you in, store and show your content to the people allowed to see it, run the agents, checks and deployments you ask for; | |
| 87 | + | - run g1t: sign you in, store and show your content to the people allowed to see it, run the checks, workflows and deployments you ask for; | |
| 88 | 88 | - keep g1t secure and fair: detect abuse, mining and fraud, enforce limits, and investigate problems; | |
| 89 | 89 | - bill workspaces and keep the records the law requires; | |
| 90 | 90 | - send you the email g1t needs to: confirming your address, resetting your password, billing alerts and receipts, answers to requests you made, and important changes to g1t or these policies. **We don't send marketing email**; | |
| ⋯ | |||
| 100 | 100 | We share information only to run g1t, at your direction, or when the law requires it. | |
| 101 | 101 | ||
| 102 | 102 | - **Service providers ("subprocessors")** that run parts of g1t for us, under contracts that limit them to doing so: Cloudflare (hosting, storage, databases, sandboxes, email and search), Stripe (payments) and HeyCatch (site analytics). The [subprocessors](/policies/subprocessors) page lists them and what each receives. | |
| 103 | − | - **Services you connect.** When you connect an issue tracker, error tracking or a webhook, or let your sandboxes reach a host, we send them what that connection needs, because you asked us to. | |
| 103 | + | - **Services you connect.** When you connect an AI provider, an issue tracker, error tracking or a webhook, or let your sandboxes reach a host, we send them what that connection needs, because you asked us to. | |
| 104 | 104 | - **Other people on g1t**, as your settings allow: your workspace's members, and everyone for public projects and your public profile. | |
| 105 | 105 | - **Vulnerability databases.** To find vulnerable dependencies, we send the names and versions of packages in your lockfiles to OSV.dev, an open database run by Google. Nothing else about you or your repository is sent. | |
| 106 | 106 | - **The law.** We disclose information when we must by law, such as a valid court order, and when we need to protect the rights, property or safety of our users, the public or Flagon. Where we can, we tell you first. | |
| 2 | 2 | ||
| 3 | 3 | ## What is charged, and why | |
| 4 | 4 | ||
| 5 | − | The forge is free. What costs money is compute (agents, sandboxes, checks, workflows, the merge queue, deployments, and storage and git traffic past what is included) at what it costs us plus 20%, and the g1t plan, $20 a month per workspace with $10 of usage included. Because usage is charged at close to what it costs us, most of it can't be given back once it has run: we've already paid for it. | |
| 5 | + | The forge is free. What costs money is compute (sandboxes, checks, workflows, the merge queue, deployments, and storage and git traffic past what is included) at what it costs us plus 20%, and the g1t plan, $20 a month per workspace with $10 of usage included. Because usage is charged at close to what it costs us, most of it can't be given back once it has run: we've already paid for it. | |
| 6 | 6 | ||
| 7 | 7 | That's why g1t works hard to keep spending from surprising you: a $5 trial that never turns into a charge, a spend limit you set, caps per run and per issue, alerts at 50%, 75%, 90% and 100%, and a pause when spending suddenly spikes until an owner says to keep going. | |
| 8 | 8 | ||
| 9 | 9 | ## Spent more than you meant to | |
| 10 | 10 | ||
| 11 | − | If a month went well past what you meant to spend (a runaway job, an agent that kept going, a loop you didn't notice), tell us. On the workspace's **Billing** page, an owner chooses **Spent more than you meant to? Tell us.**, says what happened, and sends it. | |
| 11 | + | If a month went well past what you meant to spend (a runaway job, a workflow that kept going, a loop you didn't notice), tell us. On the workspace's **Billing** page, an owner chooses **Spent more than you meant to? Tell us.**, says what happened, and sends it. | |
| 12 | 12 | ||
| 13 | 13 | - **Once every 12 months per workspace**, g1t can credit the overage above your usual month. | |
| 14 | 14 | - **The 20% we added to that overage always comes back to you.** We don't keep a margin on a mistake. |
| 4 | 4 | ||
| 5 | 5 | | Company | What they do for g1t | What they receive | Where | | |
| 6 | 6 | | --- | --- | --- | --- | | |
| 7 | − | | **Cloudflare, Inc.** | Hosting and the network g1t runs on (Workers), databases (D1), storage for repositories, avatars and screenshots (Artifacts, KV and R2), queues, the sandboxes agents and checks run in (Containers), sending email (Email Service), search embeddings (Workers AI and Vectorize), and screenshots of deployed apps (Browser Rendering) | Everything stored on g1t, and every request to it | Global | | |
| 7 | + | | **Cloudflare, Inc.** | Hosting and the network g1t runs on (Workers), databases (D1), storage for repositories, avatars and screenshots (Artifacts, KV and R2), queues, the sandboxes checks, workflows and builds run in (Containers), sending email (Email Service), search embeddings (Workers AI and Vectorize), and screenshots of deployed apps (Browser Rendering) | Everything stored on g1t, and every request to it | Global | | |
| 8 | 8 | | **Stripe, Inc.** | Payments, cards, invoices and receipts | Workspace owners' billing details, card details (entered on Stripe's page, never on g1t), and what each invoice charges | United States | | |
| 9 | 9 | | **HeyCatch, Inc.** | Product analytics on g1t.sh: page views and clicks. Visitors in the EU, EEA, UK and Switzerland are asked first | The page's address (names replaced outside the public pages), the text of what is clicked on the public pages, browser and device type, IP address, the referring site, an analytics id, and a signed-in person's internal account id. Never repository content, chat, page titles inside the app, what you type, or recordings of your session | United States | | |
| 10 | 10 | ||
| ⋯ | |||
| 18 | 18 | ||
| 19 | 19 | When you connect these, your information goes to them because you asked, under your own agreement with them. They are not g1t's subprocessors: | |
| 20 | 20 | ||
| 21 | − | - **Integrations**, such as GitHub, Linear, Jira, Sentry and Datadog. | |
| 21 | + | - **Integrations**, such as your workspace's AI provider, GitHub, Linear, Jira, Sentry and Datadog. | |
| 22 | 22 | - **Webhooks** you add, which send events to the addresses you choose. | |
| 23 | 23 | - **Hosts your sandboxes reach**, such as package registries and anything your jobs and builds fetch from or send to. | |
| 24 | 24 | - **Custom domains** you point at your deployments. | |
| 1 | − | These terms are the agreement between you and Flagon, Inc. ("Flagon", "we", "us") when you use g1t: the website at g1t.sh, its API at api.g1t.sh, its MCP server at mcp.g1t.sh, git over g1t.sh, the documentation, apps deployed to g1t.page, and the agents and sandboxes g1t runs for you (together, "g1t" or "the service"). | |
| 1 | + | These terms are the agreement between you and Flagon, Inc. ("Flagon", "we", "us") when you use g1t: the website at g1t.sh, its API at api.g1t.sh, its MCP server at mcp.g1t.sh, git over g1t.sh, the documentation, apps deployed to g1t.page, and the sandboxes g1t runs for you (together, "g1t" or "the service"). | |
| 2 | 2 | ||
| 3 | 3 | We've tried to write them the way we'd want to read them: plainly. If anything here is unclear, write to [hey@flagon.io](mailto:hey@flagon.io) and we'll explain it. | |
| 4 | 4 | ||
| ⋯ | |||
| 10 | 10 | ||
| 11 | 11 | - **You need an account to do most things.** Give us a real email address and keep it current: it's how we reach you about your account, security and billing, and how you get back in if you lose your password. | |
| 12 | 12 | - **You must be at least 13 years old**, and old enough where you live to agree to these terms yourself. If you're under 18, a parent or guardian must agree to them for you. | |
| 13 | − | - **An account is for one person.** Automation is welcome: use access tokens, workspace tokens and agents for it. Don't share a password, and don't create accounts to get around a limit, a trial, or a suspension. | |
| 13 | + | - **An account is for one person.** Automation is welcome: use access tokens, workspace tokens and coding agents for it. Don't share a password, and don't create accounts to get around a limit, a trial, or a suspension. | |
| 14 | 14 | - **Keep your credentials safe.** You're responsible for what happens under your account, your tokens and your SSH keys. If you think someone else has them, revoke them in your settings and tell us at [hey@flagon.io](mailto:hey@flagon.io). | |
| 15 | 15 | ||
| 16 | 16 | ## 2. Workspaces | |
| 17 | 17 | ||
| 18 | − | Everything on g1t lives in a workspace: its projects, repositories, issues, pull requests, agents, settings and bill. A workspace's **owners** control it. They decide who is a member, what members and agents may do, and they're responsible for paying for it. If you create a workspace for an organization, the organization is the customer, and its owners act for it. | |
| 18 | + | Everything on g1t lives in a workspace: its projects, repositories, issues, pull requests, settings and bill. A workspace's **owners** control it. They decide who is a member, what members and agents may do, and they're responsible for paying for it. If you create a workspace for an organization, the organization is the customer, and its owners act for it. | |
| 19 | 19 | ||
| 20 | 20 | ## 3. Acceptable use | |
| 21 | 21 | ||
| ⋯ | |||
| 28 | 28 | To run g1t, we need your permission to handle your content. You give Flagon a worldwide, non-exclusive, royalty-free license to host, store, copy, process, transmit and display your content **only as needed to provide, secure and improve the service for you**. That includes, for example: | |
| 29 | 29 | ||
| 30 | 30 | - storing your repositories and showing them to the people you let see them; | |
| 31 | − | - sending the relevant parts to a model provider when you ask an agent to work (see section 6); | |
| 31 | + | - sending the relevant parts to your workspace's AI provider when you ask g1t a question (see section 6); | |
| 32 | 32 | - indexing it so you can search it; | |
| 33 | 33 | - scanning it for secrets and vulnerable dependencies, so we can warn you; | |
| 34 | 34 | - making backups. | |
| 35 | 35 | ||
| 36 | 36 | This license ends when your content is deleted from g1t, except for copies in backups (which expire on their own schedule) and content others have a right to keep under section 5. | |
| 37 | 37 | ||
| 38 | − | **We don't sell your content, and we don't use your private content to train AI models.** We don't let the model providers we use for hosted agents train on it either. | |
| 38 | + | **We don't sell your content, and we don't use your private content to train AI models.** g1t itself doesn't send your content to any model provider: Ask g1t uses the AI provider your workspace connects, under your agreement with them. | |
| 39 | 39 | ||
| 40 | 40 | You're responsible for your content: that you have the right to put it on g1t, and that it doesn't break the law or someone else's rights. | |
| 41 | 41 | ||
| ⋯ | |||
| 49 | 49 | ||
| 50 | 50 | ## 6. Agents act on your behalf | |
| 51 | 51 | ||
| 52 | − | g1t's agents ("g1t agents") write code, review changes, answer questions, plan work and land changes, when you or another member of your workspace asks them to: by assigning an issue, mentioning an agent, starting a plan, or turning on something that runs on its own, such as upkeep or automatic merges. | |
| 52 | + | The coding agents you connect to g1t (through the MCP server, the API, the g1t CLI or a plugin) work with your access: they read and change what you let them, and open issues and pull requests, record their sessions and claim work as you. | |
| 53 | 53 | ||
| 54 | − | - **An agent acts on behalf of the person who started its work**, within the limits of that person's access and the workspace's guardrails. Its actions are recorded as such in the audit log. | |
| 54 | + | - **An agent acts on behalf of the person whose credentials it uses**, within the limits of that person's access, the token's scopes and the workspace's rules. Its actions are recorded as such in the audit log. | |
| 55 | 55 | - **You're responsible for what you ask agents to do**, and for checking what they produce before you rely on it, merge it or deploy it, as you would for a teammate's work. Agents make mistakes. Their output can be wrong, insecure, or similar to code that exists elsewhere, and you're responsible for making sure your use of it complies with the licenses and laws that apply. | |
| 56 | − | - **Guardrails** (time caps on runs) reduce risk. They're a safety net, not a guarantee that an agent won't do something you didn't intend. | |
| 57 | 56 | - **What agents produce for you is your content.** As between you and us, Flagon claims no rights in it. | |
| 58 | − | - **Agents cost money.** Runs, sandbox time and model use are charged to the workspace that owns the repository, as described on [pricing](/pricing). | |
| 59 | 57 | ||
| 60 | − | To run hosted agents, we send the relevant content (such as the issue, the code it needs and the conversation so far) to a model provider. The [subprocessors](/policies/subprocessors) page lists who. If your workspace connects its own model provider, your content goes to that provider instead, under your agreement with them. | |
| 58 | + | **Ask g1t** answers questions about your workspace with the AI provider your workspace connects. To answer, we send that provider the question and the content it needs (such as the issue, pull request or files it reads), under your agreement with them. Its answers can be wrong too. | |
| 61 | 59 | ||
| 62 | 60 | ## 7. Services you connect | |
| 63 | 61 | ||
| ⋯ | |||
| 66 | 64 | ## 8. Paying for g1t | |
| 67 | 65 | ||
| 68 | 66 | - **The forge is free.** Repositories, git, issues, pull requests and review cost nothing, within the free limits described on [pricing](/pricing). | |
| 69 | − | - **Compute is paid.** Agents, sandboxes, checks, workflows, the merge queue, deployments and the other metered items on [pricing](/pricing) are charged to the workspace, at what they cost us plus the markup shown there. **The g1t plan** is a monthly subscription per workspace, with some usage included. | |
| 67 | + | - **Compute is paid.** Sandboxes, checks, workflows, the merge queue, deployments and the other metered items on [pricing](/pricing) are charged to the workspace, at what they cost us plus the markup shown there. **The g1t plan** is a monthly subscription per workspace, with some usage included. | |
| 70 | 68 | - **Usage prices follow our costs.** They move when what we pay our providers moves, and every change is listed on the pricing page with its reason. We'll give owners at least 30 days' notice by email before we raise the plan's own monthly price. | |
| 71 | 69 | - **Payment.** Payments are processed by Stripe. You authorize us to charge the workspace's card, or another payment method on file, for the plan, for usage as it is billed, and when the workspace nears its limit. Invoices are available from the Billing page. Card numbers never reach g1t. | |
| 72 | 70 | - **Taxes.** Prices don't include taxes unless we say so. You're responsible for the taxes that apply to your purchases, other than taxes on our income. | |
| ⋯ | |||
| 106 | 104 | ||
| 107 | 105 | ## 12. Disclaimers | |
| 108 | 106 | ||
| 109 | − | We work hard to make g1t reliable, but **g1t is provided "as is" and "as available."** To the extent the law allows, Flagon disclaims all warranties, express or implied, including merchantability, fitness for a particular purpose, title and non-infringement. We don't promise that g1t will be uninterrupted or error-free, that agents' output will be correct or fit for your purpose, or that content will never be lost. Keep your own copies of what matters to you: git makes this easy. | |
| 107 | + | We work hard to make g1t reliable, but **g1t is provided "as is" and "as available."** To the extent the law allows, Flagon disclaims all warranties, express or implied, including merchantability, fitness for a particular purpose, title and non-infringement. We don't promise that g1t will be uninterrupted or error-free, that answers or agents' output will be correct or fit for your purpose, or that content will never be lost. Keep your own copies of what matters to you: git makes this easy. | |
| 110 | 108 | ||
| 111 | 109 | ## 13. Limitation of liability | |
| 112 | 110 | ||
| 97 | 97 | export const POLICIES_DRAFT = true; | |
| 98 | 98 | ||
| 99 | 99 | /** When any policy last changed, `YYYY-MM-DD`. */ | |
| 100 | − | export const POLICIES_UPDATED = "2026-10-09"; | |
| 100 | + | export const POLICIES_UPDATED = "2026-10-13"; | |
| 101 | 101 | ||
| 102 | 102 | /** Every change to the policies, newest first. */ | |
| 103 | 103 | export const POLICY_HISTORY: { date: string; change: string }[] = [ | |
| 104 | 104 | { | |
| 105 | + | date: "2026-10-13", | |
| 106 | + | change: | |
| 107 | + | "Terms of Service and Privacy Policy: g1t no longer runs agents of its own. Section 6 of the terms covers the coding agents you connect and Ask g1t, which answers with your workspace's own AI provider; agents are no longer billed compute. Subprocessors: your workspace's AI provider listed among the integrations you choose.", | |
| 108 | + | }, | |
| 109 | + | { | |
| 105 | 110 | date: "2026-10-09", | |
| 106 | 111 | change: | |
| 107 | 112 | "Privacy Policy: g1t.sh uses HeyCatch for site analytics, with names removed outside the public pages, and one analytics cookie, set in the EU, EEA, UK and Switzerland only after you allow it. Subprocessors: HeyCatch, Inc. added.", |
Comments
Sign in to comment.