Skip to content

Security

Your book, your database.

Each dealership runs in its own isolated database, backed up nightly and restored for real every month.

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.

  • Your own Postgres database, no shared tables
  • Your own deployment of the app
  • Backups that contain only your book

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: every payment resolves to a charge, reversals are equal and opposite, what a charge shows as paid equals the payments allocated to it, and five more. Group plan customers receive the drill report each month.

  • Nightly backup, copied off-site
  • Monthly restore into a throwaway database
  • Eight ledger invariants checked

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.

  • Roles and permissions per branch
  • Two-step verification (TOTP)
  • Device management and a full audit log

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.

  • Vercel for the app, Supabase for the database
  • EU region: eu-west-1
  • HTTPS with HSTS, Content Security Policy

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.

  • Full export on request
  • Database deleted within 30 days of leaving
  • KIWA acts only as processor

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.

  • Email hello@dealers-pro.com
  • Include steps to reproduce
  • Never test on live dealer data

Security questions

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.

See it on your own screen.

A thirty-minute demo, on your screen or in your showroom if you prefer. Live within two business days of signing up.