Legal

Signals Terms of Service

Effective Date: 14/11/2026
Version 2026.1

These terms apply to Signals, provided by Thirty-One Circles Ltd. Part A is the agreement between 31C and the organisation using Signals. Part B sets the rules every individual User accepts.

PART A — SIGNALS TERMS (CUSTOMER)

1. ABOUT THESE TERMS

1.1 These terms govern access to and use of Signals, the platform operated by Thirty-One Circles Ltd (“31C”, “we”, “us”), a company registered in England and Wales under number 13999453, registered office The Gallery, 14 Upland Road, London SE22 9EE.

1.2 They form a contract between 31C and the organisation on whose behalf Signals is accessed (the “Customer”). Each individual who accesses Signals (a “User”) also accepts Part B. A User who accepts these terms confirms they have authority to bind the Customer.

1.3 Signals is for business use only. It is not offered to consumers, and by using it the Customer and each User confirm they act for business purposes.

1.4 Signals is provided as an extension of the services 31C delivers under the Customer’s signed agreements, statements of work or orders with 31C (each a “Contract”). Where a Contract conflicts with these terms, the Contract prevails; otherwise these terms apply in full. A Contract that does not expressly mention Signals does not transfer ownership of, or grant rights in, Signals itself.

1.5 These terms replace the Signals Membership Terms (version 2024.1) for any use of Signals on or after the date at the top of this page.

1.6 By accepting these terms, the Customer and each User also accept 31C’s Website Terms, which apply to the use of 31C’s websites. If they conflict, these terms prevail for Signals.

2. DEFINITIONS

  • Account: a User’s login to Signals.
  • AI Client: any third-party AI assistant, model or agent a User connects to Signals, including through the MCP.
  • Customer Data: data the Customer or its Users submit to, connect to, or generate within Signals, including data read from Data Sources.
  • Data Source: a dataset or table (for example in Google BigQuery) the Customer connects to Signals.
  • Features: Alerts, Audience Management, Data Sources, the MCP, Published Reports, and any feature 31C adds later.
  • MCP: the Model Context Protocol server through which AI Clients query Data Sources.
  • Output: alerts, audiences, reports, query results and other material Signals generates for the Customer.
  • Personal Data: has the meaning in the UK GDPR.
  • Published Report: a dashboard or report published into a Signals workspace.
  • Signals: the platform operated by 31C, including the web app at app.thirtyonecircles.com, the MCP at mcp.thirtyonecircles.com, any related APIs, and any other domain, app or interface 31C designates for it.
  • Workspace: an access-controlled area within Signals.

3. ELIGIBILITY AND FREE ACCESS

3.1 Signals is currently provided free of charge to Customers that have had an active statement of work with 31C at any time in the previous three months (“Active Clients”).

3.2 31C may change eligibility, introduce fees, or limit Features on 30 days’ written notice. Fees will only apply once agreed in a Contract.

3.3 If a Customer stops being an Active Client, 31C will notify it and the parties may agree in a Contract for continued access on a paid basis. If no such Contract is agreed within 30 days of that notice, 31C may suspend or end the Customer’s access, and will give the Customer a reasonable opportunity to export its Outputs during that period.

3.4 Access is personal to the Customer. It may not be resold, sublicensed, or provided to third parties, except Customer’s own clients or group companies where 31C has agreed in writing.

4. ACCOUNTS AND USERS

4.1 The Customer is responsible for who it invites, the roles it assigns (for example Admin, User Admin, Publish, View), and for removing access promptly when someone leaves or no longer needs it.

4.2 Each Account is for one named individual. Credentials must not be shared. Users sign in to Signals with Google or Microsoft single sign-on, or another identity provider 31C supports. Each User is responsible for keeping that account secure, ideally with strong multi-factor authentication such as a passkey, security key or authenticator app rather than SMS. 31C is not responsible for unauthorised access caused by a compromised sign-in account.

4.3 The Customer is responsible for all activity under its Accounts and for its Users’ compliance with these terms, as if it were its own conduct.

4.4 The Customer must tell 31C promptly at the contact address in clause 20 of any suspected unauthorised access or security incident affecting Signals.

5. LICENCE

5.1 31C grants the Customer a non-exclusive, non-transferable, revocable licence, for the term of its access, to permit its Users to use Signals and the documentation for the Customer’s internal business purposes, in line with these terms.

