Privacy Policy
1. Who we are
Eclipse Competition (“Eclipse”, “we”, “us”) is an independent sim-racing team that competes on the iRacing platform. We are a team of individuals operated from Indiana, United States, not a registered company. This policy covers the website at eclipsecompetition.com, including the driver portal at /portal. It does not cover the Eclipse Discord server, Instagram, iRacing, or any other third-party service we link to; each of those has its own privacy policy.
Questions or requests about your data: send .
2. The public website
Browsing eclipsecompetition.com does not require an account and does not ask you for any information. We do not use analytics, advertising, tracking pixels, social-media embeds or any third-party scripts. Every file the page loads (fonts, scripts, images, video) is served from our own domain, so a page view sends nothing to Google or other outside services.
The site is hosted by Cloudflare (Cloudflare Pages). Like any web host, Cloudflare receives your IP address, browser type and the pages you request in order to deliver them, and keeps short-term server logs for security and reliability. We do not add our own logging on top of that.
Your browser stores a few small preferences on your own device (which result banner you dismissed, and display settings). These never leave your browser and are described in the Cookie Policy.
3. The driver portal
The portal is a private tool for team members. It is not indexed by search engines and requires signing in with a Discord account that is a member of the Eclipse Discord server.
3.1 What we receive when you sign in with Discord
Sign-in is handled by Supabase, our authentication and database provider, using Discord’s OAuth login. Discord shows you exactly what it will share on its authorization screen. That is:
- Your Discord user ID, username, display name and avatar — used to identify you in the portal and put your name on signups and rosters.
- The email address on your Discord account — Supabase requests this as part of every Discord login. We do not send email and do not use it for anything.
- The list of Discord servers you belong to — read once, in your browser, immediately after login, only to check that you are in the Eclipse server. The list is not sent to us and is not stored anywhere; your browser just remembers that the check passed.
3.2 What the portal stores
| Data | Where it comes from | Why we keep it |
|---|---|---|
| Account record (Discord ID, username, display name, avatar, email, sign-in timestamps) | Discord, via Supabase Auth | To sign you in and link your signups to you |
| Race signups (event, car class, confirmed / tentative / available, your name and Discord username, time of signup) | You, in the portal | To build lineups and keep a record of who raced what |
| Published lineups and rosters | Team admins | So drivers can see who is in which car |
| Driver board: name, Discord handle and ID, iRacing display name and customer ID, iRating and licence for sports-car and formula, region, join date, preferred cars, best result, membership status, short admin notes | The intake form you fill in when you join the Discord server, the details you enter yourself on the portal’s Start Here tab, iRacing’s public member data, and team admins | To run the team: pick lineups, meet licence requirements, and keep track of who is active |
| Start Here checklist (which onboarding steps you have ticked, and when you confirmed your details) | You, in the portal | So admins can see who still needs help getting set up |
| EclipseBot questions (the text you type into the portal’s EclipseBot chat, your Discord username, a timestamp, and a daily count of questions) | You, in the portal | To keep the bot within its usage limits and to see which questions the FAQ should answer better. Answers are not stored. |
| Discord server membership list (user IDs and usernames of server members) | The Eclipse Discord server, via our bot | To confirm portal users are in the server, on the server side |
The full driver board is visible only to team admins; this is enforced by database access rules, not just by the interface. You can see and edit your own board row (everything except the admin notes) on the portal’s Start Here tab. Signups and rosters are visible to all signed-in members. The EclipseBot question log is visible only to admins.
3.3 Where portal data goes
- Discord. When you sign up for a race, withdraw, or are placed on a final lineup, the portal posts that to the Eclipse Discord server (your name, and for lineups an @-mention of your Discord account) so the team can see it. This is the same information you would post there yourself.
- iRacing. We may look up members’ current iRating and licence class from iRacing’s data API using the iRacing customer ID on the driver board, so the board stays accurate. We do not send iRacing any information about you.
- Anthropic (EclipseBot). When you ask EclipseBot a question, your message and the recent messages in that chat are sent to Anthropic’s Claude API along with the team’s published schedules, events, lineups, public site content, your own driver-board row and the current signup lists, so the bot can answer. Anthropic processes this under its commercial API terms, which do not permit it to train on the data; we do not send it anyone’s admin notes or other drivers’ board rows. Don’t put anything in the chat you wouldn’t post in the team Discord.
- Supabase stores the database and authentication records on our behalf. Cloudflare serves the pages. GitHub runs our scheduled background jobs (the Discord and iRacing syncs). Each acts as a processor under our instructions and under their own security commitments.
We do not sell, rent or trade personal information, and we do not share it with advertisers or data brokers.
4. The public roster and media
The website shows names, photos, short biographies and race results of team owners, staff and drivers, plus our partners’ and sponsors’ logos. If you appear on the site and want your name, photo or bio changed or removed — including if you are under 18, or are a parent or guardian of someone who is — contact us and we will take it down promptly.
5. Legal bases (UK, EU and similar jurisdictions)
Where data-protection law requires a legal basis: we process portal data because it is necessary to provide the portal you asked to use (signing in, signups, lineups) and for our legitimate interest in running an organised team (the driver board, membership checks, Discord announcements). Hosting logs are processed in Cloudflare’s and our legitimate interest in keeping the site secure. We do not rely on consent for anything the portal does, so there is nothing to withdraw; instead, you can ask us to delete your data (section 8).
Our services are based in the United States. If you use the portal from the UK, EU or elsewhere, your data is transferred to and stored in the United States. Supabase and Cloudflare offer standard contractual clauses / the UK addendum for such transfers.
6. How long we keep data
- Portal account: until you ask us to delete it, or we remove inactive accounts.
- Signups and rosters: kept as the team’s record of past events; deleted on request.
- Driver board entry: while you are a member or trial member; removed when you leave or on request.
- Discord membership list: refreshed on each sync; entries for people who leave the server drop off.
- EclipseBot questions: deleted automatically after 90 days; the daily question counts after 14 days.
- Hosting logs: retained by Cloudflare for a short period under its own policy.
7. Security
The site is served over HTTPS only. Portal data lives in a database with row-level access rules: members can only read what the team as a whole can see, and only admins can read or edit the driver board. Secrets (bot tokens, webhook URLs) are kept out of the website code. No system is perfectly secure; if we learn of a breach affecting your data we will tell you.
8. Your rights and choices
Whatever country you are in, you can ask us to:
- See the information we hold about you;
- Correct it (you can also edit your own signups in the portal, and admins can fix driver-board entries);
- Delete it — your portal account, your signups, your driver-board entry, and your name or photo on the public site;
- Object to processing based on our legitimate interests, or ask us to restrict it.
Send . We will respond within 30 days and will not charge you. If you are in the UK or EU and are unhappy with our response, you can complain to your local data-protection authority (in the UK, the ICO).
You can also revoke the portal’s access to your Discord account at any time from Discord’s User Settings → Authorized Apps. This stops future sign-ins; it does not delete the data already stored, so ask us to delete that too if you want it gone.
We do not sell or “share” personal information as those terms are defined in California law, and we do not respond differently to visitors who send a “Do Not Track” or Global Privacy Control signal because we have nothing to opt them out of.
9. Children
The portal requires a Discord account, and Discord requires users to be at least 13 (older in some countries). We do not knowingly collect personal information from anyone under 13. If you believe a child under 13 has an account in the portal, contact us and we will delete it.
10. Changes
If we change this policy in a way that matters, we will update the date at the top and, for portal users, announce it in the Eclipse Discord server. Continued use of the portal after a change means the updated policy applies.
11. Contact
Eclipse Competition, Indiana, United States. Send . You can also reach us on Instagram.