Brain Gatekeeper
Privacy policy
Operator and purpose
Brain Gatekeeper is operated by the individual who configures the Google project, private server and assistant, for their own personal account. Its purpose is personal calendar and task assistance and a private notes copy. It is not offered as a public account service.
The first stage exposes reading commands only. It does not create, change, move, complete or delete calendar events or tasks. Gmail and Google Drive API access are not connected in this stage. Google permissions are displayed during authorization; later access or new uses require updated disclosures and any necessary renewed authorization before activation.
Google information accessed
Google sign-in provides account identity information, including an account identifier and email address. The integration uses and stores the connected email address to identify the owner's account. It also stores authorization tokens, granted permission names, expiry information and the sign-in time.
When authorized, the gatekeeper retrieves event records from the primary Google Calendar. Information can include event identifiers, titles, descriptions, dates and times, locations, recurrence information, and invitation details. Calendar records may contain information about other people, such as an organizer's email address.
The gatekeeper also retrieves Google Tasks list and open-task records. Information can include list names and identifiers, task identifiers, titles, notes, due dates, links and subtask relationships. Completed or deleted tasks are excluded from the current notes copy, but earlier saved versions can remain in history.
How the information is used
Calendar and task information is used to answer the owner's personal scheduling and to-do questions. Open tasks are copied into a private Markdown notes vault so the owner can also read them on their laptop. Relevant information may appear in assistant conversations, generated notes or memories, and replies sent through Telegram.
Brain Gatekeeper's use and transfer of information received from Google APIs will adhere to the Google API Services User Data Policy, including its Limited Use requirements. The operator uses Google data for the disclosed personal-assistance and private-notes features, not for sale, advertising, credit decisions, or training or improving generalized AI models. Service configurations and provider arrangements must remain consistent with those restrictions.
Services that process information
When the assistant uses calendar or task content to answer a request, relevant content may be sent to OpenRouter and the provider serving the selected AI model. Telegram processes messages delivered through its service. GitHub stores the synchronized private notes and their version history; the owner's laptop holds a local Obsidian copy. Hostinger hosts the private server. Voice messages sent for transcription are processed by Groq.
These services process information for their respective functions under their applicable policies. The integration does not promise that every provider retains no data. The operator must use configurations and providers appropriate for the disclosed purposes and Google's requirements.
Storage and protection
Google access and refresh tokens are stored on the private server in files restricted to a separate gatekeeper operating-system account and administrators. The assistant uses the gatekeeper's fixed commands rather than receiving the token files. The current gatekeeper program does not itself encrypt these token files at rest.
The gatekeeper keeps a small operational log of commands, timestamps and outcomes. Other components may retain assistant histories, memories, notes and messages. Private notes and selected assistant memories are synchronized through a private GitHub repository. No Google credentials or personal calendar or task records are published on this information website.
Retention and removal
Tokens remain until sign-out or removal. Notes, conversation records, memories, repository history and messages remain until separately removed. The current scripts do not apply a fixed time-based deletion period to all those records.
The owner can disconnect Brain Gatekeeper in their Google Account's third-party connections or use the integration's administrator sign-out command. The administrator command deletes the local token file and attempts to revoke access at Google. If Google cannot be reached, the owner should also remove access directly in their Google Account.
Disconnecting stops future authorized retrieval; it does not erase previous notes, Git versions, chats, Telegram messages, device copies or any existing backups. Removing a task from the current copy does not remove its older Git versions. Deletion requires separate cleanup of the relevant locations and any applicable provider-held copies.
This public website
Cloudflare Pages hosts only these static information pages. They have no backend, forms, assistant access, Google OAuth callback or connection to the private server. The page files contain no analytics scripts, advertising code or application cookies.
The hosting provider may process ordinary visitor request information, such as an IP address and browser details, to deliver and secure the website, under its privacy policy. Public website hosting does not give it the integration's Google tokens or private notes.
Contact and policy changes
For support, privacy questions or deletion requests, use the user-support email displayed on the Google authorization screen for Brain Gatekeeper. The operator must update this policy and obtain any required consent before enabling materially different access or uses.
This page explains the integration's data practices. It does not claim that Google has verified or endorsed the app.