Privacy Policy

What this policy covers

Two things: this website at https://decades.gg, and the Decades App, the guild's own planning software. Decades is a gaming community founded in 2005, not a company, and the people who run both are guild volunteers.

It does not cover Discord, Blizzard Entertainment, Apple, Google or any other service you reach from a link here. Those have their own policies. The terms for using either the site or the app are on the terms of service page.

This website

This website is a set of static pages. It has no accounts, no sign-in, no contact form, no advertising and no analytics or tracking scripts. It sets no cookies and builds no profile of you. The fonts are served from this site rather than a font CDN, so simply reading a page does not announce you to anyone else.

Our host, Firebase Hosting (Google), records standard server request logs — IP address, user agent, requested URL and timestamp — as part of serving and protecting the site. Those are handled under Google's Firebase privacy terms.

The Decades App

The Decades App is the guild's planning and membership app: members sign up for the week's raid nights, and officers build the raid groups from those signups. It runs in a browser and as iOS and Android apps. The Decades desktop app for Windows keeps the guild's in-game addon, Decades GuildOps, up to date, uploads what it records, and writes the guild's data into your game for the addon to show. What follows is what the app holds and does when you use it.

What the app holds about you

Signing in

You sign in with Discord. In a browser and in the desktop app it is the only way; the iOS app also offers Apple or a phone number, and the Android app Google or a phone number, and you can add those to your account in the phone app's Settings, or under Account on the web. Phone numbers are accepted from the US and Canada only. Signing in with Discord always reaches the account your Discord is linked to, however that account was first made, so Discord never gives you a second account.

Your sign-in is held by Firebase Authentication, Google's sign-in service. If you add Apple, Google or a phone number, Firebase Authentication holds the email address or phone number that comes with it; the app's own database does not, except briefly while two of your accounts are being merged. If you use Sign in with Apple, Apple may give us a private relay address rather than your real one, and that is fine; we do not rely on it to identify you. Where Apple and Google give the same verified email address, the app links the two to one account.

Signing in keeps you signed in, which means your browser, phone or PC holds a session token. Display preferences are stored in your browser too. Neither is account data and neither is used for tracking.

Discord

Discord is how you sign in and how the guild knows who you are. The app asks Discord for your identity and for your membership of the Decades server, nothing more. It stores your Discord user ID, your username, your Discord name (your server nickname where you have one), whether you are in the Decades server, the server roles you hold, when you joined the server, and when the link was made and last checked. If you have no display name yet, your Discord name becomes it.

We never store your Discord access or refresh tokens — not in the database, not in a session record, not in a log. If the server already gives you one of the guild's ranked roles, your first link sets your rank from it, once; after that, rank is the app's own and Discord roles are not read for it again. Your Discord details are refreshed only when you sign in with Discord or ask the app to check again.

What you enter

• Your profile — a display name and a timezone, and optionally the date you joined, the year you started playing, your favourite expansion, a short piece of text about yourself, your accomplishments, and lists of the expansions, other games, professions and hobbies you choose to share. You can also add your real-life name, if you want to, and choose who reads it.
• Your characters — name, class, specialization, the roles you can play, and whether a character is active or retired. You say which is your main. Each character is a claim that an officer approves or declines, with the officer's reason, where given, for you to read.
• Your availability and weekly signup — the times you can usually raid, in your timezone, and the times you are away, each with an optional note; and each week's signup, with the days you can play, which characters and a note.
• Your application — what you write when you apply to the guild, and your own words to the guild as a recruit.
• What you write and choose in the app — your answers to community events, your LFG posts and joins, your votes and nominations in polls, questions you ask leadership and replies to them, vouches for a recruit or a guildmate, quick ratings and requested feedback (below), guild bank requests and their reasons, posts in the loot council's chat if you sit on it, and ideas and bug reports you send the app's developers. When you search for a crafter, your search is sent to the app's server.

What officers record

Officers record your rank and when it changed, the decision on your application with an optional reason, their decisions on your characters, and occasional corrections to a display name or join date, each noting which officer made it and when. They also keep the guild's working records about members, such as feedback, interview notes and the officer notes the guild keeps in game.

