ReFrame Privacy Policy

Publisher, scope and account model

ZenovaApps publishes ReFrame — Same Shot Stories. Privacy and data questions can be sent to zenovaappsteam@gmail.com.

ReFrame is an accountless, local-first camera and media utility. It does not provide a ReFrame account, social feed, developer cloud-sync library or first-party analytics service. Most project processing happens on the device. Android backup, Google Mobile Ads and consent, Google Play Billing, email, and apps chosen for sharing are separate services governed by their own controls and policies.

Information stored and processed on the device

• Project names, categories, notes, cadence, reminder preferences, capture dates, camera and alignment settings, frame order, per-frame duration and local export status.
• Photos captured in ReFrame and private copies of photos you deliberately import with Android’s system Photo Picker.
• Generated transformation videos, temporary encoding files and private export copies until they are deleted or moved outside the app.
• Language, theme, reduced-motion, notification, privacy-choice, onboarding and other app settings.
• A local Pro-entitlement value and verification time used to reflect Google Play ownership. ReFrame does not store payment-card details.

Camera and Photo Picker

ReFrame requests camera access only when you enter the capture workflow. The permission is used for the live preview and photos you deliberately take. Denying it prevents new capture but does not remove existing local projects.

When you import a frame, Android’s system Photo Picker gives ReFrame access only to the item you select. ReFrame copies that item into app-private project storage. The app does not request broad photo-library access. A selected source file can contain visual content and embedded metadata supplied by its source; ReFrame does not intentionally send that file or metadata to ZenovaApps.

The current version does not request microphone, contacts, precise location or approximate location permission.

Private storage and Android backup

Current project metadata and project images are stored in ReFrame’s app-private area. Other apps normally cannot browse that area directly.

Android backup is enabled. Eligible project metadata and files can be copied through Android cloud backup or device-to-device transfer depending on the device, Google account, provider and backup settings. ZenovaApps 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.

Exports and sharing

Video creation uses the 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 receiving app or service temporary access to the selected video.

A receiving app or service can upload, copy, retain or further share that video under its own terms. Deleting a ReFrame project, clearing app storage or uninstalling ReFrame does not remove copies already saved or shared outside ReFrame.

Reminders, notifications and widget visibility

Reminders are off by default. If enabled, a notification can contain a project name and can be visible according to Android lock-screen settings. A ReFrame widget can show a project name on the launcher. Use non-sensitive project names or adjust Android notification, lock-screen and widget settings when other people can see the device.

Google Mobile Ads 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 Free export. Ordinary capture, compare and Free export do not require a rewarded ad. Active Pro subscribers and Lifetime owners do not receive ReFrame ad placements while their entitlement is active.

ReFrame uses Google User Messaging Platform (UMP) to update consent information, show a consent form where required and expose privacy options before eligible Google Mobile Ads requests. Depending on region, choices, device settings and Google configuration, Google services can process IP address, app interactions, advertising or device identifiers, diagnostics, approximate signals, consent choices, advertising measurement and fraud-prevention data.

ReFrame does not intentionally add project names, photo bytes, file paths, alignment scores, video contents or Google Play purchase tokens to an ad request. Google explains its processing in the Google Privacy Policy and its information-from-partners notice.

Google Play Billing and purchase state

Google Play provides eligible product details, handles checkout and payment, maintains transaction history, and controls subscription management and refunds. ReFrame can receive product identifiers, current purchase state and a purchase token to acknowledge and restore eligible ownership. The current app does not persist the purchase token; it stores a local entitlement value and verification time.

Deleting ReFrame does not cancel a subscription or delete Google Play purchase history. Use Google Play subscription controls to manage or cancel an eligible monthly or yearly plan.

Deletion and retention

Because ReFrame has no first-party account, there is no ReFrame account-deletion workflow. The separate Delete local data page provides step-by-step guidance without pretending to perform a remote deletion.

• Delete individual frames while a project still contains more than one frame.
• Delete a project after confirmation to remove its current app-private photos, metadata and matching private ReFrame export copies when deletion succeeds.
• Clear ReFrame storage in Android Settings or uninstall the app to remove current app-private data. Android backup can later restore eligible data depending on the provider and device settings.
• Delete saved videos, documents and copies sent to other apps from their destination separately. Google Play, advertising-consent and provider backup records are controlled separately.

Support correspondence

If you email zenovaappsteam@gmail.com, the sender address, message, attachments and mail-routing metadata are processed through the email services used by you and ZenovaApps so the request can be read, answered, secured and retained as reasonably needed for support, fraud prevention or legal obligations. You may ask support to delete a prior correspondence where applicable, subject to required security or legal retention.

Do not send passwords, access codes, raw purchase tokens, full payment-card information, unnecessary identity documents or private photos that are not needed to investigate the request.

Security, children and changes

ReFrame uses app-private storage, atomic metadata writes, temporary Android file-sharing grants and supported Google SDK and network paths. No storage or transmission system can be guaranteed completely secure.

ReFrame is a general-purpose visual creation utility. It is not directed to children and does not intentionally perform facial recognition, identity verification, medical diagnosis or sensitive-trait inference.

Material changes to these practices will be posted here with a revised effective date and communicated through the app or store listing when required.