Privacy Policy

RetroSnap

Last updated: August 19, 2026

1. Introduction

This Privacy Policy explains how RetroSnap ("we", "our", or "the app") handles information when you use the mobile application.

This policy is a notice about data handling, not a request for blanket consent. Where consent is legally required, it must be requested separately through an appropriate consent flow.

2. Photos, Edits, and Local Data

Photos captured or imported in RetroSnap, captions, displayed dates and locations, editing choices, and the in-app collection are stored on your device. App preferences are also stored locally. RetroSnap does not provide user accounts, cloud photo storage, or a developer-operated photo upload service.

When you export an image, it is saved to your device gallery. When you choose Share, the file is passed to the operating system's share sheet and then to the service you select. That service's privacy policy applies.

3. Information Processed by Online Services

RetroSnap uses software development kits provided by Google LLC. Depending on your device, settings, region, and how you use the app, these services may process information such as IP address, device and app information, advertising or app-instance identifiers, interactions, approximate location inferred from IP address, diagnostics, and crash data.

3.1. Firebase Analytics

Firebase Analytics records app and feature interactions so we can understand usage and improve RetroSnap. Events may include opening screens, capturing or importing a photo, saving, sharing, deleting, using location, and ad lifecycle events. Event properties may include counts, platform, feature state, and error text. The app does not intentionally include your photo files, caption text, or precise location coordinates in Analytics events.

3.2. Firebase Crashlytics

Firebase Crashlytics processes crash reports, exceptions, device and operating-system details, app state, diagnostic logs, and generated identifiers to help diagnose stability problems. Logs can include operation names and locally generated item identifiers, but the app does not intentionally attach photo files or caption text to crash reports.

3.3. Google AdMob

RetroSnap displays app-open ads through Google AdMob. AdMob may collect or receive advertising identifiers, IP address, device information, ad interactions, impressions, clicks, and diagnostic data to deliver, measure, limit, and protect advertising. Ad selection and measurement may also depend on Google account, device, advertising, and regional settings.

3.4. Firebase Remote Config and App Check

Firebase Remote Config retrieves settings such as supported app versions and maintenance status. Firebase App Check helps verify that requests come from a legitimate app installation. These services may process app, device, network, integrity, and technical request information.

3.5. Google Fonts

RetroSnap supports Google Fonts. Font files or font catalog pages may be requested over the internet, especially when you add a custom font. Google may receive standard network information such as your IP address and request details.

4. Camera, Photos, and Location

• Camera: Used to take photos in the app.
• Photo library or media access: Used when you import an image or save an exported result.
• Location: Optional and used only when you request a location label. RetroSnap obtains the device's current location and asks the platform geocoding service to convert coordinates into a place name. That provider may process the coordinates under its own privacy terms. The resulting label is stored locally with the photo.

You can deny or revoke permissions in system settings. Some related features will then be unavailable, while the rest of the editor remains usable.

5. How Information Is Used

• Provide photo capture, editing, local storage, export, and sharing features.
• Deliver and measure advertising.
• Understand feature usage and improve the app.
• Detect crashes, diagnose errors, and maintain security and compatibility.
• Retrieve current app configuration and minimum-version requirements.

Local processing is necessary to provide the editing features you request. Online analytics, diagnostics, security, configuration, and advertising are used to operate, protect, maintain, and fund the app. The legal basis for a particular activity depends on your region and may include performance of the requested service, legitimate interests, or consent where applicable law requires it.

6. Sharing and Service Providers

We do not sell your photos. Information described above is processed by Google through Firebase and AdMob to provide analytics, crash reporting, security, configuration, and advertising services. Google handles this information under its own terms and privacy practices.

• Google Privacy Policy
• Firebase Privacy and Security
• How Google uses information for advertising

7. Retention and Deletion

Local photos and editing data remain on your device until you delete them or uninstall the app. Files exported to your gallery or sent to another service must be deleted separately.

Google retains data collected through Firebase and AdMob according to the retention periods and criteria configured for those services and described in Google's service documentation. Diagnostic information is retained only as long as needed to investigate stability and security, subject to provider settings and legal requirements. You may reset or limit your device's advertising identifier and ad personalization through your device or Google settings.

8. Your Privacy Rights

Depending on your location, you may have rights to request access, correction, deletion, restriction, objection, or portability of personal data, and to withdraw consent where processing relies on consent. You may also lodge a complaint with the data-protection authority in your country. Contact us using the details below to exercise a right. We may request enough technical information to verify and locate data associated with third-party service identifiers.

9. Security

Online service requests use encrypted transport where supported, and local data is protected by your device's operating-system controls. No storage or transmission method can be guaranteed completely secure.

10. Children's Privacy

RetroSnap is not directed to children under the minimum age required by applicable law. We do not knowingly ask children to create an account or provide direct contact information. If you believe a child has provided personal information through the app or its services, contact us.

11. International Processing and Legal Disclosures

Google may process information in countries other than your own under the transfer mechanisms and safeguards described in Google's privacy and data-processing terms. We or our service providers may disclose information when required by law, legal process, or to protect users, the public, or legal rights.

12. Changes to this Policy

We may update this Privacy Policy to reflect changes to the app, services, or legal requirements. The date at the top shows the latest revision. Please review this page periodically.