Privacy Policy

Last updated: October 30, 2026 (v1.4.0)

What's changing on 1 December 2026

  • Refunds: our full Refund Policy now applies. If you ask for a service to start straight away and tick the waiver box, you give up the 14-day cancellation right for it. Repeatedly buying, using and cancelling can be refused.
  • Under-18s need a parent’s permission to buy, and can get a full refund, no questions asked: for a subscription any time during the period paid for, for a one-off purchase within 30 days.
  • Failed payments: the fixed 72-hour grace period is replaced by a short grace period while the payment is retried. Premium access continues during that retry.
  • TackyCoins can’t be bought with money. Spending them is final, and what they can buy may change.
  • New things we hold or show: optional Roblox verification (in leagues that use Roblox names, your verified name is shown publicly), where you heard about us, and your age range (we never keep your birth month or year). Under-16s never get optional cookies.
  • Our Discord bots changed: Tacktonic was switched off, and TackyHUB and LineLab are now covered. Some bot data is kept longer, and public rosters can show Discord names and avatars.
  • New service providers: Google AdSense for ads (replacing Mediavine), Sightengine for image checks, and Anthropic for the optional AI assistant.
  • New: no scraping, bulk copying, or using the site, API or content to build or train a competing service (takes effect 1 December 2026).
  • If you don’t accept the new version, your account is no longer frozen after 30 days; you just can’t make changes until you accept.

These changes are already shown in the text below, except where a section is marked (takes effect 1 December 2026). On or after that date we’ll ask you to accept the updated Terms and Privacy Policy before you can make changes on the site; your privacy rights and your right to download your data are unchanged.

Plain-language summary. TackyLeague is a game-sports news and league-management platform for esports communities worldwide, run by TackyLeague in Belgium. We collect the data needed to run the site — your account, your profile, your league data, your live-chat activity, your TackyCoins, payment data for paid plans, and minimal usage logs.

We do not sell your data. We do not use Google Cloud Platform for storage — everything lives on our own EU-based servers in Belgium. We use subprocessors only where we must: Stripe for payments, Discord/Google for OAuth, Sentry for crash reporting, Cloudflare for security/CDN and cookieless web analytics, Google Analytics 4 for site analytics (only with your consent), and Google AdSense for audience engagement and, from around August 2026, display advertising (governed by its own consent prompt for EU/UK visitors).

You have full GDPR rights (access, delete, export, object) — see Section 5. Deletion runs through a 30-day soft-delete grace period: your account is deactivated immediately and permanently deleted after 30 days unless you restore it via the recovery link we email you (see Section 6.1). Questions: [email protected].

Table of Contents

Contents

Expand All Collapse All

1. Controller

  • Controller: TackyLeague — established in Belgium.
  • Contact: [email protected]
  • Location: Belgium
  • No formal Data Protection Officer. We are not required to appoint one under GDPR Art. 37 (we are not a public authority, our core activities do not involve large-scale systematic monitoring of EU citizens at a scale that triggers Art. 37, and we do not process special-category data on a large scale). The controller contact above handles privacy questions.

Where this Privacy Policy speaks of the "controller contact" we are referring to the operator-level contact above, not a formal DPO appointment. We have deliberately not appointed a DPO; doing so would trigger GDPR Art. 38–39 institutional protections that exceed our current scale and are not required by law.

2. Information We Collect

2.1 Account & Authentication Data

  • Email/password registration: email address, display name, password (passwords are securely hashed — we never store plaintext passwords).
  • Google OAuth: Google account email, display name, profile photo URL.
  • Discord OAuth: Discord user ID, username, global display name, avatar URL, email, guild memberships (for role detection).
  • Account linking: if you link multiple sign-in methods, we store the association.
  • Email verification status and login timestamps.

2.2 Profile & TackyCoins Data

  • Global profile: display name, TC balance, total earned/spent, login streak, best login streak, last login date.
  • Cosmetics: owned items, currently equipped cosmetics.
  • Redemption history: item ID, name, category, TC price, timestamp for each TC shop redemption.
  • Daily reward tracking: counts of rewards per category, last reward date.
  • Milestone completion: completed milestone IDs.

2.3 League & Player Data

  • Player profiles: name, team, position, stats (pace/shooting/passing/defending/physical), tier/rating, contract terms.
  • Team data: name, logo URL, budget, wages, roster.
  • League data: name, slug, description, logo, game platform, owner ID, subscription status, active modules.
  • Competition data: fixtures, results, standings, formats.
  • Transfer data: offers, fees, acceptance status, movement records.

2.4 Live Chat Data (retired — separate profile within the same account)

Status (September 2026). The live-match system was retired on 22 August 2026 — /live redirects to the home page and no new live-chat data is being created. This section is retained because data created before that date may still be held, and it remains subject to your rights in Section 5 and the retention rules in Section 6. The description below is written in the present tense because it describes that retained data.

The live-match chat system uses your main TackyLeague account — there is no separate username/password for live chat. However, live chat maintains its own profile data alongside your main profile, with a different display name and progression that are not shared with the main site profile:

  • Live chat display name — set the first time you join live chat. Independent of your main account display name.
  • Messages: message text, timestamp, sender, equipped cosmetics at time of sending.
  • Points economy ("cookies"): balance, total earned/spent, watch time, messages sent.
  • Shop data: items purchased with cookies, equipped cosmetics (separate cosmetic inventory from the main TackyCoins shop).
  • Activity data: daily bonus count, last login date, milestone progress, quiz/poll participation.

Because the live chat surface shares the main account, acceptance of the Terms and this Privacy Policy at main-account signup also covers live chat. We do not require a separate live-chat consent moment.

(Correction note: an earlier version of this Privacy Policy described live chat as a "separate account" with its own username and password. That described an older system design. The current system shares the main account; only the profile data and cosmetics inventory are separate.)

