Exactly what is stored, why, who else sees it, how long it stays, and the two buttons that give it all back to you or erase it.
Draft of 2 October 2026. Every statement below about what is stored was read from the running code, not assumed.
[TO CONFIRM: the legal entity name that will appear on the Stripe account], at [TO CONFIRM: the business postal address - Stripe requires one on the site]. Questions, requests and complaints: [TO CONFIRM: the support email address].
| What | Why |
|---|---|
| Your email address | It identifies the account and is where receipts and monitor alerts go. It is the only piece of personal information we ask for. |
| Your account key | It is the credential that signs you in. |
| Your plan, trial dates and monthly usage counts | To know what your account is entitled to and to apply the plan's limits. |
| Your saved audits | The work you came here to do: the listing name, city, bedroom count, your rate and occupancy figures, your answers to the audit, and the measurements taken from the listing's photographs. |
| Your monitored listings | The listing URLs you asked us to watch, the competitor URLs you named, and a dated reading of each one every time we check it. |
| Anything you sync from your own Airbnb account | If you connect your listing's calendar link or load your earnings export, we keep the calendar link itself, the dated booked and blocked nights it describes, and one row per reservation: its dates, its number of nights, its amount and its confirmation code. Guest names, guest phone numbers and guest email addresses are discarded while the file is being read and are never stored. It is used for one thing - working out what each month actually earned and what the empty nights cost - and you can disconnect it at any time, which deletes it. |
| Your white-label branding | Agency name, strap line and accent colour, if you are on Studio and choose to set them. |
| Technical logs | Request times, IP addresses and errors, to keep the service running, apply rate limits and investigate abuse. |
We do not ask for and never store a password - there isn't one. We do not take card details: when payment goes live it will be handled entirely by a payment processor and card numbers will never reach our server.
When an audit is completed we keep one row of three values: a normalised city name, the bedroom count, and the score. That row carries no email address, no account key, no listing name, no URL and no date of birth of any kind - there is deliberately nothing in it that points back to you. It exists so that every customer can be told where a listing sits against its peers instead of being handed a number with no context.
Because those rows carry no link to you, they cannot be found and removed when you delete your account. We would rather say that plainly than claim an erasure we cannot perform.
To measure a listing's photographs the browser has to read their pixels, which it can only do if the images come through our own server. Those images are Airbnb's, fetched from Airbnb's image service, and are held only as a short-term cache. The cache expires automatically and holds no personal data of yours.
Nobody is sold anything. Data is shared only with the suppliers needed to run the service - hosting, the database, the email sender and, when it goes live, the payment processor - each only with what it needs. We will name them here as each one is connected: [TO CONFIRM: the legal entity name that will appear on the Stripe account] has not yet connected a hosting provider, an email sender or a payment processor.
We read public listing pages from the platforms you point us at. Those platforms see a request from our server for a page, nothing about you.
Your account and its contents are kept until you delete them, or until the account has been dormant for a long period and we tell you first. Cached photographs expire in days. Technical logs are short-lived.
These are buttons in the product, not an email you have to wait on. On your account page:
You may also ask us to correct anything, to object to a use, or to complain to your data protection authority. Write to [TO CONFIRM: the support email address].
Your account key is the only credential, it is sent in an authorisation header rather than in a web address, and writes to our data files are atomic so a crash cannot half-write a record. Rate limits sit in front of sign-up, sign-in and the listing reader.
What is not yet true, and will be before the service is sold publicly: it is not yet on a public encrypted host, and backups are not yet stored off the machine. Until those are done this is a private build and should not be used for anything you cannot afford to lose.
The service is for business use by adults. It is not intended for anyone under 18 and we do not knowingly hold a child's data.
If this policy changes materially we will say so in the service. Date of this draft: 2 October 2026.