How Samuel uses Google data

Access and purpose

With the owner's consent, Samuel can read Gmail and send requested messages, read and manage Calendar events, and read and manage Drive files. Calendar and Drive permissions cover the connected account; instructions limit everyday use to the owner's requested tasks.

Google data is used to answer questions, organize personal work, and perform actions the owner requests. It is not sold or used for advertising.

Processing and sharing

Requested Google content may be passed to the configured AI service, currently Anthropic's Claude, to complete a task. Requested answers and excerpts may also appear in the owner's Telegram conversation or private OpenClaw interface. These services process the information delivered to them under their own terms and privacy policies.

This informational website does not connect to Google, receive Google tokens, or display the owner's mail, calendar, files, or conversations. The owner runs those connections from the private Capital workspace.

Storage and access

Google authorization credentials are held in private local credential storage. Conversations, tool results, and files saved during tasks can remain in the local workspace and its backups. The owner's authorized local agents have access to the shared workspace. There is no fixed automatic retention period for saved project material or conversation history.

Revocation and deletion

The owner can revoke Google access through Google Account connections. Revocation stops future authorized access; it does not remove information already saved locally or sent to another service. The owner can separately remove local credentials, saved files, and histories, and manage copies held by connected services. Backup copies follow the configured backup retention.

Google API data

Samuel's use and transfer of information received from Google APIs will adhere to the Google API Services User Data Policy, including its Limited Use requirements.

For questions about this personal integration, contact the app owner using the support email shown on Google's consent screen.