Compliance for Employer Programmes
An employer can fund estate planning as a benefit without ever seeing what an employee writes. This guide explains where that boundary sits, what each side can see, and what happens when someone leaves. Employer Programmes were previously called Corporate Programmes.
Last reviewed
What an employer cannot see
The employer-employee boundary is architectural rather than a matter of policy: the personal estate data sits in a different place from the programme data, so there is no administrator screen that could show it and no setting that could turn it on.
- No access to estate data: will content, asset registers, uploaded documents and family details are never visible to HR or to a programme administrator
- Aggregate adoption only: an administrator sees seat counts, activation rates and programme engagement. They never see who used what, and adoption figures for any group of fewer than five employees are suppressed so a small team cannot be re-identified
- Reporting keys stop at the roster: corporate API keys read aggregate reporting and each employee’s activation status, and no key scope reaches will, vault or estate content
If you are the employee here
Nothing you write is reported back to your employer, in summary or in detail. What your employer sees is that a seat was activated, never what was done with it.
Two audit layers, never crossed
Both sides of a programme need an audit trail, and they need different ones. Keeping them separate is what makes the boundary above survive contact with a real audit request.
Programme audit, for administrators
Seat activations and deactivations, invoice events and administrator role changes. Visible to corporate administrators only, and kept for seven years.
Personal audit, for the employee
Reads, changes and shares of the employee’s own data. Visible only to that employee, with retention following the consumer privacy policy, and never rolled up into the programme view.
Paperwork available at onboarding
Procurement paperwork is available during onboarding rather than chased after signature. What follows describes the documents on offer, not what any organisation is required to hold.
- Data processing agreement: a published template for GDPR Article 28 (UK GDPR Article 28 for UK customers), with a signed copy on request. It includes sub-processor flow-through and Standard Contractual Clauses, joint-controller terms (Art. 26) apply where relevant, and the terms are negotiable
- Named sub-processors: a short published list, each bound by written confidentiality and data-protection contracts that flow through to employees
- Named-region data residency: data is stored in the location named for each sub-processor on the published list, and we do not move data between regions without contractual notice
- No jurisdiction scoping: an Employer Programme is not scoped by jurisdiction. Each employee creates a will in the jurisdiction they choose, from those where will generation is supported
Single sign-on without widening access
SAML 2.0 and OIDC are both supported, with just-in-time provisioning and group-based seat assignment.
Connecting an identity provider changes who authenticates the user. It does not change who can read the estate data, which lives in a separate identity space. Removing the connection later does not hand that data to the employer either: it ends the sign-in route, not the ownership.
What happens when someone leaves
A benefit that evaporates with the job is not much of a benefit for a document meant to last decades, so the seat and the account come apart cleanly.
- The personal account survives: the corporate seat ends and the account continues on a personal subscription or the free tier. A personal subscription held before joining is paused while the seat is active and resumes when it ends
- The evidence pack is preserved: identity verification, the witnessing record and the audit trail stay accessible to the former employee after the seat ends
- The employer cannot transfer or delete it: the personal data the employee created cannot be reassigned to or deleted by the corporate buyer
This page describes our platform, not the law
Nothing here tells you what your organisation is required to do, what a regulator expects of a benefits programme, or how employment law applies to a leaver. Those rules differ from place to place and change.
Related topics
Can’t find what you’re looking for?
Our support team is here to help. Contact us and we’ll get back to you as soon as possible.
Contact us
