RepoChat

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

WhatWhy
Your GitHub user id, username and avatar addressTo show who wrote each message and who is online.
The messages you send, and the files, images, code snippets and pull request links you shareSo the repository's collaborators can read them, now and later.
How far you have read in each chatFor read receipts.
Which repository chats you have connected to, and when you first and last didTo count seats for the repository's plan.
Reports: who reported which message, and whySo reported content can be reviewed.
For paid plans: the plan, number of seats and subscription statusTo apply the plan to the repository.

What we don't store or do

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

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

Your choices

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