Last updated: 2026-10-08
Your privacy is important to us. The app is built so that your photos, videos, and files stay on your device unless you explicitly export or share them using your operating system’s features. To keep the app reliable and understand how core features are used, we use third-party crash reporting and analytics services. This policy describes both what stays on your device and what limited technical and app interaction data may be sent for diagnostics, product improvement, and measurement of our advertising campaigns. The Apple Ads attribution described in section 4.1 applies starting with Photo Paranoid version 1.1.8.
We do not:
All content you add to the app remains stored locally on your device unless you choose to share or export it yourself.
We use Google Firebase Crashlytics (provided by Google LLC) to receive crash reports and limited technical diagnostics when the app crashes or encounters recoverable errors. This helps us understand bugs, improve stability, and fix issues. Recoverable subscription-loading errors may also include the technical context described in section 4.
Crash reports may include, for example:
We do not use Crashlytics to collect the contents of your photos, videos, or files.
We do not use Crashlytics for targeted advertising or for tracking you across other companies’ apps or websites.
Unless separately stated in the app, we do not attach custom user identifiers or custom keys containing personal information to crash reports. Non-personal diagnostic logs may include app event names to help us understand what happened before a crash.
Google’s privacy practices for Firebase are described in Google’s documentation and privacy policy. You can learn more about Firebase at firebase.google.com/support/privacy.
We use Google Firebase Analytics (provided by Google LLC) to understand basic app usage and improve the app experience. Analytics events may include onboarding progress, import and export outcomes and file counts, PIN setup and the method used to unlock the vault, viewing the paywall, selecting a subscription plan, starting or completing a purchase flow, restoring purchases, changing app settings, tapping review prompts, or enabling app privacy features.
Firebase Analytics may collect limited technical and usage information, such as app version, device and operating system information, approximate usage timing, app-instance or installation identifiers, and event names or event parameters related to app interactions, including subscription-related interactions.
We do not use Firebase Analytics to collect the contents of your photos, videos, or files. We also do not use Firebase Analytics for targeted advertising or for tracking you across other companies’ apps or websites. We do not intentionally collect Apple’s advertising identifier (IDFA); depending on device and operating system behavior, Firebase Analytics may use non-advertising app or vendor identifiers for measurement and diagnostics.
To diagnose unavailable subscription plans, we may send Firebase Analytics and Crashlytics the App Store storefront country or region, the number of products requested and returned, and technical loading outcomes and error codes. We also measure whether loading succeeds after a retry. The storefront is the region of the App Store used for purchases; it is not your GPS or physical location. These diagnostics do not contain your Apple Account identifier, payment details, or vault contents. Firebase may associate analytics events with an app-instance or installation identifier, as described above. We use storefront diagnostics only to investigate technical availability, not for advertising or profiling.
Starting with version 1.1.8, we use Apple's AdServices framework to ask Apple whether an app installation is attributed to one of our Apple Ads campaigns. The app obtains an attribution token and sends it directly to Apple's attribution service. We do not persist this token or send it to Firebase.
Depending on the information Apple makes available, the response may include attribution status, campaign, ad group, keyword and ad identifiers, attribution and conversion types, country or region, and ad placement. Keyword identifiers identify advertising keywords; we do not receive the text of your individual search query through this integration.
We save the available attribution fields locally and send them to Google Firebase Analytics with app interaction events, including paywall views, selected subscription plans, purchase-flow outcomes, and use of app features. We use this information to understand which campaigns bring users to the app and how those campaigns relate to app usage and subscription activity.
Firebase can associate these events with an app-instance or installation identifier. This means the event-level data is pseudonymous, rather than fully anonymous, even when we review it in aggregate reports. You do not need to provide your name or create an account for this measurement.
These events do not include PIN values, biometric data, filenames, media metadata, or the contents of your vault. We do not use this integration to show advertisements inside the app or to build audiences for personalized advertising across other companies' apps and websites.
The app does not require you to create an account or provide your name, email, or phone number to use its core features.
The app can lock your content behind a PIN code, and optionally let you unlock it with Face ID or Touch ID. Your PIN is stored only on your device in the system keychain and is never sent to us. Biometric authentication is performed entirely by your device’s operating system; the app never receives, sees, or stores your Face ID or Touch ID data, which remain protected by the device’s Secure Enclave. Content you add to the app is protected on disk using your device’s built-in data protection.
Payments and subscriptions are processed exclusively by Apple through the App Store. We do not receive or store your full payment card or billing details.
The app is not directed at children for the purpose of collecting personal information. If you believe information has been received in error, please contact us.
We may update this Privacy Policy from time to time. The “Last updated” date at the top will change when we do.
If you have any questions about this Privacy Policy, you can contact us at:
photo.paranoid.contact@gmail.com
For app support, visit PhotoParanoid Support.