Skip to content

Legal

DOC · REV 2026-08 · LEGAL

Privacy policy.

What we collect, why we hold it, where it lives, and how to get it back or get rid of it. Reality capture photographs places where people work, so this page is written for the crews in the frame as much as for the reviewers reading it.

Effective
1 AUGUST 2026
Version
REV 2026-08
Residency
4 REGIONS · YOU CHOOSE
Questions
PRIVACY@GROUNDREALITY.AI
SECTIONS · 08 · PLAIN LANGUAGE
  1. 01

    Who this covers

    Two relationships live on this page. When you browse groundreality.ai or contact our team, we are the controller of the handful of details you give us.

    When your organization runs the platform, you are the controller of everything inside your tenant and we are your processor, acting on the written instructions in the data processing agreement. We do not decide what is captured, who is filmed, or how long a project record is kept — you do, and the platform enforces it.

    ROLE · PROCESSOR · DPA SIGNED
  2. 02

    What we collect

    Account records: name, work email, role, company, and the projects you are assigned to. Capture data your fleet produces: imagery, video, point clouds, scans, and the positions and timestamps attached to them. Project records you enter or import: RFIs, submittals, drawings, budgets, contracts, daily logs.

    Platform telemetry: which features ran, how long a processing job took, which errors fired. Support correspondence. On this website: page views and referrers, aggregated, with no advertising identifiers attached to any of it.

    CLASSES · 5 · AD IDS 0
  3. 03

    People on site

    A site walk photographs a workplace, and workplaces have people in them. Faces, licence plates, and identifying signage are blurred automatically as the frame is ingested, before it is written to storage. The unblurred original is discarded unless your administrator explicitly retains it for a named incident investigation, and that retention is logged.

    Anyone who appears in a capture can ask your safety team for the frames they are in. We give your team the tooling to find them in seconds rather than in a week of scrubbing.

    BLUR · ON INGEST · DEFAULT ON
  4. 04

    What we never do

    We do not sell personal data and we do not hand it to advertising networks. We do not train shared or foundation models on your records: your Enterprise AI Brain is one network per organization, never pooled, never used to answer another customer's question.

    We do not read the contents of your project files for our own product analytics — telemetry is metadata about the platform, not about your buildings. Our staff cannot open your tenant without a time-boxed access grant from your administrator, and every session inside it is recorded in the log you can query.

    POOLING · NONE · ACCESS GRANTED
  5. 05

    Where it lives

    You choose your region when the contract starts: Frankfurt, Northern Virginia, Mumbai, or Sydney. Capture, project records, and your model weights stay in it. Every subprocessor is listed with the data it touches and the region it runs in, and we give 30 days written notice before adding or changing one, so your review happens before the change rather than after it.

    Where you ask us to move data across a border — a design office in one region reviewing a site in another — the transfer runs on standard contractual clauses and appears in the record.

    REGIONS · 4 · TRANSFER SCC
  6. 06

    How long we keep it

    Capture and project records are held for the life of your contract, because a building outlives the job that built it and a dispute can arrive years after handover. On exit you get a 90-day retrieval window, then we destroy the tenant — derived indexes and model weights included — and issue a certificate confirming it.

    Website analytics are rolled up and de-identified after 14 months. Support threads are kept for three years so the next engineer can read what the last one did.

    RETRIEVAL · 90 DAYS · CERT ISSUED
  7. 07

    Your rights

    If your data sits inside a customer's tenant — you work on their site, you signed their delivery note — that customer is the controller. Send your request to them; we are obliged to help them answer it inside the statutory window, and we do.

    If we hold your data directly, you can ask for access, correction, deletion, portability, or a stop on processing at privacy@groundreality.ai. We answer within 30 days, we do not charge for it, and we do not require a reason.

    RESPONSE · 30 DAYS · NO FEE
  8. 08

    Cookies and this website

    This site sets one strictly necessary cookie, for security. No advertising pixels, no cross-site trackers, no session replay. Light and dark follow your operating system rather than anything we store about you, which is why there is no theme switch to click.

    If we ever add analytics that need consent, we will ask for it first and this page will say so before the script ships.

    COOKIES · 1 · TRACKERS 0
CONTACT · SALES · REPLY 1 BUS. DAY

Bring your privacy reviewers.

We will take your DPO through the processing record, the blurring pipeline, and the residency map before a single frame is captured.