Data we collect and why

Email address and password — your viewer account (sign-in, pairing cameras to you). Stored with Supabase, our backend provider; passwords are hashed.

Photos captured by your camera device — the time-lapse and motion frames you asked the camera to capture, synced so your viewers can see them remotely. Stored on your camera device and in Supabase cloud storage, private to your account.

Live video and audio — current versions of CorvoCam do not offer live viewing; your viewer devices show the latest captured frames instead. A camera device still answers live-session requests from viewer apps installed before live viewing was withdrawn, and for the duration of such a session it may send camera video, camera audio (off unless it was enabled before that setting was removed) and receive push-to-talk audio from the viewer. These streams travel directly between your devices with WebRTC encryption; when a direct connection is impossible, an encrypted relay (metered.ca TURN) forwards them. Live streams are not recorded or stored by us.

Device health (battery level, free storage, last-seen time) — shown on your viewer’s camera list and powering low-battery and low-storage alerts. Stored in Supabase, private to your account.

Push notification tokens — for delivering camera alerts (battery, storage, motion) to your viewer devices. Stored in Supabase; delivery via the Expo push service and Google Firebase Cloud Messaging.

Capture settings and alert history — remote control of your camera and the alert log in the app. Stored in Supabase, private to your account.

What we do NOT do

No ads, no analytics sold to anyone, no sale or sharing of your data for marketing.

No location collection. Captured photos are not tagged with location.

Live streams are never recorded by our servers; relays forward encrypted packets only.

The microphone is not used by current versions of CorvoCam. It can be opened only during a live session requested by an older viewer app, only if camera audio was enabled before that setting was removed, and only while that session lasts.

Background camera use

CorvoCam’s purpose is unattended capture: when you start a time-lapse or motion job on a camera device, that device keeps capturing while the screen is dimmed, using an Android foreground service with a persistent notification. Capture only happens on a device you set up as a camera, only after you start a job, and is always indicated by the service notification.

Service providers

We use Supabase (authentication, database, file storage, realtime messaging), Expo and Google Firebase Cloud Messaging (push notification delivery), and metered.ca (the encrypted relay used only by the live sessions described above). These providers process data on our behalf and are not permitted to use it for their own purposes. Error diagnostics (Sentry) may be enabled to help fix crashes; diagnostics never include your photos or streams.

Data retention and deletion

Captured frames follow the retention settings you choose in the app and are deleted from the camera device per those settings. Cloud-synced frames remain until you delete them or delete your account.

Payments and purchases

CorvoCam sells no subscriptions. The only purchases are a one-time Pro unlock and time-limited CorvoCloud passes, and both are bought and paid for through Google Play or the Apple App Store. Those stores process the payment: your card, bank and billing details go to them and to their payment processors, never to us. CorvoCam never receives or stores them.

We use RevenueCat as our purchase infrastructure provider. The app gives RevenueCat an app user identifier — your CorvoCam account id once you are signed in, and before that an anonymous id RevenueCat generates for the install — so a purchase can be attached to the right account and restored on a new phone. RevenueCat receives the purchase events the stores send, and forwards them to our server.

For each event our server records one row in a billing event log: the event id, the event type, the product identifier, the account identifier the purchase was made under, and the time it was processed. It then updates that account’s entitlement — Pro unlocked, or the expiry date of a cloud pass. No card number, name or address is part of any of that.

Deleting your account removes the entitlement held on your profile. The billing event rows stay, because they are what stops a repeated message from the payment provider being applied twice; they hold no payment details and no captured content. Records held by Google Play, Apple and RevenueCat are theirs, and our deletion never reaches them.

Account deletion

In the app, open Account and tap “Delete account” (tap twice to confirm). This immediately and permanently deletes your account and all associated cloud data: frames, cameras, settings, alert history and push tokens.

Alternatively, email support@nestcalc.ai from your account email with the subject “Delete my account”. Deletion completes within 30 days.

A public step-by-step page describes both routes, exactly what is removed and what is kept:

Children

CorvoCam is not directed at children and does not knowingly collect data from children.

Changes

We will update this page when the policy changes and note the new effective date above.

Contact

support@nestcalc.ai