Effective date: 8 October 2026

This policy explains what the Twinn app ("Twinn", "we", "us") does with information on iPhone, iPad and Android. Twinn is published by Imran Khan, United Arab Emirates. In short: the photos you take stay on your phone and are never uploaded. Twinn has no account and shows no ads. To run the app we use a few services that receive limited technical information, described below.

1. What stays on your phone

Twinn handles the following only on your device. We never receive it:

• The camera preview and the photos you take. The camera feed is shown live on your screen and is never recorded or sent anywhere. When you take a photo, Twinn saves it to your gallery (in a "Twinn" album on Android) and may keep a copy in the app's private storage so you can see your shots in Twinn. The pose overlay is never part of the saved photo.
• A photo you pick with Use my photo (Twinn Pro). Twinn reads only the photo you choose, through your phone's photo picker, and shows it over your camera.
• Your settings and saved poses: which poses you want to see (girls, guys or both), the grid and level guides, the poses you bookmark, and whether you finished the welcome screens.
• Your daily pose count: which poses you loaded today, so the free daily limit works. It is kept in encrypted storage (the Keychain on iPhone, Keystore-protected storage on Android).

2. Information that leaves your phone

Twinn uses these services, which receive limited information:

Pose images (Cloudflare)

Twinn downloads the pose catalog and pose images from our content server, hosted by Cloudflare. As with any website, Cloudflare processes your IP address and basic request details to deliver the images and protect the service. We don't use these requests to identify you. See Cloudflare's privacy policy.

Purchases (RevenueCat, Apple and Google)

When you view, buy or restore Twinn Pro, the purchase goes through the App Store or Google Play, and our subscription provider RevenueCat receives an anonymous app user ID it creates, the store's receipt and the products bought, with standard technical data: platform, device model, OS and app version, language and store country. On iOS this can include the identifier for vendor (IDFV). It is used to provide and restore your purchase and to give us totals such as the number of subscribers. RevenueCat never receives your photos. See RevenueCat's privacy policy. Payments are handled by Apple or Google under their own privacy policies; we never see your payment details.

App analytics (Google Analytics for Firebase)

To understand how Twinn is used and make it better, Twinn sends usage events to Google Analytics for Firebase. For example: finishing the welcome screens, opening a pose category, the words you type in pose search, previewing or picking a pose (its pose and category IDs), taking a photo (zoom level, overlay opacity, mirroring, and whether a pose or your own photo was used, never the photo itself), reaching the free daily limit, and opening the Pro screen or buying. Two settings are attached to these events: whether you have Twinn Pro, and which poses you chose to see.

Firebase also collects standard information: a random app-instance ID, device model, OS and app version, language, session details, and an approximate location (country or region) worked out from your IP address. On Android, the Firebase SDK can also read your device's advertising ID; you can reset or delete it in your Android settings. We don't use analytics for advertising and don't link it to your name or contact details. See Google's privacy policy and how Google uses information from apps.

Crash reports (Firebase Crashlytics)

If Twinn crashes or hits an unexpected error, the app sends a report to Firebase Crashlytics: what went wrong in the code, device model, OS and app version, memory and storage state, screen orientation, and a random installation ID. File paths are removed before a report is sent, and reports never include your photos.

3. What we don't do