2.5 Comments & Content Data

  • Comments: article ID, author ID, author display name, comment text, likes/dislikes, cosmetics snapshot.
  • Content reports: reporter ID, content ID, content type, reason, review status.

2.6 Usage & Analytics Data

  • Article views: view count (not individually tracked per user).
  • Rulebook views: view count.
  • Ad interactions: impressions and clicks, deduplicated per session in browser session storage, only when you have consented. The server-side event record contains no user identifier and no IP address.
  • Stream watch time: minutes watched per live stream session (in the live chat system).
  • Site analytics (Google Analytics 4): pseudonymous usage data (pages viewed, device/browser type, approximate location, referral source) — only after you consent via the cookie banner. See Section 2.19.
  • Advertising (Google AdSense): advertising cookies and pseudonymous identifiers — governed by Google's certified consent prompt for EU/UK visitors. See Section 2.19.
  • How you found us (sign-up source): when you create an account we record, once, the campaign tags of the link you arrived on (utm_source / utm_medium / utm_campaign), or the name of the website that sent you (never the full address), and your optional answer to "How did you hear about us?". We use it only to count which channels bring new members. Only you and site administrators can see it on your profile. Campaign tags are remembered between visits only after you click "Accept All"; for accounts aged 13–15 only the optional answer is kept.
  • Aggregate performance analytics (Cloudflare Web Analytics): cookieless, aggregate-only page metrics — no identifier is stored on your device. See Section 2.19.

2.7 Payment & Subscription Data

  • Payment identifier: an internal identifier (Stripe Customer ID) associated with your account.
  • Subscription records: plan, billing periods, status (active / past_due / cancelled / trialing).
  • Add-on records: active add-on modules.
  • We do NOT store card numbers, CVV, or full payment details. All payment processing is handled by Stripe (PCI-DSS certified).

2.8 Moderation Data

  • Bans: user ID, email, scope, reason, issuing moderator, dates, expiry.
  • Warnings: user ID, warning message, issuing moderator, date, seen status.
  • Automod logs: profanity detections, link blocks, spam detections.
  • DSA Art. 17 statement-of-reasons records: preserved for 6 months per row.

2.9 Scoreboard Data

  • OBS scoreboards: team names, scores, match status, timing data, template, league association. Scoreboards are viewable via public OBS overlay URLs.

