Privacy policy

How the website and private email assistant access, use and store data.

01

Scope and contact

This policy covers ivandimoski.com and Gmail for Codex, Ivan Dimoski’s private email assistant. Ivan Dimoski in Stockholm, Sweden is responsible for this integration. Contact dimoski.ivan@gmail.com for questions about email data or this policy. Last updated: 5 October 2026.

02

Google account access

You connect each account through Google OAuth. The integration does not request your Google password. It requests gmail.readonly to search and read messages and threads, and gmail.send to send email on your instructions. Read access can include senders, recipients, subjects, message bodies, labels and attachments when requested. Send access includes recipients, subjects, message bodies and attachments supplied for a message.

03

Purpose and AI processing

The assistant uses this data to find messages, explain or summarise email, prepare replies and send messages that you request. The Gmail tool runs on your computer. Email content returned by the tool can be sent to the AI service that runs your agent, including OpenAI when you use Codex. This means that processing is not limited to your computer. Only connect accounts and use AI services that you are allowed to use for that data.

04

Storage, sharing and retention

OAuth credentials are stored locally; access and refresh tokens use macOS Keychain in the configured setup. Messages remain in Gmail. The integration does not maintain a separate hosted mailbox database. Tool output, email excerpts and generated replies can remain in local logs or agent conversation history. AI services and hosting providers process data under their own terms and retention rules. Check their settings before use. Delete local logs and conversations when you no longer need them; use the provider’s controls to remove stored history. Removing this integration does not delete messages from Gmail or copies already sent to recipients.

05

Limited Use

The integration’s use and transfer of information received from Google APIs will comply with the Google API Services User Data Policy and the Google Workspace API User Data and Developer Policy, including their Limited Use requirements. Google user data is not sold or used for advertising. It must not be used to develop, improve or train general-purpose AI or machine-learning models. Use AI providers and account settings that meet this requirement. Data is shared only as needed for the email features you request, security, legal obligations or a permitted transfer under those policies. Human access is limited to your consent, security investigations, legal requirements or other uses permitted by those policies.

06

Remove access and request help

You can stop use at any time. Remove the app in your Google Account’s third-party connections and remove the saved account credentials from the local Gmail tool. Revocation stops future access but does not remove existing chat history, logs or sent messages. For access, correction, deletion or other privacy requests, contact dimoski.ivan@gmail.com. Rights that apply under data protection law remain available.

07

Website and changes

This website does not set analytics or advertising cookies. Hosting and network providers can process technical request data, such as IP addresses, to deliver and protect the site. Links to other services are subject to their policies. Changes to this policy will appear on this page with an updated date.

Contact

Have a project in mind?

Email me or connect on LinkedIn to discuss how we can work together.