1. Information We Access & Process

When you authorize a migration job in CloudBridge™, we access only the minimum data required to fulfill your explicit migration instructions: (a) basic account profile information (email address and display name via userinfo.email, openid, and profile) to verify your Source and Destination account pairing; (b) Drive/OneDrive file and folder metadata, permissions, and binary file streams for the drives or folders you select in Stage 2; and (c) optional Workspace/M365 workloads (Contacts, Calendar events, Tasks, and Email Signatures) only when you explicitly select those modules.

Exclusion of Email Messages: CloudBridge™ does NOT read, access, process, store, or migrate email messages or mailbox archives (including Gmail or Outlook inbox, sent, or draft folders). Authentication utilizes only basic profile identity (email address for pairing verification).

2. Zero Persistent File Storage (Streamed Transfer Architecture)

CloudBridge™ is engineered on a transient, streamed transfer architecture. During Stage 4 execution, file binary contents are streamed directly from the Source Cloud API to the Destination Cloud API in volatile memory chunks. CloudBridge™ never stores persistent copies of your documents, spreadsheets, presentations, PDFs, or media files on server disks.

3. OAuth 2.0 Token Security & Automatic Deletion

OAuth 2.0 access and refresh tokens are stored in a protected, non-web-accessible server directory with strict 0600 file permissions solely for the duration of your active migration job so background workers can complete large transfers safely. Tokens are immediately revoked and permanently purged from disk when you click Disconnect Accounts in the header or Stage 1, or upon completing Stage 6 Final Sign-Off.

4. Audit Logs & Metadata Retention

To provide forensic accountability, CloudBridge™ records job progress events, item counts, source-to-destination object ID mappings, and cryptographic SHA-256 inventory digests in an isolated job ledger. This metadata is used exclusively to generate your downloadable Pre-Migration Discovery Report (.xlsx), Post-Migration Parity Audit Report, and Stage 6 Completion Certificate.

5. Data Protection, TLS Encryption & User Rights

All communications between your browser, CloudBridge™ servers, Google APIs, and Microsoft Graph APIs are encrypted in transit using TLS 1.3. Each workspace session is strictly isolated. You may revoke access at any time via the in-app Disconnect Accounts button, through your Google Account Security Permissions page, or by contacting our Data Protection Officer at support@technodoc.in for immediate purge of all job audit logs.

1. Account Authorization & Ownership Consent

By connecting Source and Destination Google Workspace or Microsoft 365 accounts via OAuth 2.0, you represent and warrant that you are the authorized account holder or delegated IT administrator for both accounts and possess full legal authority to copy, transfer, and provision the selected data across tenants.

2. Pre-Migration Discovery Report & Cryptographic SHA-256 Acceptance Gate

Prior to transferring any files, CloudBridge™ scans the selected Source scope and generates a comprehensive Pre-Migration Discovery Report bound to a cryptographic SHA-256 digest. In Stage 3 (Client Review & Acceptance), you must review the scope summary and explicitly record your acceptance of both these Terms (v1) and the Pre-Migration Report SHA-256 digest before Stage 4 execution is unlocked.

3. Non-Destructive Copy Mode vs. Explicit Move Mode

Copy Mode (Default & M2G Mandatory): Operates strictly in non-destructive read-only mode on the source account. Files, folders, permissions, Contacts, Calendars, Tasks, and Email Signatures are duplicated onto the destination with 100% data fidelity. The Source account remains completely untouched. For Microsoft 365 ➔ Google Workspace (M2G), Copy Mode is mandatory and Move mode is disabled.
Move Mode (Optional Administrative Operation): Available for supported directions (G2G, G2M, M2M) when explicitly confirmed by an administrator. In Move mode, source deletion only occurs after cryptographic destination receipt verification, guaranteeing zero data loss.

4. Cloud Provider API Quotas, Rate Limits & Resumability

All migrations operate within upstream cloud provider API limits, including Google Drive's 750 GB/day per-user upload quota and Microsoft Graph throttling policies. CloudBridge™ automatically manages rate limits using adaptive exponential backoff and lock-safe checkpointing so large multi-day migrations pause and resume cleanly without data loss or duplicate folders.

5. Post-Migration Verification & Final Sign-Off

Upon completion of Stage 4 transfer, CloudBridge™ executes Stage 5 Destination Parity Verification comparing source and destination folder counts, file counts, byte totals, and MD5 checksums. The Customer is responsible for reviewing the Parity Audit Report and any flagged discrepancies before executing Stage 6 Final Sign-Off.

6. Token Lifecycle, Revocation & Limitation of Liability

OAuth 2.0 tokens are used exclusively for the active migration job and are permanently purged upon Stage 6 Sign-Off or when clicking Disconnect Accounts. CloudBridge™ is provided by TechnoDoc Solutions under applicable enterprise service-level agreements; TechnoDoc Solutions shall not be liable for upstream cloud provider outages, third-party quota enforcement, or administrative misconfiguration outside the approved pre-migration scope.

7. Service Scope Limitations & Non-Supported Workloads

No Email Migration: You acknowledge and agree that CloudBridge™ does NOT migrate email messages or mailbox archives (including Gmail inbox/sent folders or Outlook / Exchange mailboxes). The service scope is strictly limited to files, folders, permissions, contacts, calendars, tasks, and email signatures.
Cross-Account File ID Generation: You acknowledge that file ID preservation across different cloud accounts is governed by upstream cloud provider limitations (such as Microsoft Graph's drive-scoped ID architecture which prohibits moving items between different drives), and that cross-account migrations will generate new destination-scoped file IDs.

1. Microsoft Cross-Account File ID Non-Preservation (M2M / M2G / G2M)

Microsoft Graph API prefixes item IDs with unique Drive IDs, precluding cross-account ID preservation. Files transferred to a new tenant receive a new destination-scoped File ID.

Copy-Only for M2G: Microsoft ➔ Google transfers operate strictly in Read-Only Copy mode (source deletion is permanently disabled). For other directions, Move mode is an optional feature requiring explicit administrative confirmation.

2. Google Workspace Cross-Domain Ownership Restrictions (G2G)

Google preserves original File IDs only within the same Workspace organization. Across different domains or personal Gmail accounts, cross-domain security blocks ownership transfer; files are cloned with 100% binary fidelity instead.

3. Upstream Cloud API Quotas & Daily Rate Limits

Transfers are governed by cloud provider rate limits, including Google's 750 GB/day upload cap and Microsoft Graph throttling. CloudBridge™ automatically rate-limits and pauses/resumes transfers without duplication.

4. Proprietary Document Conversion (Docs/Sheets vs. Office)

Google Docs, Sheets, and Slides are automatically converted to OpenXML formats (.docx, .xlsx, .pptx). Content and layout are preserved; proprietary macros and Apps Scripts do not migrate.

5. "Shared with Me" Items Ownership Boundary

Files in "Shared with Me" belong to external accounts. CloudBridge™ can copy accessible files to your destination, but cannot modify or delete original files owned by third parties.