🔍

Data Handling Verification

This page explains exactly how Babots AI handles data from connected services like Google. Designed for transparency — for our users and for Google's OAuth verification reviewers.

🏗️ Zero-Copy Data Architecture

Babots AI operates a strict zero-copy data model for all connected service integrations. User data from Google APIs is fetched in real-time, processed in server memory, and never written to any database, file, cache, or persistent storage. This is not a policy — it is an architectural constraint enforced at the code level.

Data Flow — Step by Step

💬

Step 1User Requests Data

User asks their AI companion a question like "What's on my calendar today?" or the companion proactively checks based on autonomy settings.

🔐

Step 2Real-Time API Call

Babots server makes a live API call to Google using the user's encrypted OAuth token. The token is decrypted in-memory only for the duration of the request.

⚡

Step 3In-Memory Processing

API response is processed in server memory to generate a natural language summary. The raw API data exists only in the request handler's memory scope.

✨

Step 4Response Delivered

The AI companion delivers a formatted response to the user. At this point, the raw Google API data has already been garbage-collected from memory.

📋

Step 5Audit Entry Created

A tamper-evident audit log entry records: what data type was accessed, which API endpoint was called, how many records were returned, and confirms data_persisted = false.

📦 What We Store vs. What We Don't

✓ Stored (Required for Operation)

•Encrypted OAuth refresh token (AES-256-GCM)
•List of granted scopes
•Autonomy level preference (read-only / drafting / autonomous)
•Audit log entries (what was accessed, when, hash proof)

✗ Never Stored (Zero-Copy)

•Calendar events or event details
•Email content, subjects, or sender information
•Task lists or task content
•Contact names, emails, or phone numbers
•YouTube watch history or subscriptions
•Any raw API response data from Google

🔑 OAuth Scopes & Justifications

All scopes are read-only. Babots AI never requests write access to Google services unless a user explicitly upgrades their autonomy level (which is disabled by default).

📅Google Calendar (Read Only)calendar.readonly

View upcoming calendar events so your AI companion can provide contextual reminders and scheduling awareness. Events are fetched in real-time and never stored.

📧Gmail (Read Only)gmail.readonly

View email metadata (subject, sender, date) so your AI companion can summarize your inbox. Email content is processed in-memory and immediately discarded.

✅Google Tasks (Read Only)tasks.readonly

View your task lists so your AI companion can help you stay organized. Task data is fetched on-demand and never persisted.

👤Google Contacts (Read Only)contacts.readonly

View contact names and emails so your AI companion can help you find and reference people. Contact data is never stored in our database.

▶️YouTube (Read Only)youtube.readonly

View your YouTube subscriptions and watch history so your AI companion can recommend content aligned with your interests. Viewing data is processed in real-time only.

🔗 Tamper-Evident Audit Log

Every data access creates an immutable audit entry linked in a SHA-256 hash chain. Each entry's hash is computed from the previous entry's hash plus the current entry's metadata, forming a blockchain-like chain that proves no entries have been deleted or modified.

Hash Chain Structure

Entry 1:SHA-256(GENESIS + userId + calendar + fetch + t₁)→ hash_A

↓ linked

Entry 2:SHA-256(hash_A + userId + email + fetch + t₂)→ hash_B

↓ linked

Entry 3:SHA-256(hash_B + userId + tasks + fetch + t₃)→ hash_C

If any entry is deleted or modified, re-computing the chain produces different hashes — instantly detectable.

User Verification

Users can verify their audit chain integrity and download a complete data access receipt (JSON) at any time from their Integrations settings page. The receipt includes every data access, the hash proof for each entry, and a zero-copy policy declaration — all independently verifiable.

⚙️ User Controls

Connect / Disconnect

Users connect Google from the Integrations page via standard OAuth 2.0. Disconnecting revokes the token at Google's revocation endpoint and deletes the encrypted token from our database. No further API calls are possible after disconnection.

Autonomy Levels

Level 1 (Read-Only): Companion can view data when you ask. Level 2 (Drafting): Companion can prepare actions for your approval. Level 3 (Autonomous): Companion can act independently within boundaries. Default is Level 1.

Audit Trail Access

Users can view every data access their companion made, verify the hash chain integrity with one click, and download a complete audit receipt as a JSON document for independent verification.

📜 Google API Services Compliance

Babots AI's use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements:

✓We only use Google data to provide and improve user-facing features visible to the user
✓We do not use Google data for advertising or ad targeting
✓We do not allow humans to read Google user data unless the user explicitly requests it, it is necessary for security purposes, or it is required by law
✓We do not transfer Google user data to third parties (except as necessary for providing the service, with user consent, or as required by law)
✓Google user data is never persisted — our zero-copy architecture ensures data exists only in memory during processing

Babots.ai

Your AI. Your Memory. Absolute Freedom.