Clippy privacy policy

Effective date: November 8, 2026

Clippy is a Discord bot that sits in a voice channel and, when someone asks, posts a clip of what was just said. Its dashboard is a website where people who manage a Discord server install and set up Clippy. Both are run by the Clippy team ("we"). This policy says what Clippy and its dashboard do with your data. Contact us at privacy@heyclippy.app.

What Clippy handles

Voice audio

Clippy enters a voice channel when someone in that channel asks it to with /join, or when someone with Discord's Move Members permission moves it there. While it is there, it receives the audio Discord sends it from everyone speaking, people and other bots alike.

Clippy keeps at most 120 seconds of that audio, and only in memory. Each time new audio arrives, anything more than 120 seconds older than it is dropped for good. If everyone goes quiet, the last thing said stays in memory until someone speaks again or Clippy leaves, but a clip can't reach it once it is over 120 seconds old.
The audio is never written to disk, and Clippy stores no audio.
The audio is thrown away when Clippy leaves the channel or moves to another one, and when Clippy restarts.
Clippy leaves when someone in its channel asks with /leave, and on its own after 60 seconds with nobody but bots in the channel. It also leaves when someone disconnects it, when it loses the connection and when it is removed from the server.

Clips

A clip is made only when someone in the voice channel with Clippy asks for one with /clip.

A clip is one audio file that mixes everyone heard over the last 5, 15, 30, 60 or 120 seconds (30 unless the requester picks another length).
Clippy posts it as a message in the server's clips channel. The message names the requester, the voice channel and everyone heard in the clip. Anyone who can see that channel can play and download the clip, even if they weren't in the voice channel.
Clippy keeps no copy. On our side the clip exists only as that Discord message, and deleting the message deletes it. A copy someone has already downloaded is out of our reach.
The requester and anyone the message names as heard can delete it with the message's Delete button, as long as Clippy is running and still in the server. Discord's own permissions also let the server's moderators delete it.
Once posted, the message is held by Discord under Discord's own terms and privacy policy.

Server settings

For each server Clippy is installed in, we store one record in a database:

the server's Discord id;
the Discord id of the server's clips channel, once one is picked;
the Discord id of the user who installed Clippy;
when Clippy was installed and when the record was last changed.

The record holds no audio, no clip and no message text. It is deleted when Clippy is removed from the server. If the database can't be reached at that moment, it is deleted the next time Clippy starts.

Dashboard accounts

You only have an account if you sign in to the dashboard. Being in a voice channel with Clippy, using its commands or being heard in a clip doesn't create one.

The dashboard signs you in with Discord. It asks Discord only for your identity and your server list (the identify and guilds scopes), not your email address. For each account we store, in the same database:

your Discord id, which is also the account's name;
a placeholder address built from that id, ending in @discord.invalid, which can't receive mail, because the sign-in software needs one;
the access and refresh tokens Discord gives the dashboard, encrypted, with when the access token expires and the scopes you granted;
one session per sign-in: a random token, when it was created and when it expires;
when the account was created and when it was last changed.

