Security at Propela Therapy

Clinical data deserves bank-grade care. Here is exactly what we do.

Architecture

• All production data lives in the EU (Frankfurt) — database, file storage, and backups.
• Every table is protected by row-level security: a practice can only ever read its own rows, enforced in the database itself, not just the application.
• Client-portal accounts are isolated by separate database policies — a client sees only their own records, never another client's, never another practice's.

Encryption

• TLS 1.2+ for all traffic.
• Session recordings are encrypted with AES-256-GCM before upload; the per-practice key is wrapped by a master key that never leaves the server.
• Secure-message bodies are encrypted at rest with the same per-practice envelope keys — even our realtime infrastructure only ever carries ciphertext.

Access control

• Role-based access: owners, admins, therapists, and receptionists — receptionists can run the front desk without ever opening a clinical note.
• TOTP two-factor authentication on every account, with a 12-character password minimum.
• An append-only audit log records every access and change with IDs only — clinical content never appears in logs, error tracking, or analytics.

AI processing

• Transcription and note drafting run through enterprise AI APIs under agreements that exclude training on your data.
• AI output is always a draft — a clinician reviews and approves every note.

Your controls

• One-click GDPR export and erasure per client, plus a full practice export.
• Deleting your practice removes every record, file, and account permanently.

Found something?

Report vulnerabilities to felipedafig@gmail.com — we respond within 48 hours and will credit responsible disclosures.