Skip to the page
Open public beta

Everything here is built and running, and it is early. We want to hear what breaks.

Early adopters get two years free

Privacy

What we hold, and what we do with it.

What the software actually does with your data. Where something is not built yet, this page says so, and where somebody else touches it, they are named.

The data

What is stored, and why.

Your records
Furniture, locations, projects, houses, contacts and money. Everything your company puts in, including photographs and the addresses of the properties you stage. It is stored because it is the product: without it there is nothing to answer a question with. It belongs to your company, and we act on it only to run the service for you.
Your people
The names and sign-in addresses of the staff you add. A person's record carries an internal id and the ways they sign in. What they are called and how they are reached live on their employment, so two employers each keep their own staff list and one correcting a spelling does not rewrite the other's. Where somebody turns on notices for a phone or a browser, the address that browser's push service gave for waking it is kept too, until they turn it off or the service says it is gone.
Who did what
Every material change records who made it, and where a system acted for a person, that person too. No single entry can be edited or deleted on its own, by your company or by us, which is what makes the history worth having. What can go is the whole company: ask, and its records go with it.
The realtors and clients you deal with
You are responsible for having a basis to hold them, the same as with any address book. If one of them asks you to remove their details you can amend or merge the record. What stays is the record of what actually happened, because that is a record of your business rather than of them.
What is not collected
No tracking, no advertising, no profiles. The console runs no third-party analytics, no advertising script and no session recorder, and this site runs none either. The API sets no cookie. The console sets one, and it holds your session and nothing else.

Who else touches it

Sub-processors, named.

Render, in Oregon
Runs the application and this site, and holds the database. It sees requests in transit, including the contents of API calls while they are being served.
Supabase, in us-east-1
Holds the photographs and the accounts people sign in with. Photographs sit in private storage and are served through links that expire within the hour.
Resend, for the mail we send you
Confirmation codes and password resets go out through Resend, so it sees the address of whoever is signing in and the code they were sent. So do notices to your own staff and crew about their own work, such as a change waiting for them to approve, where they have not turned those off: for those, Resend sees the address of the person being told and what they are being told about. That is the only mail this product sends. It goes to your own people, and it never goes to your clients, their agents or anybody else on your behalf.
Browser push services, for notices on a device
Where one of your people turns on notices for a phone or a browser, each notice to them goes through that browser's own push service: Google for Chrome and Android, Mozilla for Firefox, Apple for Safari. The notice is encrypted for that device, so the service cannot read it; it sees the device's push address, that a message went to it and when, and that it came from us.
Google Maps, for addresses you type
When one of your people types an address into the console, for a warehouse, a house or a contact, what they type goes to Google Maps to suggest the address and find its place on the map. Google sees that text and the address picked, and nothing else from your records.
Whichever AI you connect
If you connect ChatGPT, Claude or anything else, that provider sees whatever your agent reads. That relationship is yours and is governed by your agreement with them. We host no models and we send them nothing on your behalf.
Google Workspace, for what you write to us
hello@verastaged.com is a Google Workspace mailbox, so a message you send us sits there and is read there. That includes asking for your company's data to be removed, which names you and your company. It is the other direction from Resend, and the two are separate on purpose: nothing about your records is routed into the mailbox, and neither system can take the other down.
Nobody else
No data broker, no benchmark pool, no advertising network. Your inventory and your rates are not aggregated into a market report, anonymised or otherwise.

Keeping and leaving

Retention, export and deletion.

While you use it
Records are amended rather than destroyed where the history matters. A person who leaves is suspended rather than deleted, because they wrote half of your movement history, and a name that resolves to nobody is worse than one that resolves to somebody who left.
Export
Everything you put in can be read back out by your AI or by a script, so an export is something you run rather than something you request from us. There is no format we can read that you cannot.
If you leave
Write to us and your company's data is removed. Today that is done by hand, and there is no self-serve delete button yet.
Backups
The database can be restored to any moment in the last seven days. A company removed at its own request is gone from that window seven days after it is removed.

Changes and questions

Ask, and we will answer.

If this page changes in a way that matters, customers are told rather than left to notice. Questions go to hello@verastaged.com.