> ## Documentation Index
> Fetch the complete documentation index at: https://docs.overseer-bot.net/llms.txt
> Use this file to discover all available pages before exploring further.

# Privacy Policy

> Effective Date: Aug 13, 2022

## **Introduction**

This policy explains what information we collect when you use Overseer's Discord instance.

### Terminology

Below you will find a list of terms that one may consider technical, to prevent confusion, these words will be capitalised:

* User: A Discord user.
* Guild: A Discord server.
* Snowflake: A Discord ID that can be obtained through enabling developer mode and clicking `Copy ID` in a context menu.
* Command: A string, or registered app command that functions as a way to have Overseer 'do something'. A non-exhaustive list can be found [here](https://overseer.tech/commands).

## Data Collected

Overseer only collects data when you give it to us, or give us permission to obtain it. Data categories include:

1. Guild, role, user and channel snowflakes during **configuration**
2. A copy of any evidence attached by a suitable user when attached through the `ban` or `punish` command, the formats of these include but are not limited to:
   * image/png
   * image/jpeg
   * video/mp4
   * video/x-matroska
3. Command invocation data, such as the contents of the command, when it was used, by whom, etc.

## Data Use

Data collected by Overseer is **only** accessible to authorised users on the development team, with the exception of evidence mentioned above, which is stored by a 3rd party - Backblaze. We use this information to:

* Know where, when and how to send things. For example, which channel to send a log message to when a moderator uses the `ban` command.
* To debug any points of failure, should they ever arise
* To collect metrics and analytics to better understand our userbase and which features perform well