Privacy Policy

We run no server of our own, so nothing you do reaches us directly. Four outside services receive something, and this is all of it:

• RevenueCat, the purchase check. It receives an anonymous identifier it generates itself and your App Store receipt. No name, no email address, and nothing you do in the app.
• EAS Update, run by Expo. On launch the app asks whether a newer version of its JavaScript exists, so a fix can reach you without an App Store release. The request carries the platform, the app version and an update id, and nothing about you.
• Sentry, crash reporting. When the app crashes it receives the stack trace, along with the names of the last few screens you opened so the fault has a path leading into it. No user identifier is ever set, and breadcrumbs from the live timing feed are stripped before an event leaves your device. Nothing is sent that the app did not throw.
• Vexo, product analytics. It counts which parts of the app get used: twelve events, each one naming a screen and an action, such as a screen opened, a pick set, an exam passed. Never a result.

What is never collected: no account, no name, no email address, no user id set in any of these services, no advertising identifier, no cookies, no screen recording. Nothing is sold, and nothing is used to train a model.

Pitwall works without registration. We never ask for your email address, name, phone number, or any other contact details.

Your favourite driver and team, your picks, your lesson progress, your alert settings and the sessions the app archives are stored in a database on your device. We keep no copy and have no way to reach it. Deleting the app removes all of it.

To show the calendar, standings, results, live timing and news, your device requests them directly from public motorsport data sources and news publishers. Those hosts see the request and the network address it came from, exactly as they would if you opened the same page in a browser. We do not run them, we receive nothing from them, and no identifier of ours travels with the request. Nothing read from those feeds is ever passed on to the four services listed above.

The optional Pitwall Pro upgrade is a one-off purchase handled entirely by Apple. We never see or store your payment details. To tell whether the upgrade has been bought, the app uses RevenueCat, which receives an anonymous identifier it generates itself and the App Store receipt. It is used for nothing else.

Two services are involved. Sentry receives a stack trace when the app crashes, with the names of the last few screens opened so the fault can be read in context. Vexo counts twelve events, each naming a screen and an action. Neither ever has a user identifier set, because we set one nowhere. No result is ever sent: no lap time, no classification, no standings row, and nothing read from the live timing feed. Screen recording is switched off in the code rather than left at the SDK default, and a build being worked on sends nothing at all. There are no advertising identifiers and no cookies, and none of this counts as tracking in Apple's sense, because no identifier of ours is joined to data from another company.

The App Privacy section of the App Store listing declares three things, and these are them: Purchase History and Device ID, from RevenueCat; Diagnostics, Crash Data, from Sentry; and Usage Data, Product Interaction, from Vexo. None of it is linked to your identity, and none of it is used for tracking.

The app is distributed through the Apple App Store. Apple may collect its own information in line with Apple's privacy policy; this is outside our control and is not shared with us.

Pitwall is not directed at children, and it asks no one for personal details. The crash reports and screen counts described above carry no name, no contact details and no identifier, from a child or from anyone else.

We may update this Privacy Policy from time to time. Any changes will be posted here with a new “Last Updated” date.

Questions about this Privacy Policy? bilalcagiran [at] gmail.com