5.2 All rights not expressly granted are reserved. The restrictions in Part B apply to the Customer as well as each User.

6. CUSTOMER DATA

6.1 The Customer owns its Customer Data and Outputs. It grants 31C a non-exclusive licence to host, copy, process and transmit Customer Data only as needed to provide, secure and support Signals, and as the Customer instructs through the Features.

6.2 The Customer is solely responsible for the accuracy, legality and quality of Customer Data, and for having all rights, permissions and lawful bases needed to connect it to Signals and to let 31C process it.

6.3 31C collects and keeps basic usage data (such as features used, query volumes, performance and error logs) to operate, secure and improve Signals. Any use beyond running the Customer’s own service is in aggregated form that does not identify the Customer, any User or any individual.

6.4 31C will not use Customer Data to train any machine-learning or AI model.

6.5 Usage logging. Logging is part of the Signals service. 31C records usage, including the User, timestamps, sign-ins, reports and Data Sources accessed, queries run and estimated query costs, for security, audit, billing and support. The Customer’s admins may see these audit trails. Logs are kept for up to 24 months (clause 18.3).

7. PERSONAL DATA

7.1 No Personal Data without a signed DPA. The Customer must not upload, connect, query, publish or otherwise make available Personal Data through Signals — including through Data Sources, the MCP, Published Reports, Alerts or any AI Client — unless permitted by a signed Contract between 31C and the Customer that includes data processing terms meeting UK GDPR Article 28 (a “DPA”) and names the Feature and data concerned. Emails, chat messages and verbal agreement are not enough.

7.2 Never permitted. The Customer must never make available special category data or criminal offence data (UK GDPR Articles 9 and 10), or data about children, through any Feature. This applies even where a Contract permits other Personal Data, and despite clause 1.4.

7.3 Where permitted. Where a Contract permits it (for example for Audience Management), 31C processes that Personal Data as processor for the Customer under the DPA in that Contract. The Customer remains controller and is responsible for transparency, lawful basis, and any consent needed, including under PECR for marketing and for sending data to advertising platforms.

7.4 Pseudonymised data (for example hashed email addresses or device IDs) is still Personal Data for these terms.

7.5 If Personal Data turns up. If the Customer becomes aware that Personal Data has been made available in breach of 7.1, it must tell 31C promptly and remove it. 31C may disconnect the Data Source, unpublish the report, delete the data, or suspend the relevant Feature until it is resolved.

7.6 Users’ own data. 31C processes Users’ account and usage data (names, emails, sign-in and audit logs) as controller under its Privacy Policy.

8. DATA SOURCES AND THE MCP

8.1 To connect a Data Source, Signals’ service account must be granted access to it. The Customer may grant that access itself, or authorise 31C to grant it on its behalf, for example as part of consultancy services under a Contract or on a written instruction (email is enough). Either way the access is given on the Customer’s authority: the Customer warrants it is entitled to give it, and remains responsible for the data connected. 31C will remove access it has granted on the Customer’s request, and the Customer may revoke it at any time. Clause 7 applies to any Data Source 31C connects, so 31C will not connect a source it knows contains Personal Data unless a Contract permits it.

8.2 Queries against a Data Source, whether through the MCP, Published Reports or any other Feature, are billed by Google to the Google Cloud project in which that Data Source resides, not by 31C. The Customer is responsible for those costs and for setting any budgets or quotas.

8.3 Signals reads Data Sources only to deliver the Features the Customer uses. A Data Source continues to work for other Users in its Workspace if the User who connected it later loses access; the Customer must manage this through Workspace roles.

8.4 Field descriptions, metric definitions and other metadata the Customer adds are Customer Data. 31C’s schemas, query logic, tool definitions and prompts are 31C’s confidential information.

8.5 Users may access the MCP only through AI Clients the Customer has approved, using their own Account. Use of the MCP from scripts, bots or automated agents running without a User’s direct oversight requires 31C’s written permission.

8.6 Caching. Where caching is enabled for a Data Source, 31C stores query results in its own Google Cloud environment, in the UK, to speed up responses. Cached results are kept for no more than one month and are then deleted automatically.

9. PUBLISHED REPORTS

9.1 A Published Report runs with the data access configured by its publisher, not the viewer’s. Anyone with View access to a report can see all data it shows. The Customer must therefore only grant access to people entitled to see that data.

