Data safety summary — Hitchwise

Effective 20 August 2026

Provided by: Nikah AI Ltd, Office 1216, 60 Tottenham Court Road, Fitzrovia, London, W1T 2EW, United Kingdom

*This is the plain-English version of the Google Play Data safety form and the Apple App Privacy card for Hitchwise. It is written from this app's shipping code — the permissions it actually declares and the SDKs actually linked into the binary — and not from a template covering several products.*

Summary

Question	Answer for Hitchwise
Does the app collect data?	No
Does the app share data with third parties?	No
Is any data transmitted off the device?	No, apart from the Apple or Google purchase transaction
Is data encrypted in transit?	Not applicable — the app sends none. The store's own purchase connection uses the platform's transport security
Can the user request deletion?	Yes — immediate and on-device. See the account and data deletion page
Does the app have user accounts?	No
Is the app directed at children?	No — intended audience: 12+
Does the app contain ads?	No
Does the app use an advertising identifier?	No. The AD_ID permission is explicitly blocked in the Android manifest

Data collected: none

Hitchwise contains no analytics SDK, no crash-reporting SDK, no advertising SDK and no attribution SDK. There is no operator server. No network call is made to Nikah AI Ltd at any point, because there is no endpoint to call.

On the Play Data safety form, every "Data collected" and "Data shared" category is therefore answered No.

Data stored on the device only

The following is kept locally so the app remembers your choices between sessions. Under the Play Data safety definitions this is not collection, because it never leaves the device:

your unit preference (metres or feet)
which tow vehicle and trailer you selected
whether you have acknowledged the safety notice
whether the trailer trace is switched on
an on-device entitlement flag if you have bought Lifetime Pro

Your finished practice runs are saved on this device so you can see whether you are improving. The most recent 200 are kept and older ones are dropped automatically. They stay on your phone, are never sent anywhere, and you can delete them all at once from the History screen. Resetting your settings deliberately leaves them alone, so clearing your history is a separate, explicit action.

Permissions actually requested

Hitchwise requests no runtime permissions at all. It does not ask for the camera, the microphone, location, contacts, photos, or any device identifier. There is no permission prompt anywhere in the app.

Third-party SDKs linked into the binary

Apple StoreKit / Google Play Billing, through the in-app purchase library. It contacts the store when the app starts, to read prices and check what you already own, and again when you buy or restore. The store receives the transaction; Nikah AI Ltd receives nothing.
React Native, Expo and their standard runtime modules, which perform no data collection in this configuration.

Nothing else. There is no Firebase, no Google Analytics, no Meta SDK, no AppsFlyer, no Sentry and no Crashlytics.

Tracking

Hitchwise does not track you across apps or websites. It does not read the IDFA or the Android advertising id, and it never shows the App Tracking Transparency prompt, because there is nothing it would be asking permission for.

Security practices

Data sits in the app's private, sandboxed storage, protected by the operating system's app sandbox and device encryption. Nikah AI Ltd claims no encryption beyond what iOS and Android provide, because no data reaches us to protect.

Data deletion

Immediate, on-device, and available without an account. See the account and data deletion page.

Contact

privacy@legalnikahai.com · support@legalnikahai.com · Nikah AI Ltd, Office 1216, 60 Tottenham Court Road, Fitzrovia, London, W1T 2EW, United Kingdom

*Hosted at https://legalnikahai.com/hitchwise/data-safety.html. The answers here must stay identical to the Play Console Data safety form and the App Store Connect App Privacy card.*