Privacy — TTMNG Pharmaceutical assist

Privacy notice

Data processing for TTMNG Pharmaceutical assist.

Service provider and data controller: Kamollard Chivasatvetchakul (Thai traditional medicine practitioner)
Publisher status: Individual publisher
Privacy, security, and support contact: chivasat.clinic@gmail.com
Initial service region: Thailand
Effective date of the source notice: August 27, 2026

General users authenticate with Google through Firebase Authentication and require owner approval before using the Plugin. The OpenAI reviewer uses a separately provisioned test account. Information returned by the Plugin is informational and non-regulated; it is not a diagnostic, treatment, or patient-specific dosing service.

Data processed

Firebase UID, verified email address, email hash, sign-in provider, request or access status, roles, and grant version.
OAuth data required for authorization, such as the client identifier, redirect URI, scope, request status, and session identifiers.
Hashes of pairing codes, session secrets, authorization codes, and identifiers used to investigate security events.
Technical data such as event time, event type, request identifier, MCP tool name, and hashes of rate-limit keys or target identifiers. Audit records do not store search queries or plaintext stable target IDs.

Information not to send and not stored as plaintext

Do not send passwords, MFA codes, Firebase ID tokens, OAuth authorization codes, access tokens, refresh tokens, device secrets, or session secrets through support channels. The service is designed not to store these tokens, codes, or secrets as plaintext in Firestore or audit records.

Purposes

Data is used to verify identity, record pending requests, check owner approval, issue, rotate, and revoke sessions, prevent out-of-scope use, investigate security events, and respond to support requests. The service does not sell personal data or use sign-in data for advertising.

Retention

Pairing and OAuth authorization requests: no more than 10 minutes.
Authorization codes: no more than 2 minutes and single use only.
Access or session token records: no more than 1 hour unless revoked earlier.
Refresh-token families: no more than 30 days from initial issuance; rotation does not extend the absolute expiration date.
Rate-limit records: approximately 1 minute for short-window limits and no more than 24 hours for daily call and unique-target quotas.
Firestore security-audit records containing hashed identifiers: 90 days, using an expiration field and Firestore TTL.
Google Cloud Logging bucket _Default: 30 days; bucket _Required for Google-required audit logs: 400 days, based on the project configuration that was inspected.
Pending, approved, and reviewer user records: no scheduled entitlement expiry; retained until disabled, deleted following a verified request, or retained as required by applicable obligations.
Legacy invitation records: no longer used by the runtime to authorize users and migrated to a retired state with no scheduled expiry while retained as an audit trail.

The 10-minute, 2-minute, 1-hour, and 30-day periods above are request or credential lifetimes, not account-entitlement lifetimes. The service rejects expired credentials and suspended access immediately, although physical deletion through TTL may occur asynchronously afterward.

Service providers and cross-border processing

Firebase Authentication, Firestore, and Google Cloud process data to authenticate users, store records, and operate the server. After authorization, OpenAI sends MCP requests with an access token. These providers may process data outside Thailand under their infrastructure, terms, and data-protection measures.

User requests

Users may request access, correction, deletion, restriction, or objection regarding data controlled by this service, and may request that access be disabled or sessions revoked, by contacting chivasat.clinic@gmail.com. The data controller may verify identity before acting and may retain some information where required by law or security measures.

Security and incident reporting

The service uses HTTPS, OAuth 2.1, PKCE, token rotation, hashed identifiers, deny-all Firestore client rules, MCP input/output allowlists, search/call/unique-target limits, and session revocation. These measures reduce risk but cannot guarantee that an authorized user will not retain information the service intentionally returns. If you suspect unauthorized use of an account or token, stop using it and email the address above without including any secret.

Changes to this notice

This notice may change when the service scope, providers, or retention periods change. The latest effective date will appear on this page. Material changes require review before publication.

This US English page is a translation candidate based on the Thai privacy notice. Internal US English language reviewer: Kamollard Chivasatvetchakul. Completion, independent review, and legal review have not been recorded.