Your customer records stay on your servers.
Written for bank IT, security and compliance teams: where the system runs, what it can and cannot see, and how you stay in control of every release.
Security check
Example bank · sample view
- Hosted on
- Core banking connection
- Card numbers, PINs, OTPs
- Phone and email
- Staff sign-in
- Call recording
- This release
The system and its records run on your servers.
Installed in your environment with Docker or Kubernetes, offline if you need it. Customers reach it through your connections; core banking is never one of them.
Some steps, such as turning speech into text, can use outside providers. Before installation we tell you which ones and what each receives.
YOUR BANK'S ENVIRONMENT
✕ Core banking · never connected
Follow one card number through the system.
The caller reads out their card
It happens on every support line. Customers say the numbers out loud before anyone can stop them.
Found before anything else
Hidden from the AI
Hidden from storage and staff
“Please block my card. The number is 5061 2345 6789 0123.”
A support channel, not a banking agent.
What the system can see, and who can see what it holds, is limited by design.
No access to money
There is no connection to core banking. It never reads balances or moves funds, and banking identifiers are refused.
Sensitive numbers hidden
Card numbers, PINs and OTPs are removed from transcripts, tickets, summaries and staff screens.
Contact details masked
Phone numbers and emails are masked for staff. Every reveal is written to the audit log.
Recording only after notice
Calls are recorded only after the caller has heard your recording notice.
Roles for every job
Admin, Supervisor, Agent, Auditor and System Admin, each seeing only what the job needs.
Two-factor sign-in
Staff sign in with two-factor authentication, which you can require for everyone.
People approve what goes out
AI drafts replies and summaries; a person approves outbound email before it is sent.
A full audit trail
Data reveals, ticket reassignments, recording playback and settings changes are all logged for your auditors.
You know exactly what you're installing.
Your IT team stays in control of every version that runs in your environment.
- 01
Signed releases
Every release is signed, so your team can check it came from us and hasn't been altered.
- 02
Software bill of materials
Each release lists every component inside it, for your vulnerability management.
- 03
Guided upgrades, one-step rollback
Upgrades are applied when your team chooses, and can be undone in one step.
- 04
Offline installs
Releases can be carried into environments with no outbound internet connection.
- 05
Source-code escrow
Available on request, so your bank can keep the system running if we stop trading.
What security teams ask us.
Security walkthrough
Bring your security team to the demo.
We walk them through the system as it would run in your environment, and answer their questions directly.
- 1
Deployment architecture
What runs where, what connects to what, and what never does.
- 2
Controls and audit
Redaction, masking, roles, two-factor sign-in and the audit log.
- 3
Releases
Signing, the software bill of materials, upgrades and rollback.