Privacy Policy

1. What we collect

Information you give us

• Account details. Your email address and a password. We store only an Argon2 hash of the password, which can’t be turned back into the password.
• Google sign-in, if you connect it. Google’s identifier for your Google account, the email address Google reported when you connected it, and when it was last used to sign in. We never receive your Google password or other Google data.
• Your profile. Your name, phone number, email, website, license number, headshot, brokerage logo, team logo and QR code, if you add them. They exist to be printed on your marketing.
• Listing content. Addresses, prices, property details, features, photographs and the text you write. If you import property details from a document, we keep the listing you confirm, the document’s file name, short excerpts showing where each detail came from, and a record that you confirmed you may use the document. The document itself is not kept.
• Your instructions. The choices you make and anything you type into fields such as Make Changes, Advanced or a style description.
• Messages to us. What you send through Contact Us or by email.
• Purchases. You pay on Stripe’s checkout page. Your card details go to Stripe and never reach us. We give Stripe your workspace name and email address. Where sales tax is calculated on a purchase, Stripe asks for your billing address to calculate it. Stripe holds that address, and we can see it in Stripe’s record of the payment.

Information the service records

• Your work. Generated designs and enhanced photographs, the settings that produced them, and their version history.
• Credit and payment records. An append-only ledger of credits added, held, charged, returned and removed; for each purchase, Stripe’s references, the pack, the credits, the amount and the currency; and any refund or dispute notice Stripe sends us.
• Security records. Sign-ins (successful and failed), sign-outs, password and email changes, and similar account events. With each we keep when it happened, the outcome, a shortened form of your IP address (enough to identify a network, not a device) and the first 200 characters of the name your browser reports for itself. Sessions store the shortened IP address they started from.
• Terms acceptance. Which version of the Terms you accepted and when.
• Administrator access. When one of our administrators opens your workspace to give support or investigate a problem, we record who did it and when.
• Application logs. Account identifiers, timestamps and errors. They are written not to contain your email address, your listing text, your prompts or any password, key or token.

What we don’t collect

We use no analytics service, advertising pixel or third-party tracker, and do no behavioral profiling. We don’t buy information about you, and we don’t track you across other websites.

2. Cookies

We set only cookies that are strictly necessary. All of them are HttpOnly, so scripts on the page can’t read them.

• lc_session keeps you signed in, until you sign out or the session expires.
• lc_consent remembers the choice you make in the cookie banner shown on your first visit (Accept, Reject or Necessary Only). It lasts one year.
• lc_google_oauth protects a Google sign-in while it is in progress, for about ten minutes.
• lc_social_state protects a Facebook or Instagram connection while it is in progress, for about ten minutes.
• lc_admin_view is for our administrators only: which workspace they are viewing, for the browser session.

None is an advertising or analytics cookie. The service keeps no drafts, no content and no settings in local storage; the server holds the only copy.

3. How we use it

• To provide Listing Cavy: to build your marketing, store your work and show it to you.
• To place your headshot, logos, QR code and contact details on your pieces.
• To meter credits, process payments and refunds, and keep financial records.
• To keep accounts secure, prevent fraud and investigate misuse.
• To send messages about your account: security notices, password resets and notices of changes to our terms. Payment receipts, where sent, come from Stripe.
• To answer your messages.

We don’t use your content to train AI models, ours or anyone else’s. We don’t sell personal information, and we don’t share it for cross-context behavioral or targeted advertising.

4. AI providers

We use OpenAI to generate and edit images and to read the property details in documents you import. What is sent depends on what you do:

• Listing Marketing and Marketing Kits. The text of your request, including the listing details and the copy you wrote, and the photographs you selected. Your headshot, brokerage and team marks and QR code are not sent; we add them to the finished piece from your own files afterwards. Your contact lines are added the same way, except on layouts with no room for them, where they are included in the text of the request.
• Agent Marketing. The text of your request and your headshot, brokerage and team marks and QR code. The model draws them into the design, so what appears is the model’s rendering, not your file.
• Enhance Photo. The photograph you chose and the enhancement you asked for.
• Import Property Details. The text we read from the webpage, PDF, Word, text or RTF file you upload, or the text you paste, so the model can find the property details in it. We read the file on our server and send only its text, with scripts, hidden content and images left out. The model’s answer is a suggestion: you check and correct every value before a listing is created.
• Make Changes. The earlier design and the sentence you typed. For Listing Marketing this is the design as the model made it, before we added your headshot and marks.

OpenAI states that API data is not used to train its models by default, and that it keeps abuse-monitoring logs of API requests, including image requests and imported document text, for up to thirty days for abuse monitoring. We send imported document text with OpenAI’s response storage turned off; the abuse-monitoring logs still apply. It may keep an image longer if its safety systems flag it for review. This describes their published policy as of the effective date above and is not a promise on their behalf; OpenAI’s own terms govern what it does.