9.2 Publishers are responsible for everything in their reports, including code generated by AI tools. Reports must not contain or attempt anything harmful, including malicious code, attempts to escape the sandbox or access other reports, Workspaces or systems, connections to external hosts, collecting credentials or viewers’ data, tracking, or crypto-mining. Reports must not contain content that is unlawful, offensive, obscene, discriminatory, harassing, defamatory, misleading, or that infringes third-party rights.

9.3 Reports run in a sandbox and may only communicate through Signals. 31C may block, unpublish or roll back any report that it reasonably believes is harmful, insecure or in breach of these terms.

9.4 Sharing a report, its link, screenshots or exports outside the Customer’s organisation is at the Customer’s risk and responsibility.

9.5 What can be published. Published Reports must be reports built on Signals: they must get their data through Signals’ Data Sources or the 31C MCP. Other pages, apps, AI-generated artifacts or code may not be published unless 31C has expressly permitted it in writing.

9.6 31C may scan, review or test reports, automatically or manually, before or after publication, to enforce this clause.

10. AI CLIENTS AND AI-GENERATED CONTENT

10.1 AI Clients are third-party services chosen and contracted for by the Customer. Their terms, data handling and model training practices are between the Customer and that provider. The Customer is responsible for configuring them, including any setting that stops its data being used for training.

10.2 When a User queries Signals through an AI Client, the results leave Signals and are processed by that provider. 31C is not responsible for what the AI Client does with them.

10.3 Reports, summaries and answers generated with AI may be inaccurate or incomplete. 31C gives no warranty or guarantee about the accuracy, completeness or suitability of anything in reports, answers or other Outputs created by the Customer’s Users or their AI Clients, and the Customer relies on them at its own risk. Reports and Outputs that 31C itself produces as part of consultancy services are governed by the relevant Contract.

10.4 31C may limit, rate-limit or block AI Client access to protect Signals, its other customers or its infrastructure.

11. INTELLECTUAL PROPERTY

11.1 31C and its licensors own all intellectual property rights in Signals, including its software, design, user interface, documentation, schemas, query logic, MCP tool definitions, prompts and know-how, and any improvements to them.

11.2 If the Customer or a User gives feedback or suggestions, 31C may use them freely without obligation.

11.3 While it uses Signals and for 12 months after its access ends, the Customer and its Users must not use Signals, its documentation, Outputs that reveal how Signals works, or 31C’s intellectual property to develop, or help anyone else develop, a product or service that is the same as or similar to Signals or any of its Features. This does not restrict the Customer’s use of its own data or of general skills and publicly available information.

12. CONFIDENTIALITY

12.1 Each party will keep the other’s confidential information confidential, use it only to perform these terms, and share it only with staff and advisers who need to know it and are bound by equivalent duties.

12.2 This does not apply to information that is public (other than through breach), already lawfully held, independently developed, or required to be disclosed by law or a regulator.

12.3 Non-public features, roadmaps, pricing, documentation and the internal workings of Signals are 31C’s confidential information.

12.4 This clause survives for five years after access ends, and indefinitely for trade secrets.

12.5 While it uses Signals and for 12 months after its access ends, the Customer must not use 31C’s confidential information, including anything learned about how Signals is designed, built or works, to develop, or help anyone else develop, a product or service similar to Signals or any of its Features.

13. SECURITY AND COMPLIANCE

13.1 31C will maintain appropriate technical and organisational measures to protect Signals and Customer Data, in line with good industry practice.

13.2 The Customer will maintain appropriate security over its own systems, cloud accounts, identity providers and AI Clients connected to Signals.

13.3 Each party will comply with laws that apply to it in connection with Signals, including data protection law, the Computer Misuse Act 1990, the Bribery Act 2010, and UK sanctions and export control rules. The Customer must not use Signals from, or for the benefit of, any sanctioned country or person.

14. AVAILABILITY, SUPPORT AND CHANGES

14.1 31C will use reasonable efforts to keep Signals available, but does not guarantee uninterrupted or error-free service. Planned maintenance will take place outside UK business hours, unless it is expected to cause no interruption to Signals.

14.2 Support is provided by email during UK business hours on a reasonable-efforts basis, unless a Contract says otherwise.

14.3 31C may add, change or remove Features. It will give reasonable notice before removing a Feature the Customer actively uses, unless the change is needed for security, legal or third-party-provider reasons.

