Privacy Policy

gitby stores the coordination data it needs to work: who holds which file, notes, team membership and activity. It does not store your source code. Two features handle code briefly on its way to or from GitHub, described below.

Your account details (name, username, email address and a hashed password, or the GitHub identity you sign in with); your teams, memberships and invites; the repositories your team connects, identified by name; claims, access requests and notes on repository file paths; team chat, and the support messages and ratings you write; a history of coordination activity (claims, releases, handoffs and pushes) used for your team's statistics; and activity measurements your terminal reports while you work, stored per person: seconds active in each hour, per-file counters of lines and time for each day, and a daily total. For paid teams we keep a copy of the billing details Stripe returns, such as the plan, invoices and each saved card's brand, last four digits, expiry and cardholder name. Card numbers never reach us.

We do not keep your source code. When you push through gitby, your commits are sent to our push service, which forwards them to GitHub with your team's access and discards its temporary copy when the push finishes. A temporary copy left behind by a crash is removed when the push service next starts, or by a later push once it is 15 minutes old. Our coordination and audit records keep only file paths and commit ids. When you open a file's changes in the dashboard, the diff is fetched from GitHub and passed to your browser without being saved.

When you connect a terminal we record a keyed digest of the IP address involved, not the address itself, to tell you whether the terminal and your browser are on the same network. Your browser keeps your sign-in session, display preferences and cached copies of dashboard data in its local storage on your device; signing out clears the session.

Claims and requests last until they are released or resolved. Coordination history is kept for the statistics period your team's plan includes and then deleted; when a plan change shortens that period, history older than the new period is kept for 30 more days and then deleted. Hourly activity measurements are kept for 90 days. Per-file counters are kept for the statistics period of the teams using that repository, or 7 days once no team uses it, and daily totals for the longest statistics period any plan offers. Operational audit records of the service (for example, pushes through gitby) are kept for 180 days. Billing records are kept as long as the law requires. Other data is kept while your account or team exists. Database backups keep a copy of this data, including the data of deleted accounts, until each backup expires: our current targets are 7 days for point-in-time recovery, 30 days for daily snapshots and 12 months for monthly snapshots.

When we switch it on, an AI assistant answers support conversations first, and every answer it writes is labelled as AI. To answer, it sends the conversation's subject and messages (not your account details, and not our staff's internal notes) through OpenRouter to an AI model provider, and asks OpenRouter to use only providers that do not keep prompts or train on them. You can ask for a person at any time, and the assistant stops for good once someone on the team replies. Its answers are kept with the conversation like any other support message. While it is on, someone on our support team can also ask it about the conversations assigned to them; it then sends those conversations the same way, and nothing of that exchange is kept.

We use GitHub for sign-in and repository access, Stripe for payments, an email provider to send account email, hosting providers to run the service, and, while the support assistant is on, OpenRouter and the AI model provider it routes to. Each processes data under its own terms. We don't sell your data.

You can delete your account from your settings. That erases your account and sign-in details, your terminal sign-ins, your support conversations, your activity measurements and your registration on our coordination servers, and asks GitHub to revoke the access you granted. Teams you are the only member of are deleted with it. Claims you still hold and your pending requests are released through each repository's coordination server, including one that is offline if it comes back online within 90 days. On current coordination servers, notes and team chat messages you posted stay visible to your team under a neutral "former member" label instead of your name. Some records remain: the text of those notes and messages, coordination history until it ages out as described above, backups until they expire, billing records, and our staff audit log. To request a copy of your data, or deletion of anything that remains, email us.

Privacy questions or requests? Email contact@gitby.app.