Checkpoint / Legal

Privacy policy

Last updated: 9 November 2026

1. Who is responsible

Jordi operates Checkpoint and is the contact for data handled by the bot and this website. Email checkpoint19761@gmail.com or open a ticket in our support Discord. This policy covers Checkpoint, not Discord’s own platform or independently operated server communities.

2. Information we process

• Discord identifiers and configuration: user, server, channel, message and role IDs; tier and team configuration; language, layout and scheduling settings. Display names and role membership may be read from Discord to produce line-ups and manage attendance.
• Race activity: check-in titles, circuit names, descriptions, dates, capacity, participants, declined entries, reserve and commentator assignments, and line-up state.
• Images: custom images supplied by authorised users for check-in messages may be stored and displayed.
• Support: ticket identifiers, the requesting user’s ID, ticket channels, timestamps and status. Conversations and attachments supplied in support tickets remain in Discord and can be accessed by authorised support staff. Closing a ticket does not necessarily delete its history.
• Historical activation and payment records (where applicable): server ID, licence status, payment provider, transaction reference, amount, currency and verification timestamps. Payment providers process payment credentials separately. Do not send card details, passwords or bot tokens in tickets.
• Technical records: operational and error logs. The website’s hosting server records request information, which can include IP address, request URL, browser information and timestamps for operation, security and traffic reporting.

League management and dashboard data

League features also store seasons, divisions, event rosters, attendance responses, profile names, teams, numbers and countries, reminder preferences, league application answers and decisions, result drafts and published revisions, votes, incident reports, evidence links, responses, steward decisions, appeals and staff action records. Existing role membership is checked to determine access. Event cards are visible in the channel selected by the league. Incident records are visible to involved participants, configured stewards and server managers. Full league backups, including private records, are restricted to members with Manage Server permission.

The dashboard uses a necessary HttpOnly session cookie scoped to the Checkpoint dashboard path. Single-use login links expire after five minutes; sessions expire after one hour or a bot restart. Session and link records are held in memory and contain the relevant Discord user and server IDs. Dashboard access is rechecked against current Discord membership and roles. Optional attendance reminders are sent by Discord DM only after a participant enables them; users can disable them in their profile.

3. Why we use this information

We use this information to deliver requested bot functions, maintain server configuration, manage support and access, diagnose faults, prevent misuse and meet applicable record-keeping obligations. Where GDPR applies, the relevant grounds are performance of a contract or requested pre-contract steps, legitimate interests in operating and securing the service and supporting league participation, and legal obligations where applicable. Data is not used to train AI models or sold as an advertising product.

4. Who can see it

Discord processes bot interactions and messages on its platform. Server members can see check-ins and line-ups if their channel permissions allow it; server administrators manage those permissions. Authorised Checkpoint support staff can access support information and operational records when needed. Infrastructure providers host the bot and website. A payment provider, such as PayPal when used, processes the payment under its own privacy terms. Information may also be disclosed when required by law.

Some providers may process data outside your country. Their privacy notices explain their locations and safeguards, including Discord’s privacy policy and PayPal’s privacy statement.

5. Storage and retention

Bot state and configuration are stored on the operator’s server. We retain operational data while it is needed to provide the configured service, resolve support issues or maintain valid licences. Payment and dispute records may need to be retained for applicable legal obligations. Technical logs and backups can have different retention periods.

Removing Checkpoint from a Discord server does not currently erase stored bot data automatically. Closing a support ticket also does not automatically erase its history. To request deletion, contact us with the relevant Discord user or server ID. We will review the request, verify authority where needed, remove data that is no longer necessary, and explain any lawful reason for retaining particular records. Discord messages and copies held by other server members are also subject to Discord’s and the server’s controls.

6. Your choices and rights

You can stop using the bot, remove it from a server you administer, and request access, correction or deletion of your personal data. Depending on applicable law, you may also request restriction or portability and object to processing based on legitimate interests. Email the address above; do not send a password or token. We may ask for proportionate information to confirm that the data concerns you. Where GDPR applies, we normally respond within one month, subject to lawful extensions. You may complain to your local data-protection authority.

7. Website and links

The public Checkpoint information pages do not include advertising scripts, tracking pixels, account registration or contact forms. Website requests are still processed by the hosting server as described above. Links to Discord, payment providers and other sites take you to services with their own policies.

8. Children, security and updates

Checkpoint is intended for users who meet Discord’s minimum age and any higher local requirement. Do not submit sensitive personal information through race configuration or support attachments. Access to stored bot data is limited to operation and support needs; no internet service can guarantee absolute security. If our data practices change, we will update this page and its date.