Trust, security & operational resilience

Trust built into the technology.

Insurance technology handles customer identity, financial information, policy data and business-critical operations. Buyers need more than a security paragraph: they need to understand how access, change, automation and operational failure are controlled.

Request security or architecture informationResponsible disclosure

Identity & access

Access should reflect responsibility.

  • Role-based access
  • User lifecycle
  • Authentication integration
  • MFA and SSO where applicable
  • Privileged access
  • Customer, advisor and partner identity
  • Authorization boundaries

02 · Application & API security

Security inside engineering, not after it.

  • Secure design
  • Threat modelling
  • Code review
  • Vulnerability testing
  • Dependency management
  • API authentication and authorization
  • Validation
  • Rate limiting where applicable
  • Secrets handling
  • Encryption

03 · Data protection

Protect the data and say only what is documented.

Specific hosting, residency and retention commitments are published only when formally documented.

  • Data classification
  • Access control
  • Encryption in transit and at rest where implemented
  • Logging
  • Retention
  • Secure transfer
  • Non-production data controls
  • Privacy requirements

04 · Auditability & governance

Reconstruct what happened.

Audit history should help operations and compliance teams reconstruct important business actions.

  • 01User actions
  • 02Workflow changes
  • 03Decisions
  • 04Approvals
  • 05Overrides
  • 06Role changes
  • 07Administrative configuration
  • 08Integration events where appropriate

05 · Responsible automation

Automate with accountability.

For intelligent and AI-supported functions, the level of control should increase with the impact of the decision.

  • Defined use case
  • Approved data
  • Business rules
  • Human review
  • Authority boundaries
  • Decision traceability
  • Override
  • Exceptions
  • Monitoring
  • Change governance

06 · Secure delivery

Controls in the pipeline.

  • DevSecOps
  • Code scanning
  • Dependency scanning
  • Secrets controls
  • Environment separation
  • Release gates
  • Vulnerability remediation
  • Change evidence

07 · Operational resilience

Degrade predictably.

The application should degrade predictably when a dependent service is unavailable rather than leave business transactions in an unknown state.

  • 01Availability design
  • 02Dependency failure handling
  • 03Retry
  • 04Timeout
  • 05Circuit-breaker patterns where appropriate
  • 06Backup and recovery
  • 07Incident response
  • 08Business-continuity considerations

08 · Monitoring & incident visibility

See the user impact, not only the alert.

  • Logs
  • Metrics
  • Application health
  • API health
  • Security alerts
  • Failed transactions
  • Queue backlogs
  • Performance
  • User-impact context

09 · Third-party dependencies

Know what can interrupt the journey.

Maintain visibility into the dependencies that can interrupt a customer or operational journey.

  • Identity providers
  • Payment services
  • Communication
  • Cloud providers
  • Verification services
  • External data

10 · Enterprise assurance

This page should become a Trust Center.

As verified material becomes available, this page will publish a security overview, privacy practices, responsible automation principles, data-processing information, subprocessor information where applicable, the business-continuity approach, a security contact, responsible disclosure and an architecture and security FAQ.

Certifications and attestations will appear only when actually held.

11 · What we do not claim

No assurance without evidence.

We do not publish unsupported certifications, guaranteed uptime, recovery objectives, hosting regions, data-residency commitments, penetration-test results or regulatory compliance statements.

Automation & AI controls

Separate automation controls from AI controls.

01Automation controls

Rule ownership, approval paths, permissions, exception handling, audit, rollback and workflow monitoring.

02AI controls

Approved purpose, data boundary, evaluation, human review, source and reference visibility where possible, override, monitoring, model and service change governance, and escalation.

This distinction avoids over-governing simple rules while under-governing higher-risk AI behaviour.

Home