The desktop app and the addon

The Decades desktop app reads what the Decades GuildOps addon saves in your World of Warcraft: Forever folders, and the addon's own tagged lines in the game's chat log. It never reads the game's memory or network traffic, never sends the game input, and never reads another addon's data. The first time it reads a WoW account, it asks whether that account is yours to upload.

It uploads what the addon records about your characters — such as their gear, talents, bags and bank, gold, reputation, professions, played time, lockouts and attunements, and where in the game they were last seen — the guild's roster, bank and in-game officer notes as your game sees them, and game events such as loot. Chat and whispers are never uploaded. From your mail, only the items, gold and expiry are uploaded, and the sender only of gold you took, which officers alone read. Another guild's data is left out.

It also writes into your own game what you can read in the Decades App, so the addon can show it: the schedule, the guild's members, characters and profiles, events, and your own data, and on an officer's PC the officers' notes. It also writes when each member's desktop app last synced, which the app itself does not show. On an officer's PC the officers' notes never include notes about that officer, and a folder holding a WoW account that is not yours gets none of your own or the officers' private data.

On your PC it keeps your sign-in in Windows Credential Manager, its settings, copies of the addon's saved data as backups (up to 200 MB in all), and a log that holds no sign-in details. Each upload also sends an ID for that PC's install, the Windows version and the app's version. Uninstalling forgets your sign-in and keeps its data on the PC unless you tick to delete it. The desktop app sends no crash reports or usage statistics.

Ratings and feedback

Two features exist so members can be honest about each other, and they only work if that honesty cannot be traced back. This is exactly what they do.

Quick ratings

While a round is open, members rate raidmates from one to five stars on a few elements the Council picked. Nobody who uses the app can see who gave a rating — not officers, not the Council, not Admins. A rating reaches a chart only when its round closes, as an average of at least five members' ratings. Who rated whom, on what and how, is kept for good, through account deletion, in the guild's database outside the app, where only the guild master and the app's builder can read it, to fix problems and look into abuse. No rating is ever sent to an AI.

Requested feedback

Officers can ask the guild for a star rating and written feedback on a player. Nobody reads an individual rating, and no rating is sent to an AI. Before anyone else reads an answer, its words are rewritten by AI so they do not give away who wrote them and reach the player as constructive feedback; the rewrite may soften or leave things out, and never adds. Only the text is sent, with no name attached, to Google's AI platform on the guild's own Google Cloud account, in the US, under Google's terms: Google caches requests for up to 24 hours, and keeps a request its safety filters flag for up to 90 days. Results appear only once at least three members answered. The original words and who wrote them are kept for good, and only the guild master and the app's builder can read them.

Who can see what

This is the part most people actually want to know, so it is set out directly.

• Before you are accepted, you can see your own record and nothing else. Applicants cannot see guild data, other members or rosters.
• Other accepted members can see your profile, your display name, your rank and designations, your Discord username and name, whether you are in the Decades server and when you joined it, and your approved characters, including which are yours and which is your main. They also see what anyone in the guild could see in game: your characters' gear, talents, professions and the like, the loot you received, and who was in each raid. Character names are public information in the game, and the guild is built on knowing who plays what.
• The published week is read by every member as officers saved it: raids, groups, characters, the raid lead and the week's message. Nothing in it carries your availability, your signup or anything from Discord.
• Your availability and weekly signup, notes included, are visible to you and to officers. Other members do not see them.
• Your real-life name, if you add it, is read by officers and the Council unless you choose to share it with every member.
• Your application is visible to you, officers, the Council and recruiters, and the decision on it, with any reason, to you and officers alone. Other members see how far it has got. Who vouched for a recruit is read by officers, the Council and recruiters, never the recruit.
• Polls and questions show their results and questions to members, never who chose what or who asked. LFG posts are read by every member.
• Ratings and feedback about you: the chart built from quick ratings is on your profile for every member to read, and guild feedback about you, reworded, is read by you, the Council and officers.
• Guild bank requests are read by you and officers; nothing tells the guild one was made. Ideas and bug reports you send are read by the app's Admins, with your name.
• Your own addon data that is not public in game, such as your bags, bank, mail and played time, is seen by you and officers.
• Officers and the guild master additionally see everyone's availability and signups, applications, the guild's working records about members and the drafts of a week before it is published. Admin, a privilege only another Admin grants, adds guild-wide settings. The Council reads applications, but not availability or signups.
• Your Discord roles are read by the app's server, and officers see where your Discord role and your rank disagree. If your account was made by signing in with Discord, your Discord user ID is part of your account's ID, which the app uses to show you to other members.

