Privacy
RoomRead scans a room with your phone and checks the scan before anything is built on it. This page says what we do with what you send us — what we hold, how long we hold it, who else sees it, and how to have it deleted.
Last updated: 27 September 2026
It covers roomread.app, the RoomRead app and the RoomRead connector wherever you use it. It is a working product rather than a finished one, so where something below is not built yet, the page says so instead of describing it as though it were.
What we hold
- Your address. The email address you sign in with, a display name if you give one, and the identifier Google or Apple hands us if you sign in that way. We never see a password, because we never ask for one.
- The scan itself. A walk around a room, as the phone recorded it: the colour video, the depth and confidence frames, the path the camera took, the surface mesh and, where the phone provides one, a room plan. It is a recording of a real room, so treat it as one.
- The measurements. Which scan it was, whether it passed, the numbers it was judged on and the tolerance it was judged against. These are what a connected AI app reads.
- The connections. Which AI app you connected, what it was allowed to ask for, and when it last asked.
- Logs. Our hosting provider records requests to the service. That includes a sign-in code being sent, and the address it went to.
How long we keep it
Retention, by what it is
- The raw scan
- 30 days after it is uploaded. Video, depth frames, tracking and mesh go together.
- The scan record and its verdict
- While your account is open — the record is what explains a failed scan, and it carries no geometry.
- A plan or a pack
- Until you delete it.
- A sign-in code
- Ten minutes, and single use.
- A browser session
- 30 days, or until you sign out.
- Access for a connected app
- Until you disconnect it. Disconnecting revokes the token.
- Request logs at our host
- Up to seven days.
Thirty days is the default for raw scans, and it is a per-account setting rather than a number buried in the code, so a shorter period is possible if you want one. Nothing derived from a scan outlives the scan in a way you cannot see: the plan and the pack stay until you delete them, and deleting your account takes the files, the records and the connections with it, revokes the tokens the connected apps hold, and is done within 30 days with a receipt saying what went.
Who else sees it
Everyone who touches your data
- Cloudflare
- Runs the site, the API and the storage. Your scan files sit in Cloudflare's R2 object storage in the European Union.
- The AI app you connect
- ChatGPT, Claude or another. It gets the measurements it asks for, under your account with that provider and their terms — not ours. RoomRead does not send your scans to a model provider on its own.
That is the whole list. We do not sell your data, and we do not pass it to anyone for advertising.
Scan files are stored in Cloudflare’s R2 in the European Union, and nothing about a scan is transferred anywhere else. One thing is processed outside the UK: the mail service that sends a sign-in code runs in the United States, so your email address and the code go through it.
People, in a scan
A walk-through catches whatever is in the room — people, documents, screens — and that is why a scan is treated as personal data rather than as geometry.
The app does not blur or pixelate anyone in the video it uploads. The frame is what the camera saw, so the protection is not a filter. It is this: nothing in the pipeline reads the video. The check that measures a scan works from the depth frames, the confidence data, the camera’s path and the mesh; the video travels inside the capture bundle for provenance and nothing opens it. The whole bundle is then deleted, 30 days after upload by default, and there is a way to have it deleted sooner.
So record your own room, and keep anyone who has not agreed to being recorded out of the shot.
What we don’t do
- We do not train models on your scans. Not ours, not anyone else’s.
- We do not sell your data or hand it to anyone for advertising. This site sets no cookies of its own and runs no analytics.
- We do not watch your walk-through. The check is arithmetic on depth data, and no part of it is a person reviewing footage.
Your rights
You can ask us what we hold about you, have it corrected, have it deleted, or ask for a copy in a portable form. You can also complain to the Information Commissioner’s Office at ico.org.uk — though telling us first tends to be quicker.
To delete everything, email [email protected] from the address on the account. We remove the scan files, the records and the connections, and revoke the tokens the connected apps hold. A button for this belongs on the account page; until that page exists, the mailbox is how it happens.
Cookies
This site sets none. Signing in and connecting an app use two cookies on the sign-in host: one keeps you signed in for 30 days, and one is short-lived and exists only while an app connection is being confirmed. Both are HttpOnly and Secure, and neither is used for anything else.
Changes
If this changes in a way that matters, the date at the top changes and we email account holders before the change takes effect. A version that describes a feature we have not built yet would be worth less than this one.
Contact
RoomRead is run from the United Kingdom. Write to [email protected] and a person will answer.