Privacy policy
This policy describes how AgentOS Memory Writer ("the Writer") handles Google user data. The Writer is operated privately by its developer for their own use; it is not offered to other users. The only Google account it is authorized for is the developer's own.
1. Google data the Writer accesses
With the developer's consent, the Writer requests two Google permissions:
- Google Drive (
https://www.googleapis.com/auth/drive). The software uses it only for one configured Drive folder that holds the memory documents. In that folder it lists files, reads their content and revision history, updates documents, creates a missing memory document, and moves to the trash a duplicate it created itself. The permission Google grants is broader than this; the Writer's code restricts itself to that folder. - Google Docs (
https://www.googleapis.com/auth/documents). Used only for occasional edits, made at the developer's direction, to the developer's own design documents in Google Docs, with the document read back afterwards to confirm the change.
The Writer does not access Gmail, Contacts, Calendar or any other Google service.
2. How the data is used
The data is used only to maintain the developer's memory documents: to read their current content, apply an update, and verify from Drive's revision history that the update was saved as intended. It is not used for advertising, sold, or used to build profiles, and no person other than the developer reads it.
3. Processing by Anthropic
To apply an update, the Writer sends Anthropic's API (the Claude Haiku model) the update itself and the current text of the memory documents it may change. The model returns the edited text, which the Writer then saves to Drive. Content is therefore not kept only within Google: selected memory content is processed by Anthropic under the developer's Anthropic API account and is subject to Anthropic's privacy policy and commercial terms. The Writer sends Anthropic nothing beyond what an update requires.
4. Services involved
- Google Drive and Google Docs store the documents. Google's own terms and retention apply, including Drive's revision history.
- Anthropic processes the text needed for each update, as described above.
- The developer's own computer runs the Writer. The developer's separate AgentOS agents, including an OpenAI Codex model used as the "Brain", read the same memory documents from the developer's Google Drive for desktop folder. They do not use this application's Google authorization.
5. Authorization and revocation
Access exists only because the developer completed Google's consent screen for this application. It can be revoked at any time at myaccount.google.com/permissions. Once access is revoked, the Writer can no longer read or change anything in Google Drive or Google Docs; updates that cannot be saved wait on the developer's computer rather than being sent anywhere else.
6. Storage, retention and deletion
- The memory documents remain in the developer's Google Drive until the developer deletes them there.
- On the developer's computer, AgentOS keeps a local record of each update: its text, the edit applied, checksums, and the Drive file and revision identifiers. There is no automatic retention period; the records stay until deleted.
- Deletion requests can be sent to the contact address below. The developer can delete these local records and the Drive documents. Copies already held under Google's revision history or Anthropic's retention practices are governed by their own policies.
7. Credentials and access restrictions
The Google authorization (an OAuth refresh token) and the application's client configuration are stored as files in the developer's own user profile on their computer, outside any source-code repository. They are not published and not committed to source control. AgentOS does not give them to its other agent processes. The Anthropic API key is stored separately in the same way.
8. Google API Services User Data Policy
AgentOS Memory Writer's use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements. Google user data is used only to provide the memory-maintenance function described here and is transferred only as described in section 3. It is not used for advertising, is not sold, is not read by humans other than the developer, and is not used to develop, improve or train generalized AI or machine-learning models.
9. This website
This website is static. It sets no cookies and uses no analytics or tracking. It is served through Cloudflare.
10. Changes and contact
If this policy changes, the updated version will be posted here with a new effective date. Questions or requests: orbenhar100@gmail.com.