Security
One dealership, one database.
A dealership lives on its ledger. This page says exactly how that ledger is kept — nothing we do not do.
- Database
- One per dealership
- Backups
- Nightly, off-site
- Restore drill
- Monthly
- Hosted
- In the EU
Data isolation
One database and one deployment per dealership.
Most software keeps every customer's rows in the same tables and relies on a filter to keep them apart. One missed filter and a dealer is looking at another dealer's book. We do not take that bet with a ledger.
Each dealership on DealerPro gets its own Postgres database and its own deployment of the app. There is no other dealer's row in it to leak, your backups contain only your data, and leaving means deleting a database rather than hunting for rows.
Backups and restore drills
Nightly, off-site, and proven monthly.
Every night the whole database is backed up and the backup is copied off-site. A backup that has never been restored is a hope, not a backup, so once a month we run a restore drill: the newest off-site backup is restored into a throwaway database and checked.
The check is not a row count. Eight ledger invariants are verified — that every payment resolves to a charge, that reversals are equal and opposite, that what a charge shows as paid equals the sum of the payments allocated to it, and five more. Counts can reconcile while the ledger is nonsense; the drill exists to catch that. Group plan customers receive the drill report each month.
Access control
Roles per branch, MFA, device management, audit log.
Every login has a role, and roles are scoped to a branch: a salesman in one showroom sees that showroom's debtors, not the group's. Two-step verification (a time-based code from an authenticator app) is available for every staff login and is enabled for admins at onboarding. Device management lists every machine the desktop app is installed on and when it last checked in.
The audit log records who changed what, and when. Registered document packs and finalised end-of-day sheets cannot be edited afterwards — only voided.
Hosting
Vercel and Supabase, hosted in the EU.
The app is served by Vercel. The database is Supabase Postgres, hosted in the EU in the eu-west-1 region. All traffic is HTTPS with HSTS, so a browser will not fall back to an insecure connection, and a Content Security Policy restricts what the app is allowed to load.
Your data and GDPR
You are the controller. KIWA is the processor.
The book is yours. Ask for an export and you get all of it. When you leave, you receive a full export and your database is deleted within 30 days.
Under GDPR you are the data controller for your customers' information; KIWA Ltd is the processor, acting on your instructions and nothing else.
Responsible disclosure
Found something? Tell us first.
If you believe you have found a security issue in DealerPro, email hello@dealers-pro.com with what you found and how to reproduce it. We read every report and will keep you informed while it is fixed. Please do not test against a live dealership's data.
FAQ
Questions dealers ask about their data
Is DealerPro a general CRM?
No. It is built for vehicle dealerships that sell on hire purchase and lease: the instalment ledger, arrears, collections, the signed document pack and end-of-day banking are the product, not plug-ins. If you sell cash-only, it still works — it is just more than you need.
Who is using it today?
One of Malta's largest dealerships runs its whole book on DealerPro, live, every day. We do not name customers or publish their figures.
Where is our data kept?
In your own isolated database — no other dealership's rows are in it. It is backed up nightly, restore-tested monthly, and deleted when you leave. See the Security page.
Can we bring our existing book across?
Yes. The Group plan includes migration from spreadsheets or your current system. On other plans it is quoted separately once we have seen the data.
Does it send WhatsApp messages?
Yes — arrears reminders, statements and two-way conversations, using your own WhatsApp Business number and Meta-approved templates. Connecting the number is part of onboarding.
Does it work on phones and tablets?
Yes. It runs in the browser on any device; salesmen typically use it on a tablet in the showroom, and there is a desktop app for the office.
Security
Your book, in your own database
A dealership lives on its ledger. Here is how it is kept, in plain terms.
Hosted in the EUSupabase, eu-west-1Vercel
One Postgres database per dealership
Your dealership gets its own database and its own deployment. No other dealer's rows are in it — not behind a filter, not in the same table, not at all.
Backed up nightly, restored monthly
Every night, off-site. Once a month the newest backup is restored into a throwaway database and the ledger's invariants are checked — a backup that has never been restored is a hope.
Audited daily, locked per login
A row-level-security audit runs against the live database every day. Two-step verification available for every staff login, a list of every machine the desktop app is installed on, and an audit log of who changed what.
Yours to take, gone when you leave
GDPR done plainly: a full export of your data on request, and your database deleted within 30 days of leaving.