Türkçe tAI

GitHub Integration Privacy Policy

Last updated: August 26, 2026

1. What this policy covers

This page explains, in detail, how tAI (an Artfical product) accesses and handles your GitHub repositories if you choose to connect your account. It supplements our general Privacy Policy, which covers every other kind of data tAI collects. If anything here conflicts with the general policy, this page governs for the GitHub integration specifically.

2. How you connect it

From Settings > Connectors, you can optionally connect your GitHub account through GitHub's own OAuth sign-in flow. Nothing about your repositories is accessed until you complete that flow and explicitly grant tAI the permission below.

3. What permission we request, and why

The connection requests GitHub's repo scope — the minimum scope GitHub offers that covers reading and modifying both public and private repositories. GitHub does not offer a narrower scope for private repo access, which is why we request this one. We do not request access to your account's user profile (beyond username and avatar) or email address.

4. When and how we access your repositories

GitHub access starts only after you explicitly pick a repo in the composer. The moment you pick a repo, you're shown a warning that tAI is an AI that can make mistakes and that generated code shouldn't be used in production without review. Once you send your first message in that chat, the selected repo's default branch is downloaded into that chat's own workspace in your account (skipping large/binary files and directories like node_modules/.git, capped at 200 files) so the AI can work on it with normal file tools. This download happens once, at selection time -- your repo is never scanned or synced again afterward, and no repo other than the one you picked is ever touched.

5. How we make changes

• The AI reads and edits files on the downloaded copy -- these stay in that chat's workspace and never affect the real repo on GitHub on their own.
• When it's ready to push changes to GitHub (on its own initiative, or when you click the composer's "Commit" button), it first automatically creates a new branch off the selected repo's default branch (e.g. tai/a1b2c3d4) — it never commits directly to the default branch.
• Every subsequent push in that chat is committed to that same branch. Every commit message automatically gets a "Co-authored-by: tAI <[email protected]>" trailer appended — this is enforced server-side, not something the model could forget.
• When it's done, the AI opens a pull request. No change reaches your repo's default branch until you review and merge that PR yourself.

6. What we do with the data

Content returned from GitHub (file contents, directory listings, commit and PR details) is used only to generate the AI's reply to your specific request in that chat.

• We do not use your GitHub data for advertising.
• We do not sell your GitHub data.
• We do not use your GitHub data to train AI/ML models.
• No human at Artfical reads your repo content, except with your explicit consent, to comply with a security or legal obligation, or as part of support you've personally requested.

7. How long we keep it

Files downloaded from your repo are stored in that chat's own workspace (the same place other file uploads/creations for that chat live) -- separate from the message text itself, but tied to that same chat. It is kept for as long as that chat exists, and is permanently deleted when you delete the chat or your account, following the same retention rules as the rest of your chat data. Your GitHub access token is permanently deleted from our database when you disconnect or delete your account.

8. Revoking access

You can disconnect GitHub at any time, in either of these ways:

• In tAI, from Settings > Connectors > "Disconnect."
• Directly from GitHub, under your account's Settings > Applications > Authorized OAuth Apps.

Disconnecting stops all future access immediately. Any branches or pull requests tAI already opened remain on GitHub as-is — you can delete or close them the same way you would any branch or PR you opened yourself, directly on GitHub. Disconnecting does not retroactively delete GitHub content already saved in your existing chat history — you can remove that the same way you'd remove any other chat, by deleting it.

9. Changes to this policy

We may update this policy from time to time. For significant changes, we'll update the "last updated" date on this page.

10. Contact us

For questions about the GitHub integration or your data, you can reach out to the Artfical team.

← Back to tAI