Information & permissions
Privacy
How the personal assistant uses information, and the choices you control.
Last updated 17 November 2026
Who operates Aoife OpenClaw
Aoife OpenClaw is a private, personal-use assistant operated by Mark solely for his own use. It is not a public sign-up service. This policy explains the assistant’s use of Google account data and how this information website differs from the assistant.
Google data the assistant accesses
With your Google authorisation, the assistant can access your Google account identity, selected email headers, message bodies and attachments, and Calendar information such as event titles, descriptions, dates, times, locations and attendees. Its existing permissions include Gmail modification and settings access, Calendar read access and event creation or modification. The assistant uses those permissions for the purposes described here and follows your instructions and standing authorisations; a permission is not blanket permission to take every action it technically allows.
Why the data is used
Data supports email review and organisation, summaries and action preparation, Calendar review, preparation and reminders, and Calendar changes you authorise. The assistant can keep identifiers, selected content, summaries, action state and receipts to maintain continuity and track authorised work. This website does not request additional Google access.
Processing and service providers
The assistant runs on an operator-controlled computer. It currently uses OpenAI Codex, signed in through a ChatGPT account, to process relevant Gmail and Calendar tool results, selected content, conversation context and derived summaries. This content can therefore be sent to OpenAI; processing is not exclusively on-device. OpenAI’s applicable ChatGPT and Codex terms and account controls govern its handling of that content.
The operator uses ChatGPT Pro and has confirmed that “Improve the model for everyone” is off. OpenAI states that this preference applies to Codex and excludes new conversations and tasks from model training. Voluntarily submitted response feedback can still make the associated conversation eligible for training, so feedback containing Google data must not be submitted. The opt-out does not mean zero retention or no human access: OpenAI permits limited authorised access for security, support or troubleshooting, and legal purposes.
Memory-search embeddings are generated locally to help retrieve saved information. This local retrieval step does not send memory text to a hosted embedding service, but the assistant’s reasoning still uses OpenAI.
Google supplies Gmail and Calendar through the authorised connection. Telegram carries private assistant messages and notifications, which can include email and Calendar information or derived summaries. Cloudflare hosts this separate information website. Each external service handles the information it receives under its applicable terms and controls.
Optional event preparation can use public sources and public event, venue or location search terms. This is not permission to send raw private email or full event descriptions to public search services.
Authorisation credentials
Google access is authorised through OAuth and managed using gog. The assistant does not need your Google password. OAuth access and refresh tokens are credentials used to maintain authorised access; they are separate from retained email content, summaries and action records. This website has no Google sign-in, OAuth callback or facility for receiving those credentials or your mailbox and Calendar content.
Saved records, retention and deletion
Saved records include message and event identifiers, email headers and labels, selected Calendar details and exports, summaries, deadlines, plans, review decisions, action state and delivery or action receipts. Conversation and tool-result histories, memory files, databases and retrieval indexes, diagnostic logs, archives and local backup copies can also be retained. Selected email bodies or event descriptions read by the assistant can enter those histories even where its operational tables do not save the raw content.
There is currently no single verified automatic retention or deletion period across these records and copies. Completing or dismissing an action, removing a saved plan, archiving a conversation or disconnecting Google access does not by itself erase all associated records.
Contact the operator to request deletion. Requests require individual review of their scope and the available local, messaging, provider and backup deletion controls. There is no automatic account-wide erasure service or guaranteed deletion deadline. The operator will need to explain what can be removed and any copies or limits that remain; immediate deletion of every copy is not guaranteed.
Deleting assistant records does not itself delete the original email or Calendar events held by Google. Copies held by OpenAI, Telegram or other service providers are also subject to their applicable retention and deletion processes. No fixed provider retention period or zero-retention guarantee is offered here.
Your choices and revoking access
You can ask the operator to stop using the assistant or remove saved records. You can separately revoke the assistant’s Google access in your Google Account’s third-party connections settings. Revocation prevents future use of the revoked authorisation, but does not recall data already processed, erase messages already delivered or automatically remove retained assistant records. Do not send passwords, OAuth tokens or sensitive message contents with a support request.
This website and hosting information
The site consists of static information pages. Its own code includes no account system, contact form, analytics, advertising, tracking pixels or third-party fonts, and sets no cookies or browser storage. Cloudflare necessarily handles website requests and may process connection information, such as IP addresses, requested URLs, request times and browser details, to deliver and protect the site. Host-level security features can have their own cookie behaviour. Visiting these pages does not give this website access to your Google account.
Google data requirements
Google’s API Services User Data Policy, including its Limited Use requirements where applicable, governs use of Google user data. Authorising Google access does not authorise unrelated uses of that data. Read the Google policy using the link below.
Contact and policy updates
For privacy questions, saved-record deletion requests or support, email aoife.operator@gmail.com. This policy may be updated when the assistant’s actual practices change. The date at the top identifies this version.