Privacy

• Discord only signs you in and sets up your account. Your Discord name is never shown on the site; only admins can see it.
• You pick your username. Your Discord photo stays hidden unless you turn it on.
• Visitors who aren't signed in never see names, profiles or photos.
• We keep the IP addresses you use, to stop abuse, and we say so here. They're never shown publicly.
• Nothing is sold or shared for advertising. There are no ads, analytics or tracking cookies.
• Every ban is public, with the reason.

• Your account. Your username and machine tag (both your choice; new accounts start as “player” and a number), and whether your photo is shown. From Discord: your email address, your Discord name and handle, your Discord account ID, the link to your Discord photo, and the sign-in tokens Discord gives us. Sign-in asks Discord only for your identity and email. We don't send you email.
• Sign-in sessions. Each signed-in browser has a session, stored with the IP address and browser it signed in from. A session lasts 30 days from its last renewal and is deleted when you sign out.
• IP addresses. The addresses you sign in or use the theme from, with when each was first and last seen, so admins can block abuse (including banning addresses).
• Your plays. Everything the theme sends with a passed song: the score and judgments, timing settings, lifebars, rate, your speed mod and other player options, the chart, song and pack it was on (with their banner images), when it was played, and which of your API keys sent it.
• Cab links. Your API keys, stored only as a fingerprint (the key itself is shown to you once). QR code links expire after 15 minutes.
• Events and rivals. Your event display name and division if you chose one, your event results, and the rivals you follow.

• Anyone, signed in or not: scores, clear lamps and dates on chart leaderboards, recent plays and event boards, under a stand-in name like “Player K7QX” for visitors who aren't signed in. Chart lists, pack details and the event's chart pages are hidden from them.
• Signed-in players: your username and machine tag, your profile (stats and scores), your event display name and division, and your rivals list on event pages. Your photo only if you turn it on, and then it's served by ECFA Cloud, so the page carries no link back to your Discord account.
• Players in game: the ECFA theme shows usernames, machine tags and scores on its leaderboards.
• Admins: also your Discord name and the IP addresses you've used, to deal with abuse. Your email address isn't shown anywhere, admin pages included.
• The ban list: when we ban an account, it's published on the ban list with its username, the date and the reason. IP addresses and Discord names are never published.

• Services that run the site: Discord (sign-in), Vercel (hosting), Cloudflare (sits in front of the site) and Neon (the database). Vercel and Cloudflare see each request, including your IP address, and keep their own logs for a limited time.
• GrooveStats and ArrowCloud: for the theme's blended leaderboard, ECFA Cloud asks them for a chart's leaderboard by its chart hash. Nothing about you is sent, and your scores are never submitted to them.
• GitHub and Discord's image server: ECFA Cloud fetches theme updates from GitHub and shown photos from Discord itself, so they see ECFA Cloud, not you.
• Nothing is sold, rented or shared for advertising.

• One sign-in cookie, and a timestamp in your browser's storage so your sign-in is renewed at most twice a day.
• On your cab, the theme keeps your API key in your profile folder, plus plays waiting to upload while offline.

• Your account, plays and IP addresses are kept until your account is deleted.
• To delete everything, ask an admin in the ECFA Discord. Deleting removes your account, sessions, API keys, scores, rivals, event entries and IP addresses, plus any packs, songs, charts and banners only you played.

We list IP addresses above because we keep them. Not every score tracker tells you as much (checked October 3, 2026):

• ArrowCloud's privacy policy (last updated November 29, 2025) says: “The only personal data categories retained are: (1) email address, (2) user-selected alias, and (3) optional country designation.” Its own public source code also stores the IP address and browser of every cab sign-in, linked to the account: the DeviceLoginSession table's ipAddress and userAgent, filled in by its device login code.
• GrooveStats doesn't publish a privacy policy or terms of service that we could find on groovestats.com, so nothing says what it keeps, what it shares, or when it removes an account, and we found no public list of removed accounts.