Privacy Policy

For Otto Build, Otto Grow, Otto Guard and this website · Last updated 28 October 2026

In short

We only use what the bots and the dashboard need to work. We do not read message content, do not sell data and do not show ads.
The website uses one sign-in cookie and nothing else: no analytics, no tracking.
Data is stored in the EU: at Hetzner (Finland), with a standby in the Netherlands and a database copy at Cloudflare (EU).
You can ask us what we have about you and to delete it: the contact link at the bottom of this page.

1. Who is responsible

The team behind Otto runs Otto (Otto Build, Otto Grow, Otto Guard, this website and the dashboard) and is responsible for the personal data described here (the “controller” under the GDPR). Contact: the contact link at the bottom of this page.

When a server owner adds our bots, we process data about that server's members on behalf of the server so the bots can do their job. The server owner decides which bots and features are used.

2. What we collect

When you sign in on this website

From Discord (scopes identify and guilds): your Discord user ID, username and avatar, and which servers you are in with your permissions there. We keep only the servers you can manage, so we can show them on the dashboard. We do not get your email address or password.
One cookie that keeps you signed in for up to 7 days. We store only a scrambled (hashed) version of it.

About servers that use a bot

Server ID and name, the owner's user ID, and the user IDs of members who can manage the server (so only they can use the dashboard).
Names and IDs of channels and ranks, and permission settings — what the bots need to show choices on the dashboard and to tidy up or restore the server.
The settings you make on the dashboard, such as welcome texts, custom commands, role menus, timers, polls and ticket types.

About members of those servers

Bot	What	Why
Otto Grow	Per member: a level total, how many messages they sent and when they were last active (counts only, never the messages themselves).	Levels and activity ranks.
Otto Grow	The ranks a member had when they left.	So they get their ranks back if they return.
Otto Grow	Numbers of members joining and leaving, without who.	Growth statistics on the dashboard.
Otto Guard	Moderation cases: who was kicked, banned or timed out, by whom and the reason given.	So the server can look back with /history and in its log.
Otto Guard	Tickets: who opened, claimed and closed a ticket and when (not what was written in it).	Ticket numbers and follow-up.
Otto Guard	Backups of the server structure, including which members had which rank.	To restore the server after griefing.
Otto Guard	What happens in the server (joins, leaves, rank and channel changes), taken from Discord's audit log.	Posted to the server's own log channel; we only keep it briefly while it is being posted.

The bots do not use Discord's Message Content intent, so they cannot read what people write in normal messages. They also do not track online status or voice conversations.

When you order a server build or use Improve my server

Your answers in the order form (such as the server's name, theme and wishes) and any contact detail you give us.
The design that was made, a backup of the server structure before the build, and for Improve my server the latest suggestions and a history of the last changes, so they can be undone.

Error reports

When something goes wrong we log technical details with an error code (such as OT-7K3F9Q), sometimes including a server or user ID. You may see the code in an error message; sending it to us helps us find the problem.

Things you send us

If you contact us, we use what you send to help you. When you use Report a problem on the support page we keep your Discord user ID and name, the server you picked, the error code and what you wrote.

Buttons under Otto Guard's alerts

So a moderator can unmute, ban or give ranks back with one click, we keep which member and which ranks an alert was about.

3. Why we use it (legal basis)

To provide what you asked for (contract): signing in, the dashboard, the bots' features, orders and premium.
Legitimate interests: keeping the service and your server safe (logs, backups, moderation, abuse prevention, blocking servers that misuse the bots), fixing errors, and the features a server owner chose for their members. We keep this to what is needed and you can object (see your rights).
Legal obligations: for example keeping payment records where the law requires it.

4. Who else is involved

We do not sell personal data and do not share it for advertising. We use these services:

Discord — the bots run on Discord, and sign-in goes through Discord. Discord's own privacy policy applies to your use of Discord.
Anthropic (Claude) — when you order a server build, your form answers are sent to Anthropic's AI to create the design. No data about server members is sent. Anthropic may process this in the United States.
Hetzner (Finland) — the data centre where our main servers run, in the EU.
Cloudflare — protects and delivers this website; it sees technical data such as IP addresses to block attacks. Cloudflare also stores a continuously updated copy of our database (Cloudflare R2, EU jurisdiction, encrypted at rest), so another server can take over within minutes if one fails.
The payment provider linked on the premium page — only if you pay. It handles your payment details; we do not see them.

When data leaves the EU, this happens under the safeguards the GDPR requires, such as the EU's standard contractual clauses.

5. How long we keep it

Sign-in sessions: up to 7 days.
Error reports: 90 days, unless we keep one longer while helping you with it.
Problem reports you send us: until we have handled them, then 180 days.
What the buttons under Otto Guard's alerts need: 30 days.
Join and leave numbers: about 13 months.
Improve my server: the latest suggestions and the last 10 changes per server.
Old server after a build: downloadable for 7 days.
Server settings and member data from the bots: as long as the bot is in the server. If a bot is removed we keep the settings, so inviting it again restores them — ask us and we delete them.
Our own database backups (to recover from a failure): up to 12 weeks on the server itself, and up to 365 days as an encrypted copy off-site (Cloudflare R2, EU), so a mistake noticed late can still be undone.
Sign-in attempts on our staff portal (time, account name and IP address): one year, to detect break-in attempts.

6. Your rights

Under the GDPR you can ask us for a copy of your personal data, to correct it, to delete it, to limit how we use it, to object to it, or to receive it in a portable format. Members of a server can ask us too. Contact the contact link at the bottom of this page and tell us your Discord user ID and, if it is about a server, its ID. We may ask you to prove it is your account. We answer within one month.

You can also complain to a data protection authority. In the Netherlands that is the Autoriteit Persoonsgegevens.

7. Security

Data is stored in the EU: on our servers at Hetzner, a standby server of our own in the Netherlands, and the database copy at Cloudflare R2 (EU). Only one server runs the bots at a time. Sign-in sessions are stored only in hashed form, our staff portal is protected with two-step verification and only a few people can access it, and backups that leave the server are encrypted. The bots only ask for the Discord permissions they need.

8. Children

Otto is meant for people who are old enough to use Discord in their country. We do not knowingly collect more data about children than the bots need for the servers they are in. If you think we hold data about a child that we should not have, please contact us.

9. Changes

We update this policy when what we do changes. The date at the top shows the latest version; for important changes we will give notice on this website.