Your Google data
in Trinity
This detailed Google data notice supplements the PersonaKit privacy policy for the optional Gmail and Google Calendar connection in Trinity's private chat pilot.
Last updated: October 11, 2026.
Data accessed and purpose
After you connect a Google account, Trinity can access its email address, Gmail message metadata and contents, and primary Calendar events. It uses these data only to answer your requests to search or read mail, send a message, organize selected messages when that account has granted Gmail modify access, list events, or create and delete events. Available actions depend on the permissions actually granted to that account. Sending mail, organizing messages, and changing events require an additional action approval. Trinity does not access an account merely because another person connected theirs.
Where data goes
Google provides the requested data to Trinity, which runs on systems operated by PersonaKit. Relevant content is sent to the AI model provider configured for your Trinity profile, to prepare the response you requested. Depending on how your profile is set up, that is OpenAI, through Codex where that is allowed, or OpenRouter, which passes the request to the model provider that serves it. If Trinity moves to another provider, we name it in this notice before it handles your data. Private chat messages and Trinity's replies are delivered through the messaging service you use with Trinity, currently WhatsApp or Telegram. Google, the AI model provider, the messaging service, and PersonaKit's infrastructure providers have separate infrastructure and retention practices. We do not sell Google user data, use it for advertising, or use it to train our own models.
The sign-in relay on Cloudflare temporarily stores the Google authorization URL and a short-lived authorization code. It does not receive mailbox or Calendar content, access tokens, refresh tokens, or the identity of your chat profile. The authorization link expires after ten minutes; an unclaimed code expires after at most five minutes.
Storage and separation
Trinity stores each connected account's refresh token on systems operated by PersonaKit, separately for each person's profile and, within it, for each account. Each person has a separate Trinity profile. The integration rejects a Google account already connected to another profile and does not share one profile's token with another. The assistant's conversation history, local logs, or memory for that profile may contain mail or event details it used to answer you.
Retention and deletion
Connection credentials stay in that profile until the connection is removed or Google revokes them. Revoking Trinity in your Google Account also invalidates the connection. A result already sent through a chat service or to an AI provider cannot be recalled from those services by deleting Trinity's copy.
You can disconnect at any time by revoking Trinity in your Google Account's third-party connection settings; that stops Trinity from requesting new access. To also have the stored credential and your Trinity profile data deleted, email trinity-support@personakit.me. Copies already held by your chat service or an AI provider follow their own practices.
Your choices and contact
Connecting Google is optional. You can choose which of your own accounts to connect and which account to use for each request. If you do not grant all requested Google permissions, this combined Mail and Calendar connection will not be completed. For questions about this integration, contact trinity-support@personakit.me.
PersonaKit's use of information received from Google APIs is limited to the user-facing features described here and follows the Google API Services User Data Policy, including its Limited Use requirements.