1. About This Page

This page is a product overview, not a legal contract. It explains how Docketra currently handles data and security in early-stage testing.

2. Data Ownership Model

Firms own their workspace data. Docketra processes that data to provide core product workflows and maintain service operations.

3. Sovereign BYOS Architecture

Docketra operates on a Sovereign Bring Your Own Storage (BYOS) model. When your firm connects Google Drive, authentication is restricted strictly to Google's drive.file OAuth scope. Under this restricted scope, Docketra creates its own dedicated firm folder and can strictly only access files and folders that Docketra itself created. Docketra has zero ability to view, search, index, or touch any pre-existing client archives, private documents, or personal folders in your Google Drive.

Drive credentials and connection settings are locked exclusively to the Primary Admin via OTP verification; staff and rotating article clerks have zero administrative access to modify or re-point cloud storage credentials.

4. Google Drive Folder Tamper & Deletion Guard

A common fear among managing partners is that a trainee or clerk might accidentally move, drag, or trash a synchronized folder inside Google Drive. Docketra safeguards against this through automated cloud metadata synchronization:

Persistent Resource ID Tracking: Folders in Google Drive are mapped by persistent, immutable resource IDs rather than fragile directory path strings. If a team member drags or renames a folder in Drive, Docketra’s metadata engine maintains continuous link integrity without breaking active dockets.
Root Manifest Verification: Every firm root folder contains an encrypted identity manifest (.docketra_storage_root.json). Docketra verifies this manifest on every health check to prevent folder misdirection or accidental unlinking.
Trashed Folder Detection & 1-Click Recovery: If a synchronized folder is accidentally moved to the Google Drive Trash, Docketra’s telemetry immediately detects the event (STORAGE_ROOT_MISSING), notifies the Primary Admin, and provides 1-click folder restoration and re-sync from immutable audit history.

5. BYOAI Direction

AI features are optional. In BYOAI-style setups, firms provide and control their own AI API keys. If AI is not configured, core CRM/CMS/task workflows continue to operate.

6. Data Flow

A common flow is: intake (forms/API) → CRM lead records → task/docket execution.

This keeps client intake and downstream delivery connected in a single operating flow.

7. Backups & Responsibility

Docketra maintains operational safeguards for service continuity. Firms remain responsible for their own internal retention, backup, and recovery decisions, especially in BYOS setups where firm-managed storage controls apply.

8. Security Approach

Our baseline approach includes authenticated access, role-based access control, request-level authorization checks, and operational monitoring.

We continuously improve security controls, but no platform can promise zero risk.

9. Contact

Security or data-handling questions can be sent to sarveshgupte@gmail.com.