Privacy

This page covers ApexAgentOS, an internal tool the studio uses to triage its own business mail and read its own project files.

Who this is for

ApexAgentOS is not a product and is not offered to anyone else. It runs on one computer belonging to the studio's Managing Director, and the only accounts it connects to are his own. There are no other users, and no accounts are created.

What it accesses

It requests the narrowest read-only scopes that do the job, and nothing else:

ScopeWhat it allows
gmail.readonly Reading messages and attachments in the connected mailbox, so unanswered threads can be found and summarised.
drive.readonly Reading files in the connected Drive, so project documents and spreadsheets can be read.

It holds no permission to send, reply to, forward, delete or label mail, and none to create, modify, share or delete a Drive file. Those permissions are never requested, and the sending tools are blocked inside the application as a second line of defence. Replies it drafts are saved to Drafts, where a person decides whether to send them.

Where the data goes

Retention

Nothing from Gmail or Drive is kept as a copy. A local activity log records that a request happened — which tool ran, and against what — with identifiers redacted. It stays on the same machine and can be deleted at any time.

Sharing

Data obtained through these scopes is never sold, rented or shared with anybody.

Revoking access

Access can be withdrawn at any moment at myaccount.google.com/permissions, which immediately invalidates the stored tokens. The tokens can also be deleted directly on the machine.

Contact

Questions about this policy: jbautista@apexstudio.ph.