Account-scoped access
Public API requests require a secret API key. The authenticated key identifies the customer account, and database row-level policies restrict access to that account’s records.
Security & Compliance
Understand how Tervan’s API and data model protect customer records, and discuss the requirements for your institution.
This overview describes implemented application controls. Deployment arrangements and contractual commitments require a separate review. It is not an independent audit or regulatory certification.
01 / Application controls
Customer access is established at the API boundary and carried into each database transaction. Automated tests exercise authentication, account isolation, and restrictions on changing records.
Public API requests require a secret API key. The authenticated key identifies the customer account, and database row-level policies restrict access to that account’s records.
API keys are generated with cryptographically secure randomness. Only a SHA-256 hash and a short identification hint are stored. Revoked keys are rejected during authentication.
The application uses a database role separate from the schema owner used for migrations. Table and column grants restrict changes, including updates to append-only records.
The API validates request formats and required fields, rejects unknown JSON properties, and applies database constraints to record changes. Database error messages are not returned to API callers.
02 / Infrastructure & data protection
Sessions are pinned to an approved question-set version. Approved versions cannot be rewritten. Database rules keep completed sessions and their recorded answers from being altered by the application.
The database records audited changes with an actor, timestamp, and a per-account hash chain. Answer values, outcome inputs and results, and API key hashes are excluded from automatic change-log payloads.
When a session closes, the database records a retention deadline using the account’s configured period. An existing deadline can be extended but cannot be shortened. A retention deadline is not a promise that data is automatically deleted on that date.
Application controls are one part of supplier due diligence. Agree the infrastructure, data handling, and operational arrangements for your use case before processing live client data.
03 / Regulatory considerations
A firm that determines why and how personal data is processed acts as a controller. Processing on its behalf requires an appropriate controller–processor agreement, including responsibilities for security and assistance with individuals’ rights. Establish roles, lawful processing, retention, and rights-handling procedures for the proposed service.
Reference: EDPB guidance on controllers and processors.
Tervan’s client resource stores a reference rather than a personal profile. References can still be personal data. The website privacy notice explains enquiries and website use; it does not substitute for platform processing terms.
Financial entities remain responsible for managing ICT third-party risk. Articles 28–30 address supplier assessment, oversight and contractual arrangements. Use this overview and the API contract as inputs to your technical assessment, and discuss your institution’s due-diligence requirements with Tervan.
Reference: DORA, Regulation (EU) 2022/2554.
Suitability assessments and the explanation of advice remain the investment firm’s responsibility. Tervan’s implemented session model, versioned question sets, record protections and audit log support traceability. The interactive demo illustrates the assessment and advisory documentation workflow; the API reference defines the available integration scope.
Reference: ESMA’s MiFID II Article 25 reference.
Using Tervan does not automatically make a firm compliant. These controls and workflows do not constitute an independent compliance certification.
04 / Security documentation
The following resources are available for an initial review. Discuss any additional documentation your procurement process requires with our team.
Discuss your integration, data handling requirements, and supplier review process with Tervan. Include your technical, risk, or procurement team.
Or write to hello@tervan.io