Compliance · United Kingdom

A practical starting point for your compliance review.

Evaluate how Allarin fits your firm's confidentiality, data protection and billing governance requirements. Product controls, contractual commitments and independent assurance are different parts of that assessment.

Last reviewed: 17 November 2026

Start with the roles in the processing relationship.

A firm decides why its client and matter information is used and what professional duties apply to it. A software provider's processing role should be documented for the service it supplies. UK GDPR obligations cannot be assessed from a product feature list alone.

Identify the information involved, the intended users, the purpose of each enabled feature and the agreements governing the relationship. Include billing narratives and supporting documents, which can contain more sensitive information than the invoice total itself.

Review the operational controls.

Examine account administration, role assignments, access windows, review responsibilities and portal-sharing settings. A control is useful when the firm knows who administers it and how it will be reviewed when a person's role changes.

Use representative records to assess approval history, comments and the visibility of billing decisions. Confirm that the resulting process supports the firm's policy rather than relying on the presence of an audit-style screen as proof of complete regulatory compliance.

  • Agree which roles can prepare, review, approve and release billing work.
  • Review the recipient and access period before sharing an invoice.
  • Document the process for access changes and client requests.

Set out the data-processing arrangements.

For a UK deployment, assess the applicable UK GDPR and Data Protection Act 2018 requirements. A processor agreement should address the relevant instructions, confidentiality, security, subprocessors, assistance and information-handling obligations for the relationship.

Confirm retention, return or deletion arrangements and any international-transfer safeguards. Review enabled AI processing separately, including what information is transmitted and the relevant provider terms. Do not assume that selecting a product feature establishes a particular hosting region or retention configuration.

Ask for evidence with a defined scope.

A certification or assurance report should identify the entity, systems, period and controls it covers. An infrastructure provider's report does not automatically certify the application built on that infrastructure.

This page does not assert that Allarin holds a SOC 2 report, ISO certification, regulator approval or a professional-body endorsement. Request the current evidence relevant to your procurement process and confirm any contractual commitment in writing.

Use a focused evaluation checklist.

Bring operational, security and privacy stakeholders into the evaluation early. Agree the minimum evidence needed to make a deployment decision, then test the actual billing scenarios and information flows within that scope.

Record any requirements that still need confirmation before rollout. A successful demonstration shows how a process can work; acceptance of a production service also depends on the agreed controls, terms and responsibilities.

  • Map data categories and confidentiality requirements.
  • Review roles, sharing and approval responsibilities.
  • Confirm provider, transfer and retention arrangements.
  • Agree incident coordination and the route for rights requests.
  • Validate the required evidence and contractual scope.

Continue exploring

Have a question about this information?

Use the relevant enquiry route to discuss your account, a privacy request or the requirements for an evaluation.

Discuss your requirements