A private automation setup, operated by one person, for that person's own records.
Stoa is a small set of personal software agents run by a single individual on a single private server. They help their operator keep on top of his own documents and calendar: finding a file he already has, summarising a statement he already received, and filing a document he has just downloaded into the folder where its siblings already live.
Stoa is not a product. There is nothing to sign up for, no shared service, and no other users. It is one person's own tooling, and this page exists because Google reasonably asks any application that requests access to a Google Account to say publicly what it does.
Stoa authenticates as Google accounts belonging to its operator, and only as those accounts. It requests the narrowest scopes that let it do its job:
| Access | Why |
|---|---|
drive.readonly |
Read files and folders the operator has shared with the account, so an agent can find and summarise a document on request. |
drive.file |
File a newly downloaded document into one specific pre-agreed folder. This scope covers only files the application itself creates; it cannot read, alter or delete anything else in Drive. |
calendar.readonly |
Read the operator's own calendar, so an agent can answer questions about what is scheduled. |
Access is read-only by default. Stoa holds no scope that can send email, share a file, change a permission, or delete anything. The single write capability is confined to creating new files in one named folder, and it cannot overwrite a file it did not create.
The full statement, including retention and how access is revoked, is in the privacy policy.