Privacy Policy

1. Scope and privacy contact

This Privacy Policy applies to Pocket Performance Lite (com.pocketperformance.lite), Pocket Performance (com.pocketperformance.app), supported Pro Pack features, and the public Pocket Performance website at pocketperformance.co.uk.

Privacy questions and data requests can be sent to pocketperformance2026@gmail.com.

Last updated: 5 October 2026.

2. Lite guest mode and accounts

Pocket Performance Lite can be used without creating an account. A Lite guest can use supported features locally on that device/app install. Account creation or sign-in is optional in Lite and can be done later.

When an account is used, Pocket Performance Lite and the full Pocket Performance app use the same Pocket Performance account system. Account information can include the email address used to register or sign in, an account/user identifier, Racer ID / username, profile data, and an optional profile region where supplied by the user. Authentication is handled through Pocket Performance's Supabase-backed account service.

3. Profile, Garage and vehicle information

Pocket Performance can use profile and vehicle information needed to provide app features. This can include Racer ID / username, optional profile region, car name or nickname, vehicle details, drivetrain, gearbox and other vehicle information entered by the user.

Some Garage, calibration and vehicle records can be local to the device. Local Lite/guest data is not automatically transferred into the full app or to an account simply because the user later signs in. Where a feature is specifically account-backed or cloud-backed, supported records may be stored through Supabase to provide that feature.

4. Run history, results and local app storage

The apps create and use performance-run information such as test type, start type, selected units, timing results, speeds, distance-related results, Run Confidence, calibration data and other information needed to measure and display a run.

Private run history, calibration information, local proof recordings, Brag Cards, settings and other app records may be stored on the device. Local-only data remains on that device/app install unless the user uses a specific cloud-backed or public-upload feature.

5. Precise location, speed and telemetry

Pocket Performance accesses precise device location and related speed / telemetry signals during calibration and performance runs because these signals are required to measure speed, timing, distance and run behaviour. This use is for the core performance-testing functionality requested by the user.

In the current app implementation, precise location is processed for telemetry and run calculation, but Pocket Performance's Supabase run upload does not upload or store raw latitude/longitude coordinates or the user's raw GPS route/path. An optional profile region entered by a user is separate profile information and is not raw GPS telemetry.

Public or cloud-backed run records may contain derived information such as the test type, start type, units, vehicle details, times/results, speeds, Run Confidence and related leaderboard information where applicable.

6. Microphone, audio, camera and proof recording

Pocket Performance requests microphone access for performance runs. The current run flow records microphone audio as part of a locally created run/proof MP4. This can occur whether the proof recording uses the live camera view or the app's non-camera / overlay background.

Camera access is used when the user selects a camera/video mode that requires the camera view. If camera view is not selected, the proof recorder can use a non-camera background instead. Local recordings remain on the device unless a supported feature allows the user to save, export, share or deliberately upload them.

7. Supabase backend services

Pocket Performance uses Supabase as a service provider for account and supported cloud-backed features. Depending on the feature used, Supabase may process or store account/authentication records, profile information, optional profile region, public leaderboard records, challenge-related records and media associated with a user-controlled public upload.

Pocket Performance does not use Supabase run uploads to store the raw GPS route described above. Local-only Garage, calibration, history and media are not automatically uploaded merely because the app is installed or because an account exists.

8. Public leaderboards, challenges and proof uploads

Public leaderboard upload is a user-controlled feature of the supported full-app / Pro experience. Pocket Performance Lite does not upload Lite runs to the public leaderboards.

When a user deliberately uploads a qualifying run, public-facing or backend data can include Racer ID / username, car name and car details, event/test type, start type, units, result or time, relevant speeds, Run Confidence, board/position information and proof video where the user chooses to include supported proof media. Public leaderboard data can be viewed by other people through the app or website.

9. Google Play purchases and billing

Purchases for the paid app or supported in-app products are handled by Google Play Billing. Pocket Performance does not receive or process the user's payment-card number. The app receives purchase / entitlement information needed to verify access to paid features. Google's handling of payment and Play account information is governed by Google's own terms and privacy practices.

10. Android app analytics and crash reporting

The current Pocket Performance and Pocket Performance Lite Android apps do not include Firebase Analytics, Firebase Crashlytics, Sentry, Bugsnag, App Center, Mixpanel, Amplitude or a similar in-app analytics/crash-reporting SDK. Website analytics described below is separate from the Android apps.

11. Website analytics

The public Pocket Performance website uses Google Analytics 4 (GA4) to understand how visitors find and use the website. Website analytics may include page views, traffic/referral source, interactions with measured website links, approximate device/browser information and approximate geographic information derived by Google's analytics service.

Google may use cookies or similar technologies for this website analytics. GA4 is used to improve the public website and understand traffic and marketing performance. It does not collect Pocket Performance app passwords, Google Play payment-card details, or private on-device run history through the website analytics tag.

12. When information is shared

Pocket Performance does not sell personal data. Information is shared only as needed to provide requested features or services, including:

• Supabase for account and supported backend/cloud features;
• Google Play for app distribution, purchases and entitlement handling;
• Google Analytics for analytics on the public website only; and
• the public when a user deliberately publishes a qualifying leaderboard run or proof item.

A user-initiated share/export action may also send content to the app or service chosen by that user through Android's sharing tools.

13. Security and handling of sensitive data

Pocket Performance limits access to personal and sensitive information to the data needed for the app feature being used. Network-backed services are accessed using secure HTTPS/TLS connections, and account authentication is handled through the Supabase-backed account system. Public upload is separated from private/local use and requires a user-controlled upload action where supported.

No online or device-storage system can be guaranteed to be completely secure. Users should protect access to their device and account and avoid publishing proof media or profile information they do not want to make public.

14. Data retention

Local-only data is retained on the device until the user removes it, clears app data, deletes applicable local content, or uninstalls the app. Guest data that is not linked to an account may therefore need to be removed from that device directly.

Account-backed and cloud-backed data is retained for as long as it is needed to provide the requested account/public features, while the account remains in use, or as reasonably necessary for security, fraud prevention, abuse prevention, legal or regulatory obligations. Website analytics is retained according to the configured Google Analytics property settings.

15. Account and data deletion

Pocket Performance Lite and the full Pocket Performance app use the same Pocket Performance account when an account is created. A request to delete that account applies to the shared Pocket Performance account.

Users can start a deletion request from the app or use the public Delete Account / Data page. Deletion requests can also be sent to pocketperformance2026@gmail.com.

When an account deletion request is completed, Pocket Performance will delete the account and associated account data, including associated public/backend records and proof media that Pocket Performance controls, except for information that must be retained for a legitimate legal, security, fraud-prevention, abuse-prevention or regulatory reason. Any such retained information is kept only for the necessary purpose and period.

Local-only files or guest data on a user's device are not centrally identifiable as account data and should be removed from that device by deleting the local content, clearing app data, or uninstalling the app.

16. Changes to this policy

This policy may be updated when Pocket Performance's features, data handling or service providers change. The latest version will remain available at this public Privacy Policy URL and the "Last updated" date above will be changed when material updates are made.

17. Contact

For privacy questions, account questions, data-access or deletion requests, or other privacy enquiries, contact pocketperformance2026@gmail.com.