Privacy Policy

Last updated: August 4, 2026

This Privacy Policy explains how Pole Simulation handles information for Apex, also distributed on some platforms as Project Apex. It applies to the Apex mobile app on Android and iOS.

Privacy contact: privacy@polesim.com

Account and data deletion request page: https://polesim.com/account-deletion.html

Summary

Apex is a sim-racing reflex training app. The app uses anonymous sign-in, server-side score submission, progression, leaderboards, and limited beta telemetry so the app can run, diagnose failures, and improve training features.

Apex does not sell personal information, does not show ads, does not use data for third-party advertising, and does not track users across other companies' apps or websites.

Information We Collect

Account and Profile Data

Apex uses anonymous authentication. We collect and store:

• A Supabase anonymous user ID.
• A generated driver display name, such as Driver 0000.
• Profile and progression state, including XP, Driver Level, unlocks, benchmark progress, streak-related state, and training history needed to run the app.

We do not ask users to provide an email address, phone number, real name, password, postal address, or payment information in the app.

Training and Gameplay Data

When a user completes a score-bearing training attempt, Apex sends attempt summaries to the backend. These may include:

• Exercise name and selected level.
• Attempt status.
• Reaction time, hits, misses, omissions, false positives, empty presses, accuracy rates, decision metrics, and similar score fields depending on the exercise.
• Attempt context, including whether the attempt was ad-hoc training, Daily Training, or Daily Lights Out.
• Server-issued session IDs, block indexes, and submission IDs used for idempotency and Daily Training integrity.
• XP awarded, total XP, progression, unlock, benchmark, Daily Training, Daily Lights Out, coaching, recap, and leaderboard data derived from attempts.

Leaderboard Data

Public leaderboard features may display limited performance information to other users, including generated driver display name, rank, exercise, score metrics, and whether the viewer is seeing their own row. Leaderboards do not display email addresses, phone numbers, real names, precise location, or contact data.

App Interaction and Telemetry Data

Apex records limited app telemetry for beta reliability and product improvement. Telemetry events may include:

• App open and app lifecycle events.
• Feature views and feature actions, such as bottom navigation tabs, Guide rules cards, Training Progress detail views, Daily Training debriefs, Daily Lights Out recaps, and Daily Recap sheets.
• Tutorial, Guide Practice, training session start, completion, and abandonment events.
• Attempt submitted and attempt rejected events.
• Unlock, Driver Level, RPC failure, app error, and crash events.

Telemetry event properties are limited to stable product identifiers and broad runtime context, such as:

• App version and build number.
• Platform, OS version, phone/tablet device class, locale, timezone offset, release channel, and coarse region derived from the device locale country code.
• Feature, surface, source, tab index, exercise, level, initial tab, session context, and block index when relevant.

The coarse region value is not derived from GPS, IP geolocation, city, state, or precise location.

Crash and Error Data

For crash and error diagnosis, Apex may collect:

• Error type, source, and severity.
• A short sanitized message preview.
• Message hash and stack hash.
• Top app stack frame.
• App version/build, platform, OS version, device class, locale, timezone offset, and anonymous user ID after authentication.

Crash telemetry is designed to avoid raw full stack traces, access tokens, request headers, response bodies, screenshots, and free-form private text.

Local-Only Data

Apex stores some preferences on the device using local storage, such as whether the tutorial prompt has been shown and the local Daily Lights Out completion date. These local preferences are used for app functionality and are not used for advertising or tracking.

Communications

If a user contacts Pole Simulation by email, including to request account deletion, privacy help, support, or beta feedback, we collect the email address and message contents needed to respond and complete the request.

Information We Do Not Collect

Apex does not intentionally collect:

