ReFrameby ZenovaApps

Privacy

ReFrame Privacy Policy

This policy explains what ReFrame processes on your device, what can reach Google or an Android backup provider, and what only leaves the app when you choose to save or share it.

Effective 29 August 2026

1. Who we are and what ReFrame does

ReFrame — Same Shot Stories is an Android app published by ZenovaApps under package com.noorlabs.reframe. It helps you return to an earlier camera framing, organize repeat photos in local projects, compare changes, and create transformation videos.

ReFrame does not require a ReFrame account and does not use a ReFrame-owned cloud backend, social feed, or first-party analytics service. Most project processing happens on your device. Android backup, Google ads and consent, Google Play Billing, and the apps you select for sharing operate under their own terms.

2. Information processed on your device

ReFrame may process and store the following locally:

  • project names, internal project and frame identifiers, and creation or update times;
  • photos you deliberately capture for a project;
  • capture time, frame duration, local file path, and optional alignment score;
  • live preview brightness and edge samples used to estimate horizontal and vertical alignment;
  • temporary and private transformation-video files;
  • language, theme, onboarding, reminder, entitlement, ad-frequency, and rewarded-export-credit preferences.

The alignment analyzer works on preview samples in memory. It is not intended to identify faces, people, health conditions, or biometric identity, and it does not intentionally create a hidden preview recording.

3. Camera and device permissions

ReFrame requests camera access when you use the capture flow. It uses this permission for the live preview and photos you deliberately capture. The current app does not request microphone, precise location, contacts, or broad image- or video-library permissions. Denying camera permission prevents capture but does not affect access to existing local projects.

4. Local storage and Android backup

Project metadata and captured project images are stored in ReFrame's app-private area. Android backup is enabled. Current backup rules allow the projects directory and project metadata file to participate in Android cloud backup and device-to-device transfer. Depending on your Android device, account, provider, and backup settings, project names, metadata, and photos may therefore be copied by the Android backup system.

ReFrame does not control a backup provider's encryption, retention, restore, or deletion schedule. Clearing current app data does not prove that every older provider-held backup snapshot was immediately deleted.

5. Saving and sharing videos

Video creation uses your device's local media codec path. When you choose Save, ReFrame copies the completed video to Android shared storage or a document location you select. When you choose Share, Android gives the app or service you select temporary access to the one chosen video.

The receiving app or service may upload, copy, retain, or further share that video under its own privacy terms. Clearing ReFrame data or uninstalling ReFrame does not remove copies saved outside ReFrame's private storage.

6. Reminders and widget visibility

Reminders are off by default. If you enable them, a notification may contain a project name and may appear according to your lock-screen settings. If you add the ReFrame widget, it may show a project name on your launcher. Use non-sensitive names or adjust Android notification and widget settings if others can see your device.

7. Advertising and consent

The Free experience can request a Home banner, a frequency-controlled interstitial after certain successful video saves, and an optional rewarded ad that removes the ReFrame end card from one successful export. A normal Free export does not require a rewarded ad. Active Pro subscribers and Lifetime owners do not receive these ReFrame ad placements.

ReFrame uses Google User Messaging Platform and Google Mobile Ads. Depending on your region, choices, device settings, and Google's configuration, these services may process device and app signals, advertising identifiers, consent choices, ad interactions, diagnostics, approximate signals, and fraud-prevention or measurement data. ReFrame does not intentionally add your project names, photo bytes, file paths, alignment scores, video contents, or Play purchase tokens to ad requests.

When required, ReFrame provides a privacy-options entry so you can revisit consent choices. Google explains its practices in the Google Privacy Policy and its page about information from apps that use Google services.

8. Google Play Billing

ReFrame uses Google Play Billing to show eligible plans, start purchases, restore owned items, acknowledge purchases, and open subscription management. Google Play—not ReFrame—handles payment credentials. ReFrame can receive product details, purchase state, product identifiers, and a purchase token. The current app uses the token for Play acknowledgement and does not persist it; it stores only a local entitlement value and verification time.

Clearing ReFrame data does not cancel a subscription or erase Google Play purchase history. You can manage or cancel a Google Play subscription through Google Play.

9. Retention and deletion

  • You can delete individual frames while a project still has more than one frame.
  • Project deletion requires confirmation and removes the project's current private photos and matching private ReFrame video copies when deletion succeeds.
  • Videos already saved to shared storage or sent to another app are not removed by project deletion.
  • ReFrame currently has no single in-app “delete all local data” action. Android Settings can clear ReFrame storage; uninstalling normally removes current app-private data, subject to Android backup and restore.
  • Google ad, consent, and purchase records follow Google's controls and retention; provider backups follow the backup provider's controls.

Because ReFrame has no first-party account, there is no ReFrame account-deletion process.

10. Security and international processing

ReFrame uses app-private storage, atomic metadata writes, Android file-sharing grants, and supported Google SDK and network paths. No system can be guaranteed completely secure. Google services, an Android backup provider, and a receiving share app may process information in locations governed by their infrastructure and policies.

11. Children and sensitive uses

ReFrame is a general-purpose visual creation utility. It is not designed as a medical, biometric, identity, or child-directed service, and it does not intentionally perform facial recognition or sensitive-trait inference. Do not use ReFrame for unlawful surveillance or to process sensitive material without the necessary rights and safeguards.

12. Changes and contact

We will update this policy before shipping material changes such as first-party accounts, cloud sync, new analytics, new advertising partners, broad media import, audio, location, or cloud-based processing. The effective date at the top identifies the current version.

Privacy and support contact: zenovaappsteam@gmail.com. ZenovaApps does not publish a support phone number.