All MicHelper legal documents
Security

Your Data, Protected

MicHelper is built with security and privacy at its core. We implement industry-standard practices to ensure your sales data remains confidential and protected.

🔐

Encryption in Transit

All connections to MicHelper use HTTPS with TLS 1.2 or higher. Data transmitted between your browser and our servers is always encrypted.

🔒

Encrypted Data at Rest

Sensitive data including transcripts and personal information is encrypted at rest using AES-256-GCM field-level encryption.

👥

Role-Based Access Control

Granular RBAC ensures users only see data relevant to their role. Sellers see their own data, managers see their teams, admins manage the network.

📋

Audit Logging

Actions are logged with timestamps, user IDs, and IP addresses. Full audit trail for compliance and security investigations.

⏱️

Rate Limiting

Global, per-user, and per-endpoint rate limiting protects against brute-force attacks and abuse. Suspicious activity is detected and blocked.

✅

CSRF Protection

All state-changing API endpoints are protected with CSRF tokens, preventing cross-site request forgery attacks.

Technical Security Measures

We implement multiple layers of protection to safeguard your data.

✓

Session Security

Secure session management with automatic timeouts, IP-based session validation, and brute-force protection with account lockout after failed login attempts.

✓

HTTPS/TLS Encryption

HTTPS-only connections with HSTS enforcement. Security headers configured via Helmet.js (CSP, X-Frame-Options, X-Content-Type-Options, Referrer-Policy).

✓

Infrastructure

MicHelper uses a protected cloud environment for application services, persistent storage and encrypted backups. Approved AI services process requests under contractual privacy and retention controls; specific provider routing is confidential technical information.

✓

Input Validation & Injection Prevention

Parameterized SQL queries prevent injection attacks. XSS pattern detection on input. File upload validation with type and size limits.

✓

Data Isolation

Each customer network is logically isolated. Cross-tenant access is architecturally prevented.

Authentication & Access Control

Data Protection

Infrastructure Security

Audit & Monitoring

Data Lifecycle

Data TypeRetentionEncryption
Raw audioRemoved after successful transcription; failures, browser backlog, legal hold, quality review and backups follow separate cleanupTLS in transit (transient processing)
Source transcriptsTemporary for analysis; cleanup scheduled after a five-minute safety window for new successfully analysed chunks, with retry/hold/backup exceptionsAES-256-GCM field-level
Analytics & scoresConfigured service retention and signed customer agreementDatabase-level
Account dataConfigured service retention and legal obligationsAES-256-GCM for sensitive fields
Audit logs90 daysDatabase-level

Privacy & Compliance

Designed for the current Ukrainian market with data minimisation, purpose limitation, controlled access and human review in mind.

✓

Privacy by Design

Built around data minimisation, purpose limitation, controlled retention and access-management practices.

✓

Data Processing Agreement

Standard DPA available for all customers. We act as a processor on your behalf.

✓

Privacy Requests

In-app tools for data export and deletion requests. Respond to data subject requests efficiently.

✓

Breach Notification

Documented incident response procedures. Notification within 72 hours as required by applicable law.

Data Lifecycle & Retention

Audio Recordings

Raw audio is removed from server storage after successful transcription. Failed jobs, browser backlog, valid legal hold, quality review and backups have separate cleanup schedules; six hours is the standard retry window, not a guaranteed maximum.

Transcripts

For new recordings, source conversation text is encrypted while needed for analysis and retries. Cleanup for a successfully analysed chunk is scheduled after a five-minute safety window, subject to pending/retryable work, legal hold and backup exceptions. Historical text needs separate audited cleanup. Derived analysis and scores may remain.

Analytics, Scores & Performance Data

QA scores, coaching notes, event timelines and metadata can remain after raw audio and source text are removed. They follow the configured service retention and signed customer agreement and may remain personal data when linked to a worker.

Account & Configuration Data

User accounts, network configurations, scripts and settings follow configured retention, the signed customer agreement and applicable legal obligations.

Summary

Data Type Retention Encryption
Raw audio recordingsRemoved after successful transcription; retries, browser backlog, legal hold, quality review and backups follow separate cleanup[TODO: verify storage encryption for temporary audio in the production hosting configuration]
Source transcriptsTemporary for analysis; cleanup scheduled after a five-minute safety window for new successfully analysed chunks, subject to exceptionsAES-256-GCM field-level
Analytics & scoresConfigured service retention and signed customer agreementDatabase-level encryption
Account dataConfigured service retention and legal obligationsAES-256-GCM for sensitive fields
Audit logs90 daysDatabase-level encryption
🔒
TLS 1.2+ Transport Security
🗄️
AES-256 At-Rest Encryption
📊
SOC 2 Protected cloud infrastructure
🛡️
Privacy by Design Privacy by Design

Security Commitment & Limitations

MicHelper implements industry-standard security measures to protect your data, including but not limited to:

No Absolute Guarantee. While we employ robust, multi-layered security controls and follow industry best practices, no system connected to the internet can guarantee 100% security. We commit to:

If you discover a potential security vulnerability, please report it responsibly to security@michelper.com. Do not access other users' data or publish technical details before we can investigate.

Vulnerability Disclosure

We value the security research community and welcome responsible disclosure of security vulnerabilities.

Please do not access or modify other users' data, disrupt services, or publicly disclose vulnerabilities before we have had a reasonable opportunity to address them.

Questions About Security?

Our team is happy to discuss your specific security and compliance requirements.