• Precise location.
• GPS location.
• Advertising ID, IDFA, Android Advertising ID, or similar advertising identifiers.
• Contacts.
• Calendar events.
• Photos, videos, audio files, files, or documents.
• Camera or microphone data.
• SMS, MMS, phone call logs, or phone number.
• Email address in the app.
• Payment information.
• Health or fitness records.
• Clipboard contents.
• Installed-app inventory.
• Raw touch coordinates or raw per-frame input traces.
• Screenshots.
• Free-form private text in the app.

How We Use Information

We use information to:

• Provide app functionality, including anonymous sign-in, profile loading, training sessions, score submission, XP, progression, unlocks, Daily Training, Daily Lights Out, coaching, recaps, and leaderboards.
• Prevent duplicate or invalid score submissions and enforce server-side write limits.
• Diagnose beta crashes, app errors, and backend RPC failures.
• Understand broad feature usage and training completion funnels.
• Tune difficulty, progression, Daily Training, Daily Lights Out, coaching, and reliability.
• Maintain compatibility between released app builds and backend behavior.
• Protect the app, backend, and users from abuse, fraud, security issues, or policy violations.

We do not use Apex data for third-party advertising, targeted advertising, advertising measurement, data brokerage, or tracking users across other companies' apps or websites.

How We Share Information

We do not sell personal information.

We may share or process information in the following limited ways:

• Service providers: Apex uses Supabase to provide authentication, database, backend, and related infrastructure services on our behalf. Service providers may process data only as needed to provide services to Apex and under their own security and privacy commitments.
• Public leaderboard features: If a user participates in score-bearing training, limited leaderboard data may be shown to other Apex users as described above.
• Legal and safety reasons: We may disclose information if required by law, legal process, security investigation, or to protect the rights, safety, and integrity of Apex, users, or others.
• Business transfers: If Apex or Pole Simulation is involved in a merger, acquisition, financing, reorganization, or asset sale, information may be transferred as part of that transaction, subject to appropriate notice and safeguards.

Apex does not share data with ad networks, data brokers, or third-party tracking companies.

App Store and Platform Providers

Apple, Google, TestFlight, Google Play, and device operating system providers may collect information independently when users download, install, update, review, or use platform services. Their collection and use of data is governed by their own privacy policies and account settings.

Security

Apex transmits data using encrypted network connections. Important score, progression, XP, unlock, Daily Training, and leaderboard behavior is validated server-side. Backend access is restricted with authentication, row-level security, RPC validation, grants, and bounded write limits.

No method of transmission or storage is perfectly secure, but we use technical and organizational safeguards intended to protect user data against unauthorized access, misuse, or disclosure.

Retention

We keep profile, progression, training, leaderboard, and related app data for as long as needed to provide Apex, maintain user progression, operate leaderboards, protect the service, comply with legal obligations, resolve disputes, and enforce agreements.

Beta telemetry and crash/error data are kept only as long as needed for beta reliability, diagnostics, analytics, and product improvement. Before full public launch, Pole Simulation will define and apply a production telemetry retention period.

When data is no longer needed, we delete, aggregate, or de-identify it where practical.

User Choices and Deletion

Users may stop future data collection by uninstalling the app.

Users may request deletion of their Apex account and associated app data at: https://polesim.com/account-deletion.html

Users may also contact us at privacy@polesim.com to request access, correction, deletion, or other privacy assistance. We may need enough information to identify the relevant anonymous account or app profile before completing a request. Some information may be retained where required for security, fraud prevention, legal compliance, dispute resolution, or legitimate operational records.

Children

Apex is not directed to children. If you believe a child has provided information to Apex, contact us at privacy@polesim.com so we can review and delete the information where appropriate.

International Processing

Information may be processed in the United States and other countries where Pole Simulation or its service providers operate. Data protection laws in those countries may differ from those in the user's location.

Changes to This Policy

We may update this Privacy Policy from time to time. If we make material changes, we will update the "Last updated" date and provide additional notice where required by law or app-store policy.

Contact

For privacy questions, requests, or concerns, contact: privacy@polesim.com.