ContinuCam Privacy Policy

Serevon Labs
Last updated: September 24, 2026

This Privacy Policy explains how ContinuCam handles information when you use the ContinuCam Android app, the ContinuCam Wear OS companion experience, and the ContinuCam Relay. “ContinuCam,” “we,” “us,” and “our” refer to the ContinuCam services provided by Serevon Labs.

ContinuCam is designed around private, on-device recording. Your completed photos and videos are normally stored on your Android recorder in ContinuCam’s app-private encrypted vault. ContinuCam does not require a Serevon Labs account, does not display third-party advertising, and does not include a third-party advertising or analytics SDK in the current release.

1. Information ContinuCam handles

Camera and microphone content

ContinuCam uses your device camera when you choose to record video or capture a photo. If you enable audio for a video recording, ContinuCam also uses your microphone.

Completed photos and videos are normally stored in ContinuCam’s app-private encrypted vault on the recorder device. They are not automatically uploaded to Serevon Labs simply because you record them.

Recording and app settings

ContinuCam stores settings on your device, including items such as camera and lens selection, video or photo mode, recording quality, orientation, audio preference, recording length, photo-timer settings, saved recording profiles, remote-control preferences, and security settings.

Device and safety information

ContinuCam may process device information needed to operate its recording and safety features, such as available storage, battery state, thermal state, camera capabilities, supported media resolutions, app lifecycle state, and recording/finalization state. This information is primarily processed locally on your device.

2. Encrypted private vault

ContinuCam stores completed vault media in app-private storage and protects supported vault content with authenticated encryption. Encryption keys are protected using Android security features, including the Android Keystore.

The encrypted vault is tied to the app installation and device security state. Clearing ContinuCam’s app data or uninstalling ContinuCam can permanently delete private vault files and/or the encryption keys needed to open them. Export media you need to preserve outside the app before clearing app data or uninstalling ContinuCam.

ContinuCam’s local media operations may temporarily decrypt data when necessary to provide a feature. For example:

photos may be decoded in memory for viewing;
video playback or editing may use temporary app-private working/cache data;
sharing may create a temporary unencrypted copy in ContinuCam’s private cache and grant the receiving app temporary read access; and
exporting creates an unencrypted copy in the location you choose or in the applicable shared media collection.

After media leaves the encrypted ContinuCam vault through Export or Share, its handling is controlled by the destination, receiving app, device settings, and any person or service you choose to send it to.

3. App lock, PIN, and biometrics

If you configure a ContinuCam PIN, the app stores a salted cryptographic verifier rather than storing the PIN itself as readable text.

If you enable biometric unlock, biometric authentication is performed by Android. ContinuCam receives the authentication result; ContinuCam does not receive or store your fingerprint, face template, or other biometric template.

4. Local network discovery and Android-to-Android Remote

ContinuCam can let one ContinuCam Android phone act as a controller for another ContinuCam Android phone that you authorize as the recorder.

For local-network discovery, ContinuCam uses Android network-service discovery (DNS-SD/mDNS) and related Wi-Fi networking capabilities. On Android versions where the Nearby Wi-Fi Devices permission is required, ContinuCam requests that permission for nearby-device communication and declares that it is not used to derive physical location.

When you pair two ContinuCam phones, they exchange the information needed to establish and maintain the trusted relationship, such as device identifiers, device names, cryptographic public information, pairing/session nonces, authentication proofs, and an identifier for the pair. Long-term pairing secrets are stored by the paired endpoints and are not sent to the ContinuCam Relay as a general-purpose credential.

A paired controller may exchange recording commands and state with the recorder, including information such as recording status, pause/finalization state, capture mode, selected profile or profile names, photo-timer state, connection state, and similar control metadata. The recorder remains authoritative for camera permissions, recording safety, Premium entitlement, and whether a command is accepted.

The currently released Android-to-Android Remote experience is a command-and-control feature. It does not provide a user-facing feature for browsing or downloading the recorder’s stored vault media.

5. ContinuCam Relay

When paired ContinuCam phones cannot communicate directly on the same local network, ContinuCam may use the ContinuCam Relay to carry authorized remote-control traffic over the Internet.

Application command and state payloads carried through the ContinuCam Relay are designed to be end-to-end encrypted between the paired ContinuCam endpoints. The Relay does not possess the long-term pair secret or the endpoint decryption keys used to interpret those encrypted application payloads.

End-to-end encryption of application payloads does not mean the Relay processes no information. The ContinuCam service may process limited metadata needed to authenticate devices, establish or revoke pairs, route connections, prevent replay or abuse, and operate the service. Depending on the operation, this can include:

a ContinuCam cloud device UUID;
device platform/type information;
a device public authentication key;
PairId relationships and activation/revocation state;
temporary pairing-session identifiers;
authentication challenges, timestamps, signatures, and replay-protection information;
routing/group/connection information; and
IP address and other ordinary network/connection information visible to an Internet service.

The corresponding private device-authentication key is generated and retained on the Android device using Android Keystore protection and is not uploaded as the device’s public credential.

The ContinuCam Relay uses Microsoft Azure as underlying cloud infrastructure/service-provider technology. Microsoft may process infrastructure and network information as necessary to provide Azure services, subject to Microsoft’s applicable terms and privacy practices.

6. Cloud-assisted pairing

ContinuCam can use the ContinuCam Relay to assist first-time pairing when the two Android devices are not on the same local network.

During this process, short-lived pairing-session information and one-time pairing information may be transmitted to the ContinuCam service over HTTPS so the two devices can rendezvous and complete pairing. Do not treat a one-time pairing code as a permanent password, and do not share it with someone you do not intend to authorize.

