Security you can evaluate, not just read about.
Procurement teams need accurate answers. Below, each control is listed as implemented, partly implemented, planned or not in place, with its limits. The list comes from a review of the application code, not from marketing.
What is in place today.
Passwords are salted and hashed with scrypt. Repeated failed sign-ins are throttled per account and per source. Sessions expire after 12 hours.
No idle timeout yet.
Authenticator-app two-step sign-in with recovery codes. Built to be required for Tessellaite administrators, and can be required per organization.
Authenticator apps only; no SMS or passkeys. Optional for customers unless required for their organization.
Each organization’s data is separated in the database with row-level security. Automated tests fail if a table holding customer data lacks it.
Not independently tested. Confirmation of the production database configuration is part of pre-launch review.
Roles with defined permissions, custom roles, and time-limited access grants.
No field-level restrictions yet.
The service is served over HTTPS, with certificates provided by our hosting platform.
The application does not itself enforce HTTPS or HSTS yet.
Credentials and integration tokens are encrypted by the application. Storage encryption is provided by our database host.
Business records are not separately encrypted by the application.
Changes are recorded in an append-only, hash-chained audit trail that can be verified.
Tamper-evident rather than immutable storage. Not every table is audited.
Tessellaite staff cannot view your records unless your Owner approves a time-limited, scoped request. Each look is logged.
Two narrow scopes only. Administrators can still reset credentials, and database-level access exists.
No retention or deletion policy is published yet.
Terms for data return and deletion are confirmed with your order.
Database backups and point-in-time recovery are provided by our hosting provider. A restore procedure is documented.
Recovery times are not yet validated.
Requests require a signed-in session and are permission-checked. Sign-in and public forms are rate limited. Cross-site request protection is in place.
No general API rate limit yet.
The Health Suite demonstration uses fictional data only. No Kovaila product handles patient information today.
Not available.
A customer-controlled Companion is a proposed design for keeping patient-level records and token mappings outside Kovaila’s cloud.
Not built and not validated.
What we do not claim.
No independent testing, certification or healthcare compliance work has been completed. We do not claim:
- SOC 2, ISO 27001 or other certifications
- HIPAA compliance or a business associate agreement
- Independent penetration testing or third-party audit
- Verified EHR integrations
- Retention periods, deletion on request, or guaranteed recovery times
Patient information stays under your control by design.
The Health Suite is designed so patient-level records and token mappings stay outside Kovaila’s cloud, in a customer-controlled Companion. This is a proposal. It has not been built or independently validated, and the demonstration contains only fictional data.
The review behind this page covers the Business Suite and the Health Suite demonstration. It did not include the live production environment.