Privacy for QTIS Calendar
How Agentivex handles information through the QTIS Calendar connector.
Scope and responsibility
This notice covers the QTIS Calendar connector, its public documentation pages and related support. It does not describe every feature of QTIS or Muse. Your practice or organization determines how its scheduling records are used and retained. Agentivex operates this connector to provide that authorized service. Contact QTIS support for privacy requests.
Information processed
The connector verifies OAuth account identity, authorized client and scopes, then checks current QTIS tenant membership and role permissions. It processes selected tenant and scheduling identifiers, appointment titles, times, status, provider/location/room assignments, and the participant names and IDs needed for booking. Appointment titles and names can contain personal information.
Tool responses exclude clinical notes, patient phone numbers and email addresses, and billing data. Please keep clinical details out of appointment titles, support messages and request keys. Use random request keys.
Purposes and providers
Information is used to fulfill requested scheduling actions, enforce permissions, prevent duplicate operations, maintain audit history, troubleshoot failures and protect the service. The connector does not use calendar data for advertising or model training.
Auth0 provides authentication; Vercel and Convex provide application hosting, backend processing and storage. Muse processes information under its own terms and privacy notice when you choose to use it. Necessary information is shared with these service providers to operate the connection. We do not sell connector data.
Storage and retention
Normal appointments and audit records follow your organization's QTIS record-retention requirements and service arrangements. Cancellation preserves the appointment record. OAuth credentials stored by Muse are governed by its credential-handling process; booking receipts never contain bearer or refresh tokens. QTIS stores hashed connection credentials and limited account, client, scope and expiry metadata for up to 30 days plus hourly cleanup. Spent refresh hashes remain until their connection’s absolute expiry to detect reuse; expired records are removed automatically. Revoked connections cannot be used, and verified deletion requests can address retained control metadata.
Operation receipts support safe retries for up to 30 days. We can redact their booking payloads earlier for a verified disconnect or deletion request. Their booking arguments and response payloads are then automatically redacted, with cleanup scheduled hourly. Limited account/client/request identifiers and a redaction marker remain to prevent an expired request key from executing again. These control records can be addressed through verified account or organization deletion requests, subject to necessary record-retention obligations.
Security and access
Requests use HTTPS. QTIS validates the scoped connection credential, its resource, registered client, expiry, revocation status, scopes and current staff permissions. Only hashes of calendar authorization codes and access/refresh credentials are stored; plaintext credentials are returned only to the authorized client during exchange. Access is limited to authorized tenants. The MCP application avoids logging tokens and returns sanitized errors. Dynamic client registrations contain application names, allowed scopes, exact callback URLs and authentication settings; confidential client secrets are stored only as hashes. Unused registrations are removed after 30 days plus hourly cleanup; registrations used with consent are retained to operate the connection and can be addressed through verified deletion requests. Registration abuse controls store short-lived keyed source hashes and counts, not raw IP addresses; these records expire within 25 hours plus hourly cleanup. Hosting systems may process operational request metadata for availability and security. These safeguards do not make any online service risk-free.
Your choices and requests
You can choose read-only access where Muse offers it, disconnect the connector, and ask your QTIS administrator to remove access. Removing QTIS permissions blocks subsequent tool execution. Revoking a calendar connection immediately blocks its access and refresh credentials. Muse should clear stored credentials on disconnect.
For access, correction, deletion, retention questions or a privacy concern, contact QTIS support. Identify the organization and request, but do not send passwords, tokens or clinical records. We verify authority before acting and coordinate with the relevant organization and applicable retention requirements.
Public pages and updates
These connector information pages do not set application cookies or load analytics scripts. Hosting systems may retain ordinary security and request logs. Other QTIS pages and Muse may have separate cookie practices. We will update this notice as the connector changes and display the revision date above.