Privacy policy

This policy describes Annie’s private, personal-use Google Workspace integration, operated on her Mac through the Google Workspace CLI and Codex. It is not a public service and does not accept public signups.

Google data accessed

When Annie authorizes an account, the integration can access Google Drive files and metadata, Gmail messages and drafts, Calendar information and events, Google Docs, and Google Sheets. Basic Google account identity information is used to identify the connected account.

Access depends on the permissions granted during Google authorization and on the account’s own access rights. Read and write permissions support searching, reading, creating, and editing; they may also technically permit deletion even though local rules prohibit it.

How data is used

Google account data is used to carry out tasks Annie requests, such as finding a file, reading a document, preparing a draft, updating a spreadsheet, or managing a calendar event. Searches are intended to retrieve only the information needed for the task.

This integration does not sell Google user data or use it for advertising. Its use and transfer of information received from Google APIs will adhere to the Google API Services User Data Policy, including its Limited Use requirements.

Codex and AI processing

Information retrieved for a Codex task may be included in the conversation or tool results and sent to OpenAI for processing. OpenAI’s handling and retention of that information depend on the applicable product terms, account settings, and privacy policy. This integration does not promise that task content remains exclusively on the Mac.

Local storage and security

OAuth client configuration and account credentials are stored locally in separate profiles protected by filesystem permissions. The CLI uses encrypted credential storage with an operating-system keyring. Account data may also appear in local caches, task artifacts, downloaded files, or saved conversation history when required by a task.

Credentials are not published on this website. The integration does not ask Annie to provide passwords, passkeys, recovery codes, or MFA codes to Codex; those steps are handled directly with Google.

Controls and no-delete safeguards

Local wrappers and instructions block deletion and trashing and require approval for consequential actions, including sending email, changing sharing, editing important documents, and changing calendar events. These controls are not Google-enforced restrictions and cannot guarantee protection against every destructive content edit.

Retention and revoking access

Local credentials remain until removed or revoked. Saved files, caches, and task history can persist until cleared using the relevant application or account controls; there is no automatic retention period promised by this integration.

Annie can revoke the app’s access in Google Account third-party connections. Revocation stops future authorized access but does not automatically remove previously saved task content or files. OpenAI conversation and data controls apply separately.

This information website

These pages do not contain account-login forms, advertising, or application analytics scripts. The hosting provider may process ordinary request information, such as IP addresses and browser details, to serve and secure the website. Google account contents and OAuth credentials are not sent to the website.

Contact and changes

For questions, contact annietsai.design@gmail.com. This policy will be updated if the integration’s actual data practices change.