Keyboard shortcuts

Press ← or → to navigate between chapters

Press S or / to search in the book

Press ? to show this help

Press Esc to hide this help

Data Privacy & Model Sovereignty

Data protection and regulatory compliance are integral to the system architecture. Enterprise data processed by the assistant remains under the strict control of the customer organization.

1. Google API Services User Data Policy Compliance

The assistant complies strictly with the Google API Services User Data Policy, including the Limited Use requirements:

RequirementImplementation Safeguard
Limited PurposeData accessed through Workspace APIs is used solely to provide user-facing assistant features explicitly requested by the client organization.
Zero Advertising TransferData is never sold, leased, or transferred to third-party data brokers, advertising networks, or information resellers.
Human InaccessibilityHumans never inspect user data unless authorized by the tenant administrator to resolve a critical security incident.
Zero Model RetrainingGoogle Workspace data is never used to train generalized artificial intelligence or machine learning models.

2. Zero AI Model Retraining & Sovereign Processing

graph LR
    subgraph EnterprisePerimeter [Client Security Perimeter]
        DataIn[Inbound Communications: Email, Chat, Audio]
        Core[Cognitive Assistant Core]
    end

    subgraph LLMInference [Enterprise AI Inference Endpoint]
        InferenceEngine[Private Model Runtime]
        Weights[(Model Weights: Static Freeze)]
    end

    DataIn --> Core
    Core -->|Stateless Prompt Context| InferenceEngine
    InferenceEngine -.->|Zero Weight Update| Weights
    InferenceEngine -->|Ephemeral Response| Core
  • Stateless Inference: Text prompts and context windows sent to language model inference endpoints are processed statelessly.
  • Strict Prohibition on Model Fine-Tuning: Client communications, meeting transcripts, channel conversations, and indexed corporate documents are never retained by model providers for training, retraining, or model tuning.
  • Contractual Zero-Retention: Inference integrations utilize enterprise endpoints configured with zero data logging and zero retention agreements.

3. Data Sovereignty & Retention Invariants

  1. Dedicated Client Projects: Compute resources, Pub/Sub topics, Secret Manager secrets, and Firestore document databases reside in a dedicated Google Cloud project assigned strictly to the tenant organization.
  2. Zero Cross-Tenant Leakage: Infrastructure components are not shared across clients. No database table or messaging topic contains data from multiple tenants.
  3. Transient Memory: Short-term conversational context is retained only in volatile container memory during an active session and discarded upon session close.
  4. On-Demand Data Erasure: Tenant administrators hold full authorization to trigger immediate data deletion across all project storage buckets, Firestore documents, and local caches.