Privacy policy
This page is a template. The operator of this instance replaces every part in square brackets before going live, and has it checked if in doubt.
Last updated: [Date]. The German version of this page is the legally binding one.
#Controller
[Company name or first and last name]
[Street and number]
[Postcode and city]
Email: [Email address]
Data protection officer: [Name and contact, if appointed. Otherwise delete this line.]
#In short
- We use no tracking or advertising cookies, so there is no cookie banner.
- Sign-in runs through Discord. We only receive what the dashboard needs.
- The bot stores ticket data and transcripts so your team can work. Transcripts are deleted after 30 days (Free) or 365 days (Premium).
- Payments run through Stripe. We never see payment details.
#Hosting and server logs
The website, dashboard, bot and database run at [Hosting provider, address, country]. When you open the website, the server processes technically necessary data: IP address, time, requested address, browser identifier and status code. This keeps the service secure and defends against attacks (Art. 6 (1) (f) GDPR). Logs are deleted after [7] days. [Conclude a data processing agreement under Art. 28 GDPR with the hosting provider.]
Fonts are loaded from our own server. There are no third-party embeds such as Google Fonts or video platforms.
#Sign-in with Discord
You sign in to the dashboard with Discord (OAuth2 with the scopes "identify" and "guilds"). We receive:
- your Discord id, username, display name, avatar and language setting,
- the list of your servers with name, icon, owner flag and your permissions there, so we only show servers you may manage,
- access tokens from Discord. We store them encrypted and only use them to keep your server list up to date.
The legal basis is the use of the service, Art. 6 (1) (b) GDPR. A session ends after 30 days or when you sign out. Your user record stays as long as you use the service. We delete it on request.
#Cookies and local storage
We only use technically necessary cookies (section 25 (2) no. 2 TDDDG). They do not need consent.
| Name | Purpose | Duration |
|---|---|---|
rpt_session | Keeps you signed in to the dashboard | 30 days |
rpt_oauth_state, rpt_oauth_next | Protect the sign-in and remember where to go afterwards | Until the sign-in ends, a few minutes |
rp-lang | Remembers your language | 1 year |
Your browser's local storage also holds rp-theme, your choice of light or dark design. It never leaves your browser.
#The bot on Discord servers
When a server adds the bot, the bot processes data through Discord's interface:
- Server data: id, name, icon, owner id, member count and the settings from the dashboard.
- Ticket data: number, channel, panel, ids of the owner, the claimer and whoever acted, times, reasons and form answers. The server's statistics are built from these.
- Messages: the bot reads messages in channels it can see to run commands, custom commands and automations. Messages are not stored, except in transcripts.
- Transcripts: a copy of the messages of a ticket with names and avatars of the people involved, content, embeds and attachment names. Transcripts are stored on our server. People who took part in the ticket and people who manage the server can open them.
- Dashboard history: who changed which setting and when, with Discord id and username.
Transcripts are deleted after 30 days, on servers with Premium after 365 days. Ticket data and history stay stored while the server uses the service. Server settings stay stored after the bot is removed, so they are back when it is added again. We delete them at the request of the server's administration.
[Have the legal classification checked: the server's administration decides to use the bot on its server. Depending on the setup, the operator acts as a processor (Art. 28 GDPR) or as a controller based on Art. 6 (1) (f) GDPR. Insert the matching text here.]
#Payments with Stripe
When you buy Premium, payment runs through Stripe Payments Europe, Ltd., 1 Grand Canal Street Lower, Grand Canal Dock, Dublin, D02 H210, Ireland. Stripe processes name, email address, payment and billing details. We only receive customer and subscription ids, the status and the end of the paid period. The legal basis is Art. 6 (1) (b) GDPR, for invoices Art. 6 (1) (c) GDPR. We keep billing records as long as tax and commercial law require. Stripe may also transfer data to the USA. Details are in Stripe's privacy policy: https://stripe.com/privacy (opens in a new tab).
[Delete this section if this instance does not offer payments.]
#Analytics with Plausible
[Keep only if Plausible is set up on this instance, otherwise delete this section.]
We count page views with Plausible Analytics (Plausible Insights OÜ, Västriku tn 2, 50403 Tartu, Estonia). Plausible sets no cookies and stores no IP addresses. A value that changes daily is derived from the IP address and browser identifier and does not identify you. The legal basis is Art. 6 (1) (f) GDPR, our interest in simple audience measurement.
#Discord
The bot and the sign-in require a Discord account (Discord Inc., 444 De Haro Street, Suite 200, San Francisco, CA 94107, USA). What Discord itself does with your data is governed by Discord's privacy policy: https://discord.com/privacy (opens in a new tab).
#Your rights
You have the right of access (Art. 15 GDPR), rectification (Art. 16), erasure (Art. 17), restriction of processing (Art. 18), data portability (Art. 20) and to object to processing based on legitimate interests (Art. 21). Write to [Email address].
You can also complain to a data protection supervisory authority (Art. 77 GDPR), for example [Responsible authority with address].
#Changes
We update this policy when the service changes. The version published here applies.