Private pilot privacy notice

Effective November 4, 2026. Pit Board is an independent sim racing project in private testing, operated by Ryan Mauro. This notice describes the current pilot; features and providers may change with an updated notice.

Contact setup is pending. privacy@pitboards.io is a planned address and is not yet active or monitored. Signed-in users can submit an account-deletion request in the app. For other privacy questions or sign-in problems, contact the project owner through the channel used for your pilot invitation. Please do not send requests to the placeholder address.

What we use

Google sign-in supplies your account identifier, email address, name and profile image information to Firebase Authentication. Pit Board uses your identifier and approved-tester record to control access. It stores the display name and preferences you save, normalized lap records you choose to import, and account-deletion requests you submit. It does not request access to your Gmail or original game/SimHub files.

Why and where

We use this information to provide your private profile and lap library, manage pilot access, support exports and handle deletion. Google Firebase provides Authentication, Hosting and Firestore. The pilot Firestore database is in Northern Virginia, US (us-east4); this is not a promise that all Google services or operational processing remain in that region. Hosting and authentication may process technical connection, security and service logs.

Analytics, advertising and sharing

Google Analytics and advertising are not enabled. We do not sell your pilot data or publish your private laps. Optional analytics preferences are stored on your browser, but currently do not cause any tracking. Any future analytics integration must honor those choices and update this notice. We may access pilot records to operate the service, troubleshoot issues you report and process your requests.

Cookies and browser storage

Google sign-in uses storage necessary for its session and security. A local preference records your privacy choices separately on each hostname/browser. See cookies and storage for details and to change your choices. Refusing optional analytics does not prevent sign-in or use of the pilot.

Your data and choices

Approved testers can download their current cloud profile and lap data from Account & privacy. Any signed-in Google account can request deletion of its Pit Board account, including an account without tester approval. The request requires a fresh Google sign-in. It is a request for manual processing, not immediate erasure. Imports and profile changes are blocked while it is pending; approved testers retain export access until processing starts.

Deletion covers the Pit Board cloud account, profile, laps, access approval and request record. It does not delete your Google account, original game or SimHub data, files you exported yourself, or the local companion cache. The local companion is a separate prototype and has no cloud upload or remote wipe in this pilot.

Retention and recovery

Account and lap records are retained while your pilot account is active unless you request deletion. Requests remain until processed. There is no automated user-level cloud backup or scheduled snapshot service configured in this pilot. Before confirming deletion, the operator must check for any manual copies or recovery archives and remove or explicitly account for them. Provider-controlled security/service logs and technical recovery copies may follow Google's retention processes; we cannot promise instant removal from every provider system.

Processing a deletion

The operator reviews requests manually; the app does not send an automatic email alert or guarantee an immediate completion time. Requests are processed through the authenticated administrator tools, with data cleanup before the Firebase login is removed. We will arrange confirmation through your existing pilot contact channel. Contact the owner there if you cannot sign in or need to check progress.

Changes

Before wider community testing we will activate a working privacy contact, review this notice for the actual operating entity and applicable requirements, and document any new analytics, advertising, payments or backup behavior. Material changes will be communicated to invited testers.