R Raidy

Privacy policy

Last updated: 25/10/2026

1. Controller

Ranfred Software
Sven Gabriel
Am Klagesmarkt 43
30159 Hannover
E-mail: conoar@gmail.com

Raidy is offered by Ranfred Software (sole proprietorship). There are no ads, no tracking, no analytics tools, and no data is sold.

2. Hosting and server logs

The website runs on Vercel Inc. (USA) in the Frankfurt am Main region. The database is hosted by Supabase Inc. (USA) in Frankfurt am Main. When you open a page, the servers process your IP address, the time, the requested URL and your browser identifier, as needed to deliver the page and fend off attacks. These logs are deleted automatically after a short time.

Legal basis: Art. 6(1)(f) GDPR (legitimate interest in secure operation). Data processing agreements are in place with both providers. Possible access from the USA is covered by the EU-US Data Privacy Framework or the EU Standard Contractual Clauses.

3. Signing in with Discord

Sign-in goes through Discord (Discord Inc., USA). Raidy only requests the identify and guilds scopes and receives:

  • your Discord ID, username and avatar,
  • the list of Discord servers you are on.

Raidy does not receive your e-mail address. The server list is only used to show you the servers that use Raidy. Your membership is stored only for those servers, together with the role IDs the bot reads there for permissions (e.g. raid lead). Legal basis: Art. 6(1)(b) GDPR (providing the service you use).

4. The Discord bot

When a guild adds the Raidy bot to its server, the bot processes what you enter there (e.g. raid sign-ups via buttons or commands) and posts raid messages and events in the guild’s channels. If the guild has turned on reminders, the bot sends you direct messages about upcoming raids. Discord’s own privacy policy applies to processing on Discord itself.

5. Data you or your guild enter in Raidy

Raidy stores the data needed for raid planning:

  • characters (name, class, specialization, role),
  • raid sign-ups with status and an optional note, attendance, roster and group assignments,
  • loot data: reservations, wishlists, BiS lists, bids, rolls, points (DKP/EPGP) and awarded loot,
  • warnings, if the raid lead uses that feature,
  • the guild’s change log (who changed what and when).

Members of your guild can see this data in Raidy and, where the guild posts it there, on its Discord server. If a guild turns on its public guild page, raids and line-ups are visible there without signing in. Legal basis: Art. 6(1)(b) GDPR; for warnings and the change log Art. 6(1)(f) GDPR (the guild’s legitimate interest in transparent organisation).

6. Battle.net link (character import)

You can link your Battle.net account (Blizzard Entertainment) to Raidy to import your WoW characters. Raidy only requests the wow.profile scope. The following is processed:

  • your BattleTag and Battle.net account ID,
  • character data (name, realm, class, race, level, guild, portrait),
  • equipment and stats (item level, resistances) and the talent distribution of your imported characters,
  • for a WoW guild linked by the guild leadership, that guild’s public member list (name, class, level, rank).

The purpose is to create characters with the exact in-game name and to keep equipment and stats up to date for raid planning. Blizzard’s access token stays on the server only and is valid for 24 hours at most; after that a new sync is needed. Imported characters and their equipment are refreshed daily and, like your other character data, are visible to the members of your guild. You can unlink at any time in your Raidy profile (characters page), which deletes the token and the account mapping while imported characters stay, and additionally revoke access in your Battle.net account. Legal basis for linking and import is your consent given via the authorisation at Blizzard (Art. 6(1)(a) GDPR). Syncing the member list of a linked WoW guild, including members who do not use Raidy, is based on the guild’s legitimate interest in organising its raids (Art. 6(1)(f) GDPR); this is data Blizzard makes publicly available. Blizzard’s own privacy policy applies to Blizzard.

7. Guest links for players outside the guild

When you enter a guest code, Raidy stores your Discord ID or, if you are not signed in, your IP address to limit failed attempts. These entries are deleted after one day (Art. 6(1)(f) GDPR, abuse prevention).

8. Calendar subscriptions

When you create a calendar subscription, Raidy generates a secret link. Anyone who knows the link can see the events in it. You can regenerate the link in Raidy at any time, which invalidates the old one.

9. Cookies

Raidy only sets strictly necessary cookies:

  • Supabase sign-in cookies (sb-…) that keep you signed in,
  • locale for your chosen language,
  • raidy_view_as when a raid lead uses the “view as member” mode.

These cookies are strictly necessary for the service (§ 25(2) no. 2 TDDDG) and need no consent. There are no tracking or advertising cookies.

10. Third-party content

  • Wowhead: for item tooltips, Raidy loads a script and item icons from wow.zamimg.com (Wowhead). This transmits your IP address to Wowhead. The purpose is to show item information (Art. 6(1)(f) GDPR). Details: wowhead.com/privacy.
  • Discord avatars are loaded directly from cdn.discordapp.com, which gives Discord your IP address.

Fonts are served by Raidy itself, not by Google.

11. Payment via Stripe

If you book a paid plan, payment is handled by Stripe Payments Europe Ltd. (Ireland). You enter your card or payment details directly with Stripe; Raidy never sees them. Raidy stores the Stripe customer and subscription IDs, plan, period, status and end of term as well as your Discord ID and the guild the subscription applies to. For payment, invoicing and fraud prevention Stripe processes, among other things, name, e-mail address, payment details and IP address under its own responsibility or as a processor; transfers to the USA are possible (EU Standard Contractual Clauses). Legal basis is Art. 6(1)(b) GDPR (performance of contract) and, for invoices, Art. 6(1)(c) GDPR (statutory retention, up to 10 years). Details: stripe.com/privacy.

12. AI assistant (MCP) and API access

If you connect an AI assistant such as Claude or ChatGPT to Raidy (with a personal token or by signing in with Discord), Raidy stores the access (only as a hash), its permissions, expiry and last use, and the number of calls per day. Which Raidy data the assistant retrieves depends on your questions; that data goes to the provider of your assistant, whose privacy policy applies. Legal basis is Art. 6(1)(b) GDPR.

13. Guild applications

If you apply on a guild's public page, you sign in with Discord first. Raidy stores your Discord name, avatar, Discord ID, the character you give (name, class, spec, ruleset), the spot you apply for and your answers to the guild's questions. The application is posted to the Discord channel the guild picked for it and is visible to everyone who can read that channel (we advise guilds to use an officers-only channel). In Raidy only the guild leadership and the raid leads of the chosen team see it. You receive the answer as a Discord message from the bot. After you submit, you get a confirmation as a Discord message. Questions from officers and your replies (the chat about your application, via Discord buttons or in Raidy) are stored by Raidy with the sender name and time; they also appear in the application’s Discord thread and are deleted together with the application. Raidy deletes the application 180 days after the decision or withdrawal. Under "My area" you can withdraw an open application and delete a decided or withdrawn one yourself. To prevent abuse (waiting period after a rejection, daily limit on applications), Raidy keeps a minimal record for 14 days, even after deletion: your Discord ID, the guild, the time and whether the application was submitted or rejected. Messages that officers write in a Discord thread about the application are held by Discord and stay there. The legal basis is Art. 6(1)(b) GDPR (handling your application at your request), and for abuse protection Art. 6(1)(f) GDPR (the guilds' legitimate interest in not being flooded with applications).

14. Retention

Your data is kept as long as you or your guild use Raidy. On request I will delete your profile with all associated data; just e-mail conoar@gmail.com.

15. 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). An informal e-mail to conoar@gmail.com is enough.

You can also lodge a complaint with a data protection supervisory authority, for example in your country of residence.

Back to the start page: raidy.app