Security & compliance
Podcasters and media production houses trust MicProtocol with pre-release audio, proprietary interview notes, and high-profile guest contacts. Security is baked into every architecture layer.
Security standard
Encryption in transit & at rest
All client-server communications use TLS 1.3 with strong cipher suites. Data at rest is encrypted using AES-256 via modern encrypted block storage.
Authentication & credential security
Multi-factor authentication, salted cryptographic password hashing, short-lived JWT tokens, and strict HTTP-only secure cookies.
Isolated workspaces & tenancy
Multi-tenant workspace isolation enforced at the database and application levels. Each podcast team's assets and pipeline data remain strictly segregated.
Subprocessor transparency
We strictly audit third-party services including infrastructure hosts, email delivery providers, and payment processors to adhere to rigorous privacy standards.
Automated vulnerability monitoring
Continuous automated dependency scanning, synthetic agent penetration tests, and vulnerability alert monitoring across all system containers.
Responsible disclosure program
We welcome security researchers. Vulnerability reports submitted to our security team are acknowledged within 24 hours with coordinated fixes.
Data storage & audio media isolation
Uncompressed studio recordings, guest bios, and talking points are stored in secure object storage with strict access controls. Pre-signed URLs with short lifespans (maximum 15 minutes) are generated on demand to prevent unauthorized hotlinking or preview leakage.
Responsible disclosure
If you discover a security vulnerability in MicProtocol, please contact us at security@micprotocol.io. Please do not publicly disclose the issue until our security team has verified and deployed a patch.
Contact: security@micprotocol.io.