Privacy Policy

SketchReeler (the “Service”) explains the information processed to provide app features and support.

Service name: SketchReeler
Privacy controller: SketchReeler app operator (the exact legal entity name must be verified before release)
Privacy contact: wonder13662@gmail.com
Effective date: 2026-10-30

1. Scope

This policy applies to SketchReeler’s core creation features, feedback submissions, diagnostics, and subscription flows. Additional information about the legal entity operating the app is governed by the Service’s official notices and applicable agreements.

2. Information processed and how it is processed

2.1 Creation data processed on your device

Original images you select, corrected images, project settings, and generated videos are processed and stored on your device in the normal creation workflow. These media files are not uploaded to Service servers by that workflow. Separate SDK processing for app usage events or error reports may still occur.

2.2 Feedback data you submit

When you choose to submit feedback, the feedback text, image or video attachments you selected, app version, and device context are used to handle the submission. The feedback server path uses an anonymous authentication UID and Firebase App Check verification information to protect requests.

Only when you separately consent to diagnostic collection in result feedback may a reduced project snapshot, reproduction source images, and the project’s last-image assets also be submitted. This consent is separate from selecting an ordinary image or video attachment for feedback.

If you cancel before submission, your feedback text and selected attachments are not sent to the feedback servers. SDK analytics or diagnostics related to app use are separate from feedback submission.

2.3 Information that service SDKs may process

SDK behavior and actual collection can depend on app features, SDK settings, and provider settings. The known app processing boundaries are:

Firebase Analytics: Contracted app events and limited parameters, along with app and device context, may be sent to Firebase/Google Analytics for usage and feature-quality analysis. SDK-generated events and installation identifiers may also be processed; limits on app events do not define all SDK processing.
Firebase Crashlytics: Errors and exceptions, stack traces, app version and device context, and permitted diagnostic information may be sent to Firebase for error analysis.
Firebase Anonymous Auth and App Check: An anonymous UID, app/device attestation information, and verification tokens may be processed to authenticate feedback requests and prevent abuse.
RevenueCat: Product identifiers, the App User ID, purchase and restore results, and subscription entitlement status may be processed to provide subscription features. Account linking and identifiers handled separately by the SDK depend on RevenueCat settings and policies.
Apple App Store and Google Play: These platforms process purchase authorization, billing, subscription management, and refunds. The app does not directly collect card numbers or bank account details. Provider policies apply to transaction information processed by a platform or RevenueCat.

The app currently has no dedicated in-app toggle to disable Firebase Analytics or Crashlytics collection. App event contracts alone do not establish the actual production settings or all information processed by an SDK.

3. Purposes of processing

Information is used for the following purposes:

Providing core app features such as project editing, image correction, and video generation
Analyzing errors and improving app stability
Receiving submitted feedback, reproducing issues, and providing support
Applying purchase and restore results to subscription entitlements

4. Choices, cancellation, and requests

Feedback text is sent when you choose to submit feedback.
An image or video attachment is included only when you select it and submit the feedback.
Reproduction snapshots, images, and last-image assets are submitted only when you separately consent to diagnostic collection in result feedback.
If you cancel before submission, the feedback text and attachments are not sent to feedback servers. This does not cover separate SDK analytics or error processing that may occur.
There is no in-app setting to disable or withdraw consent for Analytics/Crashlytics collection. An email request does not automatically stop SDK collection.

5. Service providers and protection

The Service uses the following providers to operate its features. Providers may process related information to deliver, secure, or bill for their services.

Firebase (Analytics, Crashlytics, Anonymous Auth, Firestore, Storage, Functions, and App Check) and Google Analytics: analytics, error diagnostics, anonymous authentication, feedback data storage/processing, and app protection
RevenueCat: Purchase/restore status and subscription entitlement processing
Apple App Store and Google Play: Platform billing, subscription management, and refunds

HTTPS is used for transmission between the app and its servers. Direct client reads and writes to feedback Firestore data are denied, and Storage uploads are restricted by authentication and path-based access rules. Anonymous authentication and App Check are required for feedback server requests. Provider security measures and processing terms are governed by their official notices and applicable agreements; the scope of third-party protection must be considered under the terms for each service.

Whether third parties processing data on the Service’s behalf are subject to protections at least equivalent to this policy must be verified against actual agreements and official notices. Release must be held if those protections cannot be confirmed. Google Analytics terms may apply separately from Firebase privacy and security notices. Firebase and RevenueCat data processing terms depend on the scope of applicable agreements.

6. Retention and deletion

The app’s feedback-data cleanup implementation uses these criteria:

Incomplete upload sessions: eligible for cleanup when they reach their expiration time (expiresAt), 24 hours after session creation.
Submitted general attachments and diagnostic assets (reproduction source images, last-image assets, and repro manifest): eligible for deletion from Storage 90 days after submission (submittedAt).
Submitted feedback metadata in Firestore: eligible for deletion 365 days after its creation time (createdAt).

Cleanup runs daily, so deletion may occur at the next run rather than immediately at the threshold. If a Storage asset cannot be deleted, the related feedback metadata is retained and deletion is retried in a later cleanup run. This app cleanup does not set retention for Firebase Analytics, Crashlytics, RevenueCat, App Store/Google Play, or separate backups and transaction records. Retention and deletion for those data are subject to each provider’s terms and actual settings.

7. Security

The Service uses HTTPS for data in transit and restricts access to feedback data with authentication and authorization rules. The feedback server path requires anonymous authentication and App Check. See each provider’s official notices and applicable agreements for its own safeguards and protection of stored data.

8. Sale and ad tracking

The Service does not sell personal information.

Whether Firebase Analytics, RevenueCat, or connected service settings meet Apple’s definition of tracking cannot be determined from app code alone. Apple’s current definition and production SDK/console integrations must be verified before release, and the result and any required disclosures must be reflected here. Until that verification is complete, this policy cannot be used as a statement that tracking does or does not occur; release must be held until the required review and disclosures are complete.

You may contact us to ask whether submitted feedback data is held and what action is available:

Privacy contact: wonder13662@gmail.com
Examples: request access to or deletion of submitted feedback, or inquire about withdrawing consent for diagnostic submission

We may need additional information to verify your identity and define the scope of a request. An email request does not automatically stop SDK collection or delete all data held by the Service and third parties. We will assess whether submitted data can be identified, provider retention, and deletion exceptions, then explain the available actions and limitations. A diagnostic-consent withdrawal inquiry does not automatically delete diagnostic data already submitted.

10. Changes to this policy

This policy may change when laws, Service features, or external provider practices change. We will update the effective date on this page when making a material change.