Privacy Policy

context-engine · last updated 13 October 2026

1. Scope

context-engine is a private tool operated by Terry Newman for his own use. It has a single user, who is also its operator. It is not offered to the public and collects no data from anyone other than its operator.

2. What it accesses

With the operator’s explicit Google authorisation, and only for Google accounts the operator himself controls, the application accesses:

• Google Tasks (read and write) — to read open tasks and to create, update and complete them.
• Google Calendar (read only) — to read event times, titles and attendees for the daily briefing.
• Gmail (read only) — to read message headers and content in order to surface items needing attention and to locate documents and deadlines.

The application never sends mail, never deletes mail, and never modifies calendar events.

3. Where data goes

Data is processed on the operator’s own computer and stored in local files on that machine. OAuth tokens are stored locally and are used solely to re-authenticate to Google.

There is no server, no hosted database and no analytics. No data is sold, rented, published, or shared with advertisers or data brokers. No data is transferred to any third party except where the operator himself directs a specific piece of content to a service he has chosen to use.

4. Google user data and limited use

The application’s use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including its Limited Use requirements. Google user data is used only to provide and improve the operator’s own briefing and task features. It is not used for advertising, and it is not used to train generalised machine-learning models.

5. Retention and deletion

The operator can delete all stored data at any time by deleting the application’s local files, and can revoke the application’s access at any time from the Google Account permissions page at myaccount.google.com/permissions.

6. Security

Access is limited to the operator’s own machine and accounts. Credentials are stored locally and are not transmitted anywhere other than to Google’s own authentication endpoints.

7. Children

The application is not directed at children and has no users other than its operator.

8. Changes and contact

Any change to this policy will be published on this page with an updated date. Questions: admin@terrynewman.net.