Compliance and Security

Data Encryption

Vilulia protects case data through multiple layers of encryption: PHI fields in medical case records are encrypted at the field level through AWS Key Management Service (KMS), case documents are stored in Amazon S3 with server-side encryption at rest, and all API traffic is protected by TLS. PHI field encryption is part of the HIPAA add-on. Document encryption applies to all organizations regardless of plan.

What you'll learn

How PHI field encryption works with AWS KMS and AES-256-GCM
How document encryption works in S3
Which plans include PHI encryption
How encryption keys are managed and rotated

PHI field encryption

Protected health information stored in medical case records is encrypted at the field level through AWS KMS. Each field is encrypted with an encryption context of the field name and case ID, using the KMS key with alias vilulia-phi-key (configurable via KMS_MASTER_KEY_ID). PHI field encryption is enabled when the HIPAA Basic or HIPAA Enhanced add-on is active on your organization.

Key rotation

PHI field encryption uses AWS KMS, so key lifecycle and rotation are managed within KMS rather than by the application. Decryption requires the matching KMS key and encryption context. Separately, the field encryption used for non-PHI secrets (such as connected-account tokens) supports key rotation via a current and previous key, allowing data to be decrypted with either key and re-encrypted with the current key on the next write.

Document encryption

Case documents are stored in Amazon S3 with server-side encryption at rest (SSE-S3, AES-256). This applies to all organizations on all plan tiers. Document encryption does not require a HIPAA add-on. Supported file types include PDF, DOCX, and common image formats. Encryption is managed by AWS and is transparent to the end user.

Email account tokens

OAuth access tokens for connected email accounts (Gmail and Outlook) are encrypted at rest using AES-256-GCM before being stored. This is separate from the PHI encryption system and applies regardless of HIPAA add-on status.

Secure messaging encryption

Messages sent through the secure messaging feature are encrypted server-side before storage, using a per-tenant AES-256-GCM key. Plaintext is never persisted. The message body is encrypted on receipt, and decryption occurs server-side at read time for authorized recipients. This feature requires an active BAA.

Can't find what you're looking for? Contact Support