Operator and scope
Hamilton Behavioral MD, PA operates this staff service. This policy covers Google sign-in, authorized operational information, and the connected HB Ops calendar brief. It does not replace the practice’s notice of privacy practices or govern clinical records held in separate systems.
Information we access and why
Google sign-in provides account information such as name, email address, and profile image. Account identity, organization membership, and assigned role determine application access. Session cookies support sign-in. The intranet also reads information in Google Sheets made available to its configured service account, subject to application permissions.
The HB Ops calendar workflow reads the designated operations calendar for the day. The brief includes event titles and times. Calendar API responses may also contain descriptions, participants, locations, and meeting links; execution history may retain these response fields even when they are not included in the brief.
The current Calendar consent request includes viewing and editing events and seeing, editing, sharing, and deleting accessible calendars. This is broader than the daily brief requires. The daily brief reads events; it does not modify or delete calendars. Google authorization does not grant another person access to the intranet.
We use this information to provide requested staff functions, prepare administrative briefs, enforce access decisions, troubleshoot failures, and investigate unauthorized activity. Technical logs may include account identifiers, timestamps, routes, tool activity, results, and error details.
Processing and service providers
Google provides identity, Calendar, and Sheets services. Vercel hosts the intranet. The documented calendar-brief path uses n8n hosted on Hostinger, a local brief generator using Anthropic’s Claude service, and Telegram for delivery to the configured chat. Calendar text is supplied to Claude to compose the brief; the resulting brief is saved locally and sent to Telegram.
Optional AI features, when enabled by an administrator, can also send submitted prompts and authorized summaries to a configured provider such as OpenAI. Provider processing and retention depend on the applicable account settings and service terms. Users should submit only information approved for that feature.
We do not sell Google user data, use it for advertising or credit decisions, or use it to train our own generalized AI models. Our use and transfer to other apps of information received from Google APIs will comply with the Google API Services User Data Policy, including its Limited Use requirements. Human access to Google user data is limited to cases those requirements permit. Disclosure required by law is handled through the applicable legal process.
Storage and retention
Information may remain in Google source records, application caches and hosting logs, n8n execution records, local brief files, AI service records, and Telegram messages. The calendar workflow is configured to save successful, failed, and manual executions. Local briefs are saved by date; the current brief generator does not automatically delete them. Telegram copies remain until removed through the applicable chat controls.
Source records remain under the source account’s retention and deletion controls. Caches can refresh independently of source deletion. Hosting, automation, AI, and backup retention depend on their configured settings and provider terms; there is no single automatic deletion period for every copy. Administrators retain information to support operational records, troubleshooting, security, and applicable obligations, and review deletion requests with those purposes in mind.
Access choices and deletion requests
You can revoke Google authorization at Google Account connections. Revocation prevents future access under that grant but does not automatically delete copies already saved, generated, or delivered. Revoking a personal grant does not remove records separately shared with a service account.
Send access, correction, or deletion requests to hamiltonbehavioral@gmail.com. Identify the account and connected feature without including patient information or passwords. We may verify identity and authority, clarify the requested records, and explain any operational or legal reason for retaining information. Copies in a recipient’s account or backups may require separate handling.
Security and sensitive information
The intranet uses Google sign-in and application access controls for protected staff functions. No system can guarantee absolute security. The public information pages do not provide access to staff dashboards or source records.
The HB Ops calendar brief is intended only for non-patient administrative information. Do not enter patient names, clinical notes, intake details, billing information, or credentials into that calendar or brief. This policy does not authorize clinical processing or establish a business associate agreement.
Changes and contact
We will disclose new uses of Google user data before they begin and obtain renewed authorization where required. The effective date identifies this version. Questions and privacy requests can be sent to hamiltonbehavioral@gmail.com.