Booty Bay Watch – Privacy notice
Effective date: 21 October 2026
Booty Bay Watch ("BBW", "we") is a Horde guild on WoW Forever. This notice explains what personal data we process on our guild website bootybaywatch.com and in our raid app BBW Guild Manager at raid.bootybaywatch.com, why we do it, and what you can do about it. It follows the Swiss Federal Act on Data Protection (revFADP) and, where it applies, the EU General Data Protection Regulation (GDPR).
1. Who is responsible
The controller is:
Gil Zumbrunnen (private individual, guild leader of Booty Bay Watch)
Based in Switzerland
Email: privacy@zumproductions.com
Contact us at that address for any privacy question or request. We have not appointed a data protection officer. We have not appointed an EU representative.
2. The guild website (bootybaywatch.com)
- The website is a simple information page. It has no forms, no accounts, no analytics, no tracking and sets no cookies.
- It is hosted by Infomaniak Network SA in Switzerland. Like any web server, the host processes your IP address and basic request data (time, page, browser) to deliver the page and keep it secure.
- Fonts are served from our own server; no data is sent to Google.
- The "Raid progress" and "Next events" sections show public information copied from our raid app to this website's server (raid progress and kill screenshots about every 12 hours, upcoming events open to non-members every hour). Your browser does not contact the raid app when you visit this website. This information contains no player data, except that kill screenshots may show character names.
- Links to Discord and to the raid app only send data to those services if you click them.
3. The raid app (raid.bootybaywatch.com)
The raid app is for guild members and invited PUGs only. You log in with Discord; we never see your Discord password or email address.
3.1 What we process
| Category | Examples | Where it comes from |
|---|---|---|
| Discord account | Discord user ID, username, display name / server nickname, avatar, your roles on the BBW Discord server, a Discord login token (used to read your server roles at login) | Discord, when you log in |
| Guild profile | Rank (member, trial, raider, officer…), status, join and trial dates | Derived from your Discord roles; set by officers |
| Characters | Character names, class, race, spec(s), main/alt links, professions and skill, gear snapshots, owned items, attunements, achievements, best-in-slot lists | You, officers, or our in-game addons (export strings you paste in) |
| Raid planning | Event sign-ups (accept/tentative/decline, spec, note), raid roster and group placement, soft reserves, raid assignments, consumable prep confirmations | You and officers |
| Attendance and loot | Attendance (present / late / no-show), loot received, EPGP points and ledger, loot history | Officers, our in-game addons, Warcraft Logs |
| Absences | Your "away from–to" dates and an optional note | You |
| Guild bank and crafting | Bank item requests, crafting orders | You and officers |
| Combat logs | Character names and fight data (deaths, performance, consumables) from Warcraft Logs reports that officers link to a raid | Warcraft Logs (public or guild reports) |
| Officer tools | Officer notes about members (note, warning, promotion), reliability score (see 3.3) | Officers / calculated |
| Officer elections | That you stood as a candidate (character name and role), that you cast a vote in a round (not which candidate), and per-candidate vote counts including blank | You (candidacy and vote); the app (counts) |
| Notifications and messages | In-app notifications, log of Discord DMs sent by the guild bot, your DM preferences | The app |
| Security and audit | Audit log of actions (who did what and when, e.g. logins, edits); server logs with your IP address, the page requested and your browser (user agent), kept for at most 3 days | The app and hosting (Azure, Switzerland) |
Please don't put health or other sensitive details in free-text fields such as absence or sign-up notes. A reason for an absence is never required.
3.2 Why we process it, and on what basis
We process this data to run the guild: manage membership and ranks, plan raids and events, run sign-ups, soft reserves and loot (EPGP), track attendance and progress, run the guild bank and crafting orders, run officer elections, and keep the app secure.
- Swiss law (revFADP): we process data in line with the principles of the revFADP; we do not rely on your consent.
- EU law (GDPR), where it applies: Art. 6(1)(b) GDPR (to provide the guild membership and app you signed up for) and Art. 6(1)(f) GDPR (our legitimate interest in organising a fair, reliable raiding guild and keeping the app secure). You can object to processing based on legitimate interest (see section 7).
You don't have to use the raid app, but without it you cannot sign up for raids or take part in loot.
3.3 Reliability scores and officer notes (profiling)
- Reliability score: for officers, the app calculates a score per member from past raids where attendance was recorded: no-shows after accepting (50 %), lateness (30 %) and consumable preparation for raids that require it (20 %). It needs at least 3 raids.
- Officer notes: officers can write short notes about members (e.g. a warning or a promotion note).
- Both are visible only to officers and are used to help officers decide on rosters, trials and promotions. No decision is made automatically – a human officer always decides. You can ask to see what is stored about you (section 7).
3.4 Officer elections
Admins can run elections for officer roles. Members of rank member or higher can stand as candidates and cast one vote per open role (including a blank vote).
- The app does not store who voted for whom. It only records that you voted in a round (to stop double voting) and keeps separate per-candidate counts.
- Results stay hidden until voting ends. Then the winner and the counts per candidate (and blank) are shown in the app and posted on our Discord (candidate character names and counts only).
- When you stand as a candidate, your character name, the role you stand for and your vote count will be shown that way. You can withdraw until voting ends.
- No role or Discord changes are made automatically; officers assign roles by hand.
3.5 What other members and the public can see
- Other members see your display name, characters, sign-ups, soft reserves, loot and EPGP standings, absences in the calendar, and similar guild information. PUGs see only the events opened to them and the names, classes and specs of the characters signed up.
- Guild Discord: the app can post to our Discord server raid recaps (bosses killed, loot winners by character, "fun awards" from Warcraft Logs) and milestones (e.g. attunements, professions, promotions).
- Discord DMs: the guild bot can send you reminders and updates (e.g. sign-up reminders, guild bank and crafting updates). You can switch each type off under My settings.
- Public: boss kill screenshots and kill dates are public on our website and via the raid app. Screenshots may show character names. Screenshots are uploaded as taken: names are not cropped or blurred, and the app only resizes images for display. The upload screen asks officers to avoid private chat in the image. If you want a screenshot showing your character removed, contact us and we will delete it.
3.6 Cookies and local storage
The raid app uses only what it needs to work:
- ARRAffinity / ARRAffinitySameSite cookies, set by Microsoft Azure to route you to the same server (strictly necessary).
- A meteor_login_token cookie (HttpOnly, Secure, SameSite=Lax) so you stay logged in (up to 30 days). Scripts in the page cannot read it.
- A few display preferences in local storage (e.g. roster column choices).
There are no analytics or advertising cookies. The app loads the Wowhead tooltip script from wow.zamimg.com (and fetches tooltip data from nether.wowhead.com) so item links can show a tooltip. That sends your IP address and browser data to Wowhead (ZAM Network LLC, USA). For this use the script does not set cookies or write to local storage.
4. Who receives your data (processors and services)
| Provider | What for | Location |
|---|---|---|
| Infomaniak Network SA | Hosting of bootybaywatch.com, including copies of public kill screenshots | Switzerland |
| Microsoft (Azure App Service) | Hosting of the raid app, including server logs | Switzerland (Switzerland North, Zurich) |
| Microsoft (Azure Blob Storage) | Storage of kill screenshots (private storage; deleted images are removed immediately) | Switzerland (Switzerland North, Zurich) |
| MongoDB, Inc. (MongoDB Atlas, running on Microsoft Azure) | Database of the raid app and its backups | Netherlands (Azure West Europe) |
| Discord Inc. | Login, server roles, bot messages, recap posts | USA |
| RPGLogs, LLC (Warcraft Logs / Archon) | Combat log reports that officers link; the app pulls report data via Warcraft Logs' API | USA |
| ZAM Network LLC d/b/a Fanbyte (Wowhead) | Item tooltips and icons loaded in the browser | USA |
We do not use any analytics or monitoring service (no Application Insights, no Google Analytics). We do not sell your data or use it for advertising.
Transfers abroad: the raid app and screenshots are hosted in Switzerland. The database is in the Netherlands (EU/EEA), which Switzerland recognises as having adequate data protection. Data also goes to the USA through Discord, Wowhead and (when officers link reports) Warcraft Logs:
- Discord Inc. is certified under the Swiss-US Data Privacy Framework (status on the official list as of 21 October 2026: Active – Re-certification under Review) for non-HR data.
- Microsoft Corporation and MongoDB, Inc. are likewise certified under the Swiss-US DPF (Active). Their Swiss / EEA hosting is the primary location for our app and database.
- ZAM Network LLC (Wowhead) and RPGLogs, LLC (Warcraft Logs) do not appear on the DPF list (checked 21 October 2026). Loading Wowhead's tooltip script transfers your IP address and browser data to them in the USA; ZAM's privacy policy states that for EEA/UK users it relies on standard contractual clauses or adequacy assessments. For Warcraft Logs, BBW's server pulls public or guild report data that officers choose to link; members who upload combat logs to Warcraft Logs do that themselves under Warcraft Logs' terms — BBW does not send your Discord account to them.
5. How long we keep it
- While you are a member, we keep your data so the guild can run.
- When you leave the guild (or the Discord server), we delete your personal data from the raid app 8 days later, unless you rejoin within that time. Copies in our database backups disappear within a further 8 days. Where you appear in shared guild records (for example loot history, raid rosters or sign-ups), your name is replaced with "Former member" so nothing links those records back to you. Some copies are outside our control and cannot be removed this way: messages the bot already posted in Discord, names in public Warcraft Logs reports, and data saved locally in officers' game addons.
- Database backups are kept for up to 8 days, then overwritten automatically.
- Server logs are kept for at most 3 days.
- Deleted kill screenshots are removed from the raid app's storage immediately, and from the website's copy at its next refresh, normally within a day.
- Audit log entries (who changed what in the app, used for troubleshooting and fixing mistakes) are deleted automatically after 3 months (90 days).
- Records that you voted in an election round are deleted when that round closes or is cancelled.
- Election results and candidate lists are kept as guild history. If you leave, a candidate name in those results is replaced with "Former member" like other shared records.
6. Security
Login is via Discord only, access is limited by guild rank and checked on the server, connections use HTTPS, and secrets are kept out of the code.
7. Your rights
You can ask us to:
- tell you what data we have about you and give you a copy (right of access);
- correct wrong data;
- delete your data or stop processing it;
- object to processing based on our legitimate interest (GDPR);
- give you your data in a common format (data portability, GDPR).
Most profile data you can edit yourself in the app. For anything else, email privacy@zumproductions.com. We answer within 30 days.
If you think we have mishandled your data, you can complain to the Federal Data Protection and Information Commissioner (FDPIC / EDÖB), www.edoeb.admin.ch, and, if you live in the EU/EEA, to the data protection authority in your country.
8. Age
The guild website and the raid app are intended only for people aged 18 and over. We do not verify age (including at Discord login). If we learn that a user is under 18, we will remove their data from our systems.
9. Changes
We will update this notice when the website or app changes, and announce major changes on our Discord server. The current version is always at https://bootybaywatch.com/privacy.