HIPAA Compliance
Devotel provides HIPAA-ready infrastructure for organizations that handle Protected Health Information (PHI) through communication channels. This document describes the technical and administrative controls implemented when HIPAA mode is enabled.Overview
HIPAA mode is a per-organization feature flag that activates a set of enhanced security controls:- PHI Encryption at Rest — Message content encrypted with AES-256-GCM
- Access Controls — PHI access restricted to designated roles
- Audit Logging — All PHI access logged with reason codes
- Data Retention — Automatic deletion after configured retention period
- BAA Tracking — Business Associate Agreement status management
Prerequisites
Before enabling HIPAA mode, organizations must:- Sign a Business Associate Agreement (BAA) with Devotel
- Have an active subscription on the Business or Enterprise plan
- Designate a HIPAA compliance officer within their team
Technical Controls
1. Encryption at Rest (AES-256-GCM)
When HIPAA mode is enabled, all message body content is encrypted at the application layer before storage using AES-256-GCM:- Algorithm: AES-256-GCM (Galois/Counter Mode)
- Key Management: Per-organization encryption keys derived from the org’s tenant secret and stored in GCP Secret Manager
- Nonce: Unique 96-bit nonce generated for each encryption operation
- Authentication Tag: 128-bit authentication tag appended to ciphertext for integrity verification
- Scope: Applies to message
body,media_url, and any custom metadata fields marked as PHI
2. Access Controls
PHI access is restricted based on role assignments:| Role | PHI Access | Notes |
|---|---|---|
owner | Full access | Can enable/disable HIPAA mode |
admin | Full access | Can view PHI access logs |
developer | Restricted | Access requires reason code |
viewer | No access | Cannot view message content when HIPAA mode is active |
billing | No access | Cannot view message content |
developer role accesses PHI, they must provide a reason code selected from:
treatment— Access required for patient treatment coordinationpayment— Access required for payment processingoperations— Access required for healthcare operationslegal— Access required for legal compliancesupport— Access required for customer support resolution
3. PHI Access Audit Log
Every access to PHI-containing data generates an audit log entry:- Is append-only and cannot be modified or deleted
- Retains up to 10,000 entries per organization (oldest entries are automatically rotated)
- Is accessible to
ownerandadminroles via the dashboard or API - Can be exported for external compliance audits
GET /api/v1/settings/hipaa/phi-access-log
4. Data Retention
When HIPAA mode is active, data retention is enforced:- Default retention period: 365 days (configurable: 30–3,650 days)
- Scope: Message content, call recordings, media attachments
- Mechanism: Automated background job scans for expired records and securely deletes them
- Exceptions: Audit logs and PHI access logs are retained independently of the data retention policy
5. Business Associate Agreement (BAA)
Devotel tracks BAA status per organization:- Status: Signed / Not signed
- Signed date: Recorded when BAA is confirmed
- Document URL: Optional link to the signed BAA document
403 Forbidden error.
API Endpoint: PUT /api/v1/settings/hipaa/baa
API Reference
| Method | Endpoint | Description | Required Role |
|---|---|---|---|
GET | /settings/hipaa | Get HIPAA status and configuration | admin+ |
PUT | /settings/hipaa | Enable/disable HIPAA mode | owner |
GET | /settings/hipaa/phi-access-log | Paginated PHI access log | admin+ |
PUT | /settings/hipaa/baa | Update BAA status | owner |
Dashboard Configuration
HIPAA settings are available in the dashboard under Settings → Compliance:- HIPAA Mode Toggle — Enable/disable HIPAA mode (requires BAA)
- BAA Section — Track BAA signing status and date
- Data Retention — Configure automatic data deletion period
- PHI Access Log — View and export PHI access audit trail
Infrastructure Safeguards
Beyond application-level controls, Devotel’s infrastructure provides:- Cloud SQL Encryption: All database storage encrypted with AES-256 by Google Cloud
- TLS 1.3: All data in transit encrypted with TLS 1.3
- VPC Isolation: Database accessible only via private IP within the VPC
- No Privileged Containers: GKE Autopilot prevents privileged container execution
- Secret Manager: All encryption keys and credentials stored in GCP Secret Manager
- Audit Trails: Google Cloud Audit Logs for infrastructure-level access tracking
Shared Responsibility
HIPAA compliance is a shared responsibility between Devotel and the customer:| Responsibility | Devotel | Customer |
|---|---|---|
| Infrastructure security | ✅ | |
| Data encryption at rest | ✅ | |
| Data encryption in transit | ✅ | |
| Access control enforcement | ✅ | |
| PHI access logging | ✅ | |
| BAA execution | ✅ | ✅ |
| Workforce training | ✅ | |
| Breach notification procedures | ✅ | ✅ |
| PHI minimum necessary standard | ✅ | |
| Patient consent management | ✅ | |
| Risk assessment | ✅ | ✅ |
Incident Response
In the event of a suspected PHI breach:- Devotel’s security team is notified within 1 hour via automated alerting
- Affected organizations are notified within 24 hours per HIPAA Breach Notification Rule
- PHI access logs are immediately preserved and exported for forensic analysis
- Remediation steps are documented and shared with affected parties
Last updated: April 2026 For questions about HIPAA compliance, contact: compliance@devotel.io