Privacy Policy
Architectural Scope & 100% Local Source-Code Sovereignty
BoxLink (boxlink-bridge and table.developumaiengine.com), engineered and operated by Developum AI Engine / Bradley "MadBrad" Smith ("Developum," "we," "us," or "our"), provides an out-of-band mobile voice/text walkie-talkie bridge and deterministic Real-Math Context Odometer for local AI coding agents (including Google Antigravity IDE, Cursor, Claude Code, and Windsurf).
Unlike cloud sandbox agents that force you to upload your proprietary Git repositories to remote virtual machines, BoxLink is architected on a Zero-Cloud Source Code Principle: your source code files, local SQLite databases, environment variables, and full IDE conversation transcripts remain 100% on your local workstation.
Information We Collect & Ephemeral Relay Storage
We collect and process only the minimal cryptographic and telemetry metadata required to route your mobile dispatches and enforce hardware licensing:
-
Cryptographic Pairing & Hardware Lock Metadata: When you run
the-table pairorthe-table unlock, our server records an irreversible SHA-256 hash of your agent secret key (key_hash), your 24-character cryptographic lane token, and a one-way SHA-256 hardware fingerprint (machine_id) to enforce our 1-PC anti-sharing lock. - Ephemeral Mobile Queue & Feed Dispatches: Voice transcripts and text prompts sent from your phone to your PC, along with concise agent replies mirrored to your mobile HUD, are stored outside the public web root and automatically purged on a rolling TTL sweep (7-day queue TTL; 200-message rolling history cap).
-
Numeric Context Odometer Telemetry: Numeric token counts, epoch counters, and percentage load metrics (e.g.,
38.9% | 46,633 / 120,000 tok) are transmitted to calibrate your mobile HUD gas gauge and trigger your 75% compaction blast-shield alarm. - Payment Processing via Stripe: One-time Sovereign Pass purchases ($29 Solo / $49 Pro) are processed directly by Stripe, Inc. We never receive or store your credit card numbers on our servers.
Enterprise Infrastructure & SOC 2 Type II Readiness Standard
To uphold enterprise security for professional software engineers and technical teams, our relay infrastructure operates under active SOC 2 Type II readiness controls:
-
Cryptographic Token Isolation (
[WF-R41]): Every mobile lane is gated behind an unguessable 24-character cryptographic token path (/t/<token>) with strict multi-agent tenant isolation. -
TLS 1.3 Encryption & Hashed Credentials: All communications between your phone,
table.developumaiengine.com, and your local PC daemon are encrypted in transit via TLS 1.3, and agent keys are stored exclusively as SHA-256 hashes outside the web root.
Data Sovereignty & Instant Lane Erasure (/burn Protocol)
You retain complete, instantaneous control over your relay lane and message history at all times:
-
Instant Cryptographic Token Rotation (
POST /rotate): You may rotate your 24-character mobile URL token at any time, immediately invalidating any previous mobile link. -
Permanent Cryptographic Burn (
POST /burn): Executing the burn command immediately and permanently deletes your entire server-side lane directory, message history, push subscriptions, and token mappings from our disk.
Contact & Security Governance Office
Attn: Bradley "MadBrad" Smith, Principal Systems Architect
Web: https://table.developumaiengine.com • https://developumaiengine.com
Email: madbradsmith@gmail.com