ReelRoll Privacy Policy

1. Information We Access

ReelRoll operates solely as a local media viewer and reel maker. It accesses the following items locally on your device:

• Photos & Videos: Read from your device's MediaStore to display media, create reels, and organize albums.
• Media Location & EXIF: Reads camera details and GPS coordinates embedded in photos solely to resolve city names on your device using Android's native Geocoder. Location data is never sent off-device.
• Microphone: Voice-over recordings you make in the editor are stored only on your device and embedded in your exported video.
• Exported Reels: Videos and audio you export are saved to Movies/ReelRoll and Music/ReelRoll on your device.
• Collections & Tags: Custom hashtags and albums you create are stored strictly in your device's local application storage.

2. Permissions Requested

The app requests only the permissions strictly necessary for its core gallery functionality:

3. Data Collection & Sharing

• Your media: never uploaded. Photos, videos, audio, exports, tags, favorites and collections stay in local storage on your device.
• Accounts: none. There is no sign-up, login, or cloud backup.
• Analytics: optional, consent-based usage analytics (Firebase Analytics) — see section 6. There is no advertising attribution or profiling SDK, and no analytics data is sold or shared.
• Crash diagnostics: a crash reporter (Firebase Crashlytics) helps us fix bugs. It only runs after you consent, and it never sees your media — see section 5 for the exact payload and controls.
• Advertising: the app displays ads supplied by Google AdMob. The ad SDK and the crash reporter are the only third-party SDKs that receive data from the app — sections 4 and 5 describe exactly what they receive and how to control it.
• Purchases: if you choose to buy ReelRoll Pro, Google Play and RevenueCat process the purchase record needed to unlock it — see section 7. No media, account or location data is involved.

4. Advertising (Google AdMob)

ReelRoll is free and supported by advertising. Ads are served by Google AdMob, a service of Google LLC. To select and measure ads, the Google Mobile Ads SDK may access:

• Advertising ID (AD_ID): a resettable, user-controlled identifier. It is used for ad frequency capping, fraud prevention, and — only with your consent where required — ad personalization.
• Coarse technical signals: IP address (from which an approximate region may be derived), device model, operating system version, app version, language, and general ad-interaction events (an ad was requested, shown, or tapped).

What is never shared: your photos, videos, audio recordings, exported reels, file names, tags, favorites, collections, or any location derived from your media. The ads SDK has no access to your media library.

Your choices:

• Consent form: where required by law (for example the EEA, UK and Switzerland), you are asked for consent before any ad is requested. Declining does not remove any app feature.
• Change your mind: if your region requires it, Settings → Ad privacy settings inside the app reopens the consent form at any time. Consent is as easy to withdraw as to give.
• Device level: you can reset or delete your advertising ID, and opt out of ad personalization, in Android Settings → Privacy → Ads.
• Google: see How Google uses information from sites or apps that use our services and the Google Privacy Policy.

Ads in ReelRoll are requested with a maximum content rating of G and are not tagged for child-directed treatment, because the app is a general-audience tool for users aged 13 and over.

Pro users see no ads. When a ReelRoll Pro entitlement is active, the app makes no ad requests at all and no ad slot is rendered. Ads are never shown inside the editor, during onboarding, or over your media.

5. Crash Reporting (Firebase Crashlytics)

To find and fix bugs, ReelRoll uses Firebase Crashlytics, a service of Google LLC. It is the same console that tells us which Android version, device model and code path failed, so a fix can be targeted instead of guessed.

• What is sent: crash and ANR stack traces, the app version and build type, the Android version, device model and manufacturer, your device language and region, and a randomly generated Firebase installation identifier used to group reports from the same installation.
• Diagnostic breadcrumbs: short technical labels the app writes while working, for example “FFmpeg native libraries failed to load” or an export step name. They never contain file names, tags, captions, or any media content.
• What is never sent: your photos, videos, audio, exports, thumbnails, file names or paths, tags, favorites, collections, EXIF location data, contacts, or any account information — ReelRoll has no accounts.
• When it runs: only after you grant consent through the same consent form used for ads. If you decline, or later withdraw consent, crash reporting stays off. Debug builds never report.
• Retention: crash reports are kept by Google for 90 days and then deleted. You can also ask us to delete a report by contacting the address in section 9.
• Your choices: withdraw at any time via Settings → Ad privacy settings (the same consent form), or contact us. Turning it off does not affect any app feature.
• Google: see the Firebase Privacy and Security page and the Google Privacy Policy.

