Security & reliability
You're handing us your customer list, your job history and the invoices you get paid from. Here is exactly what protects them — stated as mechanisms you can check, not badges.
Last reviewed: August 1, 2026
Your money goes to you
DispatchCore is never in the payment flow.
Paid directly to your Stripe account
Your customer’s card is charged to your own Stripe account — you are the merchant of record. We do not hold, route, or settle your money, so there is no float and nothing to release.
We never see card numbers
Card details are entered on payment pages hosted by Stripe and never touch our servers. There is no card data in our database to leak.
A charge we can’t verify is refused, not guessed
If we can’t confirm what a customer already paid on a deposit, the payment page returns an error and asks them to retry — rather than charging a balance built on an assumption. A wrong number on a screen is recoverable; a wrong card charge is not.
Refunds are recorded automatically
Refund in Stripe, full or partial, and the invoice reflects it — netted out of your paid totals and any deposit credited to a final invoice.
0% platform fee during beta
We take nothing from your transactions. You pay Stripe’s standard processing rate, the same as if you’d wired it up yourself.
Your data survives a bad day
Backed by Supabase on AWS (US East).
Daily backups, 7-day retention
The production database is backed up every day and retained for a week, so a catastrophic failure costs hours, not everything.
An extra copy before risky changes
Before any migration that alters existing data, we take a separate manual backup first — so undoing a mistake never means rolling back a full day of your work.
Encrypted in transit and at rest
All traffic runs over TLS. On phones, login tokens are held in the device’s encrypted keystore (iOS Keychain / Android Keystore), not in ordinary app storage.
Your data is yours alone
One contractor’s data is never visible to another.
Isolation enforced at the database, not just the app
Core tables carry row-level security policies keyed to your organization, underneath the filtering the application already does. Two independent layers have to fail before anything crosses between businesses.
Automated checks block a release that weakens it
Two audits run on every single change: one fails the build if any table loses its protection, another fails if a privileged key could ever reach the browser or phone app. This is checked by machine on every commit, not by someone remembering.
Removing someone removes them everywhere
Deactivate a technician and access is cut at every door at once — the app, the login, the session refresh, and any live connection they already had open. No lingering session outlives the decision.
Your crew’s work isn’t lost in a basement
Offline is a normal condition in the trades, not an error state.
Work queues on the phone and replays later
Status changes and photos are saved to the device the moment your tech taps, then sent when signal returns — automatically, and again on a timer.
A failed upload is kept, not dropped
If something can’t be sent, it stays in the queue and is retried. Photos stay on the device until the upload is confirmed. Nothing is discarded quietly to make a screen look clean.
Your books stay in step
QuickBooks Online, both directions.
Invoices and payments push automatically
Send an invoice or mark it paid and it reaches QuickBooks without re-keying.
Voids retract, they don’t just stop
Voiding an invoice retracts it in QuickBooks too, rather than leaving an open invoice inflating your revenue and receivables. It is voided rather than deleted, so the document number stays accounted for.
Conflicts are reported, not papered over
If a payment is already applied in QuickBooks, we refuse to void underneath it and record the conflict for you to resolve — rather than orphaning the payment.
We find out before you tell us
Monitoring and tests on every change.
Errors are monitored across all three apps
The dashboard, the mobile app and the API all report errors to monitoring in real time, so failures surface without a support ticket.
Every change runs the test suite
Around 700 automated tests run on every proposed change before it can ship, concentrated on the parts that move money — invoice totals, tax, deposits and balances.
What we don't claim
We're a small team in beta, and a trust page that only lists strengths isn't worth reading. So, plainly:
- No SOC 2, ISO 27001 or HIPAA certification. Those are audits we have not undergone. Anyone showing you a badge should be able to show you the report.
- No uptime guarantee. We don't publish an SLA, because we don't yet run the monitoring that would let us stand behind a number.
- Point-in-time recovery isn't enabled. Backups are daily. If the database had to be restored, you could lose work done since that morning. We'll turn it on when the volume of real work justifies the cost.
Questions, or found a problem?
If you think you've found a security issue, email security@dispatchcore.io and we'll respond. Please don't test against other contractors' accounts.
Get Started Free