Privacy Policy

Agent Tool · last updated 27 September 2026

Agent Tool is a single-user application operated by Roman Parker for himself. It runs on his own computer, with a small relay server he operates so that he can reach it by message and phone while the computer is asleep. It connects only to his own Google account. There are no other users.

Google data it accesses, and why

Scope	What it is used for
`gmail.modify`	Reading messages so the assistant can answer questions about them and point out ones that need his attention, and marking them read, archived or labelled when asked.
`gmail.send`	Sending mail he has explicitly asked for and confirmed. Nothing is sent without his yes.
`calendar`	Reading the schedule for questions, briefings and reminders, finding free time, and creating or editing events when asked.
`drive`	Finding and reading files he refers to, noticing recently changed ones, and saving documents the assistant creates.
`documents`, `spreadsheets`, `presentations`	Creating and editing Google Docs, Sheets and Slides at his request.
`tasks`	Keeping his Google Tasks list in step with the things he has asked to be reminded of, and reading back which ones he has ticked off.
`userinfo.email` and `openid`	Confirming which account is connected, so the assistant can say which mailbox it is reading.

Where the data goes

His computer. Google is read from his own computer, which holds the only Google credentials. What it reads may be kept there in the conversation history and the assistant's notes, in a local database and local files.
His relay server. A small server he runs on Fly.io carries his messages and calls while the computer is asleep. It holds no Google credentials and cannot read Google. It does receive what the computer sends him — replies, reminders, briefings that mention his mail or calendar, requests for his approval — and keeps a copy of the assistant's notes so it can answer from them.
Language model providers. To answer a question about an email or a calendar entry, the relevant text is sent to the model that writes the reply: OpenAI for conversation, and models reached through OpenRouter (Z.ai's GLM, and Typesafe's Jev for small decisions). Only the content that request needs is sent. OpenAI requests are sent with storage turned off, and OpenAI does not train on API data; OpenRouter requests are restricted to zero-data-retention endpoints that do not train on it.
Messaging and phone. Replies reach him over Signal, which is end-to-end encrypted. Phone calls run over Telnyx's phone network.
Web search. When the assistant searches the web, its search terms go to Brave Search.
Nowhere else. Google data is not sold, shared, used for advertising, or used to train any model, and is not sent to analytics.

Speech

At his desk, speech recognition and synthesis run on his own computer. A voice note sent by message is transcribed by OpenAI, and a phone call is carried by Telnyx and spoken by OpenAI's realtime voice model, with storage turned off.

Retention and deletion

Conversation history and notes persist until he deletes them, on the computer or the relay. OpenAI may keep requests for up to 30 days to monitor abuse, as its API terms describe. Access to the Google account can be revoked at any time from Google Account permissions, which immediately and permanently ends this application's access. Stored credentials can also be deleted locally.

Limited Use

Agent Tool's use of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements.

Contact

Questions about this policy: romanwalterparker@gmail.com.