Effective 8 November 2026 · Last updated 8 November 2026 · Applies to: Sight, in the United States · Companion to our privacy policy and AI and data disclosures.

Data flow and storage

Where a moment comes from, what crosses each boundary, and where everything ends up. This page describes the path your data takes; the privacy policy covers what we promise about it.

How a moment is made

Sight data flow A Ring camera event goes to Ring, then to Sight's pipeline, which runs on Microsoft Azure in the United States. With the household's agreement, the pipeline sends the clip, with the sound removed and Ring's on-screen labels covered, to an AI model at Google or, for some homes, Pulses, which returns a written description; the clip is then discarded. The description is stored as text in Sight's database. Stills are encrypted with the home's own key and stored only if the household keeps pictures. Sight's API sends text to Anthropic to write the brief and answer questions, serves your app, and sends notifications through Expo and Apple. Sight's systems — Microsoft Azure, United States (Central US) Your camera motion / doorbell Ring event + clip Sight pipeline fetch · mask · discard Google, or Pulses reads the clip, writes the words Database the words Private storage stills only, per-home key only if you keep pictures Sight API scoped per home Anthropic text only Your app Expo · Apple notification words clip in, words out
  • Ring notifies Sight that something happened at a camera you linked — what kind of event, which device, and when.
  • Sight fetches the event from Ring, using the access you granted when you linked Sight in the Ring app, and Sight's own software looks at a still from it. For the clip, Sight removes the sound and covers Ring's on-screen labels, so the device details Ring prints on the picture do not travel onward.
  • An AI model at another company reads the clip and returns a written description: Google's Gemini, or Pulses for a home that has visitor recognition on and keeps pictures. This happens only if your household has agreed to AI processing; otherwise nothing is sent and Sight writes its own short note. The model receives the clip with the camera's place name and the time, and Pulses also the kind of event — never a name, an email, or an account identifier.
  • The clip is discarded. Sight keeps no video.
  • The words are stored against that moment: the description, the time, and the camera. This is what your timeline is made of, and it is a kilobyte or two.
  • Stills are stored only if your household chose to keep pictures. If it did, each still is encrypted with a key belonging to your home alone before it is written, into storage that allows no public access. If it did not — the default — nothing from the camera is written at all.
  • Anthropic writes the wording of your daily brief and answers your questions in Ask, from text Sight sends it — notes, times, places, names your household typed, and your questions — again only with your household's agreement. Never a picture or a clip.
  • Your app reads through Sight's API, which scopes every query to a home you are a member of. Notifications reach your phone through Expo and Apple, as words only.

Two things worth naming because they are easy to assume otherwise. Reading the clip does not depend on your picture setting: it happens whenever your household has agreed to AI processing, and Keep pictures decides only whether stills are written down afterwards. And your original video stays in your Ring account under Ring's own retention: deleting from Sight does not delete from Ring.

Storage locations and systems

Everything Sight stores is stored in the United States, on Microsoft Azure in the Central US region, and Sight's own systems run there. Sight stores nothing in any other region or with any other cloud. The AI companies above process what Sight sends them on their own systems, and Pulses keeps the face signatures it makes for homes that have visitor recognition on — see the privacy policy.

SystemWhat it holdsProtection
PostgreSQL Descriptions, briefs, rhythms, settings, account and household records, Ring's event signals as Ring sent them, and — only where visitor recognition is on — face records for that home. Platform encryption at rest; access scoped per home by the API. Face records are encrypted with, or derived from, that home's own key, so the same person at two households produces two unrelated values.
Private blob storage Stills — snapshots, the frame that shows each moment best, and face close-ups — only for homes that chose to keep pictures. No video. Encrypted with AES-256-GCM under a key belonging to a single home, before being written. No public access; only Sight's own services may read or write it. Every file carries an expiry date, and Sight stops serving it once that date passes.
Azure Key Vault The master key that wraps each home's own key. No customer content. Permissioned separately from the database and storage, so no single role reconstructs readable media on its own. Destroying a home's key is what makes its media unreadable immediately on deletion.
Ring access The access Ring granted when you linked, so Sight can fetch your events. Encrypted before it is stored. Deleted when you remove Sight in the Ring app, and when the home's data is deleted.
Log Analytics Application and pipeline logs: request outcomes, processing steps, errors. 30-day retention.
Database backups Encrypted point-in-time copies of the database. Rolling window of up to 14 days. We disclose this rather than implying deletion is instantaneous everywhere — see the limits of this promise.

What crosses which boundary

  • Ring → Sight: event signals, stills and clips for cameras you linked, and, when you link, your Ring account's ID and email address. Sight never sees your Ring password; the connection uses Ring's official partner sign-in.
  • Sight → Ring: when you link, a masked form of your Sight email address, so the link is recognisable in your Ring account.
  • Sight → Google or Pulses, only with your household's agreement: the clip, with the sound removed and Ring's on-screen labels covered, the camera's place name and the time; Pulses also receives the kind of event and a code that keeps your home's faces apart from every other home's. No name, no email, no account identifier.
  • Sight → Anthropic, only with your household's agreement: text only — notes, times, places, names your household typed, and the questions you type into Ask.
  • Sight → Expo and Apple: the words of a notification and your device's notification token, so it reaches your phone.
  • Sight → your app: only data belonging to a home you are a member of.
  • Sight → anywhere else: nothing. No analytics service, image host, thumbnail service, advertising network or content-delivery network receives your pictures or clips.

Questions

Questions about anything on this page? privacy@getsight.app, or through support.