Clawdot

Clawdot / SBot

Privacy policy

Last updated: 2 November 2026

This policy describes the current private SBot deployment operated through Clawdot, including its Google integration, and this information website. Your bot administrator manages access to the bot and the connected Google account.

Information the bot processes

Why Google access is requested

Clawdot requests Docs and Sheets permissions to read linked documents and spreadsheets and to create or append requested content. Google describes these permissions broadly, including editing and deleting Docs and Sheets; SBot’s current tools expose reads, confirmed file creation and confirmed appends.

The integration also requests access to Drive file metadata to check file identity and type, and app-specific Drive file access for files the app works with. These permissions are used to support the requested chat features and maintain the owner’s connection.

The bot acts as the connected Google owner. Members of a permitted chat can request human-posted links that this owner can access, even if a member does not have their own Google permission to the file. Only connect an account and share links suitable for the people in those chats. New files belong to the connected owner; file sharing is managed in Google.

AI processing and other service providers

To answer a request, relevant chat context, uploaded file content, and requested Google file content may be sent to the configured third-party AI provider. Provider settings and policies govern that provider’s processing. Use /privacy in the bot to see the configured provider information.

Chat platforms, Google, the bot’s hosting infrastructure, and the website’s hosting and delivery providers process information needed to deliver their respective services. OAuth refresh tokens are kept in private server credential files and are not placed in the website, public source files or AI prompts.

Stored records and retention

The deployment’s normal retention period for chat messages, conversation records and usage records is 12 months. Saved memories remain until removed. Shared expense ledger records, including balances and settlements, can be retained for the shared accounting history.

Direct Google read results are omitted from persistent tool-result history, but source links, generated replies, summaries, snippets and pending write previews can still contain file-derived information. These can remain in chat records or pending-action storage. Backups are normally rotated after 14 days.

Files created in Google Drive remain there until their owner removes them. Chat deletion commands do not delete those Google files.

Your choices and deletion

This website

This website provides product and privacy information. It has no account sign-in, file uploads, advertising or application analytics. Hosting and delivery services may process routine request data such as IP addresses, browser information and request times.

Questions or requests

Contact the bot administrator through the chat where you use SBot. Google account owners can also use the support contact displayed on the Clawdot Google consent screen. Ask the administrator about data access, correction, deletion, the active AI provider or disconnecting Google.

Policy updates

This page will be updated when the described processing changes. Check the date above and the bot’s in-chat privacy information for the current deployment.