5. Who else receives information

Only the providers we need to run Listing Cavy, and only for that purpose:

• OpenAI: image generation and editing, and reading imported documents, as described above.
• Railway: hosts the application and its database.
• Cloudflare: carries traffic to and from our website, stores your photographs, logos, headshots and generated work (R2), stores our encrypted database backups, and forwards email sent to our support address.
• Stripe: payments, refunds, fraud prevention and, where it applies, sales-tax calculation. Stripe also uses payment data under its own privacy policy.
• Resend: sends our emails and delivers Contact Us messages to our support inbox.
• Google: hosts our support mailbox (Gmail), which receives what you send to our support address or through Contact Us; and sign-in, only if you connect a Google account.
• Meta (Facebook, Instagram): only if you connect an account, and only when you press Post (see section 6).

We may also disclose information if the law requires it, to protect our rights or someone’s safety, or to establish or defend a legal claim. If the business is sold or merged, your information may transfer to the new owner, who must honor this policy or tell you before any new policy applies.

People in your workspace can see its listings, assets and designs. No other customer can. Our providers may process information in the United States and in other countries where they operate.

6. Social accounts

If you connect a Facebook Page or an Instagram business account:

• Meta gives us the name and identifier of each account you choose, and an access token.
• We store the token encrypted and use it only when you press Post. We don’t read your feed, followers or messages.
• For Instagram, the image is made available at a web address that stops working after fifteen minutes.
• Disconnecting, or closing your Listing Cavy account, deletes the stored token. Removing Listing Cavy in your Facebook settings deletes the connections tied to that Facebook account.
• Posts already published stay on Facebook and Instagram.

7. How long we keep it

• Your content and work. Kept while your account exists, and after closure until you ask us to delete it (section 8). Removing something from view does not always delete it:
  • Removing a photograph from a listing deletes it and its preview from storage. If storage refuses the request, we retry automatically until it succeeds.
  • Deleting a listing archives it: it leaves your list, but its photographs and marketing stay stored.
  • Removing an image you added to a marketing piece hides it.
  • Closing your account stops sign-in and removes social connections, but does not automatically delete your content.
• Uploaded photographs. Before upload, your browser converts HEIC photographs to JPEG, and resizes or recompresses a photograph larger than 5 MB or 2,560 pixels on its longest side. Photographs that don’t need this are uploaded unchanged. We keep the file your browser sent and a smaller preview. When a photograph was processed, we never receive or keep its original, so keep your own original.
• Payment and credit records. These are financial records. They are never edited, only corrected by new entries. We keep them for as long as needed for tax, accounting and legal purposes, which is at least seven years.
• Security records and administrator-access records are kept for as long as the account exists, so access to your account can always be accounted for.
• Diagnostic records of failed generations. Deleted after 90 days.
• Terms acceptance records. Kept as long as the account exists and afterwards as long as needed to show what was agreed.
• Backups. Our database is backed up daily, and each backup is deleted after 36 days. Our hosting provider also keeps its own recovery copies of the database under its retention settings. So deleted information can survive in backups until they expire. Photographs and designs are not included in those backups.
• Messages to us. Kept in our support mailbox for as long as needed to deal with them.

8. Your choices and rights

You can see and change most of your information yourself while signed in: your profile, listings and work, and your account and security settings.

You can also ask us to tell you what personal information we hold about you and give you a copy, to correct it, to delete it, or to close your account. We respond to deletion requests individually and will tell you what we deleted and what we must keep, such as payment, credit and tax records.

To make a request, email [email protected] from your account’s email address, or use Contact Us. We’ll confirm the request comes from you, normally by replying to that address, and respond within 45 days. Making a request will never cost you anything or change the service you get.

State privacy laws. Some US states give residents rights such as access, correction, deletion and portability. We give the rights above to everyone, wherever they live. We do not sell or share personal information for advertising at all, and we don’t set optional cookies, so there is nothing for an opt-out or a Global Privacy Control signal to switch off. If that ever changes, we’ll treat a Global Privacy Control signal as an opt-out.

9. Security

• Passwords are hashed with Argon2 and checked against a list of known-breached passwords.
• Every database query is limited to your workspace.
• Traffic is encrypted in transit.
• No key or secret is sent to your browser.
• Access tokens for connected social accounts are encrypted.
• Administrator access to a workspace is recorded.

No system is perfectly secure, and we do not claim otherwise. If a breach affects your personal information, we’ll notify you and the authorities the law requires, without unreasonable delay.

10. Children

Listing Cavy is a business tool for adults and isn’t directed at children. We don’t knowingly collect information from anyone under 18. If you think a child has given us information, tell us and we’ll delete it.

11. Changes

If this policy changes in a way that matters, we’ll raise its version, change its effective date and email account holders at least 30 days before the change applies.

12. Contact