Administration & compliance

GDPR and record-keeping for an MGA: what the platform does and what you do

Controller and processor, data minimisation, the GDPR card on every client, access and deletion requests, EU hosting, and what belongs in your privacy policy.

Updated 13 November 2026 · Written and reviewed by the Soldek team

Your MGA is the controller of the personal data in your environment: you decide what is asked, why and for how long. Soldek processes it on your instructions as a processor. The platform gives you the tools; the policy decisions are yours.

What the platform does

  • Keeps each tenant's data isolated, encrypted in transit and at rest, hosted and backed up in the EU.
  • Stores data as structured fields, so you can say precisely which data you hold about a person and export it.
  • Shows a GDPR card on every client record with consent, consent date and a retention date you set.
  • Records who changed what, and when, in the audit trail, which is itself part of your accountability evidence.
  • Never uses your data to train models, never sends it to a model provider and never shares it with other tenants.

What you do

Minimise
Ask only the questions you rate or decide on. Every row on the Questions sheet is personal data you will have to justify and protect.
Inform
Link your privacy policy on the online quote page (Settings → Distribution → Online quote page) and in your broker and client communications. Name the categories of data, the purposes, the retention period and the processors you use.
Record consent and retention
Use the GDPR card on the client record for consent where consent is the basis, and set the retention date from your retention schedule (typically the policy end plus the limitation period for claims in your jurisdiction).
Answer requests
For an access request, the client record shows everything you hold about the person: details, policies, quotes, claims, documents and notes; the full data export covers the rest. For erasure, check first whether a legal retention duty applies; if not, an administrator uses Erase personal data (GDPR request) on the GDPR card of the client record. The person's details and the insured persons on their policies are pseudonymised, their quotes lose name and contact data, notes are deleted and a portal login is switched off, while the policies, invoices, claims and bordereau figures stay intact for your books. The platform refuses while a policy is still active or pending, because the right to erasure does not override a running contract; cancel or let it expire first. The erasure is recorded on the audit trail, which is your confirmation to the data subject.
Sign the paperwork
A data processing agreement is part of the platform agreement; keep it with your records of processing.

Retention in practice

Most MGAs keep policy and claims records for the policy term plus the period in which a claim could still be brought or a regulator could still ask, and delete or anonymise after that. Put that period in your retention schedule, set the date on client records when a relationship ends, and review the clients whose date has passed each quarter.

Questions

Where is the data hosted?
In the EU, on certified cloud infrastructure, with daily encrypted backups kept in the same region.
Can we get a list of sub-processors?
Yes, on request, together with the data processing agreement.

See it running.

Book a demo and we show you the complete platform live. Still stuck? Write to hello@soldek.io.