What we do not do

• No ad tracking, and analytics only on the phones, only if you allow it. This website, the app in a browser and the desktop app carry no analytics at all. The iOS and Android apps send crash reports and usage statistics only once you allow each, and neither app reads an advertising identifier; nothing collected is linked to one or used for advertising. What they send, and how they ask, is set out under What the phone apps send.
• No selling or sharing. We do not sell, rent or trade your information, and we do not hand it to anyone beyond the services listed below that are needed to run the thing.
• No AI training. Member information and Discord data are not used to train AI models. The one use of AI is rewording requested feedback, above. If that were ever to change, this policy would change first.
• No unsolicited messages. The app does not send Discord messages or direct messages, and having raided with the guild is not consent to be contacted.
• No push you did not turn on. Push notifications reach a phone or browser only after you turn them on for it. To address them, the app stores, for each phone or browser registered for push, its Firebase installation ID — the address Firebase Cloud Messaging, Google's push service, delivers to — with whether it is the iOS app, the Android app or a browser, which account it belongs to, and when it was registered and last seen, along with which kinds of notification you have chosen to receive. Only the app's server reads the installation ID: no member or officer can see it, it is never written to a log or to the record of what was sent, and your data export lists your devices without it. A registration is removed when you sign out on that phone or browser, when you sign out everywhere, when the push service reports it is no longer in use, when you register more than ten, and when you delete your account, which removes your notification choices too.
• No images or files. Members cannot upload images or files to the app.

What the phone apps send

The iOS and Android apps can send two things about themselves: crash reports, through Firebase Crashlytics, and usage statistics, through Google Analytics for Firebase. Neither is sent until you allow it. This website, the app in a browser and the Decades desktop app send neither, so they never ask.

Asking first

The first time you sign in on a phone, the app asks once: Allow turns both on, Not now leaves both off, and Choose lets you turn each on by itself. You can change either at any time in the app's Settings › Privacy and data, where Crash reports and Usage statistics each have a switch. Turning one on takes effect at once; turning one off takes effect from the next time the app starts.

The choice is kept on the phone rather than with your account, so it holds for whoever signs in there, and nothing about it is stored by Decades. Removing the app forgets it, and a new install asks again.

Crash reports

A crash report carries what the app was doing when it crashed — the stack trace and the app's state at that moment — with the phone's model and system version, and an installation ID Crashlytics uses to count how many installs a crash reached. It carries no user ID and nothing about your account. If the app crashes while crash reports are off, including before you have been asked, the report is kept on the phone, unsent: it is sent if you later turn crash reports on, and answering Not now, or choosing with crash reports left off, deletes it.

Usage statistics

Usage statistics are Google Analytics for Firebase's automatic events and nothing more: when the app is first opened or updated, sessions and time spent in it, and screen views that record the app's window rather than which of its screens you use, with what Firebase attaches on its own — the phone's model, its system and app versions, and a rough location Google works out from the connection's masked IP address. On Android, the first open also says where the app was installed from, such as the Play Store, and any campaign tag the install link carried; Decades runs no ads, so most installs carry none. The app sets no user ID and sends no events of its own, and nothing about your account, your characters or your Discord is sent, so nothing Analytics holds is tied to you.

Google uses it only to run Analytics for the app. Decades' Google Analytics is linked to no Google Ads account, keeps Google signals off, and has every data-sharing setting turned off, including sharing with other Google products and services. Neither app reads an advertising identifier or asks to track you. Google keeps each event for two months, the shortest it offers; the summary reports built from them are kept beyond that, and what was sent before you turned usage statistics off is not removed.

Registering the installation

