Last updated October 21, 2026

Privacy Policy

This page describes how DrainSight actually works today (v1) and how the planned detection upgrade (v2) changes that. It is not a substitute for legal advice. Questions: hello@drainsight.ai.

DrainSight LLC (“DrainSight,” “we,” “us”) operates the marketing site at drainsight.ai and the product app at app.drainsight.ai. This policy covers both, plus published homeowner reports and any repair estimate a contractor shares.

1. Who this is for

Our customer is the contractor (the shop that creates an account and uploads footage). Homeowner name, address, and pipe video are the contractor’s customer data. We process that data to run the service they asked for. If you are a homeowner who received a report or a repair estimate, questions about that job go first to the contractor named on it; you can also email us at hello@drainsight.ai.

2. What we collect

Marketing site

The beta-access form asks for your name, company, email, and optionally phone and what camera you run. We use that to talk to you about the founding cohort. We do not run advertising pixels or a marketing analytics product on this site today.

Product accounts

When you create a company or join one: name, email, password (stored by our auth provider, not in plaintext), company name, role, optional license number, and an invite code for teammates. Session cookies keep you signed in.

Inspections (the job)

For each upload we store what the app actually uses:

  • Customer name and address (so the report can be labeled and found later).
  • Camera brand and an optional pipe-material hint.
  • The raw video you upload (private storage). The worker reads it once to pull still frames, then the product runs off those frames — review, the published report, and the PDF do not stream the video again.
  • Evidence stills for findings (a few hundred KB each), plus a bounding box when the model marked a spot.
  • Distance and pitch readings transcribed from the camera’s on-screen overlay, when they are visible.
  • Findings (kind, severity, footage range), review decisions (approved, edited, or rejected, and why a finding was rejected), and who signed off.
  • The published report: pipe material, connection-to-main marker, share token, and a PDF copy. An internally computed health score is stored with the report and is not shown on it.
  • Company logo, phone, and email if you add them — they print on the report.
  • Repair estimates, only if the shop turns the add-on on: each repair’s name, optional description, price, and which published findings it covers; one optional note for the whole quote; when it was shared; and a PDF. Sold and declined are the shop’s record of the homeowner’s spoken answer. They are not on the public page or the PDF. DrainSight does not set the prices.

Logs and cookies

Ordinary server and auth logs (IP, user agent, timestamps) for security and debugging. Auth cookies are required to use the app. The app may also store a first-party cookie for sidebar open/closed. We do not use that for advertising.

3. How analysis works (v1 and v2)

v1 (what ships today). Selected still frames — not the full video file — are sent to Google’s Gemini API. The model proposes defects and reads on-screen distance and pitch. Those proposals do not go to a homeowner until someone on your team reviews them. We do not send the raw MP4 to Google.

v2 (planned, not the live detector). Detection is intended to run first on a detection model we host, trained on still frames plus reviewer corrections (approve, edit, reject, and the reason for a reject). Gemini may still run as a fallback on some frames. Training uses extracted frames and labels, not the raw video. A separate partner footage library — if you send us archive jobs for labeling — is stored outside the product video bucket so a retention job cannot wipe gold footage. We will not put customer footage in a public dataset.

4. Who else sees data

We use these processors to run the product. We do not sell your data. Each keeps data under its own terms, for example for abuse and security monitoring for a limited time, and we do not control their retention.

  • Supabase — accounts, database, and private file storage (video, frames, reports, logos). Uploads go from the browser to storage; our web server does not buffer the video.
  • Google (Gemini API) — v1 frame analysis, and v2 fallback frames, under Google’s API terms.
  • Google Places — when address autocomplete is turned on, the street field sends what you type to Google so we can fill city, state, and ZIP. Manual entry never calls Places.
  • Stripe — subscriptions, invoices, and sales tax. Stripe collects the card and the billing address on its own pages; we never see or store the card number. We keep the plan, its status, and Stripe’s customer and subscription IDs.
  • Vercel — hosts this marketing site.
  • Our application servers — the product app and the worker that extracts frames and builds the report.
  • Email delivery — account confirmation and password-reset mail go through Resend, configured as our auth provider’s SMTP. When a video you uploaded is ready to review, or processing fails, we also email you through Resend: the customer name, the address, and a link back to the job. That mail has no footage. You can turn it off under Settings. The marketing beta form is used to contact you about access.

When v2 labeling or training uses a third-party tool, it will be a private workspace (for example a self-hosted or private CVAT project, or a paid private Roboflow workspace). We will not use a plan that publishes datasets. Training runs on a rented cloud GPU from RunPod under a private account.

Anyone you give the report share link to can open that published report (name, address, stills). Once the shop shares a repair estimate, the same link opens that quote too: the shop’s prices, the repairs, and the note. A draft is not available. Sold and declined stay off that page. The token is unguessable, but it is not a login. Search engines are told not to index app or report URLs.

5. How long we keep it

  • Raw video. Kept only as long as a job might need to run again, then deleted automatically:
    • 14 days after its report is published;
    • 60 days after upload, if the inspection is still in review;
    • 30 days after processing last failed. After that the job cannot be retried; upload the video again to start over.
    Deleting the video does not change the report, its stills, the PDF, or the share link. You can remove it sooner by deleting the inspection or usingClear footage in Settings (raw video only, across published and in-review jobs). Keep your own copy if you may need the original later.
  • Unfinished uploads. An inspection whose video never finished uploading is deleted, with anything it stored, 2 days after it was started.
  • Evidence stills, PDFs, and inspection records. Kept for the life of the inspection. That includes the findings-report PDF and, once shared, the repair-estimate PDF. Deleting the inspection removes the video, frames, both PDFs, and the database rows together from our systems. We do not time-delete frames or PDFs on their own — that would break a live share link.
  • Training data. Deleting an inspection removes its stills and review decisions from future training. A model already trained keeps what it learned.
  • Company logo. Until you replace or remove it.
  • Beta-form leads. Until we no longer need them to run the founding cohort, or you ask us to delete them.
  • Accounts. Until the company is closed or you ask us to delete them. Ask at hello@drainsight.ai if the in-app controls are not enough.

6. Your choices

In the app you can edit account and company profile, rotate the teammate invite link, turn repair estimates on or off for the company, delete an inspection (owner, or the tech who uploaded it), and clear raw video for the company. You can ask us for a copy or deletion of personal data we hold. We may need to keep a record of the request.

Homeowners are not DrainSight account holders. We will point a homeowner request at the contractor who published the report, and we will help that contractor delete or correct the inspection when the request is valid.

7. Children

The service is for trade businesses, not for children. We do not knowingly collect data from anyone under 13.

8. Security and where data sits

Storage buckets for video, frames, and reports are private. Evidence stills and logos on a report are served with short-lived signed URLs. We host in the United States (our current providers). If you access the service from elsewhere, you are sending data to the U.S.

9. Changes

If we change this policy in a material way — including when v2 detection or a new processor ships — we will update this page and the “Last updated” date. Continued use after that date means you accept the revised policy.

10. Contact

DrainSight LLC, Elk Ridge, Utah.
hello@drainsight.ai