14.4 Signals depends on third-party services (including cloud, identity and advertising platforms). 31C is not responsible for their availability, changes or failures.

15. WARRANTIES AND DISCLAIMERS

15.1 31C will provide Signals with reasonable skill and care.

15.2 Otherwise, and to the extent the law allows, Signals and all Outputs are provided “as is”. All other warranties, conditions and terms implied by statute or common law are excluded.

15.3 31C does not guarantee that an alert will be sent for every relevant event, that alerts or audiences will be delivered on time or at all, or that using Signals will achieve any particular business result.

16. LIABILITY

16.1 Nothing in these terms limits liability for death or personal injury caused by negligence, fraud or fraudulent misrepresentation, or any liability that cannot be limited by law.

16.2 Subject to 16.1, 31C is not liable for loss of profits, revenue, business, goodwill, anticipated savings, or for any indirect or consequential loss.

16.3 31C is not liable for loss or corruption of Customer Data held in the Customer’s own systems or Data Sources. Signals reads those sources and is not a backup service.

16.4 Subject to 16.1, 31C’s total liability arising from or in connection with Signals in any 12-month period is limited to:

(a) the liability cap in any signed Contract between the Customer and 31C; or

(b) otherwise, £100, reflecting that Signals is provided free of charge as an added-value service to 31C clients.

16.5 The Customer’s liability for breach of clause 7 (Personal Data), Part B, or for infringing 31C’s intellectual property is not limited by these terms.

17. INDEMNITY

The Customer will indemnify 31C against losses, fines, costs and reasonable legal fees arising from third-party or regulator claims caused by: (a) Customer Data, including Personal Data made available in breach of clause 7; (b) Published Reports created by its Users; or (c) any breach of Part B by its Users.

18. SUSPENSION AND TERMINATION

18.1 31C may suspend any Account, Workspace, Data Source, report or Feature immediately if it reasonably believes there is a security risk, a breach of these terms, or a legal or regulatory requirement. It will tell the Customer as soon as practical and restore access once the issue is resolved.

18.2 Either party may end the Customer’s use of Signals on 30 days’ written notice, or immediately for the other’s material breach not remedied within 14 days of notice.

18.3 On termination, licences end, Users lose access, and 31C will delete Customer Data held within Signals within 90 days, unless a Contract or the law requires otherwise. Audit and security logs may be kept for up to 24 months for security, legal and audit purposes. Data in the Customer’s own Data Sources is untouched; the Customer should revoke Signals’ service account access.

18.4 Clauses 6, 7, 11, 12, 16, 17, 18.3, 20 and Part B survive termination.

19. CHANGES TO THESE TERMS

19.1 31C may update these terms. Changes take effect when the updated terms are posted, except that changes which materially reduce the Customer’s rights take effect 14 days after notice by email or in-app, unless needed sooner for legal or security reasons.

19.2 Users may be asked to accept updated terms at their next sign-in. If the Customer does not agree, it may stop using Signals. Continued use after a change takes effect is acceptance. Updates do not change any signed Contract, which continues to prevail under clause 1.4.

20. GENERAL

20.1 Notices to 31C go to legal@thirtyonecircles.com; notices to the Customer go to its primary admin’s email or the address in its Contract.

20.2 Assignment. The Customer may not assign or transfer these terms without 31C’s written consent. 31C may assign them to a group company or a successor to its business.

20.3 Entire agreement. These terms (with any Contract and the documents they refer to) are the whole agreement about Signals. Neither party relies on any statement not set out in them, but this does not limit liability for fraud.

20.4 Third parties. No one other than 31C and the Customer has rights under the Contracts (Rights of Third Parties) Act 1999.

20.5 Severance and waiver. If any part is unenforceable the rest continues. A delay in enforcing a right is not a waiver.

20.6 Force majeure. Neither party is liable for delay or failure caused by events beyond its reasonable control.

20.7 Governing law and jurisdiction. These terms and any dispute or claim (including non-contractual ones) arising from them are governed by the law of England and Wales. The courts of England and Wales have exclusive jurisdiction.

PART B — SIGNALS ACCEPTABLE USE (EVERY USER)

Every User must accept this Part B when they first sign in to Signals, and again when it changes. It applies alongside Part A.

B1. YOUR AGREEMENT

B1.1 By ticking the box you agree to these rules, to Part A and to 31C’s Website Terms on behalf of the organisation you work for. You confirm you are authorised to do so and are using Signals for business purposes.

