Privacy policy
What we collect, why, how long we keep it, and who else touches it. Ambia holds two very different kinds of data — your studio's account data, and the anonymous walk records of people you send links to — and this policy treats them separately.
This document is a working draft for review, not a signed or effective agreement. Nothing on this page creates a binding obligation until Ambia publishes a final version with a real effective date.
Who we are
Ambia is the data controller for account data and the data processor for the models and walk records you generate. Contact: privacy@ambia.build.
Studio account data
We collect the name, email and role of each seat, your studio name and branding, and billing details handled by our payment processor — we never see or store full card numbers.
Your models
Geometry you upload is stored encrypted at rest, is not indexed by search engines, and is not visible to other customers. Support staff can access an unpublished model only when you ask them to, and every such access is written to your own activity feed.
If we look at your model, you see it in your activity log. There is no quiet access.
People who walk your spaces
End viewers do not create accounts. For each walk we record a coarse region, device class, browser, duration and frame-rate band — enough to tell you the walk happened and whether it performed, and not enough to identify a person.
We do not set advertising cookies in the viewer, we do not fingerprint devices, and we do not sell or share walk data.
Named-viewer access
If you enable named-viewer access, you supply the email addresses. Those addresses are processed on your instruction, used only to issue one-time codes and report who walked the space, and deleted when you remove them or delete the asset. You are the controller for that list.
Cookies
The dashboard uses a session cookie and a preference cookie, both strictly necessary. The marketing site uses privacy-preserving, cookieless analytics. The viewer sets no cookies at all, which is why an embedded walk does not need a consent banner on your site.
Embedding a walk does not add a cookie banner obligation to your website.
Subprocessors
We use a small number of infrastructure providers for hosting, object storage, transactional email and payments. The current list, with locations and purposes, is published and versioned — material additions are announced 30 days in advance.
Where data lives
Account data and models are stored in the EU or UK by default. Enterprise agreements can pin a region. Any transfer outside the UK or EEA relies on an adequacy decision or the UK IDTA and EU standard contractual clauses.
Your rights
You can access, correct, export or delete your data from studio settings, or by writing to us. We respond within 30 days. If you are unsatisfied you can complain to the ICO in the UK or your local supervisory authority.
Security
Encryption in transit and at rest, least-privilege internal access, audit logging of staff actions, and mandatory review before production changes. We disclose any breach affecting your data within 72 hours of becoming aware of it, with what we know at that point rather than after the investigation closes.
Changes
Material changes are announced by email to account owners 30 days before they take effect. Previous versions stay published so you can see what changed and when.
Questions about this document
Write to legal@ambia.build. If you need a signed copy, a DPA, or a security questionnaire completed for procurement, say so and we will send it rather than make you chase it.