Privacy Policy.

2.1 Information users create or store in the App

The App may store the following information on the user's device:

• Photos and videos captured in the App or selected by the user from the device's photo library
• Processed photos and videos, video thumbnail images, and the date and time associated with each item
• Film-roll metadata such as media type, selected camera or film preset, aspect ratio, dimensions, video duration, source, favorite status, and processing status
• Capture, processing, and export settings such as frame, timestamp, rotation, scale, image positioning, and whether to save original media
• App settings such as theme, language, onboarding completion status, and storage preferences
• Location coordinates embedded in a captured photo's metadata if the user enables the optional Save Location setting and grants location permission

This information is used to provide the App's core functionality and is generally stored locally on the user's device, such as in the App sandbox, local database, or local settings storage.

In particular, captured or imported photos and videos may be copied into the App's private local storage so that processed media can remain available in the film roll even if the original media is later removed from the user's device photo library.

2.2 Information users voluntarily submit

If a user submits feedback or a support request through the App, we may receive:

• The feedback or message content submitted by the user
• App language setting
• Time zone information
• App version
• Platform and operating system version

Feedback messages may contain personal information if the user chooses to include it. Users should avoid submitting sensitive personal information through feedback forms unless necessary.

2.3 Information that may be collected automatically

To operate, improve, and troubleshoot the App, certain technical or usage-related information may be collected automatically, including:

• Crash reports and error logs
• Device and operating system information
• App version information
• Screen view information
• Feature usage events
• Interaction events such as camera use, media imports, processing, saves, shares, film-roll actions, settings changes, and feedback submissions
• Advertising information, such as ads viewed, ad impressions, clicks, and other interactions with ads
• Device or app identifiers, which may include an advertising identifier, app set ID, app-scoped identifier, or other device identifier
• IP address and general location information inferred from the IP address
• Purchase and subscription information, such as product identifiers, purchase history, transaction identifiers, receipts or purchase tokens, subscription status, and entitlement status
• An App User ID used by RevenueCat, which may be a randomly generated anonymous identifier unless another identifier is configured
• Advertising consent and privacy preference signals

We use this information to maintain App stability, diagnose issues, improve performance, manage purchases and subscriptions, deliver and measure advertising, prevent fraud, and better understand how the App is used.

2.4 Permissions

The App may request the following device permissions:

• Camera: to allow the user to capture photos and videos in the App
• Microphone: to record audio when the user captures video
• Photo library: to import photos and videos and save processed media to the device's photo library
• Location: to embed the current coordinates in a captured photo's metadata when the user enables the optional Save Location setting
• Tracking permission on supported Apple devices: where applicable, to allow the use of data for tracking or personalized advertising. Users may deny this permission.

Users can grant, deny, or later revoke these permissions through their device settings.

5.1 Service providers

We may use third-party service providers to help operate and support the App, including providers in the following categories:

• Analytics providers: may process app usage events, screen views, and interaction data. Based on the current codebase, PostHog is integrated.
• Crash and diagnostics providers: may process crash reports, error details, device data, and app version information. Based on the current codebase, Firebase Crashlytics is integrated.
• Feedback or inquiry processing infrastructure: may process messages that users choose to submit through the App. Based on the current codebase, a Google-hosted endpoint is used for feedback submission.
• Purchase and subscription infrastructure: RevenueCat may process App User IDs, device and operating system information, purchase history, Apple receipt files, Google purchase tokens, subscription status, and related transaction metadata.
• App marketplace and billing providers: Apple App Store and Google Play process payments and may provide us and RevenueCat with purchase confirmations, transaction identifiers, receipts or purchase tokens, subscription status, and related information.
• Advertising providers: Google AdMob and its advertising partners may process IP address, general location inferred from IP address, device or app identifiers, advertising data, user interactions, crash logs, and performance data to deliver, measure, secure, and, where permitted, personalize ads.

We expect such providers to process information only as needed to provide services on our behalf and subject to their applicable contractual and legal obligations.

5.2 In-app purchases and subscriptions

Purchases and subscriptions offered through the App may be processed by Apple App Store on Apple devices or Google Play on Android devices. Those marketplaces process users' payment method details under their own terms and privacy policies. We do not directly receive or store full payment card or bank account details.

We use RevenueCat to validate purchases, maintain subscription and entitlement status, restore purchases, and support related analytics and fraud prevention. RevenueCat receives transaction information from the applicable app marketplace, which may include Apple receipt files or Google purchase tokens, and associates it with an App User ID. If the App does not use an account-based identifier, RevenueCat may generate a random anonymous App User ID.

5.3 Advertising and AdMob

The App may display ads provided by Google AdMob and participating advertising partners. Depending on the App's configuration, the user's region, consent choices, device settings, and applicable law, these may be personalized, non-personalized, or limited ads.

Personalized ads may use information about a user's interests or prior activity. Non-personalized ads use contextual information, such as the App's content and general location, rather than prior behavior for ad targeting, but may still use identifiers or local storage for functions such as frequency capping, aggregated reporting, security, and fraud prevention. Limited ads reduce the use of personal data for ad personalization, although information such as IP address may still be used to deliver an ad and protect against fraud or abuse.

Where required, we or Google may ask for consent before using personal information or device storage for personalized advertising. On supported Apple devices, the App will request permission through Apple's App Tracking Transparency framework before engaging in tracking that requires permission. Denying tracking permission does not necessarily prevent all ads from being displayed.

5.4 System-level or user-selected third-party sharing

If a user uses the App's share functionality, the destination app or platform is selected by the user. Once the user shares content to a third-party app or service, that third party's privacy practices apply.

5.5 Legal compliance and protection

We may disclose information where necessary to:

• Comply with applicable law, regulation, legal process, or government request
• Protect the rights, property, safety, or security of users, our business, or others
• Detect, investigate, or prevent fraud, abuse, malicious activity, or technical issues

6.1 Local data stored on the device

Captured or imported photos and videos, processed media, thumbnails, film-roll metadata, and app settings used for core functionality are generally stored on the user's device.

• If a user deletes an item from the film roll within the App, related local media and metadata may be deleted.
• If a user deletes the App, data stored within the App's local storage is generally removed as part of the app removal process.
• Depending on the device operating system, backup settings, or system behavior, some data may temporarily persist in device backups or caches.

6.2 Data processed through third-party services

Feedback, analytics, diagnostic, advertising, purchase, and subscription data processed through third-party services may be retained:

• For as long as reasonably necessary to respond to inquiries and improve the App
• For debugging, reliability, fraud prevention, and security purposes
• For the duration of a subscription and as needed to maintain purchase history, validate entitlements, process refunds, restore purchases, and meet accounting or marketplace requirements
• For advertising measurement, frequency capping, reporting, security, and compliance, subject to the settings and retention practices of Google and participating advertising partners
• For longer if required by law or needed to resolve disputes or enforce rights

Specific retention periods may vary based on operational settings, legal obligations, and the policies of the relevant third-party service provider.