Privacy Policy

WOTS Agent is software used by a real-estate agent to draft, review and send messages to their own contacts. This page says what it stores, who else sees it, and what it will not do.

Last updated 25 August 2026

Who this is

WOTS Agent is operated by WOTS Marketing, a marketing agency in San Antonio, Texas. Contact support@wotsagent.com with any question about this policy or to ask for data to be removed.

Google account data — the short version

WOTS Agent requests exactly one Google permission: https://www.googleapis.com/auth/gmail.send.

• It can send an email from your address. It does that only for a message you have read and approved.
• It cannot read your mail. Not your inbox, not your Sent folder, not a single message. The permission does not allow it and the application does not request one that would.
• It cannot delete or change anything in your mailbox.
• It never sees your Google password. Sign-in happens on Google’s own pages.
• You can revoke it at any time at myaccount.google.com/permissions. Sending stops immediately.

Limited Use

WOTS Agent’s use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements. Specifically:

• Google user data is used only to provide the sending feature described above.
• It is not transferred to anyone else, except as needed to provide that feature, or where required by law.
• It is not used for advertising of any kind.
• It is not used to train generalised artificial-intelligence or machine-learning models.
• No human reads it, other than with your explicit consent, for security purposes, or where required by law.

What is stored

Three kinds of thing, and nothing else.

Your account

Your email address, your name, and which organization and account you belong to. Passwords are stored by our authentication provider as a hash and are never visible to us.

Your contacts

The people you are working with, as your CRM already holds them: name, phone number, email address, Instagram or Messenger account identifiers where a conversation began there, and the notes you keep on them — stage, timeline, price band, tags, when they were last contacted and how that went.

Also stored, and deliberately: whether a contact has opted out, on what basis they consented to be contacted, and when. That record exists so the software can refuse to message someone who has said stop. It is a safeguard, not a marketing field.

Drafts and what happened to them

The message drafts prepared for your approval — the recipient, the subject, the text, and the reason it was suggested — together with any edit you made and a record of what you decided. That record says what actually happened: a text handed to your phone unsent, an email accepted by a mail server, a message posted to a thread. It never claims more than that.

Where it goes

Your data is not sold, and it is not shared for advertising. There is no analytics or advertising tracker on this application.

Who can see what

An agent sees their own account and no other. The agency that supplies the software can see that a queue exists and how quickly it is cleared; it does not see the content of an agent’s client messages. That boundary is enforced by the database, so it holds regardless of what any screen displays.

How it is protected

Google requires an app requesting a sensitive scope to say what protects the data it reaches. Everything below is a mechanism that is in place today, not an intention.

Your Google credential

Connecting Gmail gives this application a refresh token. That token is never stored in our own tables. It is held in Supabase Vault, encrypted at rest, and the record that a connection exists stores only a pointer to it — never the token itself.

Reading it is possible only through database functions that are granted to the application’s server role and revoked from both anonymous and signed-in users. A person signed in to this product cannot ask the database for a Google token — not another agent’s, and not their own. Nothing in a browser ever receives one.

The scope itself is the first protection: this application requests permission to send and nothing else. It has no ability to read, search, download, modify or delete anything in your mailbox, so there is no message content to protect because none is ever retrieved.

Everyone else’s data

• In transit: every connection — browser to application, application to database, application to Google — is TLS. There is no unencrypted path.
• At rest: the database is hosted by Supabase on infrastructure that encrypts stored data, and credentials are separately encrypted in the vault described above.
• Separation between accounts is enforced by row-level security in the database, on every table without exception, rather than by application code. An agent’s session is refused another agent’s rows by the database itself, so a mistake in a screen cannot expose them.
• Actions are recorded in an append-only log. Database triggers refuse any attempt to change or delete an entry, by anyone, including us. A record of what was approved and sent cannot be quietly rewritten.
• Access to production is limited to the operator named at the top of this page, through accounts protected by the sign-in of the platforms that host it.

If we ever discover that data has been reached by somebody who should not have reached it, we will contact the people affected and, where the law requires it, the relevant authority. Write to support@wotsagent.com to report a security concern; it reaches a person rather than a queue.

How long it is kept

A draft that has been acted on is deleted after 30 days, and that is automatic rather than something you have to ask for. The message, who it was addressed to, and the contact it named all go with it. Two things deliberately survive: the record that somebody approved it, which is an audit log nobody can edit or delete, including us; and how the agent writes, which is learned from the edits they make to our drafts and belongs to them rather than to any one message.

Contacts are kept while the account is active. Ask us to close an account and its data is deleted within 30 days, apart from records we are required to keep — an opt-out is retained precisely so that a deleted and re-imported contact cannot be messaged again by accident.

Your choices

• Ask for a copy of what is held about you.
• Ask for it to be corrected or deleted.
• Disconnect Google, and sending from your address stops at once.
• If you are a recipient rather than a user: reply STOP to any text, or ask the agent who contacted you. An opt-out applies on every channel and is permanent.

Email support@wotsagent.com. We reply within 30 days.

Children

This is a tool for licensed professionals. It is not for anyone under 18 and we do not knowingly collect their data.

Changes

If this policy changes in a way that affects what happens to your data, we will say so here and, for a material change, by email before it takes effect. The date at the top is the version in force.