Because the apps include Analytics, Firebase also registers each installation of the app with Decades' Firebase project when it starts, before you are asked and whatever you choose: that sends an installation ID, the app's ID and a description of the phone — what kind of phone it is and its system version, and on Android also its brand, which Firebase components the app uses and their versions, and the app that installed it, such as the Play Store. Nothing about your account is sent. That installation ID is also the address push notifications are delivered to, so if you turn push on for that phone, the app keeps it with your account, as the push item above describes.

Because crash reports and usage statistics are tied to no account, your data export does not include them and deleting your account does not remove them.

Where it is kept

On Google Cloud, in the United States: the database in Google's US multi-region and the app's servers in Iowa. The guild is spread across the US, so that is the sensible middle. If you are outside the US, your information is stored there.

The services involved in running the app are:

• Google Firebase and Google Cloud — sign-in, the database, hosting, the API and its logs, and push delivery through Firebase Cloud Messaging. Google processes this on our behalf under its Firebase privacy terms.
• Google's AI platform — rewording requested feedback, as described above, in the US, on the guild's own Google Cloud account.
• Google Analytics for Firebase — the iOS and Android apps' usage statistics, described above, only once you allow them. Google uses it only to run Analytics for the app: it is linked to no advertising account and shared with no other Google product.
• Firebase Crashlytics — the iOS and Android apps' crash reports, described above, only once you allow them.
• Discord — to sign you in and to confirm your membership of the Decades server and your roles.
• Apple and Google — when your account uses one of them to sign in.
• Apple's push service, and your browser's — to deliver push notifications to iPhones and to browsers you turned them on for.
• Your mobile carrier — if you sign in on a phone with a phone number, to deliver the code.

Requests to the app pass through a Google load balancer that sees your IP address and applies rate limiting, and the server keeps operational logs of requests and errors, including each request's full address — so a search for a crafter is in them. Those exist to keep the service up and to fix it when it breaks. They are not used to build a picture of you, and errors shown to you never carry internal detail.

How long it is kept

What the app holds about you is kept while you have an account. What deleting it removes, and what stays, is set out under Deleting your account.

Some things outlive an account, by design. Characters survive, unlinked from you, because raid history belongs to the character and is shared with everyone who raided beside them. The guild's own records of you, such as officers' feedback and the messages you wrote to the guild, stay as the guild's. Who gave each quick rating, and the original words of requested feedback with who wrote them, are kept for good.

A guild bank request is deleted 90 days after it closes, a few working records the desktop app holds expire on their own, and Google keeps the phone apps' usage statistics for two months.

Your data, your choices

You can edit your profile, characters and availability yourself at any time. If something an officer recorded is wrong, ask an officer to correct it.

The app lets you export your own data — everything you wrote, gave, asked, answered, chose and own, including what the desktop app uploaded for you and any account merged into yours, with no credentials in it. It leaves out what would reveal another member's choices, such as their votes or ratings of you, and the guild's own deliberation about members, such as officers' notes. You can also sign out everywhere, which signs the device you are using out at once, ends your other sessions within an hour, and removes every phone and browser registered for push, and delete your account yourself, which requires a recent sign-in and a typed confirmation so it cannot happen by accident (below).

If you end up with two accounts, they can be merged: you merge them yourself once you have proved both are yours, or an Admin does at your request when both are linked to Discord. A merge moves what the second account holds into the one kept, along with its other ways to sign in, then deletes the second account and its sessions. The account kept keeps its own rank; the other's is dropped. A merge cannot be undone, and the guild's record of it names both accounts.

Removing a phone app signs you out there, and its next install starts signed out. It deletes nothing from your account.

Deleting your account cannot remove anything from Discord, Blizzard or any other service we do not control, and signing out of a browser is not by itself proof that anything was deleted on the server. We would rather say that than let a delete button imply more than it does.

Depending on where you live you may have further rights over your information. Ask us and we will do what we can.

Deleting your account

This is how to delete your account in the Decades App, listed as Decades GuildOps on Google Play, by Decades Guild, and on the App Store, by John Anderson. You delete it yourself, and you do not need the phone app to do it.