ContinuCam’s permanent device-to-device pairing secret is established for the paired endpoints and is not provided to the Relay as a credential that the Relay can use to decrypt normal paired application traffic.

7. Pair removal and revocation

You can remove an authorized ContinuCam pairing. ContinuCam attempts to synchronize revocation between the paired devices and the ContinuCam Relay so the removed PairId can no longer be used to reconnect.

If the Internet or Relay is temporarily unavailable, local removal can complete while service-side revocation remains pending for retry. A future authorized pairing creates a new trusted relationship.

Pairing and revocation metadata may be retained for as long as necessary to maintain active authorization, complete revocation, protect the service, comply with applicable law, or support reasonable operational/security needs. We do not promise a single fixed retention period for all security and service metadata because the appropriate period depends on the type and purpose of the record.

8. Wear OS companion

ContinuCam’s Wear OS companion uses the Google Play services Wearable Data Layer to communicate with the paired ContinuCam phone.

The watch may send small remote-control requests such as Start, Stop, Pause, Resume, still-photo capture, saved-profile selection, and status requests. The phone may send limited control/state information such as recording state, timer/countdown information, selected-profile information, recording duration, and command acknowledgements.

The Wear OS companion does not need to own the phone camera or encrypted vault. The released Wear experience does not send your recorded video, recorded audio, vault contents, app-lock PIN, biometric templates, or vault encryption keys to the watch.

Wear communication depends on Google Play services and may use Bluetooth or other connectivity managed by the Android/Wear OS platform. Google may process device, connection, and service information under its own privacy policies when providing those platform services.

9. Google Play purchases and subscriptions

ContinuCam Premium subscriptions are sold and managed through Google Play. Google processes your payment method, billing address, transaction processing, and other payment information under Google’s policies.

ContinuCam receives information needed to determine entitlement, such as the relevant subscription/product information and purchase/entitlement status. ContinuCam may store local entitlement state so Premium features can be enabled appropriately. Serevon Labs does not receive your full payment-card number through the ContinuCam app.

10. QR-code pairing scanner and other Google Play services

ContinuCam may use Google Play services components to provide platform-integrated functions, including QR-code scanning used for pairing and Google Play app-update/purchase functionality. When you use those features, Google Play services may process technical information needed to provide the requested platform feature under Google’s applicable privacy policies.

Export and Share are actions you choose.

When you export a photo or video, ContinuCam creates an unencrypted copy outside its private encrypted vault, such as in the applicable Android media collection. That exported copy may then be visible to other apps with appropriate permission, synchronization services you have enabled, or other people who have access to your device or storage.

When you share media, ContinuCam may create a temporary unencrypted copy in app-private cache and grant the app you selected access to that copy. The receiving app or service then handles the media according to its own privacy practices.

12. Advertising, analytics, and sale of information

The current ContinuCam release:

does not display third-party advertising;
does not include a third-party advertising SDK;
does not include a third-party analytics or crash-reporting SDK; and
does not sell your personal information to advertisers or data brokers.

Infrastructure providers may generate ordinary operational or security records as part of providing the ContinuCam Relay and related services. Those records are not used by ContinuCam to serve third-party advertising.

13. How long information is kept

Retention depends on the type of information:

Encrypted vault media: remains in ContinuCam’s private app storage until you delete it, clear app data, or uninstall the app, subject to device/storage failure.
Local settings and pair records: remain on the device until you change/remove them, clear app data, or uninstall the app.
Temporary app-private working/cache data: is intended to be temporary and may be removed when an operation completes, the app cleans its cache, or Android removes cached data.
Temporary cloud pairing sessions: are short-lived and are intended to expire when pairing completes or the session expires.
Relay authorization/security metadata: may remain while needed to operate an active pairing, complete revocation, secure the service, investigate abuse, meet operational needs, or comply with law.

Because security, fraud-prevention, and infrastructure records can have different operational requirements, this Policy does not state a single universal server-log retention period.

14. Your choices and controls

Depending on the feature, you can:

choose whether to record video or capture photos;
choose whether microphone audio is enabled for video recording;
grant or deny Android permissions;
enable or disable Watch Remote and Wi-Fi Remote Recorder features;
remove paired devices;
delete media from the ContinuCam vault;
export media you want to keep outside ContinuCam;
disable biometric unlock or remove your ContinuCam PIN;
cancel or manage Premium through Google Play; and
clear app data or uninstall ContinuCam, understanding that doing so can permanently remove encrypted vault media and keys.

Depending on where you live, applicable privacy law may provide additional rights concerning personal information processed by Serevon Labs. You may contact us using the address below to make a privacy request. We may need information sufficient to verify and process the request.

15. Security

ContinuCam uses technical safeguards appropriate to its design, including authenticated encryption for supported vault media, Android Keystore protection for sensitive device keys, authenticated pairing, encrypted device sessions, HTTPS for service APIs, and end-to-end encryption for normal paired application payloads routed through the ContinuCam Relay.

No application, device, network, encryption system, or cloud service can guarantee absolute security. Keep your Android device updated, protect access to your device and Google account, use ContinuCam’s lock features where appropriate, and remove pairings you no longer trust.

16. International processing

Internet services and their infrastructure providers may process service metadata in locations different from the country where you use ContinuCam. When this occurs, information may be subject to the laws applicable in those locations and to the safeguards used by Serevon Labs and its service providers.

17. Changes to this Privacy Policy

We may update this Privacy Policy when ContinuCam features, service architecture, legal requirements, or third-party services change. When we make changes, we will update the “Last updated” date. We may provide additional notice when appropriate or required by law.

18. Contact us

For questions, privacy requests, or concerns about this Privacy Policy, contact:

Serevon Labs
Email: serevon.studio@gmail.com