Privacy policy

When it records

Exposer only records when someone in a server asks it to, with the /join command or its shortcuts, or when whoever manages the server has turned on joining Discord scheduled events by itself. While recording it shows up as one more participant in the voice channel, with a [🔴REC] flag on its name, and it leaves a recording notice in that channel's chat and in the recap channel. Anyone who joins once the meeting has started is told as well.

Whoever starts the recording is responsible for making sure the people present know and agree, under whatever rules apply to them.

What data is handled

• Voice. The audio of whoever speaks in the channel during the recording.
• Transcript and recap. The text of what was said, and the summary, decisions and action items generated from it.
• Discord identifiers. Each participant's display name and ID, and those of the server, the channels and the meeting's thread.
• Website login. When you log in with Discord, your ID, name, avatar and the list of servers you belong to are stored, to show you the ones you share with the bot. No Discord credential is stored.
• Server settings. The settings chosen and the name of whoever last changed them.
• Subscription. If you buy a paid plan, your Discord ID, the plan, the minutes used, the server you assign it to and Stripe's customer and subscription IDs are stored. Card details are handled by Stripe and never reach Exposer. On the free plan, the minutes used per user and per server are stored.

What it is used for

To write the meeting's recap, post it on Discord and show it on the website, to play the audio back while it is kept, and to keep count of each plan's minutes and charge for subscriptions. They are not used for advertising, are not sold, and are not used by this service to train models.

Who else receives it

• api.groq.com. Receives the audio of each utterance to turn it into text.
• OpenAI. Receives the transcript to generate the summary. How these providers handle it is governed by their own terms.
• Discord. The recap is posted as messages in the server, subject to Discord's terms.
• Stripe. Handles subscription payments and receives your Discord ID along with the payment details you give it.

How long it is kept

• Audio. 7 days by default, up to what the server's plan allows: 1 day on the free one and up to 30 on paid ones. Each server can pick a shorter period or keep no audio. After that it is deleted automatically, and it can be deleted sooner.
• Recaps and transcripts. Until someone who manages the server deletes them.
• Working copy. While recording, the transcript is saved to a temporary file so it is not lost if the bot restarts. It is deleted after 7 days.
• Website session. 7 days from login, or until you log out.

Who can see it

A recap and its audio are visible to whoever can see, in Discord, the channel it was posted in. This is checked on every visit, so losing access to the channel or leaving the server removes access on the website too.

A server's settings are only visible to, and changed by, people with the Manage Server permission.

How to delete data

If you took part in a recorded meeting and want to access your data, correct it or have it deleted, you can ask whoever manages that server or the contact below.

• A recording. Whoever manages the server can delete it before it expires, from the recap page or with the recap's button in Discord.
• A recap. Deleted the same way. It removes the transcript, the audio and what was posted in Discord.
• Stop keeping audio. With /config audio-retention or in the server's settings on the website.
• Your session. Logging out removes it from the server.

Cookies

The website only uses first-party, necessary cookies: one remembers the language, one keeps you logged in, and a third, lasting a few minutes, protects the login. There are no advertising or tracking cookies, and no third-party resources are loaded, other than the avatars and icons served by Discord.

Contact

For questions or requests about your data, write to meetbot@rubenhidalgo.dev, meetbot@rubenhidalgo.dev.