Privacy Policy
Last updated November 8, 2026
This policy explains what Roompop LLC (“Roompop,” “we,” or “us”) collects when you use our website and services, why we collect it, who we share it with, and the choices you have. It applies to both real estate professionals who publish walkthroughs (“Agents”) and people who view them (“Visitors”).
1. Information we collect
Information you give us
- Account details. Your email address, name, and a password. Passwords are stored only as salted hashes by our authentication provider; we never see or store your password in readable form. If you sign in with Google instead, Google shares your name, email address, and profile picture with us, and we do not receive a password.
- Listing content. Room photographs and property details — address, price, bedrooms, bathrooms, square footage, description — that Agents upload. We remove location, camera, and other embedded metadata from uploaded photographs, except a photographer credit and copyright notice if the file carries one.
- Photo-rights certifications. When an Agent certifies that they have the rights to upload a listing’s photographs, we record their account, email address, the listing, the time, and the wording they agreed to.
- Prompts. The text you type to describe how a room should be restyled.
- Billing details. Entered directly with Stripe. We receive a customer identifier, subscription status, and the last four digits and brand of your card. We never receive full card numbers.
- Support messages. Anything you send us when you ask for help.
- Copyright notices. The contents of copyright infringement notices and counter-notices, including the sender’s name and contact details.
- Listing reports. When you report a listing, we record the listing and the room you were viewing, the reason and any details you give, the email address you give if you choose to, your account if you are signed in, and a one-way hash of your IP address (never the address itself), used to prevent abuse of the report form.
- Photo reviews. If an Agent asks for a person to review a photograph that our automated screening rejected, we record the request and the decision.
Information collected automatically
- Usage data. Which listings and rooms are viewed, how many AI generations are requested, and when — used to enforce plan limits and to show Agents how their listings are performing.
- IP address. Recorded in server logs by our hosting provider. For abuse prevention on the public generation endpoint we store a one-way hash of the IP address rather than the address itself, so repeated requests can be counted without retaining the address.
- Photo screening. Each photograph an Agent uploads is sent to OpenAI for automated content screening, and we record the result. A photograph that appears sexually explicit or graphically violent is rejected and never published; we keep it, unpublished, for a limited time so that a person can review it if the Agent asks.
- Enforcement records. When a person finds that an account broke our Terms, we record any strike against the account, with its reason and the listing or notice it relates to.
- Device and browser information. Standard request metadata such as user agent and referring page.
We do not use advertising networks, third-party analytics trackers, or cross-site tracking cookies, and we do not build advertising profiles. Because we do not track you across other sites, we treat every visitor the same way whether or not their browser sends a “Do Not Track” or Global Privacy Control signal.
2. How we use information
- To create and maintain your account and keep you signed in.
- To generate restyled room images at your request, which requires sending the selected photograph and your prompt to our AI provider.
- To publish and serve the walkthroughs Agents create.
- To process subscription payments and maintain credit balances.
- To enforce plan limits, rate limits, and passcode protection, and to detect and prevent abuse and fraud.
- To provide support, and to send service and billing notices.
- To diagnose errors, monitor reliability, and improve the Service.
- To keep evidence of photo-rights certifications, handle copyright notices and counter-notices, and apply our repeat-infringer policy.
- To screen uploaded photographs, handle listing reports, and enforce our Terms — including reviewing rejected photographs, taking down listings, and recording strikes.
- To comply with legal obligations and enforce our terms.
We do not sell your personal information, and we do not share it for cross-context behavioural advertising.
3. Legal bases (EEA and UK)
Where the GDPR applies, we rely on: contract, to provide the Service you signed up for; legitimate interests, to secure the Service, prevent abuse, screen uploaded content and handle reports about it, improve reliability, and establish, exercise, or defend legal claims (including keeping photo-rights certifications and handling copyright notices); legal obligation, for tax and accounting records; and consent, where we ask for it specifically.
4. Who we share information with
We use the service providers below to run the product. Each processes data only as needed to provide its service to us.
- SupabaseAccount records, listing data, and photo storage (database and object storage).Data: Email, name, listing details, uploaded and AI-generated images.
- VercelApplication hosting and delivery.Data: IP address and request metadata, in standard server logs.
- StripeSubscription billing and payment processing.Data: Name, email, billing address, and payment details — entered directly with Stripe. We never receive or store card numbers.
- ResendSending account emails, such as sign-up confirmations and password resets.Data: Your email address and the content of those emails.
- Google WorkspaceOur email inboxes, for the support, privacy, and copyright messages you send us.Data: Your email address, name, and anything you include in your message.
- OpenAIGenerating restyled room images from a photo and a text prompt, and automatically screening photos Agents upload for sexually explicit or graphically violent content.Data: The room photo being restyled and the prompt describing it, and each photo an Agent uploads. Sent through the OpenAI API, which does not train on API data by default.
- SentryError monitoring, so crashes and failed requests can be diagnosed and fixed.Data: Error details, the page or request that failed, browser and device type, and IP address. Cookies, credentials, and email addresses are removed before sending.
- CloudflareBot protection (Turnstile) on the sign-in, sign-up, and password-reset forms, and before a visitor’s first AI design on a listing.Data: IP address, browser characteristics, and interaction signals used to tell people from bots.
Copyright notices. As the U.S. Digital Millennium Copyright Act contemplates, when we receive a copyright notice about content an Agent uploaded we send the Agent a copy, including the sender’s contact details; and when an Agent sends a counter-notice we send it, including the Agent’s contact details, to the person who sent the original notice. See our Copyright Policy.
We may also disclose information when required by law or valid legal process, to protect our rights or the safety of others, or in connection with a merger, acquisition, or sale of assets — in which case we will give notice before your information becomes subject to a different policy.
5. AI processing
When you request a restyled image, the source photograph and your prompt are sent to OpenAI’s API and the returned image is stored in your account. OpenAI does not use data submitted through its API to train its models by default. We do not use your photographs or prompts to train any model of our own.
Photographs that Agents upload are also sent to OpenAI’s moderation service, which screens them for sexually explicit or graphically violent content on our behalf. Designs are not screened this way; prompts are checked before a Design is generated, and Designs stay private to the person who made them.
6. Listing visibility
Listing visibility is controlled by the Agent. A published listing without a passcode is accessible to anyone who has its link and may be indexed by search engines; a listing protected by a passcode reveals no property details until the passcode is entered, and is excluded from search indexes. Agents choose what property information to publish and who receives the link.
7. Cookies and local storage
We set only cookies that the Service needs to work:
- Authentication cookies that keep you signed in. They are HTTP-only, restricted to our own site, and sent over HTTPS only.
- Listing unlock cookies that remember you entered a valid passcode, so you are not asked again on every page.
- A short-lived sign-up cookie (about ten minutes) that remembers whether you chose an agent or buyer account when you sign up with Google, so we can finish setting up the right kind of account when Google sends you back.
When you view a listing without signing in, we also set a visitor cookie holding a random identifier. It is HTTP-only, is not derived from anything about you, and lasts up to a year. Its only purposes are to keep your AI designs on that listing between visits, to count them against the per-visitor allowance the agent set, and to remember that you passed our security check. If you later sign in, your designs are moved to your account and the identifier is no longer used.
Because these are strictly necessary to provide the Service, they do not require consent. Blocking them will prevent sign-in, passcode-protected listings, and saved designs from working.
8. Retention
- Account and listing data is kept while your account is active. When you delete your account from Settings, your profile, listings, photographs, saved homes, and AI designs are removed immediately (photo-rights certifications are the exception described below); anything remaining in logs or backups is deleted or anonymized within 30 days, except where we must keep it longer by law. Deleting a single listing, or removing a photograph from one, removes those photographs and the designs made from the listing within 30 days. A photograph removed because of a copyright notice is kept, unpublished, for up to 90 days — or until a counter-notice about it is resolved — so that it can be restored if the notice turns out to be mistaken.
- Photo-rights certifications are kept while the listing exists and, after the listing or your account is deleted, until four years have passed since the certification was given. They are the evidence we need if a copyright claim about the photographs is made, and such claims can be brought up to three years after an infringement is discovered. Copyright notices and counter-notices are kept for the same reason, for as long as a claim could be brought.
- Designs made without signing in are tied to the visitor cookie described above. Once no browser can reach them — at most about 13 months after the last visit — they are deleted automatically.
- Rejected photographs that the Agent does not ask to have reviewed are deleted 30 days after they were rejected. A photograph that is reviewed is deleted 30 days after the decision if the rejection is upheld; if it is approved, it becomes an ordinary listing photograph.
- Listing reports are deleted 180 days after they are resolved.
- Strike records are kept for two years after the strike is recorded.
- Billing records are retained as long as tax and accounting law requires — generally seven years.
- Hashed IP records used for rate limiting are short-lived and pruned automatically.
- Backups may retain deleted data for a limited additional period before they roll over.
9. Security
Data is encrypted in transit with TLS and at rest by our infrastructure providers. Listing photographs are held in private storage and served only through short-lived signed URLs. Database access is constrained by row-level security so accounts cannot read one another’s data. Passwords are checked against known public breach corpora using a method that never transmits your password. No system is perfectly secure, but if a breach affects your personal information we will notify you and any required regulator as the law requires.
10. Your rights
Depending on where you live, you may have the right to access, correct, delete, or receive a portable copy of your personal information; to object to or restrict certain processing; and to withdraw consent. California residents have the rights to know, delete, correct, and to opt out of sale or sharing — we do not sell or share personal information as those terms are defined by the CCPA.
To exercise a right, email privacy@roompop.ai. We will verify your request and respond within the time the applicable law allows. We will not discriminate against you for making one. Much of this is also self-service from Settings: you can edit your profile, change your email, download a copy of your data, delete listings and images, and permanently delete your account.
11. International transfers
We operate in the United States, and our providers may process data there and elsewhere. Where personal information is transferred out of the EEA or the UK, we rely on appropriate safeguards such as the European Commission’s Standard Contractual Clauses.
12. Children
The Service is not directed to children under 13 (or under 16 in the EEA and UK), and we do not knowingly collect their personal information. If you believe a child has provided us information, contact us and we will delete it.
13. Changes to this policy
We may update this policy. We will change the “last updated” date above and, for material changes, give notice by email or in the product before the change takes effect.
14. Contact
Privacy questions and requests: privacy@roompop.ai
Roompop LLC, 5900 Balcones Drive, Suite 100, Austin, TX 78731
See also our Terms of Service.
p