B1.2 Breaching these rules can lead to your Account or your organisation’s access being suspended or ended.

B2. SECURITY, VIRUSES AND MISUSE

You must not:

  1. introduce or transmit any virus, malware, ransomware, worm, logic bomb or other harmful or malicious code, or anything designed to disrupt, damage or gain unauthorised access to Signals or any system connected to it;
  2. attempt to access any Account, Workspace, Data Source, report or data you have not been given access to, or probe, scan or test the vulnerability of Signals, or bypass any authentication, access control, sandbox or rate limit;
  3. carry out penetration testing or security research on Signals without 31C’s prior written consent — report suspected vulnerabilities to admin@thirtyonecircles.com instead;
  4. overload or interfere with Signals, including through denial-of-service, excessive automated queries, or running queries designed to drive up cost;
  5. use another person’s Account, share your credentials, or let anyone else use your session or tokens, or fail to keep the Google or Microsoft account you sign in with secure (ideally with strong multi-factor authentication such as a passkey, security key or authenticator app);
  6. send prompts, code or content designed to manipulate Signals, its MCP or any AI Client into revealing data, instructions or functions you are not authorised to use (“prompt injection” or “jailbreaking”).

B3. REVERSE ENGINEERING, COPYING AND AI

Except to the extent the law expressly allows despite this restriction, you must not, and must not use any person, tool or AI system to:

  1. copy, modify, translate, decompile, disassemble or reverse engineer any part of Signals;
  2. extract, reconstruct or replicate Signals’ source code, architecture, user interface, schemas, query logic, MCP tool definitions, system prompts, data dictionaries or workflows, including by systematically querying the MCP or Signals and analysing the responses;
  3. use Signals, its documentation, MCP responses or Outputs to build, train, fine-tune, evaluate or benchmark any product, model or service that competes with Signals or replicates its features;
  4. scrape, crawl or bulk-export Signals content or data except through export functions Signals provides;
  5. publish benchmarks or comparative tests of Signals without 31C’s written consent;
  6. remove or obscure any proprietary notices or branding;
  7. license, sell, rent, frame, mirror or otherwise make Signals available to anyone outside your organisation.

B4. DATA YOU PUT INTO SIGNALS

You must:

  1. not upload, connect, query, publish or share personal data (any information relating to an identified or identifiable individual, including hashed emails, device IDs and customer-level records) through any Feature — including the MCP, Data Sources, Published Reports and Alerts — unless your organisation has a signed contract with 31C, including a data processing agreement, that permits that use;
  2. never make available health data, or other special category, criminal offence or children’s data, under any circumstances;
  3. only connect data your organisation is entitled to use, and only share reports and Outputs with people entitled to see the data in them;
  4. tell your Signals admin and 31C straight away if you think personal data, credentials or confidential information has been made available by mistake.

B5. LAWFUL AND RESPONSIBLE USE

You must use Signals in line with all applicable laws and regulations, including data protection, marketing (PECR), consumer protection, competition, sanctions, anti-bribery and intellectual property laws. You must not use Signals to store or publish content that is unlawful, defamatory, discriminatory, infringing, or misleading, or to target advertising in a way that breaches advertising platform policies or law.

B6. AI CLIENTS

If you connect an AI assistant to Signals through the MCP, you must only use one your organisation has approved, through your own Account. AI-generated reports and answers may be wrong, and you rely on them at your own risk.

B7. MONITORING

Logging is part of Signals. 31C logs access and activity (including your user ID, sign-ins, reports and data sources accessed, queries, publishing and estimated query costs) to secure Signals, enforce these rules, and provide audit trails to your organisation’s admins. See the Privacy Policy.

B8. PUBLISHING REPORTS

You are responsible for any report you publish, including AI-generated code. You must only publish reports that get their data through Signals or the 31C MCP, unless 31C has agreed otherwise in writing. You must not publish anything harmful (malicious code, sandbox escapes, tracking, credential collection, connections to outside services) or anything unlawful, offensive, discriminatory, misleading or infringing.

We use cookies to run this site and, with your permission, to understand how it's used and improve it. Choose what you're comfortable with — you can change this anytime from the footer. See our Privacy Policy.

Cookie preferences

Choose which categories of cookies we're allowed to use. Strictly necessary cookies keep the site working and can't be switched off.