Data processing agreement
This agreement governs the personal data that Independent Check Ltd processes on behalf of an adviser firm using Your Family Financial Hub. It is the contract required by Article 28(3) of the UK GDPR, and it applies from the moment the firm is given access to the product.
The firm is the controller — their clients are their clients, they decide what goes into a hub and why, and they answer to those clients for it. Independent Check Ltd is the processor: we run the software and act on the firm’s instructions. Where this agreement says “we” it means Independent Check Ltd, and “you” means the firm.
Independent Check Ltd is a private limited company registered in England and Wales, company number 08302295, registered office Celtic House, Caxton Place, Cardiff, Wales, CF23 8HA. We have not appointed a statutory data protection officer; data protection questions go to info@independentcheck.co.uk, and support to tom@independentcheck.co.uk.
1. What we process, and on whose instructions
Article 28(3)(a): we process personal data only on your documented instructions, including where we transfer it outside the United Kingdom, unless we are required to do otherwise by law — in which case we will tell you before processing, unless the law forbids us to.
Your instructions are your use of the product. Creating a household, uploading a document, reading it, asking the Companion a question, arranging a meeting: each is an instruction, and the software does that and nothing else with what it is given. Two things happen without anybody pressing a button, and they are part of the service you instruct: after a material change to a household the software looks for a topic an adviser may wish to raise (Annex C says what that sends), and each night it takes the backups in Annex B. We do not read, mine, sell, share or analyse your clients’ information for any purpose of our own, we do not use it to train any model, and the terms we rely on forbid our AI provider to (Annex C).
Annex A sets out the subject matter, the duration, the nature and purpose, the types of personal data and the categories of data subject, as Article 28(3) requires.
2. Confidentiality, and our own access
Article 28(3)(b): everybody we authorise to process your clients’ data is under a duty of confidence — by contract of employment or engagement where they are our people, and by the terms of the agreements in Annex C where they are a sub-processor.
The operator role is held by one named person: Thomas Cummings, Developer, at Independent Check Ltd. The operator can reach a firm’s data in the product in two ways, and uses either only to provide support the firm has asked for, to investigate an incident, or where the law requires it. Entering the firm is a deliberate act: it asks for the operator’s password and authenticator code again, then for a typed reason; it lasts at most sixty minutes; and going in, the reason and coming out are written to your firm’s own audit trail, labelled as the operator, where your firm admins can read them. Attaching an account to your firm as an adviser or firm admin gives it your data as your own staff have it, with none of those controls, and what it does is recorded under its own name; the attachment appears on your firm’s audit screen. The trail records changes, not reading: every change, document opened, export and preview, and the operator coming and going — never which records or pages somebody read. Anybody with access to the server and the master key could read data outside the application, and that access cannot be recorded by the application; it is held by the same one person.
3. Security
Article 28(3)(c): we take the measures required by Article 32. What those measures actually are is Annex B, written as claims about the software rather than as adjectives, so that you can check them.
4. Sub-processors
Article 28(3)(d) and Article 28(2): you give us general written authorisation to engage the sub-processors listed in Annex C. We will give you at least 30 days’ notice before adding or replacing one, and you may object within that period; if we cannot resolve your objection you may end this agreement and we will return or delete your data under clause 7.
Article 28(4): each sub-processor is bound by written terms imposing the same data protection obligations as this agreement, and we remain fully liable to you for their performance of them.
5. Helping you answer your clients
Article 28(3)(e): we will help you meet requests from your clients to exercise their rights, by appropriate technical and organisational measures and taking account of what we can see.
In practice most of this needs no help from us, which is the design. Access and portability: a household’s export is a file of everything the person exporting may see — every record, every original document and photo, the people and their details, goals, Companion conversations, the household’s accounts and its audit trail — with the machine-readable data behind it; and your staff can export everything about one person. Rectification: a reading is corrected by your adviser and the original kept as superseded; your staff can rename a person and a household; a person who signs in can move their account to a new email address, confirmed by a link sent to it. Erasure: your staff can delete a single document, which withdraws every reading taken from it, or a whole household, which removes its records, documents, files and memberships; deleted rows are overwritten in the database file rather than merely unlinked. We can erase an account on your instruction — its name, email address, password, second step and sessions — which leaves only an identifier behind. Who has seen or changed it: your firm admins can read, filter and export the audit trail on the product’s audit screen — every act in your households, the operator coming into your firm and leaving it, your firm’s whole file being taken, and, from the platform’s own trail, your people’s sign-ins, refused sign-ins and account changes, your team changing, this agreement being agreed, and what the operator does to your firm or to your people’s accounts. Where a request needs something the product does not do, write to info@independentcheck.co.uk and we will do it. A request made to us by one of your clients is passed to you without undue delay.
6. Helping you with security, breaches and assessments
Article 28(3)(f): we will help you comply with Articles 32 to 36 — security, breach notification to the ICO and to your clients, data protection impact assessments, and prior consultation — taking account of the nature of the processing and what is available to us.
If there is a personal data breach we will tell you without undue delay after becoming aware of it, with what we know: what happened, which categories and roughly how many people and records are affected, the likely consequences, and what we are doing about it. If we do not have all of it at once we will send what we have and follow up. Reporting to the ICO is yours to do, because you are the controller — our job is to put you in a position to do it inside your 72 hours.
7. Keeping, returning and deleting
How long data is kept is yours to decide. The product keeps what you put in it until your firm deletes it — a document, a household, or an account through us — and nothing in it expires by itself. Retention periods are a controller’s decision, and the tools to carry yours out are the ones in clause 5.
Article 28(3)(g): when the service ends, we will — at your choice — return your clients’ personal data to you or delete it, and delete the copies we hold, unless we are required by law to keep something. Returning it means your firm’s whole file: one download holding every household’s own export and your firm’s complete audit trail. A firm admin can take it from the audit screen at any time while your firm is active, before the end as well as at it. At the end your firm is suspended first, which stops anybody using it; once it is suspended nobody at your firm can sign in, so we take the file and hand it to you. Deleting is a deliberate act by the operator, which the software permits only once we have recorded that the file reached you, or 30 days after the suspension, whichever comes first — so a file not collected within those 30 days may not be available afterwards. Deleting removes your firm’s database, its audit trail and its documents from the server.
Backups hold deleted data for a while, and then do not. Each night’s backup is kept for thirty-one days and then removed by the storage’s own expiry rule (Annex B). Anything deleted — a document, a household, a whole firm — therefore stays in the encrypted backups taken before it was deleted until those backups expire, and is then gone. Until they expire those backups can be restored, which is what they are for, using the master key we hold.
One thing is deliberately kept while your firm uses the service, and you should know about it before you sign. The product keeps an audit trail of what was done in your firm and by whom: the act, the time, the person’s name as it stood, and for many acts the detail of the change — a value before and after, a name before and after. It is encrypted like the rest of your data, and the database refuses to change or delete a row of it, so neither we nor anybody using the application can rewrite it. It is kept after a household is deleted, because it is your record of what happened, which a regulated firm must be able to show. Erasing a person’s account does not rewrite the trail: the rows they appear in keep the name they had when the act was done. Your firm admins can read it, filter it and export it on the audit screen at any time (clause 5). It leaves the server only with your firm, at the end, as above. The platform’s own trail — sign-ins, account changes and the operator’s acts, including those on your firm — is ours and is kept after your firm is deleted; it names no household and holds none of its records.
8. Audits and information
Article 28(3)(h): we will give you the information you need to show that we are meeting these obligations, and allow and contribute to audits and inspections by you or an auditor you appoint. Give us reasonable notice; we will not charge you for the first audit in any twelve months.
9. Where the data is, and transfers out of the UK
Your clients’ records are held in Germany, on a server run by Hetzner, and the nightly backups are stored in the European Union by Cloudflare. The United Kingdom has made adequacy regulations for the European Economic Area, so holding them there is not a restricted transfer. What is on the server’s disk and in the backups is encrypted as Annex B describes.
Anthropic, who provide the AI model, process what Annex C lists in the United States. That transfer is made under Anthropic’s own data processing addendum, which incorporates the Standard Contractual Clauses together with the UK International Data Transfer Addendum issued by the ICO.
Brevo, who send the email, hold what they are given in the European Economic Area. The United Kingdom has made adequacy regulations for the EEA, so that is not a restricted transfer and no addendum is required for it.
Cloudflare is a United States company, and the backups it stores in the European Union are covered by its data processing addendum, which incorporates the Standard Contractual Clauses and the UK Addendum. What it holds is already encrypted, and the key is never given to it.
If a transfer mechanism we rely on is invalidated, we will move to another valid one or stop the transfer.
10. Term, changes and law
This agreement runs for as long as we process personal data for you. We may update it — to add a sub-processor, or because the law changes — and each version is numbered; this is version 4. When the version changes, every firm admin at your firm is sent one email saying so, with a link to this page, and no new client can be added until a firm admin agrees the new version; everything already in the product keeps working meanwhile. Agreeing records the version, the date, who agreed it and a SHA-256 fingerprint of the exact text they were shown, in a trail that cannot be edited; the fingerprint also covers the company details, names, addresses and version number inserted into the text. Nothing here reduces your rights or ours under the UK GDPR, and where this agreement and that legislation disagree, the legislation wins. It is governed by the law of England and Wales.
Annex A — the processing
Subject matter. Providing Your Family Financial Hub: holding a household’s documents and the records read out of them, and presenting them to the household, their adviser and whoever else the household has given access.
Duration. For as long as the firm uses the product, and then as clause 7 provides.
Nature and purpose. Storage; reading uploaded documents with an AI model to produce structured records; computing figures from those records; presenting them; a conversational assistant (the Companion) inside each hub; suggesting topics an adviser may wish to raise; messaging and scheduling between a household and their adviser; email; and backups. The purpose is the firm’s provision of financial advice to their own clients.
Types of personal data. Names, contact details and dates of birth; family relationships, including members who have died or are estranged; the contents of documents a household uploads — wills, pension and investment statements, policies, valuations, mortgage statements, correspondence — and the records read out of them, which include financial values, account and policy identifiers, property addresses and named beneficiaries, executors and attorneys; questions, answers, messages, meeting details, notifications and Companion conversations; photos a household uploads, re-encoded with their location and camera data removed; the audit trail in clause 7; and, for people who sign in, an email address, a password hash, an authenticator secret, sessions, and a record of refused sign-ins holding a keyed hash of the address typed and of the network address.
Special category data and identity numbers are processed when a document holds them. Reading a document records the details that change advice, and those include health information — smoking status, health habits, a condition stated in a policy — and identity numbers such as National Insurance and passport numbers. They are held under the health and identity permission categories, which nobody in a household sees unless they have been granted that category. The original document is not: it is filed under the one category that best describes it, and anybody granted that category, its uploader and all your firm’s staff can open it. A document may also hold other special category data the household chose to upload, such as a religious trust in a will. Nothing is used to sort, score or select anybody. Your lawful basis, and your Article 9 condition, must cover this processing.
Categories of data subject. The firm’s clients; members of their households and families, including children — as household members, beneficiaries or dependants — and people who have died; professionals a household gives access to, such as solicitors and accountants; and the firm’s own staff who use the product.
Annex B — technical and organisational measures
Separation. Every firm has its own database file and its own encryption key. There is no shared table of client records: a request resolves exactly one firm from the signed-in session, and reaching a second one is refused by the software rather than filtered out of a result.
Encryption. People’s names, figures, filenames, document contents, the sentences people write and the audit trail’s names and details — and every stored file — are encrypted with AES-256-GCM before they are written, individually rather than as a whole-disk measure. Some values are kept in plain text so the software can sort, filter and check them without opening anything: what kind of record each is, and its category, date, currency and approval state; ownership shares; how people are related, and whether a relationship is marked estranged or a person as having died; the names of staff recorded as having reviewed or approved something; and the name of whoever agreed this agreement for your firm. The key that opens a firm’s data is itself encrypted with a master key. The master key is supplied to the running application as a runtime secret, and is never written to a database, the container image, the source repository or a backup; a copy is held offline, apart from the server, so that losing the server does not lose the data. Data in transit is protected with TLS, and browsers are told to use nothing else.
Signing in. A password checked against a scrypt hash. An authenticator code as well is required of every member of firm staff and of the operator, who can reach nothing until they have set one up, and is offered to everybody else; a code is accepted once. Turning off your own second step needs a current code. A firm admin, or the operator, can turn off somebody else’s — for a lost phone — after confirming who they are again, and doing so ends every session that person had. Sign-in attempts are limited per email address and per network address, and ten wrong passwords in a row lock an account’s password sign-in until a new password is set through the emailed reset link, or the operator lifts the lock. Refused sign-ins are recorded. Sessions are stored only as a hash of the identifier in the cookie; firm staff and the operator are signed out after thirty minutes idle and twelve hours in all, and everybody else after seven days idle and thirty in all. A password set by somebody else ends every session the account had. Exporting, deleting a household or a document, changing the second step, changing the team, the operator entering a firm, every operator act on accounts and firms (creating a firm among them), approving or killing a law-change alert, and switching or running a scheduled job each ask for the password — and the code, where there is one — again first. Ending a stand-in never asks: leaving must never be blocked.
Access control. Inside a household, access is granted per person and per category, so a solicitor given sight of the legal papers cannot see what the family owns; the filter is applied when data is read rather than when a screen is drawn. A firm’s staff reach the households of that firm and no other. The operator’s access, attached accounts included, is as clause 2 says.
Accountability. Every change to a household’s records, every document opened, every export and every permission change writes a record naming who did it and when to your firm’s own trail, in the same database transaction as the act. Sign-ins, refused sign-ins, password and second-step changes, team changes and the operator’s acts on accounts and firms are written to the platform’s own trail, as they happen but not necessarily in the same transaction. The database refuses to edit or delete a row of either. Your firm admins can read, filter and export your firm’s trail in the product, together with the rows of the platform’s trail that concern your firm and its people.
The application itself. Every page is sent with security headers — a content security policy that forbids other sites from framing it and runs no script but the site’s own, whose only third-party allowance is embedded video from www.youtube-nocookie.com, player.vimeo.com and drive.google.com; strict transport security, no content sniffing, a strict referrer policy and a permissions policy denying camera, microphone and location. Uploads are identified by their content and capped on the server: five megabytes for a document, fifteen for a photo. Deleted database rows are overwritten, not merely unlinked. The server’s logs carry no names, email addresses or client content — an error is logged by its kind and a reference.
Resilience. Every night a consistent copy of every database and every stored file is taken and sent off the server to Cloudflare’s storage in the European Union, each night in its own dated folder. The application deletes no backup and cannot: each is kept for thirty-one days and removed by the storage’s own lifecycle rule. They are copies of already-encrypted files and do not contain the master key. Restoring is tested by an automated drill each month, which restores the newest backup, decrypts it and compares it with the live data, and reports the result to the operator.
Assurance. The rules above are enforced by automated checks that run before any change is released, including checks that a household’s data cannot be reached without the right permission and that nothing sensitive is written unencrypted.
Annex C — sub-processors
Four, and no others. Each is engaged under written terms imposing the obligations in this agreement, and we remain liable to you for them.
Anthropic PBC — the AI model. This is where a client’s papers leave our systems and it is the thing you most need to have told your clients about. What each use sends:
Reading a document, when somebody asks for it to be read: the document’s text, with its lines numbered — or the file itself: a photograph as it is, and a PDF whole, every page of it, when any one page could not be read on our own server or while the server’s PDF reader is unavailable. With it: the fixed list of permission categories a record may be filed under; the names of the people the hub already knows, and which of them is its main subject; the record types it already uses, each with its label, its category and the fields it is expected to have; and up to sixty questions it has already asked, each with whether it is waiting, answered or set aside (the questions, never the answers). Not the filename.
The Companion, when somebody writes to it: their message, and their own earlier conversation with it — only theirs, and only the last eight thousand characters or so; their name, their role, their permission level and which categories they may see; the hub’s name and kind; its page and section titles and what each block on them shows; each record they may see as its type, category, approval state and label; the names of its people, with the internal identifier each has in the product; how many gaps and open questions there are, and the list of gaps that person may be asked about; and, only when they are the hub’s owner or its adviser, the standing layout instructions the household has written. No record’s value or date and no cited sentence — though a label, a title or a person’s own words may contain one.
Opportunities, run automatically after a material change to a household — a document read, a record added or approved, ownership set, a person or relationship added, a person marked as the account holder or no longer — and at most once every fifteen minutes: the same outline of the household the Companion is sent, as seen by an adviser at your firm — it includes the name of the adviser whose view it runs as, and no conversation — and the names of the calculations available. No record’s value or date.
Research and verification of changes in the law: official public sources only, and no client data at all.
The terms we rely on, as Anthropic published them when we checked on 21 September 2026: its Commercial Terms of Service (effective 17 June 2025) say that “Anthropic may not train models on Customer Content from Services” and incorporate its data processing addendum; its privacy centre (updated 1 July 2026) says it deletes API inputs and outputs within thirty days of receipt or generation, except where it must keep them longer to enforce its usage policy — up to two years for content flagged as a violation — or where the law requires it. We have no zero-data-retention arrangement with Anthropic. These are Anthropic’s commitments, not something the software can enforce. Processed in the United States under that addendum, which incorporates the Standard Contractual Clauses and the UK International Data Transfer Addendum.
Hetzner Online GmbH — running the server, in Germany. The data on its disks is encrypted as Annex B describes.
Cloudflare, Inc. — storing the nightly copies described in Annex B, in its R2 storage, restricted to the European Union. They hold encrypted files and are never given the key.
Brevo (Sendinblue SAS) — sending email. They receive the address, the sender’s firm name, the text of what is sent and, on a digest, the adviser’s email address as the one a reply goes to; and what is sent is deliberately thin: an invitation into a hub (naming the inviter’s first name and the firm, never the household), a password reset link, a link confirming a new email address, a notice to firm admins that this agreement has a new version, a digest saying how many things are waiting with a link and nothing about which household — sent only while we run it, and each person can turn it off — a note to a household that their adviser’s firm has put something new on their hub, with a link and none of what it says, and to an adviser how many of their households have changed their records, where the firm has switched either on (each person can turn these off too) — and reports to the operator on scheduled jobs, which carry counts and codes and no client data. Sent one at a time through their transactional interface and never as a marketing campaign, so nothing your clients receive from us is tracked, profiled or added to a mailing list. Held in the European Economic Area, which the United Kingdom has adequacy regulations for.
This list changes only as clause 4 says: with at least 30 days’ notice, and a new version of this agreement for you to agree. Write to info@independentcheck.co.uk with any question about it.
Back to the hub