Privacy Policy

Last updated: 2026-08-27

AGENTIC OS is a personal, self-hosted application built and operated by a single individual for their own use. It is not offered to the public, has no other users or customers, and does not collect, process, or store data on behalf of anyone other than its own operator.

What Google data AGENTIC OS accesses

With the operator's explicit, per-account authorization, AGENTIC OS can request read-only access to:

These scopes are read-only. AGENTIC OS never sends email, never creates, edits, or deletes Drive files, and never creates, edits, or deletes calendar events.

How that data is used

Google data is only ever fetched in direct response to a specific request the operator makes to one of their own AI coding agents (for example, asking it to look up an email or check a calendar event), and is used only to answer that request. It is never used to train any machine learning model, never shared with any third party, and never sold.

How data is stored

OAuth refresh tokens are stored only in a local file on the operator's own machine, outside of any application source code or version control, and are never transmitted anywhere except directly to Google's own token endpoint to obtain a short-lived access token. Retrieved Gmail/Drive/Calendar content is used transiently to answer the operator's request and is not separately retained beyond the application's own short-lived task memory.

Your control over this data

Since the operator is the only user, they can disconnect any connected Google account at any time from within AGENTIC OS, which deletes the locally stored token and attempts to revoke it with Google. Access can also be revoked directly at myaccount.google.com/permissions.

Contact

Questions about this policy can be sent to libic.oliver@gmail.com.