Security practice
How our services are protected.
A summary for customers and reviewers. A fuller Security Overview, with service boundaries and shared responsibilities, is in preparation.
Separation
Public and private surfaces are kept apart.
The public website, the Customer Portal and staff tools are separate surfaces with separate access. This Trust Center is public and holds no account, customer or staff data, and it offers no administrative functions.
Payments
Card details never reach our servers.
Payments are taken on Stripe's hosted checkout page. Donegal receives confirmation of the payment, not your card number.
Accounts
Sign-in is protected against abuse.
Customer sessions are verified on the server. Account actions are protected against cross-site request forgery, and sign-in and public forms are rate-limited.
Transport
Encrypted in transit, hardened by default.
Our sites are served only over HTTPS with HTTP Strict Transport Security, and send headers that stop content-type sniffing, restrict framing and limit referrer and browser-feature access.
Change control
Every change is reviewed and tested.
Code changes go through pull requests and automated test suites before they are merged. Release to production is a separate, explicitly authorised step, and secrets are never stored in source code.
Records
Public records show the minimum.
The record verifier publishes only what is needed to confirm a Donegal record. Findings, scores and customer evidence stay private, and file checks run in your browser without uploading the file.
How verification works →