Security and data
Who can see your files, what leaves your drive, and how to check each claim on this page.
The short answers
| Question | Answer |
|---|---|
| Who can see a file? | In your My Drive, only you. In a shared drive, the people you give it to, plus your team's owners and admins. |
| Are my files used to train models? | No, never. |
| What does a search send to a model? | The question, and the passages the search reads. |
| Can I delete my files? | Yes. Deleting a file removes it, its revisions and its searchable text. |
| Is ByteRover audited? | Yes. ByteRover is SOC 2 Type II audited. |
Who can reach your files
Access is set per drive, and every search, read and write goes through an access check.
| Caller | Reaches |
|---|---|
| A team owner or admin | Their own My Drive and every shared drive. Never someone else's My Drive. |
| A member | Their own My Drive, and only the shared drives they're given, as a Viewer, Editor or Admin. |
| An agent | Whatever its person can reach. ByteRover checks the person's access on every call. |
| An API key | Every shared drive of the team, including ones made later, or only the shared drives chosen for the key, within its scope. Never a My Drive. A new key starts at All shared drives and the scope Search. |
A caller without access to a drive can't tell whether a document ID exists. For the full permissions, see Roles.
The app shows each connected agent and API key with the time it was last used, and you can revoke it immediately:
- API keys are listed under Team > API keys, which only team owners and admins can open.
- Agents are listed under AI tools, and each person sees only the agents they connected. Only that person can revoke one. To cut off someone else's agents, a team owner or admin removes that person from the team.
Sign-in
- People sign in with GitHub, Google or a link sent to their email. ByteRover doesn't store passwords.
- A sign-in link works once and expires after 15 minutes.
- Under Account > Sessions, a person can see every device they're signed in on and sign out the others.
- An agent signs in through your browser, and you approve it by name.
- An API key is shown only once. ByteRover keeps only a hash of it.
What a search sends out
Searches run on your files inside ByteRover. To do its work, a search sends ByteRover's model providers the question and the passages it reads. Whole files aren't sent, and nothing that's sent is used to train a model.
What ByteRover keeps about searches
Each search and answer is recorded with its drives, its source, its cost and how long it took. The text of the question is kept only when the search found nothing or the answer was "not found". The Usage page shows those questions to everyone who can use the drives searched, so a team can see which files are missing. A question is cleared after 90 days; the counts stay.
Encryption
| Data | Protection |
|---|---|
| In transit | TLS 1.2 or higher |
| At rest | AES-256 |
What a delete removes
| You delete | What is removed |
|---|---|
| A file | The original file, every revision and its searchable text. The file no longer appears in search results. |
| A drive | Every file in the drive and its access list. The drive is also removed from every API key that could reach it. |
| A team | Only an owner can delete a team, after typing its name. The team goes with its drives, members and API keys, and anything using those keys stops working. Each drive's files and search index are then removed, as when a drive is deleted. |
| Your account | You leave every team. The API keys you created stop working and your agents are disconnected. Files you added stay in their drives. If you're the only owner of a team, make someone else an owner or delete the team first. |
Deletes can't be undone.
Monitoring and tests
ByteRover is monitored around the clock. Independent testers examine it, and ByteRover fixes what they find.
Audit
ByteRover is SOC 2 Type II audited, which means an independent auditor examined its controls over a period of time rather than at a single point.
The trust center has the audit report, available on request, and the list of providers that process data for ByteRover.
Sensitive data
ByteRover is meant for work documents such as policies, contracts, specifications and runbooks.
Do not upload patient data.
Report a vulnerability
Email security@byterover.dev. We confirm each report within 5 working days.
For a security review
If your company reviews vendors before buying, the trust center has the documents for that review. For a questionnaire or your own terms, talk to us about Enterprise. See Pricing and billing.