Service scopeWhat the product is for
These terms are written for firms using Entity Watch in real operations. The product is meant to support a professional workflow around Companies House monitoring and verification coordination, not to blur responsibility for judgment calls.
Business workflow product Entity Watch helps teams monitor Companies House changes, organize follow-up work, track verification progress, and report on status inside a shared workspace.
Not a substitute for professional judgment Nothing in the service transfers legal, regulatory, filing, or customer due diligence responsibility away from the customer. Firms remain responsible for the decisions they make.
Public source material remains public source material The product uses Companies House public-register data. Customers are paying for workflow, alerting, coordination, and visibility around that source material rather than for exclusive ownership of the source itself.
Built for internal business use The intended audience is accountants, ACSPs, corporate services teams, and similar operators using the service inside a legitimate business process.
Customer responsibilityUse the platform as a control layer, not a replacement brain
Professional customers usually want clear boundaries more than legal theater. The practical point is simple: the software should support a process that already has accountable owners.
You decide how to act Customers remain responsible for filings, client communications, deadline interpretation, escalation decisions, blocker management, and the final view on what a given change means.
Use accurate information Account details, workspace setup, and team membership information should be kept accurate enough for billing, support, access control, and operational follow-up to make sense.
Only use data you are entitled to use If you enter private notes, client-related information, or internal workflow detail into the service, you remain responsible for making sure your firm is entitled to handle that information in the platform.
Do not use Entity Watch as your sole control Alerts and workflow status should support an internal review process. They should not be treated as the only control standing between your team and a regulated obligation.
Access and securityTeam access should be managed like a serious business tool
A large share of avoidable risk comes from weak access hygiene. These terms therefore put straightforward expectations on account use and team administration.
Protect credentials Users should keep passwords private, avoid sharing accounts, and treat sign-in access as something personal rather than communal.
Use roles appropriately Owner, admin, member, and viewer access exist for a reason. Customers should assign the lowest level of access that still allows a person to do their work.
Remove old access promptly If a team member leaves, changes role, or should no longer be in the workspace, the customer is responsible for removing or reducing that access without delay.
Use two-factor where appropriate The product supports two-factor verification for local accounts. Firms handling sensitive workflow should enable it where that fits their internal policy.
BillingCommercial terms should stay clear and predictable
The billing model is meant to be understandable in procurement and day-to-day use. Plan boundaries should be visible in the product rather than hidden in fine print.
Plans define access to paid features Seats, tracked company limits, verification access, and other paid capabilities follow the active workspace plan shown in the service.
Payments are processed by Stripe Stripe handles payment details and subscription mechanics. Entity Watch keeps the billing identifiers and status needed to operate the workspace plan, rather than storing raw payment card data itself.
Trials, upgrades, and renewals follow the live billing state If a workspace moves between trial, free, or paid access, the current state shown in the product and linked billing records controls what the workspace is entitled to use.
Billing questions should be raised early If a customer sees a billing problem or needs clarification before rollout, the correct route is to use the support page so the issue can be reviewed against the actual workspace and subscription state.
Data and confidentialityA practical position on customer data
Professional customers expect a sensible answer here. Entity Watch does not need to own customer workflow data in order to operate the service, and it should not pretend otherwise.
Your firm keeps ownership of its internal workflow content Entity Watch does not claim ownership over your watchlists, internal notes, verification workflow detail, or client-facing operational decisions just because they are entered into the workspace.
Entity Watch may use data to operate and support the service Workspace and account data may be used to run alerts, provide support, secure accounts, process billing, troubleshoot issues, and improve product operations.
No ad-tech resale posture The service is not positioned as an advertising network or data-broker platform, and private workspace data is not sold for those purposes.
Do not misdescribe the product to third parties Customers should not present Entity Watch as legal advice, filing authority, or a passport and driving-licence vault when the product is not being sold for those purposes.
AvailabilityReasonable boundaries on what the service can promise
Respected terms are not written to dodge responsibility. They are written to describe the real operating boundary of a service that depends on infrastructure providers and public data sources.
The service depends on upstream providers Hosting, database, payment, email, Companies House availability, and the OpenAI-backed assistant path when used all sit partly outside the direct control of Entity Watch.
No promise of uninterrupted or error-free delivery Entity Watch aims to operate with reasonable care, but it cannot promise that every alert, sync, assistant response, or upstream dependency will be available instantly or perfectly at all times.
Use the platform with human review Customers should keep an internal review process and not take regulated or legal action based solely on a single alert, summary, or assistant reply without independent judgment.
Raise serious issues through support If there is a genuine operational problem, contact support with the relevant workspace and company context. The right response is investigation and correction where possible, not silence.
