Security is not a feature. It’s the architecture.
How Klyniq handles patient data, isolates practices, and proves what happened.
Trust model
Default deny
Every action with a real-world consequence is refused unless a rule explicitly permits it. There is no implicit allow.
Practice isolation
Each practice is a separate tenant at the data layer. One practice cannot reach another's records, conversations, or configuration.
PII redaction
Sensitive fields are redacted from stored records, with a note of what was removed and from where. The audit trail stays complete without retaining the values.
Append-only records
Execution receipts cannot be edited or deleted after creation — not by staff, and not by the agent that created them.
Fail closed
If Klyniq cannot reach your calendar or verify a rule, it takes a message and escalates. It never acts on uncertainty.
No clinical scope
Klyniq does not diagnose, prescribe, or give medical advice. Clinical questions route to providers.
Data handling
Encryption in transit
All data encrypted with TLS 1.3. No plaintext channels.
Encryption at rest
Patient data encrypted at the database level. Credentials managed through secure vaults, never hardcoded.
No third-party data sharing
Patient data is never sold, shared, or used to train models for other practices. Your data is yours.