Skip to content
Covenant Desk

Region and language

Get a Demo
Security and compliance

Your obligations. Our evidence.

Covenant Desk is software. The obligations on this page remain your institution's. What we publish is which of them our records, controls and exports are built to evidence.

How it is protected

Separate storage, and a locked front door.

Every client gets their own database cluster. Your borrower records are not rows in a shared table alongside another lender's. They live in storage provisioned for you, which is what keeps one client's data private from every other client rather than relying on a filter in the application to hold the line.

Getting in takes more than a password. Two-factor authentication protects staff accounts, reCAPTCHA screens automated sign-in and form attempts, and an account is limited to one active session at a time, so a shared or stolen credential cannot quietly be used in two places at once.

Inside, access is scoped and recorded. Staff see only the companies and modules their role allows, exact-HKID lookups across companies are permission-scoped, phone numbers are masked, and sensitive lookups, edits and admin changes are written to an audit log against a named user and timestamp.

A+Mozilla ObservatoryA+SSL Labs

Vendor due diligence

What a bank's vendor review asks, answered before it asks.

  1. 01

    Dedicated instance

    Your instance, database and backups are yours alone. Nothing is shared with another customer.

  2. 02

    Data residency

    Database, uploaded documents and backups stay in the agreed region. The only outside call is to the AI model your bank approves.

  3. 03

    AI governance

    Identifiers are masked before any AI call and every call is logged. AI prepares the decision; rules grade the case and a named credit officer approves it.

  4. 04

    Access

    Two-step sign-in, roles, approval limits and a second-person check; single sign-on with your directory is set up in your deployment.

  5. 05

    Encryption

    TLS on every connection; each uploaded document encrypted on its own with AES-256-GCM; database and backups encrypted at rest.

  6. 06

    Audit

    Every action goes into an append-only, hash-chained log that shows if anything was changed afterwards. Retention follows your policy.

  7. 07

    Independent testing

    An independent CREST-accredited tester that you accept tests your deployment before any real customer data goes in.

  8. 08

    Exit

    At the end of the contract you receive a full export of your data; we then delete it and confirm the deletion in writing.

We prepare the mapping of our controls to the rules your supervisor applies, for example HKMA SA-2, TM-G-1 and OR-2, MAS Technology Risk Management and Outsourcing Guidelines, Taiwan FSC outsourcing rules and BNM RMiT, for your own assessment. Our security pack is shared under NDA.

See every provider that handles client data

Hosting

Run on independently certified infrastructure.

Our hosted service runs in Singapore on independently certified infrastructure: ISO/IEC 27001-certified data centres and cloud and database providers with SOC 2 Type II reports. A deployment in your own cloud or data centre runs under your provider's certifications.

Application servers

DigitalOcean, Singapore data centre. DigitalOcean holds SOC 2 Type II and SOC 3 reports and CSA STAR Level 1, and lists its colocated data centres, Singapore among them, as ISO/IEC 27001 certified.

Database

Neon managed PostgreSQL, which holds ISO/IEC 27001 and ISO/IEC 27701 certification and SOC 2 Type 2 and SOC 3 reports.

Underlying cloud

The database runs on Amazon Web Services in Singapore. AWS holds ISO/IEC 27001, ISO/IEC 27017 and ISO/IEC 27018 certification.

The framework

Nine obligations, and what the software does about each.

Each item names the instrument and the body behind it. Banks map the same controls to HKMA requirements; where a duty is your institution's alone, it says so.

Controls

What your team can review before production setup.

Role-based access

Admin, manager, staff and viewer roles combine with module, feature and action-level permissions.

Company scoping

Staff can be scoped to one company or a controlled set of company units, while admins keep the group-level view.

Audit logs

Sensitive lookups, assistant queries, profile edits, sync actions and admin changes are recorded for traceability.

HKID and phone handling

Exact-HKID search is permission-scoped and audit-logged. Phone numbers are masked where the user context requires it.

Borrower consent

Intake and loan request flows preserve the borrower's consent, so a lender receives only the requests the borrower chose to share.

AI controls

Every AI action is logged, permissioned and reviewable. The AI prepares the work and your credit officers approve it; edits require proposal, confirmation, application and audit logging.

Review the controls against your own supervisory requirements.

Bring your regulatory requirements, your AML procedures and the records your auditor asks for. We will show you where each one lands in the system rather than walking through a feature list.

Book a personalised demo