Privacy policy

Last updated: 17 October 2026

This policy covers Martin’s Personal Assistant and its public information website. The assistant is operated by Martin for personal productivity, not as a public account-registration service.

Information the assistant accesses

With the account owner’s authorization, the assistant can access Google account identity information and the Google services permitted by the consent screen and its configuration:

Some permissions allow changes, including creating or updating events, tasks, spreadsheets and email drafts, or organizing email. The exact operations depend on the enabled tools and granted permissions.

Why this information is used

Information is used to answer requests, produce personal briefings and reminders, find relevant material and carry out authorized productivity tasks. Scheduled workflows can access connected services without a new sign-in for each run.

Google account passwords are not requested or stored by the assistant. OAuth credentials are stored privately on the operator’s server and are not included in this public website.

AI processing and other service providers

Relevant instructions, retrieved content and conversation context may be sent to OpenAI to produce responses or perform requested tasks. Configured messaging services can receive delivered responses, and configured storage or synchronization services can receive generated notes and records. These services process information under their own terms and data settings.

Sharing must be limited to what is needed for the assistant’s disclosed features. The operator does not sell Google user data or use it for advertising or to train generalized AI models. AI services used with Google-derived content must be configured consistently with Google’s Limited Use requirements.

The assistant’s use and transfer of information received from Google APIs must comply with the Google API Services User Data Policy, including its Limited Use requirements.

Storage, retention and access

Conversation history, retrieved information and generated outputs may be retained in private databases, logs and notes on the operator’s server. Copies may also exist in configured backups, synchronized storage or messaging history. The operator and administrators explicitly granted access can access these records.

There is no automatic deletion period promised by this policy. Records remain until removed by the operator or the relevant service’s retention process. Removing a live record does not necessarily remove every backup, version-history entry or provider-held copy immediately.

The public website has no access to these stores. It contains no assistant backend, Google sign-in flow or account data.

Revocation and deletion

To stop future Google access, remove the assistant from your Google Account connections. Revocation does not itself delete information already stored by the assistant.

Contact goettem@gmail.com to request deletion of stored credentials or assistant-held records. The operator will confirm the scope of deletion, including any backup or third-party retention limitations.

Website visitors

This static website does not request Google access, use application analytics, set application cookies or load third-party scripts. Cloudflare hosts the pages and may process technical request information, such as IP addresses and security logs, to deliver and protect the website. See Cloudflare’s privacy policy.

Information emailed to the contact address is used to respond to that correspondence.

Changes and contact

This notice will be updated when the assistant’s data practices change. Material new uses of Google information require appropriate disclosure and consent. Questions can be sent to Martin at goettem@gmail.com.