SlipTraceSlipTrace

Legal

Privacy Policy

Last updated: June 2026

SlipTrace is in beta. This policy describes the data handled by sliptrace.com, the SlipTrace mobile app, the Windows PC Companion, Firebase backend services, and related support/donation workflows.

1. Information We Collect

CategoryData
Account and profileFirebase UID, email, display name, username, bio, avatar URL, auth provider state, donor/pro flags, deletion flags.
Signup and legacy invitesEmail, email verification status, signup source, account status, legacy queue/invite token status, timestamps, donation boosts, and hashed IP rate-limit records.
Racing sessionsSimulator, track, car, session type, timestamps, duration, lap count, lap times, sectors, validity, pit flag, top speed, incidents, notes, and visibility.
Device pairingPC device ID, anonymous device UID, device name, token hash, short code status, linked account ID, link state, and last-seen timestamps.
Social featuresFollows, likes, comments, public profile fields, public session projections, and author snapshots copied to published sessions.
NotificationsFirebase Cloud Messaging tokens and notification event content for session, social, and milestone notifications.
Analytics and diagnosticsPseudonymous Mixpanel events tied to an internal account identifier, optional Google Analytics web traffic data, Crashlytics crash/error data, and app version/platform metadata.
Donations and supportKo-fi transaction ID, amount, currency, donor name, donor message, extracted email, donor tier, support ticket content, ticket status, and related timestamps.
Local storage and logsMobile Drift cache, PC SQLite session/device cache, app logs, bridge logs, and diagnostic payload logs only when enabled for debugging.

2. How We Use Information

  • To create accounts, manage profiles, and secure sign-in.
  • To pair the PC Companion with your account and upload draft sessions after a session ends.
  • To save, review, publish, display, and share racing sessions, laps, stats, milestones, and public profiles.
  • To operate social features such as follows, likes, comments, feeds, and notifications.
  • To run signup, email verification, legacy invite, donation, support, feedback, abuse-prevention, and beta tester workflows.
  • To monitor App Check signals and harden abuse prevention before strict enforcement is enabled for beta clients.
  • To improve the product with pseudonymous analytics, crash reports, and aggregated usage information.

We do not sell your personal data.

3. Public Content

Your username, avatar, public profile stats, public sessions, public comments, likes, and displayed donor tier may be visible to other users or public visitors depending on the feature and visibility setting. Private sessions are intended to remain private to your account, except where needed for support, security, or legal operations.

4. Analytics, Cookies, and Crash Reports

Mixpanel events are pseudonymous, not anonymous, because they are tied to an internal account identifier after sign-in. We use this to understand feature usage and beta stability. Crashlytics may receive crash/error details, device model, operating system, app version, stack traces, and Firebase installation identifiers.

Google Analytics is optional on the website. It is only loaded after you accept analytics in the cookie banner. You can change your choice from the Cookie Settings link in the footer.

5. Third-Party Providers

ProviderPurpose
Firebase / Google CloudAuthentication, Firestore database, Storage, Cloud Functions, hosting, FCM, App Check, and Crashlytics.
MixpanelPseudonymous product analytics on the EU endpoint. We do not send emails, raw lap telemetry, or payment data to Mixpanel.
Google AnalyticsOptional website analytics after you accept analytics cookies in the cookie banner.
ResendTransactional email delivery for verification, legacy invite, feedback, and support workflows.
Ko-fiDonation checkout and donation webhook data. Ko-fi handles payment details directly.
Firebase App DistributionBeta app distribution to invited testers, including tester email/device metadata handled by Google/Firebase.

6. Local Device Data

The mobile app stores local cache data for offline and performance reasons. The PC Companion stores local SQLite device/session state and app logs under the user profile on the PC. Full Firestore upload payload logging is disabled in production builds and may be used only in diagnostic/debug builds.

7. Retention and Deletion

We keep account and session data while your account is active. For beta, account deletion is a manually reviewed process: the app creates a deletion request, an admin reviews it, completes deletion or lawful retention steps, and records completion status. This is not yet an automated deletion cascade.

Some records may be retained where needed for security, abuse prevention, accounting, support disputes, legal compliance, backup windows, or anonymized/aggregated analytics. Donation/payment records may be retained for accounting obligations. Support tickets and diagnostic records are retained only as long as needed for beta support and operational review.

8. Your Choices and Rights

  • You can request access to your data.
  • You can request correction of inaccurate account/profile data.
  • You can request deletion of your account and associated personal data.
  • You can object to or restrict certain processing where applicable law gives you that right.
  • You can request a portable export of data we can reasonably provide during beta.
  • You can accept or reject optional website analytics cookies.

To make a privacy request, email sliptrace.support@gmail.com. We may need to verify your identity before acting on a request.

9. Children

SlipTrace is not directed to children. Beta users must meet the eligibility requirements in the Terms of Service. If you believe a child has provided personal data without appropriate permission, contact us so we can review and delete it where required.

10. International Processing

SlipTrace uses providers that may process data in the United States, European Union, United Kingdom, India, or other regions where they operate. We intend to maintain appropriate provider terms, data processing agreements, and transfer mechanisms as the beta expands.

11. Changes and Contact

We may update this policy as the beta changes. Material changes will be posted on this page and, where appropriate, communicated in-app or by email.

SlipTrace Motorsport Data

sliptrace.support@gmail.com