Enterprise Security, Escrow & Platform Governance
Institutional StandardA comprehensive overview of our cryptographic architecture, milestone escrow, on-device AI mode, and data protection.
Held until client approval
Credentials at rest, TLS in transit
UK & EU statutory compliance
Two-factor sign-in
Enterprise Security Architecture
Four layered security controls engineered to protect commercial transactions, user identity, and confidential marketing IP.
Milestone Escrow
For escrow milestones, the client pays by card through Stripe and Telemoz holds the funds. They are released to the agency's Stripe Connect account only when the client approves the milestone, which reduces late-payment risk for agencies and delivery risk for clients.
On-Device AI Mode
The AI Studio offers a local mode that runs an open model inside your browser, so confidential briefs and brand copy are not sent to a cloud AI provider. It needs a WebGPU-capable browser (recent Chrome or Edge). If local mode cannot run, nothing is sent; you choose whether to switch to cloud mode.
Role-Based Access Governance (RBAC)
Granular multi-seat governance allows agencies to scale client delivery teams while maintaining strict data boundaries. Owners assign roles (admin, manager, media buyer, creative, auditor, contributor) with permissions over billing, contract signing and campaign data, and can limit staff to specific clients.
Audit Logging
Changes to team members, roles and client access are recorded in the agency audit log, with who made them, when, and from which IP address. Sign-in attempts are rate-limited to slow down password guessing.
Compliance & Subprocessor Standards
Rigorous vendor risk verification and international regulatory frameworks.
GDPR & UK DPA 2018
Full adherence to European Union and United Kingdom statutory privacy regulations, including Article 15–22 Subject Access Rights.
PCI-DSS Processors
Payments are taken on the hosted checkouts of PCI-DSS certified processors: Stripe, plus Paystack and Bachs for African payment methods. Card details never reach Telemoz's servers.
TLS 1.3 & AES-256
Encrypted connections for data in transit, connected-account credentials encrypted with AES-256-GCM, and passwords stored only as salted bcrypt hashes.
Payment Data
Telemoz stores no card numbers. Saved cards for retainer billing are held by Stripe and referenced by token.
Responsible Vulnerability Disclosure & Compliance Desk
Security researchers and enterprise compliance teams can contact our designated security engineering office directly for audit requests or responsible vulnerability reports.