Raid-Calender
Privacy Policy
Last updated: 2026-10-11
This page describes what Raid-Calender stores, why, and for how long. The bot keeps only what raids and sign-ups need to work.
What is stored
When you sign up for a raid (in Discord or on the web): your Discord user ID, your display name in the server, class, spec, role and status (signed up, tentative, bench, can't make it).
Your last class and spec, per server, so the next sign-up is one click.
Soft reserves: the items you reserve for a raid. They are visible to the server's members and removed if you withdraw.
Raid groups and bench: which group a raid leader put you in, and how often you have been benched, counted from past sign-ups.
Planned absences: dates and an optional note. The server's raid leaders can see them.
A linked character, if you add one: name, realm and region. Raid leaders see item level, the bosses you have killed in the raid and Mythic+ rating next to your name.
Reminder DMs: whether you turned them off. The calendar link is stored only as a hash, with when it was last used.
Raids: title, description, time, settings and who created them (Discord ID).
Change log: when a raid leader creates, edits or cancels a raid, moves players or changes settings, who (Discord ID and name), what and when is recorded. Your own sign-ups are not logged there.
Server settings: timezone, channel, raid leader role, reminder time and language.
Raid templates raid leaders save, and Premium: which servers have it, from and until when, and Discord's ID for the purchase. Payment details are handled by Discord and never reach the bot.
Logging in on the web: Discord ID, username, display name and avatar, plus a hash of the login token (the token itself is never stored) and when the login expires.
The bot does not read messages in your channels and stores no passwords, email addresses or payment details.
Logging in with Discord
The dashboard asks only for the identify scope (name and avatar). The access token Discord sends is used once to see who you are and is revoked straight away; it is never stored.
Which servers you can see is decided by the bot itself: only servers that both you and the bot are in, and only raid leaders see the change log and settings.
If you apply to a guild in the guild finder, your Discord ID, display name and username, the character, class and message you write, and the guild's decision are stored. The guild's raid leaders see your application. Withdrawing a waiting application deletes it. The guild's listing — name, raid nights, description — is public for as long as its raid leaders show it.
If a raid leader makes a public sign-up link for a raid, anyone with the link sees its sign-ups — display name, class, spec and status — and can sign up with their Discord login without being in the server. The link stops working when the raid leader turns it off.
Cookies and browser storage
rc_session keeps you logged in (HttpOnly, up to 30 days). rc_oauth_state protects the login itself and expires after ten minutes.
The browser's local storage remembers the language and server you last picked.
There are no advertising, tracking or analytics cookies.
Who sees what
Sign-ups and raids are visible to the members of the Discord server the raid belongs to, in Discord and on the web. Other servers never see them.
Data is not sold or shared. Discord receives what the bot posts in channels. Traffic to the dashboard passes through Cloudflare, which therefore handles data such as IP addresses.
If you link a character, its name, realm and region (no Discord ID) are sent to Blizzard to look up item level, boss kills and Mythic+ rating, and for Classic to Warcraft Logs to look up boss kills from the logs. The link to Raider.IO opens only when you or a raid leader clicks it.
If a raid leader pastes the log from the Raid-Calender addon, the names of the characters in the group at each boss and the items they received are stored with the raid. They are deleted with the raid.
The calendar link shows your raids to whoever has it. You can replace or remove it at any time, and the old one stops working.
The bot runs on a private server in Sweden. Whoever runs it has access to the database and to technical logs, which can contain Discord IDs.
How long
Raids and sign-ups are kept as history until a raid leader deletes the raid, which also removes its sign-ups. Whoever runs the bot can set finished raids to be deleted automatically after a number of days.
A login expires after 30 days without use and is then deleted. Logging out deletes it at once.
Absences, a linked character and the calendar link stay until you remove them (with /absence, /character or on the web).
Your rights
You can remove your sign-up at any time with the button in Discord or on the web.
You can download everything stored about you as a file: the download button next to Log out in the dashboard.
You have the right to know what data is held about you, to have it corrected or deleted, and to object to its processing. It is processed so the service works for the servers that use it (legitimate interest).
Get in touch to exercise these rights. You can also complain to the Swedish Authority for Privacy Protection (IMY).
Contact: [email protected].