Privacy
Last updated 13 October 2026
RepoChat is run by Dashovia Innovations. This page says what the service stores, why, and how to have it removed. The short version: we store what you choose to share in a chat so your collaborators can read it, and very little else.
What we store
| What | Why |
|---|---|
| Your GitHub user id, username and avatar address | To show who wrote each message and who is online. |
| The messages you send, and the files, images, code snippets and pull request links you share | So the repository's collaborators can read them, now and later. |
| How far you have read in each chat | For read receipts. |
| Which repository chats you have connected to, and when you first and last did | To count seats for the repository's plan. |
| Reports: who reported which message, and why | So reported content can be reviewed. |
| For paid plans: the plan, number of seats and subscription status | To apply the plan to the repository. |
What we don't store or do
- Your GitHub token. The extension sends it to our server to ask GitHub whether you can push to the repository. It is used for that check and then discarded.
- Your repository. RepoChat does not read or upload your code. Only a selection you explicitly send to the chat leaves your editor.
- Your email address or card details. We don't collect them. Payments are taken by Polar, which holds the billing details.
- Tracking. The extension has no analytics and no advertising, and we don't sell or share your data for marketing.
- Scanning. Messages and files are not scanned or read automatically. A person at Dashovia Innovations sees a message only if someone reports it, or if the law requires us to look.
Why the extension asks for GitHub's "repo" permission
GitHub only answers "can this person push to this private repository?" for a token with that permission. The extension also uses it, directly between your editor and GitHub, to list and show pull requests. RepoChat never writes to your repositories.
Who can see your content
- People with push access to the same repository, for as long as they have it.
- That repository's admins and maintainers, who can also delete messages.
- Us, for a specific message and its files, when that message has been reported.
Where it is kept, and for how long
Content is stored with Cloudflare, our hosting provider. It stays until its author or a moderator deletes it, or until you ask us to remove it. On the Free plan, messages older than 30 days are hidden but not deleted, so they return if the repository upgrades. Deleting a message also deletes its files.
Companies involved
- Cloudflare hosts the service and stores the content. Like any host, it processes connection details such as IP addresses to deliver and protect the service.
- GitHub confirms who you are and what you can access.
- Polar takes payment for paid plans and holds the billing details.
Your choices
- Edit or delete your own messages at any time from the chat.
- To get a copy of what we hold about you, or to have your messages and records removed, write to contact@dashovia.app from an address we can connect to your GitHub account. We will act on it within 30 days.
- Uninstalling the extension stops all further collection.
Children
RepoChat is not meant for anyone under 13, the minimum age for a GitHub account.
Changes
If this policy changes in a way that matters, we will say so here and update the date above.
Contact
Dashovia Innovations · contact@dashovia.app