Privacy

Last updated 2026-11-06

In short

Grayhaven Labs LLC runs Dialect. Dialect looks through cameras at real places, and sometimes at people. This page says what it keeps, who else sees it, and for how long, as the software works today.

What we handle

  • Photos from your cameras

    Whole frames, crops of the part being read, and photos taken during setup, tests and when an agent looks. Anyone in view is in them. Dialect doesn’t blur faces or remove people, and it has no face recognition feature. It takes photos, not sound.

  • Readings

    What each field read, when, and how sure. A reading can hold text from a screen or a sign.

  • What you and your agents write

    Your requests, endpoint questions, alert settings, and notes agents save.

  • Your account

    Your name, email address and workspace are held by Clerk. Dialect’s own database keeps your Clerk ID, not your email address. It looks your address up in Clerk when it sends you an email.

  • Payment

    Stripe and Link take your card and billing details. We can see payments in Stripe, and we keep a record of which workspaces have paid.

  • Gateway health

    Storage, heat, power, memory, Wi-Fi signal, restarts and camera settings. Never a photo or a reading.

  • Logs

    API logs, an audit log of changes in your workspace, load balancer logs, which include IP addresses, and error reports from your browser.

  • Cookies

    Clerk’s sign-in cookies, and a few that remember your time zone and how you arrange the console. Your theme is saved in your browser. There are no ads and no analytics trackers.

On your side of the network

A gateway runs next to your camera and decides what to send. If it can’t reach us, it holds reports on its own disk for up to 24 hours. It also keeps your camera’s login and, while it reads a view, a few grey stills of it so a restart knows the scene. A software gateway connects to us, never the other way. Its setup page answers only on the computer it runs on.

Who processes it

Reading a camera means sending photos to these companies. Without them Dialect doesn’t work.

  • Amazon Web Services

    Runs the API and database, and stores the photos and logs, in its Ohio region (us-east-2). Amazon SES sends our email. An alert email includes the crop it was read from.

  • TypeSafe

    Its vision model reads crops and finds things in whole frames, each time a watched region changes and at least every 10 minutes.

  • Cloudflare

    Its Workers AI models read numbers and text and give a second opinion on crops. Requests from gateways to TypeSafe also pass through a Cloudflare Worker of ours.

  • Anthropic

    Its Claude models see camera frames and your request during setup, whole frames when a reading is in doubt, kept crops when Dialect rewords a field that keeps reading unsure, and a camera’s latest frame when the console suggests what to watch. That last one can happen when the Endpoints page loads.

  • Clerk

    Sign-in, and your name, email address and workspace membership.

  • Vercel

    Hosts this site and the console. Photos and readings you open in the console pass through its servers, and console errors go to its logs.

  • Stripe and Link

    Take payment, as merchant of record, and handle receipts, tax and billing support. Their own privacy policies cover what they collect.

Each of them handles data under its own terms. We make no promise here about how long they keep what we send or what else they do with it.

What you send elsewhere

What you connect is your choice. Webhooks send readings, not photos, to the address you give. Your agents get photos when they look, and so does whichever model runs them. Alert emails stay in the inboxes they reach.

Who at Dialect can see it

People in your workspace see what their access allows. People who run Dialect can reach your photos and readings through our AWS account, to run the service and fix problems. Our read-only way into the database records who opened it.

Training and testing

Each night we build a set of labelled photos to test and train our own models on. Your workspace is left out unless it has agreed, and the default is no. There’s no switch for this in the console: write to us to agree or withdraw. If you withdraw, new sets leave you out. Sets already written aren’t changed. If your workspace has agreed, labelled photos stay in these sets beyond the times below.

Separately, when a field keeps reading unsure, Dialect uses that endpoint’s kept crops to reword its question. That happens in every workspace.

How long it’s kept

A sweep runs once a day, so something can outlast its time by about a day.

  • Readings

    No end date. When a photo goes, the reading stays.

  • Whole frames

    7 days. Dialect keeps one with each new reading and each camera check, up to 500 per endpoint. An endpoint’s newest frame stays until a newer one replaces it, even after the endpoint stops.

  • Crops where the value changed

    90 days.

  • Crops where nothing changed

    Only the newest for each field, for up to 7 days.

  • Photos behind an alert

    365 days.

  • Photos that were hard to read

    365 days, in every workspace. When a reading was unsure or needed a second look, its crop and frame are kept this long for testing and training, which only uses them if your workspace has agreed. A field that stays unsure adds about one an hour.

  • Photos on log entries

    365 days.

  • Setup, test and agent photos

    14 days.

  • Photos you confirm an endpoint from

    No end date. They stay with that version of the endpoint, and versions aren’t deleted.

  • Check the view

    The frame on screen is deleted soon after you leave.

  • Audit log

    No end date.

  • Gateway health and logs

    Gateway health, API logs, database logs and load balancer logs: 30 days. Webhook deliveries: 7 days. Database backups: 7 days.

Deleting

There’s no delete button for a workspace or its history yet. Stopping an endpoint stops the reading and keeps its history. Cancelling or a refund keeps it too. Deleting your organization closes the workspace, revokes its tokens and pauses its webhooks, and what’s stored stays.

To ask for a copy of your data, or for it to be deleted, write to tyler@grayhavenindustries.com. We do this by hand. Backups can hold it for up to 7 more days.

Security

  • The API takes HTTPS only. Plain HTTP is redirected.
  • The database and photo storage are encrypted at rest. Neither is open to the internet.
  • Photos are served only to people and tokens allowed to see them. No photo has a public address.
  • A software gateway keeps its camera’s password on your machine.

This encryption protects stored files. It doesn’t stop Dialect, or the companies above, from seeing photos, because reading them is the job.

If you run the cameras

You decide where cameras point and who they may catch. You’re responsible for using them lawfully and for telling people on camera what the law requires, including that their photos go to a third-party service.

If you’re on someone’s camera

Ask whoever runs the camera first. We can’t tell who is in a photo or whose camera you’re on without them. You can also write to tyler@grayhavenindustries.com.

Your rights

Depending on where you live, you may have rights to see, correct or delete your personal data. Write to us to use them. Our storage is in the United States.

Changes and contact

If this page changes, the date at the top changes. Questions go to tyler@grayhavenindustries.com.