Privacy Policy

Sorcery AI Racing League (SARL) is organized by Data Sorcerers. In this notice, “we”, “us” and “our” refer to the SARL organizing committee acting on behalf of Data Sorcerers. This notice applies to sarl.data-sorcerers.com.

For questions about personal information, email [email protected]. If you cannot reach the event team, contact [email protected]. Use the subject “SARL privacy enquiry” so your message can be directed to the appropriate person.

• When you browse: technical request information, such as your IP address, browser and device details, requested page, request time and connection errors. Hosting and security services process this information to deliver and protect the website.
• When you accept analytics cookies: browser identifiers, page visits and related usage information that help us understand how visitors use the site.
• When you contact us: your email address, name if supplied, message, attachments and correspondence needed to respond.
• When authorized staff sign in: account and session information, together with records of administrative activity where enabled.

Avoid putting sensitive personal information in page URLs or sending passwords, login tokens or identity documents in an initial enquiry. We do not ask public visitors to create a committee account.

• Deliver website content, resources and video playback, and resolve technical problems.
• Protect staff accounts, detect misuse and maintain reliable access to the site.
• Respond to enquiries about eligibility, resources, accessibility or event arrangements.
• Understand website use and improve event information when you allow Google Analytics.

Accepting analytics cookies is a choice about website measurement. It does not register you for the competition or subscribe you to a mailing list. Visiting the website does not give us permission to use your contact details for unrelated promotions.

We use Google Analytics 4 on public website pages after you select Accept cookies. Google processes usage and technical information through its analytics service. Our page-view integration removes query strings and URL fragments from the page address it sends, and does not pass registration field values to Google.

Advertising storage, advertising personalization and Google signals are disabled in our website tag configuration. The tag is not initialized on committee pages or local development pages. Browser settings and content blockers may also prevent collection.

Select Essential only to continue without our Google Analytics tag. You can change your choice through Cookie settings in the footer. Withdrawing consent stops future collection by our tag; it does not automatically delete information already sent.

Read the Cookie Policy for storage details, and how Google uses information from partner websites for Google’s processing practices.

The website uses Vercel for hosting and Cloudflare for delivery and security. These services process technical requests needed to serve and protect the website. Cloudflare also supplies website performance measurements; its Web Analytics service is described by Cloudflare as not using cookies. This infrastructure measurement is separate from the Google Analytics cookie preference.

Service providers may process information in countries other than your own, depending on their infrastructure and service arrangements. Their policies explain their processing practices: Vercel, Cloudflare and Google.

Enquiries are handled through the committee’s email service. Access to correspondence and administrative information is intended for staff who need it to respond or operate the event. External links, social platforms and third-party services have their own privacy notices.

Official registration is not currently open. The preview registration page does not accept official entries or send participant confirmation emails. Viewing or completing a preview does not reserve a place.

When registration opens, the entry process is expected to request team and participant information, including contact details, institution, study program and evidence needed to establish eligibility. The current planned administrative services are Supabase and Google Sheets. Their use, the required fields, access arrangements and retention periods will be explained before collection begins.

Finalists may be required to provide competition work and development records for rule-compliance review. Details of any required records, review access and retention will be communicated before the final. Participants should keep unrelated personal files and credentials outside competition submissions.

Different types of information have different purposes and retention settings. There is no single retention period for all website data.

• The committee sign-in cookie lasts up to one hour unless cleared earlier by signing out.
• Our Google Analytics cookies are configured for up to 180 days, with expiry refreshed by subsequent activity. Cookie expiry is separate from the retention of data already held in Google Analytics.
• Your cookie preference remains in browser storage until removed; the website treats it as valid for 180 days and asks again after that period.
• Email correspondence, infrastructure logs and analytics records are subject to the relevant administrative and provider retention settings. This notice does not specify a fixed deletion date for those records.
• The retention schedule for official participant information will be published before registration opens.

For a retention or deletion question about a particular record, contact [email protected] and describe the information concerned.

You may contact [email protected] to ask what personal information the committee holds about you, request a correction or deletion, withdraw an optional consent, or raise a concern about its use. Requests will be assessed under the requirements that apply to the information and your circumstances.

Include the email address you used to contact us, the relevant date or event, and a clear description of your request. We may ask for proportionate information to confirm your identity before disclosing or changing records. Do not send identity documents unless the committee explains why they are needed and how to submit them securely.

Some information may need to be retained for security, a dispute or another applicable obligation. If a request cannot be completed in full, we will explain the reason. Changing cookie preferences alone does not submit a request to delete historical records.

The website uses HTTPS, restricted committee access and other controls intended to protect information. No online service can guarantee complete protection against every incident. Report suspected exposure or unauthorized access privately to the committee; do not include another person’s private data in a public post.

We will update this notice when website features or information-handling arrangements change. The review date above identifies the current version. Material changes to registration or participant processing will be explained through the relevant event communications.