Artemis Privacy Policy

Encryption

Data is encrypted in transit (TLS 1.2 or higher) and at rest (AES-256 with AWS KMS keys) across the database, file storage, cache and queues. This is specified in the architecture docs and confirmed in the infrastructure code.

Tenant isolation

Each customer's data is separated at the database level with row-level security. The application connects with a restricted role that can't bypass it, and automated cross-tenant access tests run on every release. Alethea staff access across customers is sometimes granted, with permission: it requires step-up authentication and a logged justification, and every access is written to an immutable audit log.

Member PII

Protected persons are stored with name and role, both flagged as PII in the code. Family members are stored as linked protected-person records. Monitoring can't start without a consent attestation, and no customer admin can bypass that gate.

Privacy by design

Notification payloads are redacted, error reports are scrubbed, and LLM processing stays in-region.

Data residency

All data stays in the US.

Delete User Data

Send a request to your Alethea point of contact to request data/org deletion.