Security & data handling

Security & data handling

Client deadlines are confidential. Here is how the service keeps each firm's data separate, protects credentials, and lets you get your data out or deleted.

Details on this page describe the current build. Infrastructure specifics (hosting region, backup retention) are marked TBC and will be finalised before the service is generally available.

Per-firm data isolation

Every firm's records live in one database, and each row is tagged with a firm identifier. The database enforces row-level security: each application connection is scoped to a single firm for the duration of a request and can physically only read or write that firm's rows. The scoping is applied by the database, not just by application code, and a connection that fails to set its firm scope reads nothing rather than everything.

Credentials & encryption

  • Your Twilio credentials (for SMS and WhatsApp) are stored encrypted at rest using public-key sealed boxes — the decryption key is held only by the reminder worker, not in the database.
  • Admin passwords are stored only as salted one-way hashes.
  • All traffic to the app and the board is over HTTPS/TLS.
  • Staff access to the support console requires two-factor authentication, and any staff action on a firm's account is written to an audit log.

Payments

Billing is handled by Stripe. Card details are entered on Stripe's own hosted checkout and are never sent to or stored by Deadline Board. We keep only Stripe's customer and subscription identifiers.

Reminders are at-most-once

The reminder engine uses a claim → send → confirm ledger with a uniqueness constraint, so a crash mid-send cannot double-send a reminder and cannot silently drop one. A send that can't be confirmed is escalated to a person rather than retried blindly.

Backups & availability

The database is backed up regularly with off-site copies. Retention period and hosting region: TBC — the service is hosted in the UK or EU for data residency.

Sub-processors

We use a small number of sub-processors: Stripe (payments), Brevo (transactional email), Twilio (SMS/WhatsApp — under your own account), our hosting provider, and error monitoring. The current list, with purpose and location, is on the sub-processors page.

Your data, your control

  • Export — deadline and matter data can be exported from the admin area at any time.
  • Deletion — on request, or after your account is closed, your firm's data is permanently deleted from the live database; residual copies age out of backups within the retention window.
  • No lock-in — the schema is plain PostgreSQL with no proprietary extensions.

Reporting a vulnerability

Email security@matterdue.com. We will acknowledge within a few working days and keep you updated on the fix.

See also the Privacy Policy and the Data Processing Addendum.

Questions before you sign up?

Happy to walk through the isolation model, the encryption approach, or anything else on this page.