Built for regulated collections.
Auditors, regulators and lending partners ask for proof. Duenex gives you the evidence — isolation, masking, access rules and an audit trail that’s on by default, not on request.
Six promises we build around.
Your data, walled off
Every organisation’s data is isolated at the database level. One customer of Duenex can never see another’s accounts.
Encrypted, masked, logged
Personal details are encrypted at rest and masked on screen. Every reveal and export is written to an access log.
Access when you say
Set working hours, holidays and an IP allow-list. People on leave can’t sign in. Two-step verification on request.
Do-not-contact, enforced
A customer who opts out is blocked across every loan they hold. Attempts to call are refused and recorded.
An audit trail nobody can edit
Who did what, who saw customer data and who was turned away — append-only, searchable and exportable.
Clean off-boarding
When a contract ends, data is exported to you and then permanently destroyed along with its encryption key.
What’s switched on for every organisation.
Sign-in
- Unique usernames across Duenex
- Two-step verification on request
- Sessions expire and can be revoked
- Repeated failures are rate-limited and logged
Access
- Role-based permissions, enforced on the server
- Team and allocation limits on every account
- Working hours, holidays and leave
- IP allow-list per organisation
Customer data
- Encrypted at rest, TLS in transit
- Phone numbers and IDs masked by default
- Every reveal written to the access log
- Exports masked and logged
From upload to destruction, accounted for.
Customer data enters Duenex one way, is protected the whole time it’s there, and leaves one way.
Your Admin uploads a portfolio file; it’s validated before anything is saved.
Personal fields are encrypted at rest, under your organisation’s key.
Screens show masked contacts until a permitted user reveals one.
Every view, reveal, change and export is recorded.
When a contract ends, you receive your data.
The data and its encryption key are then permanently deleted.
Can another organisation ever see our accounts?
No. Each organisation’s data is isolated at the database level, so a query from one cannot return another’s rows — even if the application had a bug.
Can we see who looked at a customer’s phone number?
Yes. Every reveal is written to the access log with the user, account and time. Admins can search and export it.
What happens when someone tries to call a do-not-contact customer?
The attempt is refused, the agent sees why, and the refusal is recorded for review.
What happens to our data if we leave?
We export it to you, then permanently destroy it along with its encryption key.
See Duenex on your own portfolio.
Book a 30-minute walkthrough. We’ll load a sample file with you and walk through the full workflow — no slides.
- Your products, your buckets, your languages
- The full workflow, live
- A written summary afterwards