Fluffing the pillows…

Skip to content
STRADVSTRADV
FeaturesIntegrationsPricingSign inCreate account

Security

Ring data architecture

STRADV shows short-term rental owners their own Ring cameras next to their houses. This page explains where Ring data is stored and how it moves between Ring, STRADV and the owner's screen.

1. Where Ring data is stored

STRADV runs on Vercel (application servers, United States) and Supabase Postgres (database, United States). Ring data is stored only in that database.

Ring access and refresh tokens: encrypted with AES-256-GCM before they are saved, and read only by server code. Deleted as soon as the owner disconnects Ring in STRADV or removes STRADV in the Ring app.

Ring account id and device list (each device's id, name, type and whether it is online): deleted with the tokens.

Which camera is on which house: kept so a relink puts each camera back on its house, and erased when the STRADV account is deleted.

Guest arrival record: when a camera the owner put on a house sees a person (or any motion, when Smart Alerts are off in Ring), STRADV saves the time and the camera's id on that house, at most once every 10 minutes per camera. No picture or video is saved with it. It is erased when the house or the STRADV account is deleted.

2. What is never stored

Camera pictures: fetched from Ring when the owner opens the Cameras page and passed to their browser, which may keep a copy for 20 seconds. STRADV does not save them.

Live video: set up through STRADV and streamed from Ring to the owner's browser. STRADV does not record or save it.

Doorbell presses, device events (added, removed, online, offline) and vehicle and package alerts: the signature is checked and the event is discarded.

3. How data moves

1. Linking: the owner starts from the Ring app, signs in to STRADV and chooses the Ring devices to share. Ring and STRADV exchange a one-time code for tokens over HTTPS, and STRADV saves the tokens encrypted.

2. Latest picture: the owner's browser asks STRADV for a camera's picture. STRADV reads that owner's tokens, scoped to their own account, requests the snapshot from Ring and passes the picture back without saving it.

3. Live view: the owner taps to go live. STRADV passes the session setup to Ring, and the video goes from Ring to the owner's browser.

4. Events: Ring sends events to STRADV's webhook. Every event must carry a valid HMAC-SHA256 signature; unsigned or altered events are refused. A person seen by a camera on a house becomes a guest arrival record, and everything else is discarded.

5. Unlinking: when the owner removes STRADV in the Ring app, Ring sends an app removal event, and STRADV deletes that account's tokens and device list at once.

4. Safeguards

All traffic uses HTTPS. Only the account owner or an admin can link or disconnect Ring.

Every database read and write is limited to the owner's own account, so one owner can never see another's cameras.

Ring data is never sold, never used to train AI models and never shared beyond Vercel and Supabase. Error reports in Sentry contain no Ring pictures or video.

If we confirm a security incident involving Ring data, we notify the affected owners and Ring no later than 72 hours after confirming it, as our Privacy Policy says.

Questions? Email support@stradv.co.

Terms of Service·Privacy Policy
STRADVSTRADV

© 2026 STRADV LLC

Product

  • Features
  • Integrations
  • Pricing

Company

  • About
  • Help and contact
  • Email us

Account

  • Sign in

Legal

  • Terms of Service
  • Privacy Policy
  • Security
  • Text messaging