We don't store your Discord username, your avatar or your real email address, and sessions don't record your IP address or browser. When it needs them, the dashboard reads from Discord your username, your server list (each server's name, icon, member count and your permissions there) and the text channels of the servers Clippy is installed in. It shows them to you and stores none of it. Installing Clippy stores only the server's record above.

A session lasts seven days from sign-in and is never extended. Logging out deletes that session, and a session that has run out is deleted within about a day.

Once an account has no session left, because you logged out or your last session ran out, we delete the account and its Discord tokens within about a day. So nothing about your account stays for more than about eight days after you last signed in, even if you revoke Clippy's access in Discord or delete your Discord account. If you sign in again, you start a new account.

Visiting the dashboard

The dashboard sets a cookie that keeps you signed in for seven days and a cookie that lasts five minutes while you sign in. If you pick a theme, a third cookie remembers it for a year. It uses no analytics or advertising cookies and loads no tracking scripts.

Your IP address and browser details reach our host with every request, so that it can answer. They aren't stored, except in the failed requests described under Logs. To limit repeated sign-in attempts, the dashboard holds IP addresses in memory only.

Logs

Clippy and the dashboard write logs of what they do, so we can run them and fix problems. The logs never hold audio or message text. Clippy's logs record Discord ids and numbers:

the ids of the server, the voice channel, the clips channel and a clip's message;
the id of the user who ran a command or pressed a clip's Delete button, the ids of everyone heard in a clip, and the id of a speaker whose audio stream failed;
the command's name, the clip's length, size and timing, and whether a request was refused and why;
error details from Discord and the database, with the request addresses and request bodies of Discord's errors removed.

The dashboard logs only errors from Discord, the database and the sign-in. A database error can repeat the values of the failed query. In Clippy's logs those are Discord ids. In the dashboard's they can also be the placeholder address, a session's token or the encrypted Discord tokens.

The web server in front of the dashboard keeps no record of ordinary visits. If a request fails because the dashboard can't be reached, it logs that request: your IP address, the address you asked for and the headers your browser sent, without your cookies.

Logs are kept by size, not for a set time. Each service keeps up to about 100 MB of logs, and when that fills up the oldest entries are dropped. A service's logs are deleted when the service is replaced, as happens when we update it. Because the limit is by size, an entry can stay for a long time when little is logged. OVH's automatic backup of the server's disk can hold a copy of the logs until a later backup replaces it.

Data Discord sends while Clippy is running

To work, Clippy receives from Discord the server's details and channels, who is in which voice channel with their Discord profile, and who ran a command or pressed a button. It uses this in memory only and stores none of it, apart from the ids listed above.

Why we handle it

We handle this data only to provide Clippy: to make and post the clips people ask for, to know which channel a server's clips go to, to sign people in to the dashboard and check which servers they manage, and to keep Clippy running.

If the GDPR or a similar law applies to you, we rely on these legal bases. For dashboard accounts and server settings: providing the service you or your server asked for. For voice audio, clips and logs: our legitimate interest, and that of the people in the channel, in making the clips they ask for and in keeping Clippy secure and running. You can object by leaving the voice channel or by contacting us. You also have the right to access, correct, delete, restrict or receive a copy of your data, and to complain to your data protection authority.

We don't sell your data, use it for advertising or share it with anyone except as below.

Who else is involved

Discord: Clippy runs on Discord, and clips are posted there. The dashboard's sign-in goes through Discord, and your browser loads server icons from it. Discord's privacy policy applies to everything on Discord.
OVH, our host: Clippy, the dashboard, the audio in memory and the logs run on a server at OVH in Virginia, United States.
Neon, our database provider: the server settings and dashboard accounts are in a database at Neon, on Amazon Web Services, in the same region as our host. We make no backups of it. Neon keeps up to six hours of the database's history, so a deleted record can stay there for up to six hours.

These companies can be in a different country from you.

Your choices

Clippy can't hear you while you're not in the voice channel it is in.
Anyone in Clippy's voice channel can make it leave with /leave.
You can delete any clip you asked for, or that names you as heard, with its Delete button.
Anyone who manages a server can remove Clippy from the dashboard, and anyone allowed to kick it can remove it in Discord. Either way the server's settings are deleted. Clips already posted stay, and once Clippy is gone their Delete buttons stop working, so only someone with Discord's Manage Messages permission can delete them.
You can log out of the dashboard, and you can revoke Clippy's access in Discord's settings, which stops its stored tokens from working.
Clippy has no per-person opt-out yet. If you don't want to be in a clip, leave the voice channel while Clippy is in it.

To ask about your data, to have it changed or deleted, or to exercise any right you have over it, contact privacy@heyclippy.app and give your Discord id. We can delete your dashboard account with its tokens and sessions, and remove your id from any server's record. We can't remove one person's entries from the logs, so your id stays there until the logs roll over. Clips are Discord messages, so use the Delete button or ask the server's moderators.

Age

Clippy is not meant for anyone under 13, or the minimum age to use Discord in your country if that is higher.

Changes to this policy

We'll update this page when Clippy or its dashboard changes what they do with data, and change the effective date at the top.