Privacy Policy

Last updated: Early Access. This policy is a draft pending legal review.

1. Data minimization by design

AthenaDB licensing is built to see as little as possible. The licensing service never receives your documents, memory, search queries, RAG prompts, embeddings, or domain records (case numbers, patient data, reports). Device binding uses salted one-way hashes of stable identifiers — not raw hardware serials — by default.

2. What the portal collects

To create and manage your account, the portal collects the email address and a securely hashed password you provide, and the references needed to link your account to its AthenaDB licenses. Passwords are stored only as salted hashes and are never logged in plaintext.

3. What licensing handles

The licensing service handles only what licensing requires: a license-key hash or activation token, your account and product/edition, hashed device and instance identity, activation and instance counts, pack identifiers, and trial state and timestamps. It does not collect the prohibited categories in §1.

4. Data in AthenaDB instances

Data you store inside AthenaDB instances you operate is yours and is not transmitted to the portal or licensing service. It is encrypted at rest by the engine, and — via the Instance Trust Fabric — any inter-instance exchange returns permission-filtered context over encrypted channels, never raw access. A per-vault data encryption key is never transmitted.

5. Auditability

Licensing lifecycle events and inter-instance trust decisions are recorded to append-only, hash-chained audit logs that are exportable to your SIEM — supporting compliance and incident review without exposing your content.

6. Compliance framing

Because licensing never sees documents, embeddings, queries, or protected health information, and binding uses hashed identifiers, AthenaDB is designed to support privacy-sensitive deployments (e.g. HIPAA/PHI, attorney work-product, and government/high-security controls via the planned Compliance and Government paths). These are design goals during Early Access, not certifications.

7. Your choices

You can request deletion of your portal account by contacting [email protected]. Deleting your account removes your portal profile and license links.

8. Contact

Privacy questions: [email protected].