Privacy Policy

Chief of Staff — last updated 19 October 2026

Chief of Staff ("the application") is a private, single-user personal assistant tool operated by, and for, one individual. This policy describes what data the application accesses and how it is handled.

1. Who uses it

The application has exactly one user: its owner. There is no registration, no sign-up, and no facility for any other person to use it. It is not a public or commercial service.

2. What it accesses

With the owner's explicit authorisation via Google's OAuth consent flow, the application requests two scopes, both limited to the owner's own account:

No other Google data is requested or accessed.

3. Where data is stored

The application runs locally on the owner's own computer. Email and calendar content is processed transiently to produce the briefing and is not transmitted to any third party. An OAuth refresh token is stored locally on that machine so the owner does not have to authorise access on every use.

4. No sharing, selling or third-party access

Data accessed by the application is not sold, rented, shared, or disclosed to any third party. It is not used for advertising, profiling, or training machine-learning models. There are no advertising or analytics services in the application.

5. Google API Services User Data Policy

The application's use of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements.

6. Retention and deletion

Locally stored credentials can be deleted at any time by the owner, which immediately ends the application's access. Access can also be revoked at any time from the owner's Google Account permissions page.

7. Changes

If this policy changes, the "last updated" date above will be revised.

8. Contact

phillipmuza@gmail.com