Privacy Policy

Applies to all AEI Theatrical applications · last updated 18 October 2026

These are personal tools with a single user: their author. They are not offered to the public, have no sign-up, and collect no data from anyone else. This policy describes how they handle that one person's own Google data.

Google data accessed

Each application requests only the scopes it needs. Across all of them, access may include:

Where the data goes

These applications run locally on the user's own computer. Message contents, proposals, notes and other records are stored in local databases and in the user's own files. There is no hosted server, no account system, and no analytics.

Some applications send text to a third-party large language model provider for classification or drafting, under that provider's API terms, and receive a response. That is the only circumstance in which content leaves the user's machine. Google user data is sent to Google's own APIs solely to perform a read or an approved write.

Sharing

No data is sold, rented, shared, or disclosed to any other party. Google user data is never used to train any model, and is never transferred except as described above.

Retention and deletion

Data lives on the user's own machine and in their own Google account, and is retained until the user deletes it. Access can be revoked at any time at myaccount.google.com/permissions, which immediately ends all further access. Deleting the local databases and files removes everything these applications have stored.

Security

OAuth tokens are stored on the user's own machine and are never transmitted anywhere else. The applications expose no public network interface.

Changes

If this policy changes, the date at the top of this page is updated.

Contact

kipp@aeitheatrical.com