replayon← Back home

App privacy policy

ReplayOn App Privacy

This policy describes ReplayOn’s Android phone app and Wear OS companion. “We” and “us” refer to mintakalabs.

Effective September 22, 2026

Developer and contact

Developer: mintakalabs.

Privacy and support contact: [email protected].

Website data is covered separately in our Website Privacy policy.

Camera, microphone, and replay recordings

ReplayOn uses your phone's camera to display the live preview and record a rolling replay buffer. The camera preview can be active before you press Start. If audio is enabled and microphone permission is granted, microphone capture begins as part of starting replay recording. You can turn audio off in Settings.

During recording, recent encoded video and optional audio are held temporarily in phone memory. Older buffered content is discarded as the replay window advances. Unsaved buffer content is not retained as a saved video when the recording session ends. This is not a guarantee of secure memory erasure; a save already in progress can retain its snapshot until that operation finishes.

When you save a replay from the phone or watch, ReplayOn writes an MP4 to your phone's shared media storage, normally under Movies/Camera Replay. A pending file or media entry is used while saving. The app attempts to remove incomplete saves if an error occurs, but a crash or interrupted cleanup can leave remnants.

Saved videos remain until you delete them using your Gallery or file manager. Uninstalling ReplayOn does not necessarily remove these shared-media files. ReplayOn does not upload recordings to a developer-operated server or send recorded video, audio, or preview images to the watch.

Settings and permissions

ReplayOn stores your selected replay duration, audio setting, and video quality locally so they can be restored when you reopen the app. You can change them in Settings or clear the phone app's storage through Android settings.

The phone uses camera permission for preview and recording, microphone permission for enabled audio recording, and storage permission on older Android versions to save replays. The Wear app uses notifications to show recording readiness and replay duration. This status may be visible on the watch's lock screen, depending on device settings. You can manage permissions and notifications in system settings; denying permissions can limit related features.

Phone and watch communication

To support the optional Wear OS companion, the phone app publishes limited replay-status information through Google Play services. This can begin when the phone app opens, even without a currently connected watch.

The devices exchange recording/save status, replay duration, buffer readiness, timestamps, session and request identifiers, and save commands and results. Connection identifiers supplied by Google Play services are used to discover devices and route messages. Recordings, preview images, filenames, and saved video locations are not included in these messages.

Google Play services can carry these messages over Bluetooth or through Google's servers, depending on connectivity. Google documents that cloud-routed Data Layer content is end-to-end encrypted. See the Data Layer overview and Google Privacy Policy linked below.

Google Play services stores and synchronizes the latest status item. ReplayOn updates it as status changes; stopping normally replaces active status with inactive status rather than deleting the item. There is no app-defined expiry for this synchronized item, so do not assume it disappears when the watch disconnects. It is status metadata, not a copy of a recording.

Backups, other apps, and diagnostics

Android backup or device-transfer services may copy or restore the phone app's settings according to your device and account configuration. Gallery, photo backup, file-management, or sharing apps may also access or back up saved videos under their own permissions and settings. Manage those copies and backups with the relevant service; deleting one copy does not necessarily remove other copies.

ReplayOn has no user-account system, advertising integration, or integrated analytics or crash-reporting SDK. It does not automatically send recordings or diagnostic logs to a developer-operated server. Android, Google Play, Google Play services, and your device manufacturer may process their own operational or diagnostic information under their policies and your settings.

Support, retention, and security

If you contact us, we receive your contact details, message, and any attachments you choose to provide. We use this information to respond to your request and retain it only as long as needed to resolve the matter and meet applicable legal obligations. You may contact us to request deletion of information you provided to support. Do not send sensitive footage unless you intend to share it.

We do not sell your recordings or use them for advertising. We cannot remotely retrieve or delete recordings kept only on your devices. Protect your phone and watch with device security controls, review media-backup settings, and remove unwanted recordings through your Gallery or file manager. Saved videos are ordinary media files, not an app-encrypted vault; other apps with appropriate access may read them. No storage or communication method guarantees complete security.

Changes and contact

We will update this policy when the app's data practices change and show the effective date above. For privacy questions or requests about information you have provided to us, contact [email protected].

Google Data Layer overview · Google Privacy Policy

replayon

For a life worth replaying.

Instagram Help & contactTester feedbackApp PrivacyWebsite PrivacyTerms
© 2026 ReplayOn. Stay in the moment.Back to the good part