How we handle your data
Last updated
This is Vizbild’s privacy policy, in plain words: what Vizbild keeps, who can see it, and how to delete it. It describes how the app works today, on the web and in the phone app.
Your account
- Sign-in runs on Supabase Auth. It keeps your email address, a hashed password (if you set one) and the name you give us.
- Your name is shown next to your comments, requests and edits to the people on the same project.
- The site sets sign-in cookies so you stay signed in, and a short-lived cookie that makes sure an emailed sign-in link only works in the browser that asked for it.
- If you pick a language on a shared home or a presentation page, a cookie remembers it in that browser for a year. It holds only the language.
Your homes
- Each project stores the home as a building model (walls, rooms, doors, windows, finishes) together with every saved revision, so history and undo work.
- Blueprints you upload, plan images you trace over and aerial photos of the site are kept in private storage that only the project’s owner and the editors they invite can open. Blueprints are kept as you uploaded them, with their file name: photos inside a scanned PDF keep any location data they had, and a file name can contain an address. Plan images are saved again without their metadata, and keep their file name.
- Room scans sent from the phone app are the measured plan (walls, doors, windows, stairs and furniture as boxes, with their sizes and heights) and up to 12 photos of the rooms (2 a room) that the app takes during the scan, never video. The scan goes to private storage while it is imported; lapsed ones are cleared out every 15 minutes by a scheduled clean-up, and whenever someone pairs or sends a scan. Its photos are stored only briefly, as described under “Room photos”.
- Vizbild does not keep a scan’s camera frames. Keeping them with a project is a setting that is off for every project and that nobody can turn on yet; this page will say so before anyone can.
- When you auto-trace a plan image, the traced plan (walls and room names, measured in pixels) is kept for 30 days with the image’s size and a fingerprint of it (a hash, which can’t be turned back into the image), so a trace that went wrong can be checked again. Never the image or its file name; the room names and labels read from it are kept as the plan shows them, so they hold an address only if the plan wrote one there.
- Comments, change requests and the people a project is shared with are stored with the project.
- Photoreal renders and films are kept in private storage that the project’s members can open.
- Finish textures you create are stored in public storage under an unguessable address, so every 3D view can load them: anyone who has that address can open the image without signing in. A texture made from your photo of a material is a new image; the photo itself is not kept, only a fingerprint of it, to recognise the same request again.
Room photos
- You can give Vizbild photos of your rooms (one room’s photo from the editor, several at once in the editor or in a scan’s import review), and the phone app takes a few during a scan, so it can read their floors, walls, ceilings, cabinets, counters and fireplace, and which room each one shows. What a photo costs is said before you send it (on the photo buttons, and in the Room photos review before you press Read), and every change it suggests is shown for you to accept before anything is changed.
- What the AI provider receives for each photo: the photo itself, shrunk to at most 1568 pixels on its long side (a browser that can’t shrink it sends it at its own size, without its metadata), and the names and types of the home’s rooms and levels, with what each room already has (for example “stairs” or “fireplace”). Nothing else: not the address, the coordinates or the aerial photo, and not your name or email.
- Location data is removed before a photo leaves: your browser re-encodes it, or strips the metadata from the file where it can’t, which drops its metadata (EXIF, including the GPS position where it was taken), and the server strips any metadata that is left before the photo is sent on. The phone app saves its photos with no metadata at all, and the server strips them again.
- A photo you pick in the browser is sent once to an AI provider (Anthropic or OpenAI) to be read, and is deleted once it is read: Vizbild holds it in memory for that one request only and never stores it, logs it or gives it an address. What is kept is only the changes you choose to apply.
- Photos from a phone scan are different: they travel with the scan into private storage, where only the Vizbild account the scan was sent to can open them, through Vizbild (when someone scans with your pairing code, that is your account). They are deleted as soon as that account’s editor picks them up for the import review, or by a scheduled clean-up, usually within 15 minutes of the scan (a photo that arrives late is cleared by a later clean-up, within about 35 minutes of arriving). They are never kept with a project, and the AI provider reads them only if you press Read. Before a scan is sent, its photos wait in the app’s own folder on the phone, outside your backups, until the scan is sent or deleted.
- Once your browser has a photo, picked or from a scan, it waits in that tab until you press Read in the editor; closing or reloading the tab forgets it.
- The provider’s own handling is described under “Services that handle your data”: neither trains on the photos, and they may keep a request for up to 30 days to check for abuse.
Where the home is
- If you add an address, it is looked up with the US Census geocoder, and the matched address and coordinates are stored with the project.
- The exact location, the address and the aerial photo are visible only to the project’s owner and invited editors.
- People who open a share link never get the address, the coordinates or the aerial photo. They see only a coarse, smoothed copy of the ground shape around the house; nearby building outlines are shown to the owner and editors only, because their true-scale shapes could identify the street.
Who sees what
- Owner: everything in the project. Editors (invited by the owner): the model, its history, uploads and the location. Share-link viewers: the 3D home and plans, comments and their own requests, without the location.
- Other Vizbild accounts see nothing of your projects.
Services that handle your data
- Hosting: the app runs on Vercel and the database and files live in Supabase.
- AI features: when you type a prompt, match room photos or a furniture photo, or auto-trace a plan image, that prompt or image is sent to an AI provider (Anthropic or OpenAI) to produce the answer. These calls to OpenAI ask it not to store them; Anthropic has no such option.
- Renders and custom finishes: the 3D view you render, or the words (and any material photo) you give for a finish, are sent to OpenAI’s image service, and finish words and images are checked by OpenAI’s moderation service. That service has no option to not store a request.
- Films: the Hero shot render a film is made from is sent to a video service, either xAI’s or a video model run through fal.ai (such as HeyGen’s or MiniMax’s), and the finished clip is copied into Vizbild’s private storage. A film along a drone path starts from a short video your browser draws from the 3D model (no photos, no site, no location), which is kept in the project’s private storage and sent to a video model run through fal.ai (LTX). A photoreal walkthrough starts from short videos your browser draws the same way and renders of the home (at most four for each part), which are kept in the project’s private storage and sent to a video model run through fal.ai (Kling). With fal.ai, we ask it not to keep a history of the request. The clip stays on fal.ai’s servers at an unguessable but public address until fal.ai deletes it, about a day later. fal.ai says it does not train on what we send, except for models it marks “Pending Enterprise Ready”. The model’s maker receives the image under its own terms.
- OpenAI, Anthropic and xAI do not train their models on what we send. They each say they may keep requests for up to 30 days to check for abuse, then delete them (OpenAI keeps no such record of moderation checks).
- Payments: if you buy a plan, checkout, card details, invoices and cancelling run on Stripe. Your card number goes to Stripe, never to Vizbild. We give Stripe your email address and an account reference; we keep your Stripe customer reference, your plan, its status and when it renews.
- Site data: elevation, aerial imagery and nearby buildings come from public datasets (USGS, Overture Maps, OpenStreetMap, and Meta and World Resources Institute tree heights). Those requests carry map positions, not your name or email.
Usage records
- Vizbild has no third-party analytics, advertising or tracking scripts.
- Inside a project, the app records what people do (for example which rooms they visit, which finishes they preview, which edits they make). These records are stored in our own database, and the project’s owner can see the ones for their project.
- Of what people type, the app records only prompts typed into the prompt bar, with whether the edit worked. The prompt’s text is removed from the record after 90 days.
- When the editor freezes or its memory use climbs fast for a project’s owner or an editor (never a client), the app records how long and how much, the device type (phone or computer, its memory and processor count, the graphics quality setting) and the kinds of actions taken just before (for example switching to 3D or opening a panel), never their content.
- To stop abuse, some features count requests per account and per network address.
- On a plan, the app counts how many AI renders and custom finishes your account used this month, to show what is left.
Deleting things
- An owner can delete a project from the projects list. That removes the project, its revisions, comments, requests, share links and site data, and its stored files: the blueprint it was imported from, plan images, the aerial photo, renders, films and exports. Files are deleted right away; if storage is briefly unavailable, the ones left are kept on a list and deleted by the scheduled clean-up, or when the delete is tried again.
- A blueprint you upload but never turn into a project (you leave the import review) is deleted with its import after a week.
- Removing or replacing a plan image in the editor deletes the old image; if storage is briefly unavailable, it goes on the same list for the scheduled clean-up.
- You can delete your account from the Account page (the person icon on your projects list). You type DELETE to confirm, and if you signed in more than 10 minutes ago you are asked to sign in again first.
- Deleting your account deletes every project you own (for everyone it was shared with, files included), removes you from projects others shared with you, deletes the blueprints you uploaded, and then deletes your sign-in account (email, password and name) and the finishes you created that are private to you. If you have a paid plan, it is cancelled at once and your customer record (email and saved payment methods) is deleted at Stripe; Stripe keeps the invoices and payment records it must keep by law. From the moment you confirm, your account can’t start projects, comment, request changes or join projects. If a step can’t finish right away, the scheduled clean-up completes it.
- Some things stay because they belong to other people’s projects: comments, change requests and edits you made on someone else’s project keep their text but show “Deleted user” instead of your name, plan images you added there stay with that project, and usage records there no longer point to your account. Finishes you created that were approved into the shared library stay in it, without your name, and a private finish that a home owned by someone else uses stays for that home.
- Finish images are served through a content delivery network. After a finish is deleted, copies already cached there can still load for up to an hour (finishes created before 27 October 2026: longer).
Who is responsible, and changes
- Vizbild is run by A&P Studio LLC, doing business as Aetrai, a Michigan limited liability company, which is responsible for the data described here. For a question about your data, or a request to see, correct or delete it, write to support@aetrai.com.
- When what Vizbild keeps or shares changes, this page changes first, with a new date at the top.