Version: beta-2026-08-20
Account information may include your email address, name, business/trading details, phone number, trade type, professional registration details, billing status and consent records. The service may also hold information you enter about your customers, sites, jobs, equipment, certificates, quotations, invoices, signatures, photographs and payments.
Information is used to provide and secure the WorkOps service, create and store business records, synchronise offline work, send documents and service messages, administer trials and memberships, process payments you request, provide integrations you enable, prevent misuse, support users and understand service performance.
The final production notice must identify the appropriate lawful basis for each processing purpose. Likely bases include performance of the service contract, legitimate interests in operating and securing the service, legal obligations where applicable and consent for optional marketing communications.
WorkOps may use infrastructure, email, payment and integration providers to deliver functions you choose to use. Current architecture includes Hatchable-hosted application services and Stripe for payment-related functions; accounting providers may include Xero, QuickBooks or Sage when an engineer explicitly connects them. The final notice must list or categorise production processors accurately.
Marketing consent is separate from accepting the Terms or acknowledging this Privacy Notice. Optional marketing can be declined without preventing use of the core WorkOps service.
WorkOps is designed to preserve business and compliance records rather than silently delete them when a subscription ends. The final production policy must specify retention periods or clear criteria for account data, document records, security logs, payment metadata and backups.
Depending on the circumstances and lawful basis, UK data-protection law may provide rights including access, correction, erasure, restriction, objection and data portability. WorkOps also provides a self-service export of key workspace data. The final notice must provide the controller's contact details for exercising rights.
UK users may have the right to complain to the Information Commissioner's Office about the handling of personal information. The final production notice should include the controller contact route first and current ICO contact information.
WorkOps uses authenticated workspaces, organisation scoping and controlled public document tokens. No internet service can guarantee absolute security; users should protect access to their email and devices and promptly report suspected account misuse.
Privacy notices should be reviewed as the product, providers and law change. Signup records store the version acknowledged so changes can be audited rather than silently backdated.