Privacy policy

Last updated 19 August 2026

This explains what we collect, why, who else touches it, and how to get rid of it. It is written to be read, not to be survived.

The short version

The Listing Bench is a tool for real estate teams to produce their own marketing content. We hold the information your team puts in, the content we generate from it, and the account details needed to sign you in. We do not sell any of it, we do not use it to train AI models, and we delete it when you ask.

What we collect

Three kinds of information, all of it given to us by you:

  • Account details — name, email address, and optionally a phone number and headshot, used to sign you in and to put your contact block on flyers and postcards.
  • Your content — listing addresses, prices, features, photographs, brand assets (logos, fonts, colours), voice guidelines, testimonials you enter, and everything we generate from those.
  • Access requests — if you ask for early access we keep your name, email, brokerage, market, team size, and what you told us about how you market listings today, along with the page that referred you.
  • Usage records — which kinds of content your team generated and when, so we can enforce fair-use limits and understand what the product is used for.

What we do not collect

We do not use advertising trackers or third-party analytics cookies. The only cookies we set are the ones that keep you signed in, which is why you are not asked to dismiss a cookie banner.

We do not store the IP address of people who submit the access request form. It is used in memory to rate-limit the form and is not written down.

Who we share it with

We do not sell your information and we do not share it with anyone for their own purposes. We use a small number of service providers to run the product, and they only process data on our instructions:

  • Supabase — database, authentication, and file storage.
  • Render — application hosting.
  • Anthropic — generates written content. It receives the listing facts and brand voice needed for the piece you asked for.
  • OpenAI — generates lifestyle imagery, only when you choose to use that option. It receives the image prompt, not your listing data.
  • Resend — sends invitation and account emails.
  • Amazon Web Services — renders video, only if video is enabled for your deployment.
  • Stripe — will process payments when billing is enabled. It receives your billing details directly; we never see your card number.

AI and your content

Written content and images are produced by third-party AI models as listed above. We send them only what is needed to produce the piece you requested.

These providers do not use data submitted through their business APIs to train their models, and neither do we. Your listings, photographs, brand assets, and generated content are not used to improve any model.

Content we generate for you is yours. You are free to use, edit, and publish it. Because it is produced by an AI model from the facts you supply, you should read it before publishing — see the terms for more on that.

How long we keep it

We keep your account and content for as long as your team has an account with us. Generated content stays in your library so you can find and reuse it.

When a team is deleted we remove its database records and every file it stored — brand assets, listing photographs, and generated graphics, documents, and video — along with the accounts of its members.

You can ask us to delete your team's data at any time by writing to hello@thelistingbench.com. We will confirm when it is done.

Your rights

You can ask us for a copy of the information we hold about you, ask us to correct it, or ask us to delete it. Most of it you can also see and change yourself inside the app.

Write to hello@thelistingbench.com and we will respond. Depending on where you live you may also have the right to complain to a data protection authority.

Security

Data is encrypted in transit. Uploaded files are held in private storage and are only reachable through short-lived links generated for a signed-in member of the team that owns them. Every record is scoped to one team, and those boundaries are enforced in the database queries themselves rather than only in the interface.

No system is perfect. If you believe you have found a security problem, please write to us before disclosing it publicly.

Changes

If we change this policy in a way that materially affects you, we will tell you by email before it takes effect.