Privacy Policy

1. Scope and who controls data

Veetbot is a self-hostable AI agent. The operator of a Veetbot deployment controls that deployment and its stored records. This policy describes the current Veetbot public website and the owner-operated Gmail integration. It does not replace the policies of Google, an AI model provider, or another service you choose to connect.

2. Public website data

The public website does not provide accounts, forms, behavioral analytics, advertising, or advertising cookies. Hosting and security infrastructure may process ordinary request data such as IP address, browser type, requested URL, and timestamps to deliver the site, prevent abuse, and diagnose failures.

3. Google data Veetbot accesses

Veetbot requests three separate Gmail permissions. Each is used only when its corresponding integration is enabled:

gmail.readonly

Search threads and read message metadata, headers, labels, snippets, and plain-text message bodies. HTML is reduced to text. Attachment names, media types, and sizes may be seen, but attachment contents are not downloaded.

gmail.modify

Google's grant permits Veetbot to read, compose, and send all Gmail messages. Veetbot restricts the separate write integration to creating drafts; adding or removing labels; archiving or marking threads read; and moving threads to or from Gmail trash. Sending uses the separate gmail.send integration and approval path.

gmail.send

Send a plain-text message after the complete proposed message has been presented for approval, or, for an unsubscribe you confirm, the message that sender's own list header specifies.

Veetbot does not use these permissions to permanently delete Gmail messages, download attachments, access calendars, or connect additional mailboxes without a new authorization.

Generated summaries, classifications, drafts, approval records, and other derived output are treated as Google user data under this policy. Veetbot does not create cross-user aggregate or anonymized Gmail datasets.

4. How Google data is used

Google data is used only to provide user-facing features, including:

• searching, reading, and summarizing mail you ask Veetbot to review;
• preparing drafts and organizing messages at your direction;
• sending messages that you explicitly approve;
• running email-triage schedules you configure; and
• maintaining security, reliability, and an inspectable record of agent work.

When enabled, Email mode retrieves priority mail on opening and refreshes while it is active. It progressively analyzes received, archived, and Sent correspondence, including older history, from your connected work and personal accounts. Your feedback, draft edits, and explicitly endorsed examples inform importance and writing style. Useful memories and preferences are shared with Chat and your other connected account within the same assistant, never with other users. Suggested replies remain internal drafts until you approve the exact message for sending.

When People memory is enabled, Veetbot keeps a private directory of the people you know or write to. From your correspondence it records their names and email addresses, how they relate to you, facts stated in messages, dated exchanges with short generated summaries, and open commitments, each linked to the message it came from, so Chat can recall them. Automatic People analysis covers the last 90 days of mail; older mail is analyzed only in an import you start. Bulk mail does not form People records or memories.

When enabled, Veetbot reads the list headers of bulk mail to show you who sends it. It sends an unsubscribe request only when you ask for that sender, by your tap or your approval. The request is the one the sender published in its own message header, returned to that sender with no other Google data, no cookie, and no credential. It is sent from your Veetbot server, so the sender can see the address of your Veetbot server and learn that the mailbox is active. When a sender publishes only an unsubscribe email address, Veetbot instead sends the message that header specifies, and nothing else, from your Gmail account to that address; the confirmation names the address before anything is sent. Veetbot never follows an unsubscribe link in a message body, and it offers no automated unsubscribe for mail that Google did not authenticate.

Veetbot does not sell Google user data, use it for advertising, use it to determine creditworthiness, or use it to train a general-purpose AI model. It is not an email-warming, cold email, unsolicited bulk-send, or recipient-profiling service.

5. AI processing and sharing

To perform an email task, relevant message content and metadata may be sent to the AI model provider configured by the Veetbot operator. This processing is limited to producing the requested user-facing result, such as a summary, classification, draft, proposed action, learned writing-style observation, or useful memory. Historical Email mode analysis uses this same hosted model processing. The hosted deployment uses the OpenAI and Anthropic APIs, depending on the selected model. Veetbot does not permit either provider, or any replacement provider, to use transferred Google user data to train or improve a general-purpose AI or machine-learning model. A self-hosted local model keeps that processing on the operator's host.

Under their standard API data controls, each hosted provider may retain request and response content for abuse monitoring for up to 30 days, subject to limited safety or legal exceptions. See the OpenAI API data controls and the Anthropic API retention policy.

Veetbot may otherwise disclose data only to service providers needed to operate the requested feature, to investigate a security incident, when you explicitly direct or consent to the disclosure, or when required by law. Human access is limited to those purposes and to support you explicitly request. Veetbot does not transfer Google user data to advertisers, data brokers, information resellers, or lending and eligibility services.

6. Storage and retention

OAuth client secrets and refresh tokens are stored in private operator-controlled credential files. Production storage that contains Google user data is encrypted at rest. Tokens and raw Google error responses are excluded from Veetbot tool results, events, and logs.

Email mode caches full message bodies for 30 days after their last access and refetches older content when needed. Minimal source identifiers and synchronization cursors remain while the account is enabled. Writing-style examples are limited to 500 excerpts of at most 2,000 characters each. Unsent drafts remain until discarded; sent or discarded draft body revisions are removed after 30 days. Structured feedback and derived preferences remain until reset or erased. People records and exchange summaries remain until you correct, delete, or forget them or exclude their source.

Gmail content selected for a task, tool inputs and outputs, generated summaries and drafts, approval records, and related artifacts may be retained in Veetbot's operational and conversational session and run history until you delete the session, use source exclusion, or ask the deployment operator to delete it. These copies can outlast the separate 30-day cache and draft-store windows. This supports inspection, continuation, recovery, and auditing. Deletion removes the corresponding live records and artifacts; encrypted backup copies may remain for no more than 35 days before automatic expiration. Deleting mail in Gmail does not automatically delete a copy already retained in a Veetbot record.

7. Your choices and deletion

You may:

• decline the Gmail permissions and use Veetbot without email tools;
• revoke Veetbot's Google access through your Google Account's third-party connection settings;
• disable the Gmail integration and remove its credential files;
• pause email learning, reset importance preferences or writing style, and exclude an email thread from retained sources and derived learning;
• delete an individual memory, remove a fact about a person, or forget a person, which also removes the copies generated from it; and
• delete available sessions or ask the deployment operator to delete associated Veetbot records and artifacts.

Source exclusion removes matching retained email content and its derived influence, including operational copies. Independently supported owner statements and content-free audit metadata remain. It does not delete the original messages in Gmail.

Revoking Google access stops future Gmail API access but does not automatically erase existing Veetbot records. A deletion request may be subject to short-lived backup retention and any legal obligation that requires preservation.

8. Security

Veetbot uses scoped credentials, access controls, encrypted transport, deterministic policy checks, approval requirements, bounded outputs, and secret-redaction controls. No system is perfectly secure, and operators remain responsible for securing their hosts, provider accounts, and backups.

Gmail content is treated as untrusted external input. It cannot authorize an action, grant itself additional access, or bypass policy. Mailbox changes and sends require a separate explicit human approval after Veetbot displays the proposed action.

10. Changes and contact

This policy may change when Veetbot's data practices change. The effective date above will be updated, and material changes affecting Google data will be disclosed before the new use begins. For privacy or deletion requests, use the support address displayed on Veetbot's Google OAuth consent screen. For non-sensitive public questions, use the project issue tracker.

See also the Veetbot Terms of Service.