Legal

Privacy and AI notice

Effective 30 August 2026 · GeoSocial Reality LLC

This notice is for publish.re and api.publish.re. Homendo and TimeToSell.AI publish their own notices. We wrote it so a person — and a regulator — can see what Publish.RE does with data and with AI.

1. Who we are

Controller: GeoSocial Reality LLC, 6020 Greenwood Plaza Boulevard, Greenwood Village, CO 80111, United States. Contact privacy@publish.re or +1 (303) 930-5152.

If you are in the EEA or UK and use Publish.RE, we process your account data as controller. Listing facts we pull from an MLS or Homendo API are processed on your instructions as processor for that workspace.

2. What we collect

Account. Name, email, password hash, Google sign-in identifiers if you choose that path, plan, seats.
Profile and sources. Display name, public URLs, MLS originator and member id, source taps, listing cards a provider returns (address, price, status, photos, public remarks).
Content. Drafts, voiceover scripts, hashtags, approved and published items, render job ids.
Networks. OAuth tokens and page or channel ids you connect; send receipts from those APIs.
Operations. IP, user agent, logs under /tmp, security events, usage meters.
Payments. Handled by the processor we name at checkout. We do not store full card numbers.

3. Why we process it

To run Publish.RE you asked for: authenticate you, attach sources, generate drafts, compile reels, publish when you approve or automate, bill the plan, keep the service secure, and meet law. Colorado Privacy Act lawful bases we rely on: the product you request, security, and (where required) consent for optional analytics or marketing email. GDPR bases where it applies: contract, legitimate interests (secure the service, understand product use at aggregate level), and consent where we ask for it.

4. AI systems — EU AI Act transparency

Publish.RE is an AI-enabled publishing product. We are not offering a prohibited practice under Regulation (EU) 2024/1689. Publish.RE is designed as a limited-risk / transparency system: it drafts marketing content from sources you attach. It is not intended as a high-risk system under Annex III (it does not decide credit, hiring, biometric identity, or essential private services).

4.1 What the model does

Third-party models (text completion) draft posts, emails, and spoken scripts from the listing or source packet. A separate render node (Homendo cinematic engine) may synthesize a voiceover and burn captions onto listing photos. Those outputs are AI-generated or AI-manipulated.

4.2 What the model must not do

Publish.RE is instructed not to invent a source. If a field is missing on the listing card, the draft should stay silent on that field. You can rewrite or delete any draft.

4.3 Human oversight (Article 14 spirit / product rule)

Manual is the default for a send: you approve. Automation is an explicit workspace setting. You can turn a source off, delete a draft, or disconnect a network at any time.

4.4 Marking (Article 50)

Where we control the file (a compiled reel with synthetic speech), the production chain is machine-generated. We will keep machine-readable or visible marks when the render path supports them. You must not remove marks in order to present a synthetic voice or image as an unaltered recording of a person. On social networks you remain responsible for any extra disclosure that platform requires.

4.5 Training

GeoSocial Reality does not sell your workspace contents as a training corpus to third parties. Providers we call (text or speech APIs, the render node) process prompts and media to return a result. We configure those calls so customer content is not used to improve a provider’s general model where the provider offers that switch. We do not scrape the open web to build a Publish.RE foundation model.

4.6 Accuracy and risk

Models err. A square-footage or price spoken in a reel can be wrong if the source was stale. You must check facts against the live listing or bulletin before a send. We log generation events so a workspace owner can see what was drafted.

5. Who we share with

Infrastructure and email hosts that run publish.re.
Homendo / MLS.RE listing APIs when you enable an MLS source.
The render node when you compile a reel.
Text-to-speech and language-model providers when you generate or regenerate copy.
Social and email APIs you connect.
Authorities when law requires it.

We do not sell personal information as Colorado and California define that term.

6. Retention

Account and workspace data last for the life of the account plus a short legal archive. Deleted drafts are removed from the working library; backups expire on the host cycle. Render files on the node follow that node’s retention. Logs are rotated. You may export or delete a workspace by writing privacy@publish.re; we complete a verified request within the period Colorado law sets (usually 45 days).

7. Your rights

Colorado Privacy Act and, where they apply, GDPR / UK GDPR: access, correction, deletion, portability, opt-out of targeted advertising and certain profiling, and appeal of a denial. EU/UK users may also object or restrict processing and complain to a supervisory authority. We will not deny service solely because you exercised a privacy right, except that Publish.RE cannot run without the account data it needs.

Authorized agents may write privacy@publish.re from the account email. We will verify.

8. Children

Publish.RE is for professionals. We do not direct it at children under 16 and we do not knowingly collect their data.

9. International transfers

Primary hosting is in North America. If you are in the EEA/UK, transfers use the safeguards the destination law requires (standard contractual clauses or an adequacy decision when available).

10. Security

TLS in transit, hashed passwords, hashed API keys with a server pepper, role-separated admin, and signed render webhooks. No method is perfect. Tell us of a suspected incident at privacy@publish.re.

11. Cookies

Session cookies keep you signed in. Theme preference may sit in localStorage. We do not run a third-party advertising pixel on Publish.RE chrome. reCAPTCHA and Google sign-in, when enabled, set cookies those services describe in their own notices.

12. Changes

The date at the top is the effective date. Material AI or data-use changes will be posted here and, for account holders, noted in the product.