Privacy Policy

Dipo Chief of Staff – Gmail Integration · Effective 26 September 2026

Who this applies to

This integration is used only by its owner, Dipo, for his own Gmail accounts. It is not offered to the public. It only accepts an authorisation from a Google account it has been configured to expect.

What Google data is accessed

• The integration requests one Google permission: read-only Gmail access (https://www.googleapis.com/auth/gmail.readonly).
• It retrieves message metadata only: the From, To, Cc, Bcc, Subject, Date, Message-ID, In-Reply-To and References headers; Gmail message, thread and label identifiers; and the mailbox's email address and message counts.
• It does not retrieve message bodies or attachments.
• It does not send, delete, modify or label email.

How it is used

The metadata is used only for the owner's personal "Chief of Staff" email monitoring: helping him see and prioritise messages that need his attention across his own accounts.

Email metadata may be processed or reviewed using AI assistant tools as part of the owner's personal Chief of Staff workflow. These tools are used to help identify, organise, summarise and prioritise information requiring the owner's attention. When this happens, the metadata being reviewed is sent to the provider of the AI assistant tool so that the tool can process it.

Account identity and authorisation

• Each Google account is authorised separately and has its own authorisation token.
• When an account is authorised, the signed-in email address is checked against the address that account is configured for. If they do not match, the authorisation is discarded and nothing is saved.
• The same check is repeated before every retrieval.

Where the data is kept

• Authorisation tokens are saved as files on the owner's own computer, in a folder separate from his working files.
• Retrieved metadata is written to files in the owner's personal working folder on his own computer.
• The integration itself does not delete these files; they remain until the owner removes them.

Sharing

• Apart from processing by AI assistant tools as described above, the data is not shared with anyone.
• The data is not sold and is not used for advertising.

Google API Services User Data Policy

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

Revoking access

Access for any account can be revoked at any time at myaccount.google.com/permissions.