Your information
Privacy policy
Last updated:
Agentic Integrations is a private, non-commercial assistant integration for its owner’s personal Google accounts. It is operated solely for personal use, not as a professional service or business venture. It is not a general-purpose application offered to the public, and it has no public registration.
Who may use the integration
Only people explicitly approved by the operator may use the assistant. Each connected account must be individually authorized by its account holder. Connected-account data is processed to carry out tasks authorized by an approved user; visiting this website does not connect an account or give the assistant access to visitor data.
Authorized mail and calendar content can include information about other people, such as message senders, recipients, and event attendees. The private nature of this tool does not mean that all processed information is solely about the person using it. The data-handling practices below apply to that content as well.
What information is accessed
Access is granted separately for each connected Google account. Depending on the task and permissions granted, the integration can access:
- Account identity: the email address and account identifiers needed to select the correct connected account.
- Gmail: message contents and metadata, recipients, attachments when needed, drafts, labels, filters, and basic mailbox settings.
- Calendar: calendars, availability, event titles, descriptions, times, locations, and organizer and attendee information.
- Assistant activity: requests, replies, retrieved task content, and records of actions or errors.
Google authorization tokens are retained so the integration can continue working without a new sign-in for each request. The integration does not ask you to give it your Google password.
How information is used
Information is used to carry out requested mail and scheduling tasks, such as searching and summarizing messages, preparing or sending replies, organizing mail, managing filters, checking availability, and creating, editing, or deleting calendar events. Task history can provide context for subsequent requests and help diagnose failures.
We do not sell Google account data or use it for advertising. Use and transfer of information received from Google APIs is governed by the Google API Services User Data Policy, including its Limited Use requirements.
AI processing and other services
The assistant uses OpenAI or Anthropic, depending on the selected model. Relevant requests, retrieved mail or calendar content, and task results may be transmitted to that provider for processing. Data does not remain exclusively on the operator’s computer. Provider processing and retention depend on the applicable account settings and service terms.
Google handles account authorization and the connected mail and calendar services. Apple handles messages and replies delivered through iMessage; those replies may include information requested from a connected account. When you request sending an email, sharing information, or inviting an event attendee, that action discloses the relevant information to the recipients you specify.
The operator can access records in the private service environment. Google data is not made available for unrelated human review; access is limited to the account holder’s authorized purposes and the security or legal exceptions allowed by Google’s policy.
Storage and retention
Authorization credentials, conversation history, task outputs, and diagnostic records are stored in the operator-managed environment with access restricted to the service’s macOS account. Google credentials use an encrypted local store. The assistant processes running under that account can use those credentials and access stored information.
There is currently no fixed automatic deletion period for local conversation history, task outputs, logs, or backups. Records can remain until the operator removes them. Removing an integration or revoking Google access does not automatically delete previously stored records or copies held by other service providers.
Revoking access and requesting deletion
You can disconnect the integration using your Google Account’s third-party connections settings. Revoking access stops future access using that authorization; it does not delete messages or events already in your Google account.
Contact clu@heckman.io to request removal of stored authorization credentials and retained local data, including relevant backups. Identify the connected account and what you want removed, but do not send passwords or tokens. Requests are handled by the operator, who may need to verify account ownership.
For copies held by Google, Apple, OpenAI, or Anthropic, the relevant provider’s account controls and retention policies also apply. Deletion requests for this integration do not independently erase those providers’ records.
This public website
This site contains informational pages only. It has no sign-in form, analytics scripts, tracking cookies, or access to your mailbox or calendar. GitHub Pages hosts the site and may process visitor connection information, including IP addresses, under the GitHub Privacy Statement.
Policy changes
This page will be updated when the integration’s data practices change. Material new uses of Google account data require updated disclosures and consent before the new use begins.
Support and privacy contact: clu@heckman.io