6. Usage Analytics (Firebase Analytics)

If you allow it, ReelRoll sends anonymous usage analytics through Firebase Analytics (a service of Google LLC) so we can see which features are used, where people give up, and what to improve. It is optional and can be switched off at any time.

• What is sent: which screen was opened (gallery, collections, studio, settings, editor), whether Pro or free, editable events such as "export started / finished / failed" with the chosen resolution and frame rate, whether the Pro offer was shown and what happened (purchase started, completed, cancelled, restored, rewarded ad result), plus app version, Android version, device model, language/region and a randomly generated app-instance identifier.
• What is never sent: your photos, videos, audio, exported files, thumbnails, file names or paths, tags, favorites, collection names, captions, EXIF or location data, contacts, or any account information — ReelRoll has no accounts.
• Not used for advertising: analytics data is not shared with advertisers and is not used for ad personalisation. Ad measurement is covered separately in section 4.
• When it runs: only after you accept the consent form, and never if you switch off Settings → Usage analytics. Debug and QA builds never report.
• Retention: Google Analytics retains event data for up to 14 months, depending on the property's retention setting, after which it is deleted. Aggregated reports may be kept longer.
• Your choices: turn it off any time in Settings → Usage analytics, or withdraw all consent in Settings → Ad privacy settings where that form is available. Turning analytics off does not affect any app feature.
• Google: see the Firebase Privacy and Security page and the Google Privacy Policy.

7. In-App Purchases (RevenueCat)

ReelRoll Pro is an optional in-app purchase that unlocks 2K/4K and 50/60 fps exports, keyframes, masks, chroma key, voice-over and removes ads. Purchases are processed by Google Play Billing and the entitlement is validated and kept in sync with RevenueCat, a service of RevenueCat, Inc.

• What RevenueCat receives: an app-generated anonymous user identifier (not your name, email or Google account), the product you bought, the purchase token issued by Google Play, your store country, the app version, and the platform (Android). It is used to validate the purchase, keep the Pro entitlement in sync after a reinstall, and support Restore Purchases.
• What is never sent: your photos, videos, audio, exports, thumbnails, file names or paths, tags, favorites, collections, EXIF location data, contacts, or any account information — ReelRoll has no accounts and no media leaves your device.
• Payments: card and payment details are handled entirely by Google Play. ReelRoll and Prodev Infotech never receive them.
• Advertising ID: RevenueCat does not receive the advertising ID from ReelRoll. Buying Pro stops ad requests in the app entirely (see section 4).
• Retention: the purchase record is kept as long as needed to provide the entitlement and to meet tax and accounting obligations. You may ask us to delete the anonymous identifier, but the app can then only restore Pro through Google Play's Restore Purchases flow.
• RevenueCat: see the RevenueCat Privacy Policy.

8. Data Retention & Deletion

Because all of your content is stored on your device:

• You can delete all application data (tags, collections, favorites, cached ad settings and the local Pro flag) at any time by clearing the app data in Android Settings → Apps → ReelRoll → Clear Storage or by uninstalling the app. A Pro purchase is tied to your Google Play account and can be restored afterwards with Restore Purchases.
• Uninstalling the app will not delete your original photos or videos from your phone.
• Ad-related data held by Google, purchase records held by RevenueCat and usage analytics held by Google Analytics are governed by their own retention policies, linked above.

9. Children's Privacy

ReelRoll is intended for a general audience aged 13 and over and is not directed to children under 13. We do not knowingly collect personal information from children. If you believe a child has used the app, contact us and we will help you remove any local app data.

10. Changes to This Policy

If this policy changes, the updated version ships with the app and the effective date above is revised. Material changes — for example a new category of data processing — will be disclosed in the app before they take effect.

11. Contact