Dispute DojoYour data. Your terms.
Dispute Dojo deploys in your cloud, ours, or a hybrid of both, with role-based access, audit trails on every action, and 100% human review before any dispute is submitted. Security that fits your policy, not the other way around.
Pending approvals
3
Active roles
6
Audit events today
42
Auto-submissions
0
Deploy where your policy requires.
Three deployment models for three different risk profiles. Each has a real trade-off — here's the honest version, so your security team isn't the last to know.
Your cloud
Dispute Dojo runs inside your own cloud account. Your network policies, your security tooling, and your access rules apply end to end.
- Data never leaves your environment
- Your security toolchain applies throughout
- Best fit for teams with existing cloud governance
The trade-off
Your infrastructure team shares the operational load — standing up and maintaining the environment sits on your side of the line.
Our cloud
Hosted and managed by Dispute Dojo. We run the infrastructure, patching, backups, and monitoring. You connect and go.
- Encryption in transit and at rest
- Managed backups and recovery
- Fast setup with no engineering lift on your side
The trade-off
Your data lives in our environment. We walk your security team through exactly how it's handled and protected before you commit.
Hybrid
Sensitive data and credentials stay in your environment. Dispute Dojo runs the application and AI layers across a documented boundary.
- Data residency where your policy requires it
- Documented split of responsibilities
- Built for operators with strict data policies
The trade-off
A shared responsibility model takes coordination. The boundary is documented, but each team owns its side of it.
Yours on the way in. Yours on the way out.
Ownership and access rules that hold from the day you connect to the day you leave, if you ever do.
Your data stays yours
Your operational data remains your property. We don't sell it or share it between customers. Your data isn't used to train models — ours or anyone else's — unless you explicitly agree to it. The default is no.
Role-based access
Permissions scoped by role, location, and brand. Store managers see their store, regional leads see their region, owners see everything.
Least privilege by default
Access starts at the minimum needed to do the job. Elevated permissions are granted explicitly by your admin — never assumed from a title.
Audit trails
Every data access, admin change, and case action is logged: who did what, when, and to which case. Available for review whenever you ask.
Approval workflows
Sensitive actions route through explicit approval before anything executes, and every approval is recorded with who signed off and when.
Offboarding takes your data with you
No long-term contracts, and no hostage data. If you leave, you take a full export with you, and we delete what remains on request.
AI that drafts. People who decide.
The AI layer inside Dispute Dojo is governed, not autonomous. It assembles, flags, and drafts. A Recovery Analyst signs off before anything reaches a platform.
100% human review before submission
Every dispute is reviewed by a Recovery Analyst before it goes to a platform. We do not run automated dispute submissions — no exceptions.
AI is assistive, not autonomous
AI assembles evidence packages and flags patterns. It drafts; it never decides. A person approves everything that leaves the building.
Reviewed and traceable
AI output carries the data it was built from, so a Recovery Analyst can check the work. Anything that doesn't meet the bar goes back for review, not out the door.
Budgeted by design
AI spend runs against defined budgets with monitoring, so model costs stay predictable as you add locations — no runaway automation.
DoorDash — missing item claim
Uber Eats — quality complaint
DoorDash — order issue adjustment
Uber Eats — missing item claim
Deployment
Your cloud, ours, or hybrid
Access
Role-based, least privilege
Audit
Every action logged
Dispute review
100% human
Your data
Stays yours — in and out
Frequently asked.
Bring your security team.
Get a demo and we'll walk through deployment options, access controls, and data handling for your environment — before you commit to anything.