1. Who we are
Forever Sync is run by Plats Gaming. We decide how your data is used (we are its "controller"). This policy covers foreversync.app, guild subdomains and guild sites on their own domains, our bot, free tools, addon and desktop app. Questions and requests go to [email protected].
2. What we keep
When you sign in
- Your Discord ID, username, display name and avatar, received through Discord OAuth.
- Which of your Discord servers are linked to a Forever Sync guild, and your roles there, to check membership and the access your guild grants.
- If you sign in with Google to set up a guild: your Google account ID and email address.
- If you connect Battle.net: your Battle.net account ID and BattleTag, to recognise your account and link it to your Forever Sync sign-in. With your permission, we read your World of Warcraft Forever characters and their guilds from Blizzard, to help you choose a guild and to verify which roster characters are yours. Your Battle.net access token is used only for that request and is not stored.
From the game
Free member armories may use Blizzard character summaries, equipment, talents, statistics and character images. Images are served by Forever Sync. Blizzard armory data is refreshed or deleted within 30 days. You can remove it from My characters; removal also stops future armory collection for those characters in that guild. Unlinking Battle.net or deleting your account removes its cached armory data across guilds. A minimal character-ID opt-out prevents recollection; image files are removed by the retention job and stop being served immediately. Data from Blizzard does not imply Blizzard endorsement.
- If the guild connects Battle.net: its roster from Blizzard (character names and surnames, character IDs, levels, classes and guild ranks), to start the roster and keep it fresh. It shows only on the guild's members-only roster, may be incomplete or late, and the addon's data wins where the same character can be matched. A verification mark never grants membership or officer access.
- The guild roster, your characters' names, and what the addon records about them for your guild: class, level, rank, professions, events and sign-ups, attendance, DKP, loot and the guild bank.
- Only the kinds of data your guild chooses to share. Officer-only notes in the addon never leave the game.
- Which of your characters you link to your Discord account.
Game data comes from the free addon through the desktop app or imports, and from your guild's officers. Officers control which data is shared and who can access it.
Discord IDs and character names are personal data, and we treat them that way. Public pages show counts and the class mix, never member names. Guild member names show only to signed-in members of that guild. Free public tools use sample names; anyone with a shared tool link can view its shared content. Do not put member names or private data in public shares.
First-party page analytics
We measure visits ourselves, without third-party analytics scripts or new cookies. For 90 days we keep the time and day, site host and page path, campaign tags (utm_source, utm_medium and utm_campaign), referring host only, country, device category and browser family. Other query strings, full referrer URLs, IP addresses and full user agents are not stored in analytics.
A daily salted hash of IP address and user agent estimates daily people. The random salt stays in server memory, rotates daily and is never saved with visits. If signed in, visits include your Discord ID and the guild site. Only the site owner can see this activity. New shared links also record their creator, guild, country and visit source for owner moderation; older links have no creator history. Shared-link attribution stays with the link until deletion; links not opened for 180 days are deleted.
From the app
- The name of each PC you connect, its app version, and when it last sent an update.
When you apply to a guild
- What you write in the application. The guild's officers see it.
What you post or upload
We store guild pages, posts, messages and uploaded images, such as crests, banners and screenshots, along with their authorship. Content published by officers can be public; member and officer areas require the appropriate access.
When you pay
- Who paid (your Discord ID), for which guild, how much, when, payment and subscription status, and Stripe's reference for the payment. We never see or keep card details: Stripe and Link hold those.
To keep the service running
- Session records, including a hashed sign-in token and expiry, to keep you signed in.
- Server logs, such as IP addresses, to spot abuse and fix problems.
- If you accept it: which link first brought you here (its campaign tags, the kind of page you landed on and the date), saved with a guild you create, so we can see which links bring guilds.
3. Why we keep it
- To run your guild's site and bot. That is the service your guild asked for (our contract with the guild, and our legitimate interest in running it for its members).
- To take payments and keep the records tax and accounting law requires.
- To keep Forever Sync safe: stopping abuse, and checking that officer data comes only from officers.
We never sell your data, and we never use it for ads.
4. Who else handles it
- Stripe and Link take payments, through Stripe Managed Payments. Stripe, through Link, its checkout, is the merchant of record for each sale, and has its own privacy policy for the payment details it holds.
- Discord, for signing in and for the bot.
- Google, if you choose to sign in with Google.
- Cloudflare, for CDN delivery, DNS and protection from attacks. Cloudflare Web Analytics provides aggregate traffic counts with a cookieless beacon.
We host the service on servers we operate in the United States, so your data is stored and handled there. These companies may handle it in other countries too, under their own safeguards.
5. How long we keep it
- While your guild uses Forever Sync, we keep what it needs.
- When a guild's Plus ends, it continues on Free and its data and uploads are kept. Plus ending never triggers deletion; we delete a guild's data when its owner asks, as described below. Sign-in accounts and connected-device records are separate and stay until you ask us to delete them.
- Sign-in sessions end when you sign out or when they expire. We retain account and connected-device records while needed to provide access, unless you request deletion.
- We handle deletion requests as described below. We may retain records needed for legal obligations, security or disputes.
6. Your rights: a copy, or deletion
You can ask for a copy of the data we hold about you, ask us to correct it, or ask us to delete it. Under the GDPR and similar laws you can also object to how we use it, or ask us to limit it. Email [email protected] and tell us which Discord account the data is about. We may ask you to prove it's you. We answer within 30 days.
One thing to know: your guild's game data also lives in your guildmates' addons, inside the game. We can delete it from Forever Sync, but not from their games. Requests about payment records held by Stripe/Link go through Stripe/Link and are subject to their retention rules.
If you're not happy with our answer, you can complain to the data protection authority where you live.
7. Cookies
We use one cookie to keep you signed in, and a few short-lived ones that protect each sign-in and setup step. Only if you choose Accept on the bar that asks, we set a first-party cookie for up to 90 days that remembers which link first brought you to Forever Sync, and save its campaign tags, the kind of page you landed on and the date with a guild you create. Reject sets nothing. There are no ad cookies and nothing goes to ad networks; Cloudflare Web Analytics does not use cookies.
8. Children
Forever Sync is not meant for anyone under 13, and you must also meet Discord's minimum age in your country. If you think a child has given us data, tell us and we'll delete it.
9. Security
We use encrypted connections, hashed session tokens and access checks to protect data. No system is completely secure. Report suspected misuse to [email protected].
10. Changes
If we change this policy in a way that matters, we will say so on this page and in every guild's Admin before it takes effect.