Privacy Policy

Tuesday — Personal Automation Tool · Last updated 14 September 2026

1. Who this covers

This policy describes the Tuesday personal automation tool operated by Ahmed Elbannan ("the operator", "I"). The tool has a single user — its operator — and is used against his own Google account. There are no other users.

2. What Google data the tool accesses

With the operator's own consent, the tool requests these Google API scopes. Each is used only for the purpose stated:

Scope	Purpose
Calendar	Read events to track commitments, deadlines and protected family time.
Gmail (read)	Read and search mail to surface items needing the operator's attention.
Gmail (modify)	Apply labels and mark messages read as part of triage.
Gmail (send)	Send a message only after the operator has explicitly approved that exact message and recipient.
Drive	Read and store files used in document and record work.
Contacts	Resolve who a message or calendar event concerns.
Sheets and Docs	Read and update spreadsheets and documents the operator works with.

3. What is done with it

Data is used only to perform tasks the operator asks for.
Data is never sold, rented, or shared with any third party.
Data is never used for advertising, profiling, or training machine-learning models.
Data is never used to determine creditworthiness or for any lending purpose.
No human other than the operator reads the data.

4. Where data is stored

The tool runs entirely on the operator's own computer. Calendar, mail, file and contact content is fetched on demand and processed locally; it is not copied into a database elsewhere or uploaded to a server controlled by a third party.

The OAuth credential that authorises access is stored as an encrypted-at-rest token file on that same computer. It is not transmitted anywhere except to Google's own API endpoints.

5. Sharing with AI service providers

To summarise and organise the operator's own information, selected content may be processed by the AI model that powers the assistant. That processing happens under the operator's own API accounts and is limited to what is needed for the task at hand. No client data, employee data or other people's personal information is submitted for processing.

6. Retention and deletion

Because content is fetched on demand rather than warehoused, there is no long-term store to purge. The operator can revoke the tool's access at any time at myaccount.google.com/permissions, which immediately ends all API access. Deleting the local token file removes the stored credential.

7. Limited Use disclosure

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

8. Children

This tool is not directed at children and is not used by anyone under 18.

9. Changes

Any change to this policy will be published on this page with an updated date at the top.

10. Contact

Questions about this policy or the handling of data: ahmedelbannan80@gmail.com