Last updated .
Stoa is used by one person, its operator, on Google accounts the operator owns. Nobody else signs in to it. If someone shares a file or calendar with one of those accounts, Stoa can read it until they remove the share.
The Google permissions Stoa requests, and what each is for, are listed on the home page. Google user data is used only to answer the operator's requests and to save documents where the operator directs.
Stoa uses commercial AI model providers to understand requests and work with what it finds. Data needed for a request, which can include whole documents, is sent to those providers. Where a provider has a setting that would let it train its models on that data, the setting is off. The other providers do not train on customer data.
Access credentials, and content Stoa has read, are stored on the operator's own cloud systems, including in the software's logs and in backups of those systems. They are kept until the operator deletes them, and are not published anywhere.
Google user data is not sold, and it is not used for advertising, profiling or credit decisions. It is not given to anyone except the service providers Stoa runs on (the AI model providers and the cloud host), and then only to provide the features described here, or where the law requires it.
Stoa's use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements.
Access can be removed at any time at myaccount.google.com/connections. Removing it stops Stoa reading anything further from that account.
It sets no cookies, runs no scripts and has no analytics.