2.10 Discord Bot Data (Tackify, TackyHUB, LineLab & the retired Tacktonic)

  • Tacktonic (retired October 4, 2026): our former companion bot was switched off on October 4, 2026 and left every Discord server it was in. Role sync, the league directory and Career Mode alerts now run in Tackify (see the Tackify entry below); its free agent sync, its /lft list command and its full member directory scan were switched off with it. Tacktonic had no database of its own: everything it saved went through our API into our main database, is covered by this Policy, and was not deleted when Tacktonic was switched off. We keep what Tackify or the website still uses. What only Tacktonic needed is kept for 30 days after the switch off, in case we have to turn it back on, and is then deleted on or after November 15, 2026: records that you allowed Tacktonic direct messages, and the free agent and team role holder entries that no bot has updated since October 4, 2026. Each kind of data is:
    • Server details for the league directory: server ID, name, icon, member count and owner ID. Tackify now keeps the name, icon and member count up to date. Kept to run the directory and to let a server be listed again, and deleted on request.
    • Team role holders: for each connected league, the Discord user ID, server nickname or display name, avatar and team roles of members holding a team role, including people without a TackyLeague account. This list feeds the league's rosters and the check of who holds a team role; Tackify still updates a member's entry when their team roles change. An entry that no bot has updated since October 4, 2026 is deleted on or after November 15, 2026. An entry Tackify has updated since then is kept while the league exists, and deleted with the league or on request.
    • Free agents: the Discord user ID, display name and avatar of members who held a league's free agent role or listed themselves with /lft. An entry that no bot has updated since October 4, 2026 is deleted on or after November 15, 2026. Any other entry is kept until the listing is removed or the league is deleted. Ask us and we remove it sooner.
    • Account links made with /link: kept while both the Discord account and the TackyLeague account exist.
    • Career Mode and membership alerts (transfer offers, contract changes, free agent applications, league membership decisions) sent to people who had linked their Discord account: recipient Discord ID, event type, league ID, time and delivery status, kept until the recipient's account is deleted.
    • Direct message records: whether you allowed or switched off Tacktonic direct messages (your Discord ID, the bot, the time and how it was recorded), and a log of the messages it sent or held back (recipient, message type, time and outcome, never the message text). The log, and the booking record behind each message, are deleted after about 180 days; if you delete your account before then, the Discord ID in the booking record is replaced with a code. A record that you allowed Tacktonic messages is deleted on or after November 15, 2026, or sooner when you delete your account or ask us to. A record that you switched messages off is kept even after your account is deleted (your Discord ID and the opt out only), so that choice can never be lost.
    • Logs: its error reports are deleted after about 30 days; its server logs are deleted when we remove the switched off service.
    We keep the team role holder and free agent entries of people who never linked an account, for as long as set out above, on the basis of our legitimate interest (Art. 6(1)(f)) in showing accurate league rosters and letting league staff see who holds a team role; Tacktonic only ever read Discord IDs, names, avatars and roles, never messages. You can object to this at any time (Section 5). The standalone Tacktonic Privacy Policy is replaced by a short retirement notice.
  • Tackify: when added to a Discord server, we collect team configs, player data, match results, role assignments. See the Tackify Privacy Policy. Tackify has also taken over three jobs from the retired Tacktonic: it keeps the league directory's server details up to date (server name, icon, member count and which bot permissions are missing), keeps team roles and league membership in sync with the website, and, for leagues that still have the original Career Mode switched on, sends Career Mode alerts (contracts and offers) by direct message to people who have linked their Discord account. The Tackify Privacy Policy sets out the data, purpose, legal basis and retention for each job. You can switch off each alert type, or all Tackify direct messages, in Profile > Settings > Alerts.
  • TackyHUB: TackyHUB is the directory companion bot for league listings on /leagues. For each server it is in, it sends our API the server ID, member count, server icon and server banner; for servers that have a directory listing these are saved on the listing (the banner only where the listing uses the Discord server banner) and refreshed about once an hour. Servers without a listing are not saved, apart from a status entry in our bot audit log each time TackyHUB starts (server ID, server name, member count). To verify a listing, TackyHUB checks whether the Discord account that submitted it is a member of the server with the Administrator permission, and we store only the result (verified or not, the reason, and the time). Once a night it checks that the listing's saved Discord invite still works; if it has expired, TackyHUB uses the server's vanity invite or creates a new permanent invite in a channel it can access, saves that invite link on the listing, and the listing owner is notified on the website. When someone runs /bump, the server ID and that member's Discord user ID are sent to our API; we update the listing's last-bump time and bump count, and, where per-member bump tracking is switched on, we record that member's Discord user ID with the server and the time to apply a per-member cooldown and calculate the server's activity streak. If TackyHUB is removed from a server, the listing is marked unverified and the listing owner is notified on the website. TackyHUB may post one announcement in the server when a listing is first verified, replies to /bump in the channel where it was run, never sends direct messages, and does not read or store message content. Verification results, bumps and invite changes are also written to our bot audit log, which is deleted after 90 days (Section 6). This Privacy Policy is TackyHUB's privacy policy; there is no separate one.
  • LineLab: LineLab draws lineup graphics in Discord with /lineup. To draw an image it uses the server nickname and avatar of the members the command user picks, any names typed in by hand, the name, colour and icon of the team role they choose, and the server icon. These are held in memory only while the image is built and are not stored by us; the finished image is posted in the channel only after the command user confirms the preview. If the command user turns on Roblox avatars, LineLab sends possible Roblox usernames (each picked member's server nickname and parts of it, such as the name after a team tag, plus any names typed in by hand) to Roblox's public user-lookup service, and downloads the matching Roblox avatar picture from Roblox. No Discord IDs are sent to Roblox. If the command user supplies an image link, LineLab downloads the image from that address. To count renders against the free monthly allowance and a daily abuse limit, we store the command user's Discord user ID with a daily and a monthly render count; daily counts are deleted after 40 days and monthly counts after about 13 months. LineLab never sends direct messages and does not read or store message content. This Privacy Policy is LineLab's privacy policy; there is no separate one.
  • Role management: when team roles are renamed via the website dashboard, the bot accesses Discord role data to apply the rename. Role IDs are stored to maintain the database↔role association.
  • Public roster display: public league pages may display the Discord display name and avatar of members of a connected server, including people without a TackyLeague account, where the league owner has enabled the roster view. We do not publish Discord account IDs on these pages, and avatars are served through our own systems rather than linking to Discord.

2.11 Streaming Configuration Data

  • Stream settings: platform (Twitch/YouTube), channel/video IDs, accent colours, background images, banner text, rich-text descriptions configured by League Owners.
  • YouTube embeds: video URLs and titles added by League Owners.

2.12 Career-Mode Data

  • Contracts & offers: terms, sender, recipient, status, loan agreements.
  • Free-agent data: registration status, availability, interested leagues.
  • Proxy players: Discord ID, display name, team assignment (created by managers on behalf of unregistered players). The proxy invite is delivered as a shareable link the manager forwards via their league Discord — we do not cold-DM the proxy.

2.13 Donation & Sponsorship Data

  • Donations: amount, tier, date, Stripe transaction ID. No card data stored.
  • Sponsor inquiries: name, email, company, preferred placement, duration, message submitted via the advertiser inquiry form.

2.14 Logo Builder Data

  • Projects: logo designs, template, text, colours, exported images.
  • Credits: purchase history, balance, usage records.

2.15 Notification Data

  • In-app notifications: content, read status, timestamps. Auto-deleted after a retention period (read: 30 days; unread: 90 days; max 100 per user).

2.16 Consent Records

  • Signup acceptance: email/password registration requires ticking an explicit "I agree to the Terms of Service and Privacy Policy" checkbox. For Google/Discord OAuth sign-ups, a blocking acceptance gate requires you to accept the Terms and this Privacy Policy before you can use the Platform.
  • Consent log (live): we maintain an append-only consent log recording each consent event (user, timestamp, the document version shown, and acceptance workflow), retained for the lifetime of the account + 7 years for legal-claim defence (GDPR Art. 17(3)(b)/(e)). A material version change triggers a re-acceptance prompt, and a server-side gate blocks data-changing actions until you have accepted the current version.

2.17 Special-Category Data (Art. 9)

We do not process special-category data (health, race, religion, biometric, sexual-orientation, criminal-conviction). If a user-provided field (a chat message, a comment, a team description) incidentally contains it, we treat that as outside the intended scope and may remove on report.

2.18 Sentry Crash and Replay Data

Errors and exceptions are sent to Sentry for debugging. Sentry's session-replay feature is consent-gated: the replay recorder is only initialised after you click Accept All in the cookie banner, and even then captures only obfuscated recordings around errors (text is masked and media blocked, so input fields and embedded media are not recorded; ~10% of error sessions). Choosing Essential Only means the replay recorder never loads, and withdrawing consent later (footer → Cookie settings → Essential Only) stops it. Error reporting without replay runs under our legitimate interest (Art. 6(1)(f)). See Cookie Policy Section 2.2.

2.19 Web Analytics & Advertising Technology

Google Analytics 4 (Google LLC). We use GA4 to understand how the site is used. When you consent (cookie banner → Accept All), GA4 sets the cookies _ga and _ga_BWDE9L3NVN and collects: a pseudonymous client identifier, pages viewed, interaction events, device and browser type, referral source, and approximate location (country/region/city derived transiently from your IP address — GA4 does not log or store the IP address itself). We do not send your name, email address, TackyLeague account ID, or any profile data to Google Analytics. Google Signals and ads-personalization are not enabled on our Analytics property, so GA4 builds no cross-device advertising profile from your visit. Our site signals Google's advertising consent states (ad_storage, ad_user_data, ad_personalization) as denied by default; they are granted only if you consent through the separate advertising consent prompt described below, and that consent applies to advertising, not to Analytics. Google processes this data as our processor under the Google Ads Data Processing Terms. If you choose "Essential Only" (or make no choice), the Google Analytics script is not loaded at all: nothing is sent to Google Analytics, no cookies are set and no identifier is stored on your device.

Google AdSense (Google LLC). We use Google AdSense to display advertising on this site. Third-party vendors, including Google, use cookies to serve ads based on your prior visits to this website or other websites. Google's use of advertising cookies enables it and its partners to serve ads to you based on your visit to this site and/or other sites on the Internet. You may opt out of personalised advertising at any time in Google Ads Settings, and you can opt out of some third-party vendors' use of cookies for personalised advertising at aboutads.info/choices.

For visitors in the EEA and UK, advertising cookies are not set until you consent through Google's certified consent prompt (a Google-certified Consent Management Platform operating under the IAB Transparency & Consent Framework v2.2). Until you consent, our site signals ad_storage, ad_user_data and ad_personalization as denied by default (Google Consent Mode v2) and no advertising identifier is stored on your device. If you decline, you may still see non-personalised ads — chosen from the content of the page and your approximate (coarse) location, not from a profile of you. When ads are served with your consent, Google may collect: IP address, device and browser type, operating system, approximate location, the pages you view on this site, and your interactions with ads. See Google's advertising technologies and how Google uses data from sites that use its services. For interest-based advertising, Google and its advertising partners may act as independent controllers of the advertising data they collect under the consent you give through Google's prompt; see the Subprocessor List.

Change note (August 2026): until 2026-08-13 this site used Grow by Mediavine for audience engagement, and Mediavine was named here as our prospective advertising provider. Grow was removed on 2026-08-13 and set no advertising identifiers during the period it ran. Google AdSense replaces it, and advertising consent is now handled by Google's certified prompt rather than Mediavine's.

Cloudflare Web Analytics (Cloudflare, Inc.). A cookieless measurement beacon. It sets no cookies, no localStorage keys, and uses no fingerprinting; we receive only aggregate metrics (page views, load performance, country-level origin). Because it stores nothing on your device, it does not require consent under ePrivacy Art. 5(3); the processing runs under our legitimate interest (Art. 6(1)(f)) in understanding site performance.

2.20 Automated Image Screening

Images uploaded to the Platform may be screened automatically for unsafe or illegal content, using the third-party service described below. Where screening runs, it applies to league and team logos, banners, profile and player avatars, article cover images, and poll images. It does not run on every upload: an image that has already been checked, or that is unchanged from one we have seen, is skipped, and the service can be unavailable. Screening is one safeguard among several — it does not replace reporting content to us, and we do not present it as a guarantee that every image has been reviewed.

  • Who performs it: Sightengine (Kozelo SAS, Paris, France), acting as our processor.
  • What is sent: the URL of the uploaded image only. Sightengine retrieves the image from that URL itself — we do not upload the file to them, and we send no name, email address, TackyLeague account ID, or other profile data alongside it.
  • What we receive back: scores indicating the likelihood that the image contains unsafe content. We store the outcome of the check against the image, not a copy of the image at Sightengine.
  • Legal basis: legitimate interest (Art. 6(1)(f)) in keeping the Platform free of illegal and unsafe imagery, and in enforcing our Terms.

Where a check results in an image being removed or restricted, the moderation record and your right to a reasoned explanation are covered by Section 2.8 (Moderation Data). Processing details and transfer safeguards for Sightengine are listed on our Subprocessor List.

Change note (September 2026): automated image screening was previously described only on the Subprocessor List. It is set out here so that this policy, on its own, tells you that an uploaded image may be sent to a third party for screening. The processing itself is unchanged. This section was reworded the same day it was published, to say "may be screened" rather than "are screened" — the original wording asserted a guarantee we do not make.

2.21 AI Setup Assistant (beta)

League owners and staff can choose to use an AI assistant that helps them set up and run their league. It is optional and only runs when you use it. Every change it suggests is shown to you first, and nothing changes until you approve it. The assistant always tells you that it is an AI.

  • Who performs it: Anthropic (the Claude AI model), acting as our processor. Services to the EU are provided by Anthropic Ireland Limited.
  • What is sent: the messages you type to the assistant, any text or screenshots you paste in, and the league data the assistant reads to help you — team, player, competition and fixture names, scores, and the settings of the league you are working on. We never send your email address, password or payment details.
  • Training: Anthropic does not use this data to train its models.
  • How long Anthropic keeps it: deleted within 30 days, except content that Anthropic's automated systems flag as breaking its Usage Policy, which it may keep for up to 2 years.
  • What we keep: a record of each job the assistant proposed or ran, so it can be undone and audited. Names are removed from finished jobs after 30 days, and the audit log keeps no names. Your chat history stays in your browser.
  • Legal basis: contract (Art. 6(1)(b)) when you use the assistant; legitimate interest (Art. 6(1)(f)) for usage limits and abuse prevention.
  • Transfers: data may be processed in the United States, under Standard Contractual Clauses (Modules 2 and 3) plus the UK Addendum and the Swiss Addendum, as set out in Anthropic's Data Processing Addendum.

Processing details and transfer safeguards for Anthropic are listed on our Subprocessor List.

Change note (October 2026): this section was added for the AI Setup Assistant beta. During the beta, the assistant is available only on a small number of leagues invited to the beta. All other leagues can use it from 11 November 2026, after the 30-day notice in our Subprocessor List.

2.22 Roblox Verification

You can choose to prove that you own a Roblox account. It is optional. TackyLeague is not affiliated with, endorsed by, or sponsored by Roblox Corporation.

  • Way 1 — a code in your Roblox About: we give you a code. You paste it into the About text of your Roblox profile. We then read that public About text from Roblox to find the code. The code expires after 10 minutes.
  • Way 2 — Verify with CheckRo: CheckRo is TackyLeague's own Roblox verification bot. You sign in to CheckRo with the Discord account linked to your TackyLeague account and press Allow. Only after you press Allow does CheckRo share with us your Roblox username, Roblox user ID and Roblox display name, the Discord user ID it checked, how you verified on CheckRo, and when. We use the Discord user ID only to check that it matches the Discord account linked here. We do not store it again.
  • What we store on your profile: your Roblox username, Roblox user ID and Roblox display name, that the account is verified, when you verified, and which way you used. While a code check is open, we also store the username you typed, the code, and when the code expires. The code is removed when the check succeeds or when you unlink.
  • Locks against account swapping: after you verify, you cannot verify a different Roblox account for 15 days. For the same 15 days, that Roblox account cannot be verified on another TackyLeague account. To enforce this, we keep a record of the Roblox user ID, your account ID and the date the lock ends. Unlinking does not end a lock early. A site admin can end it early, for example after a Roblox ban. The record is kept after the lock ends; it no longer blocks anything.
  • Verification log: each verification through CheckRo adds a log entry with your account ID, the Roblox user ID, the method, when CheckRo verified the link, the Roblox user ID you had verified before (if any), and the time. Entries are deleted after 90 days.
  • Who can see it: in leagues that identify players by their Roblox account, we show you on the league's player lists, tier list and leaderboards by your verified Roblox username, with a "Roblox verified" tick. Anyone who views the league can see it, signed in or not. We do not show it while your profile is private or while your account is waiting to be deleted.
  • What Roblox receives: to check your account, or to update your name when you tell us it changed on Roblox, we look up the Roblox username or Roblox user ID on Roblox's public web service (Section 7).
  • How to remove it: go to Profile > Settings > Connections and press Unlink. This removes your Roblox username, Roblox user ID, Roblox display name, verified status, verification time, method, and any open code from your profile. Locks that are still running keep running, and the lock record and the verification log are kept as described above.
  • Legal basis: contract (Art. 6(1)(b)) for the verification you ask for and for showing it in your leagues; legitimate interest (Art. 6(1)(f)) for the locks and the verification log, which prevent account sharing and abuse.

Change note (October 2026): this section was added. Earlier versions of this Policy did not describe the Roblox verification data we hold.

3. How We Use Your Information

We process data for the following purposes and legal bases under GDPR Article 6:

PurposeData UsedLegal Basis (GDPR Art. 6)
Provide Platform servicesAccount, profile, league, chat dataArt. 6(1)(b) — contract
Process paymentsEmail, Stripe Customer ID, subscription dataArt. 6(1)(b) — contract
Authenticate identityAuth tokens, linked providers, emailArt. 6(1)(b) — contract
Display league dataPlayer profiles, standings, fixtures, team dataArt. 6(1)(b) — contract
Moderate contentMessages, comments, reports, bans, warningsArt. 6(1)(f) — legitimate interest
Prevent abuseRate limits, App Check (reCAPTCHA v3) scores, audit logsArt. 6(1)(f) — legitimate interest
Serve advertisementsAd impressions, clicksArt. 6(1)(a) — consent (where required)
Sentry crash + replayError traces, replay snippets when consentedArt. 6(1)(f) for error logs; Art. 6(1)(a) for session replay
Improve PlatformAnonymised usage analyticsArt. 6(1)(f) — legitimate interest
Site analytics (Google Analytics 4)Pseudonymous usage data, GA4 cookiesArt. 6(1)(a) — consent (ePrivacy Art. 5(3) for the cookies)
Interest-based advertising (Google AdSense)Advertising identifiers, device data, IP, approximate locationArt. 6(1)(a) — consent via Google's certified CMP (IAB TCF v2.2)
AI Setup Assistant (beta) — see Section 2.21Messages to the assistant, pasted text/screenshots, the league data it readsArt. 6(1)(b) — contract when you use it; Art. 6(1)(f) — legitimate interest for usage limits and abuse prevention
Aggregate site performance (Cloudflare Web Analytics)Cookieless aggregate metricsArt. 6(1)(f) — legitimate interest
Belgian tax / accounting compliancePremium records, transaction historyArt. 6(1)(c) — legal obligation
Communicate with youEmail addressArt. 6(1)(b) — contract
Record consentSignup acceptance records + append-only consent log (Section 2.16)Art. 6(1)(c) — legal obligation (Art. 7(1) burden of proof)

4. Cookies & Local Storage

We use the minimum cookies / browser storage needed to run the site. For the full per-key inventory, see the Cookie Policy. Summary:

Essential (always active)

  • Authentication session storage.
  • Firebase App Check via reCAPTCHA v3 (Google) — sets a _GRECAPTCHA cookie and loads a Google script; strictly necessary for abuse / fraud prevention.
  • Cookie-consent preference (tl_cookie_consent in localStorage).
  • User preferences (display settings, chat cosmetics).

Consent-required (off by default)

  • Google Analytics 4 — _ga / _ga_BWDE9L3NVN cookies (see Section 2.19). Off until you click "Accept All".
  • Ad impression tracking — session-deduplication keys in browser session storage.
  • Ad click tracking.
  • Google AdSense advertising identifiers — governed by Google's certified consent prompt (IAB TCF v2.2), shown to EU/UK visitors before any advertising cookie is set.
  • Sentry session replay — off by default; activates only after you click "Accept All" in the cookie banner.

Withdraw consent

You can re-open the cookie consent settings at any time via the "Cookie settings" link in the site footer. Choosing "Essential Only" disables analytics and ad tracking (and removes the Google Analytics cookies from your device) while keeping the Platform fully functional.

Third-party embeds (Twitch streams, YouTube videos) may set their own cookies according to their respective privacy policies.

5. Your Rights (GDPR)

If you are in the European Economic Area, the United Kingdom, or another jurisdiction with similar laws, you have the following rights (GDPR Arts. 15–22):

  • Right to access (Art. 15): get a copy of your data (JSON) — Profile > Settings > Data > Export My Data, or email us.
  • Right to erasure (Art. 17): delete your data via Profile > Settings > Data > Delete My Account, or email us. Deletion runs through a 30-day soft-delete grace period: your account is deactivated immediately and permanently deleted after 30 days unless you restore it via the recovery link we email you (see Section 6.1). Billing records are retained per the Belgian tax-records exception (Art. 17(3)(b)) where present — see Section 6.
  • Right to rectification (Art. 16): correct inaccurate data via Profile settings, or email us.
  • Right to data portability (Art. 20): your exported data is provided in machine-readable JSON format.
  • Right to restrict processing (Art. 18): email us.
  • Right to object (Art. 21): object to legitimate-interest processing by emailing us. We will stop unless we can demonstrate overriding grounds.
  • Right to withdraw consent (Art. 7(3)): the "Cookie settings" footer link, Google's advertising consent prompt, deleting your account, or email us.

To exercise any right: the self-service tools in Profile > Settings > Data, or email [email protected]. Some Discord bot data is stored against a Discord user ID rather than an account (for example the team role holder list in Section 2.10), and the self-service tools may not reach it: email us with your Discord user ID and we handle it by hand. This is also the way in if you have no TackyLeague account. We respond within 30 days as required by GDPR.

5.1 Lodge a Complaint

If you believe we have not properly handled your data, you have the right to lodge a complaint with our lead supervisory authority — the Data Protection Authority (APD/GBA), Belgium: dataprotectionauthority.be. You may also lodge a complaint with the supervisory authority in your country of residence.

5.2 How Analytics & Advertising Data Relates to Export / Deletion

The in-app Export My Data and Delete My Account tools cover the data we hold about your account in our own systems. Analytics and advertising data works differently, and we want to be precise about it:

  • Our own ad measurement is anonymous. First-party ad impression/click events are recorded against the ad, not against you — the server stores no user ID and no IP address with these events. There is therefore nothing account-linked to export or delete.
  • GA4 data is pseudonymous and cookie-keyed, not account-keyed. We do not send your account ID to Google Analytics, so GA4 data cannot be looked up by your TackyLeague account and is not included in your JSON export, nor removed by account deletion. To stop and remove it: withdraw consent (footer → Cookie settings → Essential Only, which also deletes the GA4 cookies from your device), clear your cookies, or install Google's Analytics opt-out browser add-on. User-level GA4 data expires automatically per the retention period in Section 6.
  • Google AdSense advertising data is controlled through Google's consent prompt. Use the prompt to withdraw consent at any time, and Google Ads Settings to turn off ad personalisation. For data-subject requests to Google directly, use Google's privacy tools; you can also reach them through us and we will pass the request on without undue delay.
  • Cloudflare Web Analytics holds no user-level data — there is nothing to export or delete.

5.3 US State Privacy Rights

TackyLeague is a small Belgian-operated service. We do not currently meet the applicability thresholds of the California Consumer Privacy Act (as amended by the CPRA) or similar US state privacy laws (which apply from certain annual-revenue, data-volume, or data-sale thresholds that we are far below). We nevertheless voluntarily extend the same rights to everyone, without requiring proof of residency:

  • Access, export, deletion, correction — the self-service tools above work identically for US users.
  • We do not sell your personal information for money.
  • When display advertising launches, interest-based advertising via Google AdSense may constitute "sharing" (cross-context behavioural advertising) as some US state laws define it. You can decline it through Google's consent prompt, which supports the IAB Global Privacy Platform (GPP) signals used by US state privacy laws and honours the Global Privacy Control (GPC) browser signal.
  • If our size ever brings us within scope of these laws, we will update this section and add any required notices and links.

6. Data Retention

Data TypeRetentionReason
Account & profile dataWhile account is activeProvide ongoing service
TackyCoins & shop dataWhile account is activeProvide ongoing service
League, team & player dataWhile league is activeProvide league management
Chat messages & live-chat dataIndefinitely (while system active)Chat history, leaderboards
CommentsWhile account is active (or until deleted)Community engagement
Subscription & payment records7 years after account deletion — archived (not deleted) to a restricted internal billing store for Belgian accounting/tax compliance, then permanently removed (see Section 6.2)Belgian tax & legal compliance
Moderation logs (bans, warnings)Duration of ban + 90 daysAbuse prevention
Content reports90 days after resolutionModeration review
DSA Art. 17 statements of reasons6 monthsRegulatory transparency
Audit logs90 daysSecurity & abuse prevention
Roblox verification on your profile (Section 2.22)Until you unlink it, or while your account is activeShow and check your verified Roblox account
Roblox account lock record (Roblox user ID, account ID, lock end date)The lock runs 15 days; the record is kept after that (no automatic deletion)Prevent account sharing
CheckRo verification log90 daysSecurity & abuse prevention
LineLab render counts (per Discord user)Daily counts: 40 days; monthly counts: about 13 monthsFree-allowance metering + abuse limits
Discord direct message log (messages sent or held back by our bots; never the message text) and the booking record behind each message sentAbout 180 daysAnti-spam limits and delivery checks
Record that you switched off a bot's direct messages (Discord ID and the opt out only)Kept, also after account deletionSo the choice is never lost
Data saved by the retired Tacktonic botAs listed for each kind of data in Section 2.10. What only Tacktonic needed is deleted on or after November 15, 2026Directory, rosters, account links, alert history
AI Setup Assistant job records (Section 2.21)Names removed from finished jobs after 30 days; the audit log keeps no names; chat history stays in your browser. At Anthropic: deleted within 30 days, except content flagged as breaking its Usage Policy (up to 2 years)Undo and audit
Error logs30 daysDebugging
Sentry session-replay (consented error sessions only — Section 2.18)30 days (Sentry side)Debugging
Ad analytics (when consented)While ad campaign is active + 90 daysCampaign measurement
Google Analytics 4 user-level dataExpires automatically after at most 14 months (Google's maximum for standard properties; the default is 2 months); cookies last up to 2 years (Google default; modern browsers cap at ~400 days — observed on this site July 2026)Site-usage analysis
Google AdSense advertising identifiers & ad dataPer Google's advertising policies and Google's published retention periods; exact cookie lifetimes are confirmed at the advertising phase and listed in the Cookie PolicyAd delivery + measurement
Cloudflare Web AnalyticsAggregate only — no user-level retentionSite performance
Anonymised analyticsIndefinitelyService improvement
Consent log rows (Section 2.16)Lifetime of account + 7 years after deletionGDPR Art. 7(1) burden of proof + legal-claim defence

6.1 Account Deletion Cascade

When you click Delete in Profile > Settings > Data, a 30-day soft-delete grace period begins:

  • Day 0 (you click Delete): your account is immediately deactivated — you are signed out, cannot log back in, are hidden from public search, and your content is hidden from public view. A recovery-link email is sent to you.
  • Recovery: using the recovery link any time before Day 30 fully restores your account and all associated data.
  • Day 25: a reminder email is sent.
  • Day 30: if you have not restored, your account and personal data are permanently hard-deleted in a single cascade across profile, comments, league memberships, career data, live-chat data, ad analytics, moderation history, and notifications, and your authentication account is deleted. This cannot be reversed.

Retained beyond hard-delete: billing/tax records (to the extent legally required — see Section 6.2), the consent log (pseudonymised on deletion, retained for the lifetime of the account + 7 years), and data subject to an active legal dispute (for the duration of the dispute).

6.2 Subscription / Payment Record Retention

Belgian accounting law generally requires 7-year retention of accounting records. When your account is deleted, your subscription and payment records are archived — not immediately deleted — to a restricted internal billing-archive store, retained for 7 years to meet this legal obligation and then permanently removed. The archive is limited to the minimum needed for accounting, tax, and legal-claim-defence purposes (GDPR Art. 17(3)(b)).

7. Data Sharing & Subprocessors

We use the following subprocessors. Each is bound by appropriate contractual safeguards.

SubprocessorRoleLocation
TackyLeague self-hosted infrastructurePrimary data storage + application runtimeBelgium (EU)
Google (Firebase Auth + App Check via reCAPTCHA v3)Authentication + abuse prevention (reCAPTCHA v3 sets a _GRECAPTCHA cookie)EU + US
StripePayment processingUS + EU
DiscordOAuth + bot platformUS (parent), global edge
Google OAuthOAuth loginEU + US
CloudflareDNS / CDN / WAF + cookieless Web AnalyticsGlobal edge
Sentry (Functional Software, Inc.)Error + crash reporting (and session replay when consented)US
Google LLC (Google Analytics 4)Site analytics (consent-gated) — see Section 2.19EU + US
Google LLC (AdSense)Display advertising, ad measurement, and advertising consent management — see Section 2.19US
Anthropic (EU services: Anthropic Ireland Limited)AI Setup Assistant (beta), only when you use it — see Section 2.21US

Roblox (not a subprocessor). Lineup graphics made with LineLab (when the command user turns on Roblox avatars) or with the Tackify lineup builder (for every member picked from the server) look up Roblox usernames and avatar pictures through Roblox Corporation's public web service in the United States. Roblox receives only the possible usernames described in Section 2.10 — no Discord IDs, emails or account data. When you verify a Roblox account (Section 2.22), we also look up the Roblox username or Roblox user ID being checked, and read that account's public profile. Roblox does not process this data on our behalf and no agreement between us and Roblox covers these lookups; Roblox's own privacy policy applies to what it receives.

We do not sell your data, and we do not share your account data (profile, league, chat, payment records) with advertisers or data brokers. With your consent, Google and its advertising partners process the advertising-technology data described in Section 2.19 — that consent is collected and withdrawable through Google's prompt, separately from anything we hold about your account.

The full list with vendor-policy links and transfer mechanisms is published at /subprocessors. Before adding any new subprocessor, we update that list; for material changes (a new processor in a new category), we give 30 days' notice via in-app banner and email before activating the processor.

Correction from the previous version: earlier versions of this Privacy Policy did not surface Sentry in the disclosed list — corrected here. Addition (v1.1, July 2026): Google Analytics 4, Grow by Mediavine, and Cloudflare Web Analytics were added to the site in July 2026 and are disclosed here — including a display-ads phase, disclosed in advance. Update (v1.2, August 2026): Grow by Mediavine was removed from the site on 2026-08-13 and our advertising provider is now Google AdSense. Advertising consent moved from Mediavine's prompt to Google's certified consent prompt, and the international-transfer basis for advertising moved from Standard Contractual Clauses to the EU–US Data Privacy Framework. Section 2.19, the lawful-basis table, the retention table and the subprocessor list were updated accordingly. Addition (v1.1.6, October 2026): Section 2.10 now covers the TackyHUB and LineLab Discord bots, and Roblox is disclosed above. LineLab (when Roblox avatars were switched on) and the Tackify lineup builder already looked up Roblox usernames and avatars; earlier versions of this Policy did not disclose it. Update (v1.1.7, October 4, 2026): the Tacktonic Discord bot was retired and the standalone Tacktonic Privacy Policy is replaced by a short retirement notice. Everything that policy said about data we still hold now sits in this Policy: Section 2.10 lists each kind of data Tacktonic saved, how long we keep it and the legal basis for keeping the entries of people without an account, and says which jobs Tackify took over. What only Tacktonic needed (records that you allowed its direct messages, and the free agent and team role holder entries no bot has updated since the switch off) is kept for a 30-day rollback window and deleted on or after November 15, 2026; records that you switched its messages off are kept. Section 6 adds the direct message log and the booking record behind each message (both about 180 days) and the kept opt out records, which only the Tacktonic and Tackify policies mentioned before. Section 5 now gives the current place of the self-service tools (Profile > Settings > Data) and the email route for data stored against a Discord user ID. Nothing we collect changed.

8. International Data Transfers

TackyLeague is operated from Belgium. Your data may be processed in the following locations:

  • Primary infrastructure — Belgium (EU). All application data remains in the EU.
  • Authentication services — Google Firebase, EU + US.
  • Stripe — payment processing in EU and US.
  • Discord — servers primarily in the United States.
  • Sentry — servers in the United States.
  • Roblox — Roblox Corporation, United States; receives only possible Roblox usernames for lineup graphics, and the Roblox username or Roblox user ID being checked when you verify a Roblox account (Sections 2.10, 2.22 and 7). This is a lookup against Roblox's public service, not a transfer under an agreement with us, so the safeguards sentence below does not cover it.
  • Cloudflare — global CDN edge nodes.
  • Google Analytics — Google LLC, United States (EU–US Data Privacy Framework and/or Standard Contractual Clauses).
  • Google AdSense — Google LLC, United States. Google is self-certified under the EU–US Data Privacy Framework (and its UK Extension and the Swiss–US DPF); Standard Contractual Clauses apply as a fallback. See Google's data-transfer frameworks.
  • Anthropic — AI Setup Assistant (beta, Section 2.21), only when you use it; may be processed in the United States under Standard Contractual Clauses (Modules 2 and 3) plus the UK Addendum and the Swiss Addendum in Anthropic's Data Processing Addendum. EU services are provided by Anthropic Ireland Limited.

All third-party services we use employ appropriate safeguards for international transfers, including Standard Contractual Clauses (SCCs) where required.

9. Children's Privacy

TackyLeague requires users to be at least 13 years old. Belgian Law of 30 July 2018, Article 7, sets Belgium's digital-consent age at 13. (Some EEA countries set the age higher; where local law requires a higher age, that local law applies for users in that jurisdiction.) We check the age requirement with a birth month and year question at signup and keep only the resulting age range (13–15, 16–17 or 18+) — never the month or year themselves. For users aged 13–15 we never ask for consent to analytics (Google Analytics), session replay or advertising cookies: they stay off.

  • We do not knowingly collect data from children under 13.
  • Under-13 discovery cascade: if we discover an under-13 account, we (a) suspend the account, (b) delete personal data within 7 calendar days, (c) where we have a reliable means of contact, notify the parent, (d) where a serious-crime context applies, notify Belgian law enforcement per DSA Art. 18.
  • If you believe a child under 13 has created an account, please contact us immediately at [email protected].
  • Users must be 18+ (or have parental consent) to purchase subscriptions or add-ons.

10. Data Security

We implement the following security measures:

  • Encryption in transit — all data transmitted via HTTPS / TLS.
  • Encryption at rest — database files on EU infrastructure with full-disk safeguards. Sensitive fields (authentication tokens, email addresses) are encrypted at rest using industry-standard encryption.
  • Authentication security — passwords securely hashed. Minimum password strength enforced.
  • Token security — third-party authentication tokens encrypted before storage.
  • Bot prevention — automated abuse-prevention checks on all relevant endpoints.
  • Input validation — all inputs validated and sanitised to prevent injection attacks.
  • Access control — server-side RBAC on all endpoints, including MFA-gated workflows for staff actions.
  • Rate limiting — request rate limits to prevent abuse.
  • Daily backups — automated daily database backups with multi-generation retention, plus regular secondary backups; all stored on EU infrastructure under our control.
  • Security headers — industry-standard security headers on all pages.
  • Live error monitoring — Sentry.
  • Incident response — breach notification within 72 hours to the APD/GBA (GDPR Art. 33), affected-individual notification where required (Art. 34).

No system is perfectly secure. We do not promise zero-incident operation; we promise to act quickly and transparently if an incident occurs.

11. Data Breach Notification

In the event of a personal-data breach likely to result in a risk to your rights and freedoms, we will:

  • Notify the Data Protection Authority (APD/GBA) within 72 hours of becoming aware of the breach, as required by GDPR Art. 33.
  • Notify affected users without undue delay via email and/or a prominent notice on the Platform, as required by GDPR Art. 34.
  • Provide details of the breach, data affected, and steps taken to mitigate impact.

12. Changes to This Policy

We may update this Policy when our practices change, when law changes, or when we add new features.

  • Minor edits (typos, clarifications, contact-detail changes) take effect on publication and are signalled by an updated version stamp at the top.
  • Material changes take effect on a date stated in a banner at the top of this document, at least 30 days after publication. Affected users receive notification via email (where we have one) and via an in-app banner. Where a change requires fresh consent, we will ask you to re-accept before it applies to you.
  • We never reduce your privacy rights without explicit consent.

13. Refunds

Subscription payments are processed by Stripe. (The full Refund Policy is now published and is the authoritative refund framework — EU Consumer Rights Directive 14-day cooling-off, per-service table, and waiver mechanics. The summary below is retained for convenience and yields to it.)

  • Refund requests should be submitted within 14 days of purchase via our contact page.
  • Refunds are evaluated on a case-by-case basis.
  • Partial-month refunds are not provided for mid-cycle cancellations; your subscription remains active until the end of the billing period.
  • If we discontinue the Platform, active subscribers will receive pro-rata refunds for unused time.

EU consumer-protection law always applies — where this section gives you less than your statutory rights (including the 14-day cooling-off right for distance contracts), your statutory rights win.

14. Contact

For privacy-related inquiries, data access requests, or to report a concern:

  • Email: [email protected]
  • Contact page: tackyleague.com/contact
  • Response target: within 30 days for GDPR-rights requests; within 14 days for general inquiries; within 72 hours for credible data-breach reports.

15. Related Documents