Legal
Terms and Conditions
These terms set the basic rules for using Back Office, Context and their websites.
Effective 18 November 2026
About these terms
Build Context, Inc., a Delaware corporation, makes Back Office and Context. These terms apply to the public websites at runbackoffice.com and context.build, to Context at app.context.build, and to access to Back Office or Context software or services where no separate written agreement applies. “The service” means Back Office or Context, whichever you use.
If your organisation has a signed subscription, onboarding, data processing or other agreement with Build Context, that agreement controls to the extent it conflicts with these public terms. By using the website or service, you agree to these terms. If you use the service for an organisation, including by starting a team on Context, you confirm that you are authorised to accept these terms for it.
What Back Office and Context provide
Back Office helps accounting practices bring client, tax and workflow information together, including information from authorised third-party systems, and use it to understand and move work forward. Context helps a team run its work with an AI agent, in conversations, pieces of work and their documents, using the services the team connects. The exact features available depend on the customer setup, connected services and any written agreement.
Evaluation, early-access and onboarding features may change as the product develops. Any service levels, support commitments, pricing, data export commitments or other customer-specific promises apply only when they are stated in a written customer agreement.
Accounts and authorised use
You agree to:
- provide accurate account and organisation information;
- use the service only for lawful internal business purposes;
- keep your own account and authentication methods secure;
- connect only systems, accounts, clients and information that you are authorised to access and instruct us to process; and
- follow the usage and permission limits shown in the product.
If you start a team on Context, you are responsible for the people you add to it and the services you connect to it.
You must not use the service to gain unauthorised access, interfere with the service, introduce malicious code, evade access controls, misrepresent your identity or rights, or infringe another person’s rights.
Customer information and instructions
As between a customer and Build Context, the customer remains responsible for its source records, for deciding why its information is used, and for having the authority and lawful basis needed to provide that information and connect third-party systems.
Build Context handles customer information to provide and support the service and under the customer’s documented instructions. The applicable customer agreement and data processing terms govern ownership, confidentiality, return, deletion and other customer-specific handling. Our Privacy Policy explains the public-facing position in more detail.
Using HMRC connections
HMRC connections use the permissions approved during HMRC’s authorisation journey. You must connect an HMRC account only if you are authorised to act for the relevant person, business or clients, and you remain responsible for keeping that authority current. Do not share HMRC sign-in details with another person through Back Office.
Back Office is not HMRC or a government service, and HMRC does not endorse Back Office. HMRC may change or withdraw its APIs, permissions and service availability. Your use of HMRC services also remains subject to HMRC’s own terms.
Professional judgment and source information
Back Office and Context organise information and support workflow. They are not legal, tax, accounting or financial advice. Work and answers produced by AI can be wrong or incomplete. You are responsible for reviewing source records, checking the accuracy and completeness of information, applying professional judgment, and making or approving filings, payments, communications and other professional decisions.
Information from HMRC or another connected service can be delayed, incomplete or unavailable. Build Context does not control third-party services, and a link or integration does not make Build Context responsible for their content or operation.
Ownership
Build Context and its licensors retain rights in Back Office and Context, including their software, interface, documentation, integration methods and related materials. Customers retain their rights in the information they provide, subject to the permission needed for Build Context and its service providers to operate the service under these terms and any written customer agreement.
You may not copy, sell, sublicense or distribute Back Office or Context, or attempt to extract their source code, except where the law does not allow that restriction or Build Context agrees in writing.
Availability, changes and suspension
Unless a written customer agreement says otherwise, the website and early-access service are provided as available and without a promise that every feature will be uninterrupted or error-free. We may update the service and these public terms. The effective date at the top shows when this version took effect.
We may restrict or suspend access where reasonably needed to protect the service or other users, respond to a legal requirement, address misuse or non-payment, or where a connected provider makes the feature unavailable. A signed customer agreement may give more specific termination, continuity, liability and dispute terms. Nothing in these public terms excludes liability that cannot lawfully be excluded.
Privacy and contact
Our Privacy Policy explains how we handle personal information. Questions about these terms can be emailed to hello@help.runbackoffice.com. Include “terms” in your message so it can be directed appropriately.