How ACTI-BLITZ™ handles call data, who has access, what's stored, and what's not. Written plain. Updated as we go.
ACTI-BLITZ™ is in Design Partner Pre-Access. We are not yet SOC 2 or ISO 27001 certified — formal audit work begins during Phase 2. What follows is an honest account of how data flows through the system today, and the operational controls in place during the cohort phase. Design Partners with stricter security requirements receive a full architecture brief on NDA.
Audio from your live call is captured at the call layer (Zoom, Google Meet, Teams) via the ACTI-BLITZ™ Chrome extension. The audio stream is transmitted over encrypted connection to AssemblyAI for transcription with speaker diarization.
Transcribed text is then passed through the ACTI-BLITZ™ detection layer — Claude API for primary state analysis, Cohere Command R7B for budget routing and load distribution, and Cohere Embed 4 + Qdrant for semantic state-detection embeddings. The detection result returns to your rep's screen within the timing windows described on the FAQ page.
No call audio is stored long-term during the Design Partner phase. Transcripts are retained only for the duration of an active session unless a Design Partner explicitly opts in to extended retention for product improvement.
Each vendor is selected because they meet or exceed the security posture we'd hold ourselves to as the platform matures. Vendor changes during the Design Partner phase are communicated to partners in advance.
Production data access is restricted to Ron Magic Jackson. No external contractors have production access during Phase 1. Engineering access is granted only to named technical partners under written agreement, with audit logging on all production reads.
Cohort partners can request a full access-control review at any time. Email [email protected].
All data transmitted between the client, the ACTI-BLITZ™ application layer, and vendor APIs is encrypted in transit using TLS 1.3. Data at rest in Qdrant and operational databases is encrypted using AES-256. API credentials and secrets are managed in encrypted secret stores, never committed to source.
We will not claim certifications we don't hold. As compliance milestones are reached, this page is updated with the date and the auditor.
In the event of a security incident affecting Design Partner data, affected partners are notified within 72 hours of incident discovery, with details on scope, remediation, and any actions required on the partner's side. This commitment is in writing in the Design Partner agreement.
Design Partners — and prospective partners under NDA — receive the full ACTI-BLITZ™ Technical Architecture Brief on request. It covers the complete data-flow diagram, vendor agreements, model selection rationale, infrastructure topology, and the Phase 1 → Phase 2 → Phase 3 security roadmap.
To request the brief: email [email protected] with subject line "Architecture Brief Request." Ron sends a mutual NDA, you countersign, you get the document.
Anything not answered above — anything you'd ask in a vendor security review — comes straight to the founder. No support queue. No security-theater form. Email goes to Ron's inbox.
[email protected]