How to delete it

1. Sign in to the Decades App on the web, at app.decades.gg, with Discord. Signing in on the web needs no app, so this works even if you have removed it.
2. Open Account, or go straight to app.decades.gg/settings.
3. Under Delete your account, press Delete my account, type DELETE MY ACCOUNT exactly as shown, and confirm.

You can do the same in the iOS and Android apps, in Settings — the gear at the top of Profile, or of any screen while you are joining — under Delete your account. If you only ever signed in on a phone with Apple, Google or a phone number and never linked Discord, the web cannot reach your account, so delete it in the phone app.

Deleting always needs you signed in, with a sign-in from the last 15 minutes — if yours is older, sign out and back in first. That is how a deletion is proved to be yours. There is no way to ask for a deletion without signing in, by email, in Discord or otherwise, because we could not tell someone who has lost their sign-in apart from someone trying to delete another member's account.

What deleting removes

• Your sign-in, and every session signed in with it.
• Your account record, your profile and real-life name, and the guild's record of your Discord link.
• Your availability, your weekly signups and your application, with your own words as a recruit and the vouches you gave and received.
• Every phone and browser registered for push, your notification choices, and your Inbox.
• Your signups for community events, your LFG joins, your votes on polls still open, your sims, your accolades, your open guild bank requests, your posts in the loot council's chat, and the ideas and bug reports you sent.
• Questions you asked that were not answered and published, unless you asked them anonymously, and your replies to named questions.
• Characters you submitted that were never approved. They were never placed in a raid, so they carry no history.
• What the Decades desktop app uploaded for you. A game event other members also recorded loses your part in it; one nobody else recorded is deleted.

What stays, and why

• Your approved characters are archived, not deleted. Each loses you as its owner and keeps its name, its class and its history, because raid history belongs to the characters and is shared with everyone who raided beside them. Published weeks and the guild's raid history stay intact for the same reason.
• Feedback officers have written about you stays, with interview notes and the guild feedback about you, and so do your characters' officer notes in Decades, read from the game, and their history. So does the guild's history of you, such as raids you led and who moved you in and out. These are records of what the guild's officers did rather than records you own, and they outlive an account the way a completed raid keeps its lead.
• Who you rated stays, kept outside the app as described above, as do the original words of feedback you wrote; what of it was passed on stays with no name on it. A chart keeps your ratings until it next changes.
• Your radar chart stays: what the guild says about you is kept.
• Messages you wrote to the guild stay, with their author shown as Former member, and so do polls you made and answers you wrote to questions. They are the guild's words to its members.
• Some things stay without your name: votes on closed polls, so results stand; questions that were answered and published; anonymous questions and replies; LFG posts and events you started; and closed guild bank requests, without their reason, until their 90 days run out.
• The guild's roster and bank, as your Decades desktop app read them from the game, stay, being the guild's.
• Nothing outside Decades is touched. Deleting cannot remove anything from Discord — your Discord account, server membership and roles are untouched — or from Blizzard or any other service we do not control. Crash reports and usage statistics from the phone apps are tied to no account, so there is nothing of them to remove.
• Sign in with Apple. If your account has Sign in with Apple, deleting in the iOS app also withdraws Decades' access to your Apple Account. Where that does not happen — on the web or Android, or if the iOS app cannot do it — the deletion still completes, and you are told how to withdraw it yourself at account.apple.com.

A deletion cannot be undone. Signing in again afterwards starts a new account, with none of what deletion removed.

Children

You must be at least 13 to hold an account, matching Discord's own minimum. We do not knowingly collect information from anyone younger. If you believe a child under 13 has an account, tell us and we will remove it.

Links away from here

Our Discord invite and the official game links take you to services we do not operate. What you share there is governed by their terms, not this policy.

Changes to this policy

This policy changes when what the website or the Decades App does changes. The date at the top is the current version, and any change that affects members is announced in Discord.

Contact

Questions about this policy, or a request about your information, go to support@decades.gg, which reaches the guild master and the app's builder, including if you are no longer in the Discord server. Members can also ask guild leadership in the Decades Discord. To delete your account, follow the steps under Deleting your account.