Trust
Trust center
Last updated: November 16, 2026
Privacy and security facts for an organization deciding whether to keep client and matter information in Signal & Line, and for the accreditation, certification and professional-duty work that decision brings with it. The service facts are those published for the product on October 7, 2026.
This page is not a certificate, not an auditor's report, and not legal advice. Signal & Line does not hold Cyber Essentials, Cyber Essentials Plus, ISO/IEC 27001, ISO/IEC 27701 or SOC 2. Nothing here discharges a firm's, or a regulated person's, own duties.
On this page
- How to use this page
- Before the service opens
- Who this covers
- Certifications
- This website
- Cookies
- Who decides
- What the service holds
- Who else processes it
- Transfers outside the UK
- How long it is kept
- Where the service runs
- Access and sign-in
- Encryption
- Backups and recovery
- Separation and logging
- Incidents and rights
- AI
- Supplier questions
- Your own assessment
- Professional duties
- Chambers
- Advice agencies
- Lawyer directory
How to use this page
There are two different things. This website, including the waiting list, is described in the privacy notice. The service at legalworkflows.co.uk is the workspace. This page covers both, so a privacy notice, a record of processing, a data protection impact assessment or a supplier questionnaire can point at the right part.
These pages are not the contract. A firm that stores client files needs a processor agreement under UK GDPR Article 28, agreed with us separately. We have not published that agreement on this website.
The service is not open to new organizations yet. What follows is what we can state today, including the gaps. It does not say the gaps are acceptable.
Before the service opens
We will not take a firm's live client files until a processor agreement is in place and the database backup gap on this page is closed. We will not send a live client file to a model while our AI assessment remains unaccepted. A plan to close a gap is not the same as closing it.
There is no accessible backup of the database today. That is a known gap. The planned replacement is automated backups kept for 35 days, in London. The gap is not closed until those backups exist.
We have opened our own data protection impact assessment for using AI on a firm's files. It has not been accepted. It is not a substitute for the firm's own assessment.
We have not published a data protection registration number. Before the service is opened to organizations, we will reassess whether a data protection fee is due and, if it is, publish the number here. No number on this page means that reassessment has not been published.
Who this covers
These facts are for one service. They are the same for a law firm, an in-house legal team, a chambers, and an advice agency, including a Law Center and a provider of money or welfare advice. There is not a separate region, backup or certificate for each.
- Law firms.
- In-house legal teams, where the employer is the organization that decides the purposes of the file.
- Chambers.
- Advice agencies, including Law Centers and providers of money or welfare advice.
A chambers pack, for instructions, diaries, fee notes and aged debt, and a money and welfare advice pack are on the roadmap. They are not part of the workspace. Keeping a file here does not provide them. The product page lists those packs with the rest of what is not available yet.
Certifications
None of the following is held. No assessor's certificate or report is published. A document in a repository is not a certificate: a certification body certifies an organization after an audit.
- Cyber Essentials, and Cyber Essentials Plus. Not held. This is the certification we intend to seek first, and then Plus.
- ISO/IEC 27001 and ISO/IEC 27701. Not held. We intend to seek 27001 after Cyber Essentials Plus, and 27701 after that.
- SOC 2, Type I or Type II. Not held. We intend to seek it on the same scope as ISO/IEC 27001, after that certificate.
Intending to seek a certificate is not progress an assessor can rely on. Until a certificate is published, the answer to “are you certified?” is no. An organization's own certificate is its own. Our not holding one does not, by itself, pass or fail that assessment.
This website
Fraser Matcham, trading as Signal & Line, is the controller of personal data collected through this website. He acts as a sole trader. We have not published an ICO registration number or a postal address. The email address on this page is the contact for privacy requests.
The waiting list asks for a name, a work email, the organization, a role, a size band, and a record that consent was given. The lawful basis is that consent. The details are emailed to us through Amazon Web Services in London and kept in a Google inbox. Vercel hosts the website and may process technical data, including an IP address, outside the UK. The full categories, retention periods and rights are in the privacy notice. We do not sell waiting-list data or use it for advertising.
An email about the waiting list or the launch says it is from Signal & Line and how to stop further emails. The address is not used for any other marketing. Consent covers a sole trader, and anyone else who is an individual subscriber, even when the address looks like a work address. We do not treat a work address as permission on its own.
We have not published a data protection registration number. Before the service is opened to organizations, we will reassess whether a data protection fee is due and, if it is, publish the number here. No number on this page means that reassessment has not been published.
Cookies
This website sets no cookies. It does not use analytics or advertising trackers.
The service sets a cookie to keep a person signed in. It is strictly necessary, so there is no consent banner for it, and JavaScript on the page cannot read it. The Word add-in uses its own sign-in cookie for the same reason. The service does not use analytics or advertising cookies.
Who decides
When an organization stores its client and matter files, that organization is the controller of that material. Fraser Matcham is the processor. He does not have a direct relationship with the people in those files. They ask the organization, not us, when they want to use their rights.
For a law firm, the firm is the controller. For an in-house team, the employer is. For a chambers, the controller is whoever decides the purposes of the file, often the barrister for their own practice, or the chambers where it holds the records. This page does not decide which of those it is. For a Law Center or another advice agency, the agency is the controller of the files it keeps for the people it advises.
For the accounts of people who sign in — the email address, the sign-in, and membership of an organization — Fraser Matcham is the controller. A client is not in that category unless they also have a login.
Files an organization uploads can contain special-category data, criminal-offense data, and material covered by legal professional privilege, because the organization put them there. The organization decides what to upload. Privilege is not lost by calling the material personal data, and a transfer of it is the organization's problem as well as a data protection one.
What the service holds
- Files the organization uploads, text taken from them, and generated documents.
- Chats with the assistant, tabular reviews, workflows, tasks and matter records.
- An audit trail, which can include a file name and a short excerpt of a message.
- Account data: email address, organization role, and the secret for an authenticator app, held by the sign-in service.
There is no automatic expiry of file content. It stays until the organization, or a person with the right to, deletes it. A signed-in person can export their account data as an archive with a tamper-evident manifest, and can delete their account. Deleting an account does not delete material that belongs to the organization. Where matters are switched on, a matter admin can place a matter on legal hold, which blocks destroying it and deleting what it holds.
Who else processes it
These parties are on the path for every deployment of the service.
- What for
- Hosting, object storage, encryption keys, secrets, logs and the network in front of the service.
- Where
- Storage and compute in London (eu-west-2). HTTPS may terminate at an edge in North America or Europe, which does not store client files.
- What is sent
- Application traffic, files, secrets and operational logs.
- What for
- Transactional email from the service, such as confirming an address or resetting a password.
- Where
- London (eu-west-2).
- What is sent
- The email address and the message. Not document content, prompts or matter names.
- What for
- The database and the sign-in service, until we replace them with a database we run ourselves in London.
- Where
- United Kingdom (London).
- What is sent
- Account records, document details, chats, reviews, access grants and the audit trail.
A language-model provider receives prompts and document text only when that provider is configured and a person sends the work. Which of them is in use depends on the keys the deployment has.
- What for
- Claude models, when an Anthropic key is configured.
- Where
- United States, unless a UK or EU endpoint is contracted.
- What is sent
- Prompts and document text for the assistant, a tabular review, or a title.
- What for
- Gemini models, when a Gemini key is configured.
- Where
- United States, unless a UK or EU endpoint is contracted.
- What is sent
- Prompts and document text for the assistant, a tabular review, or a title.
- What for
- GPT models, when an OpenAI key is configured.
- Where
- United States, unless a UK or EU endpoint is contracted.
- What is sent
- Prompts and document text for the assistant, a tabular review, or a title.
- What for
- A router to other models. Not for matter-linked work unless the organization has allowed that destination.
- Where
- United States. The model behind the router varies.
- What is sent
- Prompts and document text, when that route is used.
- What for
- A gateway to other models. Not for matter-linked work unless the organization has allowed that destination.
- Where
- Depends on how Vercel routes the request.
- What is sent
- Prompts and document text, when that route is used.
- What for
- OpenCode models, when an OpenCode key is configured.
- Where
- OpenCode's published endpoints, unless a UK or EU endpoint is contracted.
- What is sent
- Prompts and document text for the assistant, a tabular review, or a title.
- What for
- An OpenAI-compatible model added by configuration.
- Where
- Wherever that configuration points.
- What is sent
- Prompts and document text, when that destination is used.
- What for
- A model running on the operator's own host, when configured.
- Where
- That host. No third party if the host is inside our network.
- What is sent
- Prompts and document text, kept on that host when it is inside our network.
- What for
- Case-law search and citation lookup, when those tools are used. Not a language-model vendor.
- Where
- United States.
- What is sent
- The query and the citations. Sent only when the tool is used.
- What for
- A provider key or a tool the firm configures itself.
- Where
- Unknown until the address is recorded. Treat it as a transfer outside the UK until it is shown not to be.
- What is sent
- Whatever the firm sends there, which can include prompts and document text.
Not current processors of client files:
- Resend. Transactional email from the service goes through Amazon SES.
- Cloudflare R2. Files are stored in Amazon S3 in London.
Transfers outside the UK
Files and account data we store stay in London. Public HTTPS ends at a content-delivery edge in North America and Europe. Storage and compute stay in London (AWS eu-west-2). The certificate used at the edge is issued in us-east-1 and does not hold client files. Model providers are not in the UK unless a UK or EU endpoint has been contracted and the organization is limited to it. The honest default is the United States.
The service is set up to prefer a UK or EU model endpoint, with no retention of prompts by the provider, and to refuse an unvetted destination for work tied to a matter. Those settings are not yet enforced. Until they are, treat a model call as able to send text outside the UK.
A transfer of personal data outside the UK needs a lawful mechanism under UK GDPR Chapter V, such as the UK Extension to the EU–US Data Privacy Framework where the provider is certified, or the UK International Data Transfer Addendum. Which mechanism applies to a provider is a term of that provider's contract. This website does not publish the mechanism for each provider.
How long it is kept
How long a stored file can be restored, and the database gap, are under backups and recovery. There is no accessible backup of the database today. That is a known gap. The planned replacement is automated backups kept for 35 days, in London. The gap is not closed until those backups exist.
An organization that needs content deleted on a fixed schedule has to agree that with us. The service does not enforce one. Soft-deleted details of a file, such as its name and a fingerprint of its contents, can remain after the bytes are gone.
Where the service runs
Operator-controlled storage and compute are in London (AWS eu-west-2). Public HTTPS ends at a content-delivery edge in North America and Europe. Storage and compute stay in London (AWS eu-west-2). The certificate used at the edge is issued in us-east-1 and does not hold client files.
Access and sign-in
A password must be at least 10 characters. There is no forced expiry; a person can change their password at any time, and refresh tokens are rotated. Each person can set up an authenticator app. An organization admin can require that second factor, and turning the requirement on or off needs the admin's own verified second factor. While it is required, matter pages refuse a session that has not completed it, and a member who has not set one up is sent to do so first. A member who has set one up must still use it for matter pages whenever the organization holds a matter or is creating one, even if the organization has not required it of everyone. If that policy cannot be read, matter pages are refused in the same way.
There is no published single sign-on with Microsoft or SAML. The Word add-in signs in with its own cookie, which page scripts cannot read.
Encryption
- TLS 1.2 or newer on every public connection.
- Files in object storage are encrypted with a key we manage (S3 SSE-KMS, customer-managed key).
- The database is hosted in London. Encryption at rest is the supplier's until we replace it with a database we run ourselves in London, which will also be encrypted at rest.
Backups and recovery
Files stored as objects are copied within seconds of a write to a separate, write-locked bucket in London. A replaced version is kept for at most one day in the live bucket, and for 35 days in the replica. Restoring one file takes minutes; restoring many takes longer. Object restore was last drilled on September 18, 2026.
There is no accessible backup of the database today. That is a known gap. The planned replacement is automated backups kept for 35 days, in London. The gap is not closed until those backups exist.
Because the database has no accessible backup, there is no recovery point for matter rows, chats and account records today, and no recovery time we can state. Object restore does not bring those rows back.
Separation and logging
One customer's data is not readable as another's. The build fails if a route can reach stored data without establishing whose it is. Request logs are written so they do not include the body of a request, its headers, the query string, an IP address or an email address.
Organization admins can review an audit trail of activity and export it as a CSV file. A project can be exported with an integrity manifest, so the person who receives it can check each file.
Incidents and rights
Where we are the controller and we become aware of a personal-data breach that is likely to result in a risk to people, we tell the Information Commission without undue delay and, where feasible, within 72 hours of becoming aware of it. Where that breach is likely to result in a high risk to people, we also tell them without undue delay. Those 72 hours are our clock for this website, the waiting list, and sign-in accounts. They are not a firm's clock.
If we become aware of a personal-data incident that affects a firm's files, we tell that firm, as controller, without undue delay, and in time for the firm to meet its own clock. Seventy-two hours is the firm's clock under UK GDPR Article 33, not ours.
We have not published an independent penetration test. Container images are scanned for known vulnerabilities when they are built. They are not continuously re-scanned between deploys.
For personal data on this website, the rights and the one-month reply time are in the privacy notice. For an organization's client files, the request belongs to the organization. Tell us what you need and we will help you meet it. There is no per-person search inside a matter that would list every place one individual is named.
A complaint that we have not complied with the UK GDPR, where we are the controller, follows the data protection complaints procedure. We acknowledge it within 30 days. You can also complain to the Information Commission, which is still known as the ICO, at ico.org.uk/make-a-complaint.
AI
The service has no training pipeline. We do not use a firm's prompts or documents to train models, and keys we hold do not grant a provider that right. If a firm supplies its own provider key, or connects a tool of its own, that provider's terms are the firm's, not ours.
The service is set up to prefer a UK or EU model endpoint, with no retention of prompts by the provider, and to refuse an unvetted destination for work tied to a matter. Those settings are not yet enforced. Until they are, treat a model call as able to send text outside the UK.
We have opened our own data protection impact assessment for using AI on a firm's files. It has not been accepted. It is not a substitute for the firm's own assessment.
A draft is not saved until a person saves it. That is a product rule, not a finding that the processing is low risk. The assistant's output is not legal advice, and the organization decides whether a privileged file should be sent to a model at all. The providers, and where they are, are in who else processes it.
Supplier questions
These are the questions an organization is often asked about a supplier when it renews Cyber Essentials, ISO/IEC 27001 or SOC 2, or when it updates its own data protection record. The answer is the position today, not a control mapped onto a clause.
- Answer today
- Files and the database are in London. Public HTTPS may pass through an edge in North America or Europe, which does not store client files.
- Answer today
- TLS 1.2 or newer on every public connection. Files in object storage are encrypted with a key we manage (S3 SSE-KMS, customer-managed key). The database is hosted in London. Encryption at rest is the supplier's until we replace it with a database we run ourselves in London, which will also be encrypted at rest.
- Answer today
- Amazon Web Services, Amazon SES and Supabase are on every deployment. A language-model provider receives text only when that provider is configured and someone uses it. The list is on this Trust Center.
- Answer today
- The service has no training pipeline. We do not use a firm's prompts or documents to train models, and keys we hold do not grant a provider that right. If a firm supplies its own provider key, or connects a tool of its own, that provider's terms are the firm's, not ours.
- Answer today
- A password must be at least 10 characters. There is no forced expiry; a person can change their password at any time, and refresh tokens are rotated. Each person can set up an authenticator app. An organization admin can require that second factor, and turning the requirement on or off needs the admin's own verified second factor. While it is required, matter pages refuse a session that has not completed it, and a member who has not set one up is sent to do so first. A member who has set one up must still use it for matter pages whenever the organization holds a matter or is creating one, even if the organization has not required it of everyone. If that policy cannot be read, matter pages are refused in the same way.
- Answer today
- Files stored as objects are copied within seconds of a write to a separate, write-locked bucket in London. A replaced version is kept for at most one day in the live bucket, and for 35 days in the replica. Restoring one file takes minutes; restoring many takes longer. Object restore was last drilled on September 18, 2026. There is no accessible backup of the database today. That is a known gap. The planned replacement is automated backups kept for 35 days, in London. The gap is not closed until those backups exist.
- Answer today
- If we become aware of a personal-data incident that affects a firm's files, we tell that firm, as controller, without undue delay, and in time for the firm to meet its own clock. Seventy-two hours is the firm's clock under UK GDPR Article 33, not ours.
- Answer today
- No. Cyber Essentials, Cyber Essentials Plus, ISO/IEC 27001, ISO/IEC 27701 and SOC 2 are not held. No assessor's certificate or report is published. We intend to seek Cyber Essentials first, then Plus, then ISO/IEC 27001, then SOC 2 on the same scope. Intending to seek them is not the same as holding them.
- Answer today
- We have not published an independent penetration test. Container images are scanned for known vulnerabilities when they are built. They are not continuously re-scanned between deploys.
- Answer today
- Signal & Line does not hold client money, and it does not operate a client account. A records-only ledger is on the roadmap. It would record receipts and payments. It would not send them.
Your own assessment
An organization using AI on client files should expect to need its own data protection impact assessment, and may need to update its privacy notice and its record of processing. This page does not complete that work. The usual remaining work is:
- Decide the lawful basis for the organization's own processing, and for any special-category data in the file.
- Tell clients, in the organization's privacy notice, who the processor is and whether text is sent to a model provider.
- Tell staff if their names and messages are in the audit trail, and if they are screened once that feature exists.
- Record the international transfer if model text leaves the UK, and the safeguard the contract uses.
- Record the database backup gap until it is closed.
- Decide what may be uploaded, including privileged material, and who may turn a model on.
- Agree the processor contract before live client files are stored.
What we can give an assessor today is this page: location, encryption, access, sub-processors, backups including the database gap, incidents, and the AI position. We cannot complete the organization's assessment, write its statement of applicability, or sign its system security plan.
Conflict checks, client due diligence and sanctions screening are not available yet. When they are, they will support the organization's own procedures. They will not replace them, and they will not replace a money-laundering reporting officer or the organization's own decision on a match. The product page says what is still being built.
Professional duties
Using Signal & Line does not discharge duties under the SRA Standards and Regulations, the BSB Handbook, the Immigration Advice Authority's code, the rules of any other regulator, or the conditions of a funder or a quality mark. Confidentiality, supervision, authorization to advise, and the choice of systems stay with the regulated person or body.
- Solicitors Regulation Authority. Confidentiality, the firm's arrangements for its systems, and supervision stay with the firm. An audit trail, recorded workflow runs, matter-level access and two-factor sign-in are tools a firm can use. They are not a COLP's or a COFA's compliance. Where an advice agency is also a regulated firm, this point applies to it as well.
- In-house legal teams. The employer's confidentiality, its policies and its own assurance stay with the employer. A solicitor working in-house remains individually regulated. Nothing here certifies the employer.
- Other regulators of authorized persons, including CILEx Regulation, the Council for Licensed Conveyancers and the Intellectual Property Regulation Board, are in the same position. The regulated person or body remains responsible.
Signal & Line does not hold client money, and it does not operate a client account. A records-only ledger is on the roadmap. It would record receipts and payments. It would not send them.
Chambers
Bar Standards Board. A barrister's confidentiality and practice duties under the BSB Handbook stay with the barrister. Where the chambers is a BSB entity, the entity's duties stay with it. The workspace does not clerk a chambers. Instructions, diaries, fee notes and aged debt are a planned pack, and they are not part of the workspace.
Advice agencies
Immigration Advice Authority, and the agency's own duties. A Law Center, and a provider of money or welfare advice, keeps its own duties. Where the work is immigration advice, the Immigration Advice Authority's code stays with the adviser unless a legal exemption applies. This workspace is not a check on the quality of advice or on an adviser's registration. Where the work is reserved to an authorized person, that person's regulator still applies. Where debt advice is a regulated activity, the Financial Conduct Authority's rules and the agency's authorization stay with the agency. A funder's conditions, and any quality mark the agency holds, stay with the agency. A legal aid pack and a money and welfare pack are planned and are not part of the workspace. Keeping a file here does not make a legal aid claim, complete a budget, or meet a contract with a funder.
Lawyer directory
A separate site, Find a Lawyer, lists information taken from the SRA and BSB registers. An objection or a correction is made there, on the profile, not in this workspace. An upheld objection removes the listing. Details that come from a regulator are corrected at the regulator.
Questions about the trust center: frasermatcham@gmail.com.