Terms of Service

1. About these terms

These Terms of Service (the Terms) are an agreement between [Legal entity name], a company registered at [Registered address] under company number [Company registration number] (RegSignal, we, us), and the organization that creates a RegSignal account or signs an order form that references these Terms (the Customer, you).

RegSignal is offered to businesses only. The person accepting these Terms confirms that they have authority to bind the Customer. If you do not have that authority, or do not agree, do not use the Service.

These Terms incorporate the Data Processing Addendum, the Acceptable Use Policy and, while the Service is in beta, the Beta program terms. If you signed an order form, the order form prevails over these Terms where they conflict, and the Data Processing Addendum prevails on the processing of personal data.

2. Definitions

• Service: the RegSignal console, the REST API under /v1, the MCP server, webhooks, email digests, Slack and Microsoft Teams notifications, Jira and ServiceNow connectors, and the TypeScript and Python SDKs.
• Customer Data: content you or your users submit to the Service, including internal documents ingested as signals, product profiles, questions asked in Ask and their conversation history, triage notes, tasks, saved filters, webhook and connector configuration, and feedback about specific outputs.
• Corpus: the public regulatory publications RegSignal collects from official publishers and the metadata it derives from them.
• Output: classifications, summaries, key points, impact assessments, answers, citations and translations the Service generates.
• Users: the people you invite to your organization and anyone using your API keys.
• Beta: the pre-general-availability period described on the Beta program page.

3. Accounts, users and API keys

• Each organization has members with one of four roles: owner, admin, analyst or viewer. You decide who is invited and which role they hold, and you are responsible for what your Users do in the Service.
• API keys are credentials. Keep them secret, do not embed them in public code or client-side applications, and revoke any key you believe is exposed. Integration keys act with the analyst role.
• You must give accurate account information and keep the owner's contact details current so we can reach you about security, billing and changes to the Service.
• Tell us promptly at [Support contact email] if you suspect unauthorized access to your organization. Report security vulnerabilities through the process on the Trust page.

4. Beta terms

While the Service is in beta, the following applies in addition to the rest of these Terms:

• Features, endpoints, plan limits and coverage may change, be renamed or be removed. We will try to announce breaking API changes in advance, but during the beta we cannot guarantee a notice period.
• The beta runs from the date you are admitted until [Beta end date], or until we announce general availability, whichever comes first. What happens to your organization at the end of the beta is described in [Beta transition terms].
• Fees during the beta: [Beta commercial terms].
• Feedback you give us may be used to improve the Service without obligation to you. We will not publish your name, logo or quotes without your written permission.

5. API use, rate limits and plan limits

Your organization is assigned a plan. Each plan sets ceilings on requests per day, billing units per month, seats, product profiles and active webhooks. The plan and current usage are visible in the console under Settings and through GET /v1/billing/plan. The default ceilings at the date of these Terms are:

• Requests count from 00:00 UTC each day. Billing units count from the first day of each calendar month (UTC); ask costs 10 units, classify 5, an impact run 20 and every other request 1.
• A request over a request or unit ceiling is refused with 429 plan_limit_exceeded and a Retry-After header. Creating a seat, profile or webhook over its ceiling is refused with 403 plan_limit_reached.
• To protect the Service, RegSignal applies a daily ceiling on language-model spend. When it is reached, ask and classify may return 429 with Retry-After and enrichment of new documents pauses until the next day.
• An optional gateway may apply additional per-key rate limits. Do not try to get around any limit, for example by creating extra organizations or rotating keys to reset counters.
• We may change plan limits. During the beta we will tell organization owners by email or in the console before a reduction takes effect, where we reasonably can.

6. Customer Data

• You own Customer Data. As between you and RegSignal, you keep all rights in Customer Data. You grant RegSignal a limited licence to host, copy, process and transmit Customer Data only as needed to provide, secure and support the Service for you, and as described in the Data Processing Addendum.
• Private to your organization. Internal documents you submit are visible only to your organization, in the feed, search, Ask, impact matching and webhooks. They are never added to the shared Corpus.
• No model training. RegSignal does not use Customer Data to train or fine-tune any machine learning model. Language-model processing is performed by Anthropic under its commercial API terms, which [Counsel to confirm: Anthropic's current commercial terms do not permit training on API inputs and outputs]. Search embeddings are computed by RegSignal's own services using an open-source model; no third party receives your text to compute embeddings.
• Your responsibilities. You confirm you have the rights and any notices or consents needed to submit Customer Data. Do not submit special categories of personal data, health data about identifiable individuals, payment card data or government identifiers unless we have agreed to it in writing.
• Service data. RegSignal records operational data about use of the Service (for example request counts, units, latency, error reports and audit events) to operate, secure, bill and improve the Service. This data does not include the content of your documents beyond what the audit log describes.
• Deletion. You can delete internal signals, conversations, profiles and members at any time, set retention windows for your organization, and delete the whole organization. Retention and deletion are described in the Privacy Policy and the Data Processing Addendum.

7. Public regulatory content

The Corpus is collected from official publishers such as regulators, gazettes and the WTO notification system. Publishers keep their rights in their publications, and your use of their content remains subject to their terms. Each signal links to its official source.

Sources are polled on a schedule, and publishers change their sites, so the Corpus may be incomplete, delayed or temporarily out of date for a jurisdiction. Coverage figures we publish describe the source registry at the time stated and are not a promise that every publication is captured.

8. AI output is informational, not legal advice

Output is produced with the help of large language models and automated matching. It can be wrong, incomplete, out of date or inconsistent, including where it cites a source.

• Output is provided for information only. It is not legal, regulatory or compliance advice, and it does not create a lawyer-client or consultant relationship.
• Always verify Output against the official source before relying on it. Citations are provided so that you can do this.
• You are responsible for your compliance decisions, product decisions and filings, and for having qualified people review them.
• Accuracy figures we publish are measured on labelled evaluation subsets with a stated method. They describe those subsets, not the accuracy you will see on your own documents or questions.
• Translations are machine-generated. Where a translation and the original differ, the original publication controls.

9. Availability and support during the beta

During the beta the Service is provided without a service level agreement. There is no uptime commitment, no guaranteed response time and no service credits. We may take the Service down for maintenance, sometimes without notice, and features may be unavailable for periods of time.

Support is provided on a reasonable-efforts basis by email at [Support contact email]. Any service level commitments for general availability will be set out in a separate document or order form.

10. Fees and billing

During the beta: [Beta commercial terms]. Plan limits still apply whether or not billing is enabled.

When paid plans are enabled for your organization:

• Subscriptions and invoices are handled by Stripe. An admin starts a subscription through Stripe Checkout and manages payment methods, invoices and cancellation through the Stripe customer portal. RegSignal does not store payment card numbers.
• Plans are billed monthly in advance, and metered billing units are reported to Stripe after the end of each calendar month and billed in arrears, at the prices shown at checkout or in your order form: [Pricing and payment terms].
• If a payment fails, the subscription is marked past due and we may limit the Service after [Payment grace period]. A cancelled or unpaid subscription returns the organization to the free plan limits.
• Fees exclude taxes. You are responsible for applicable taxes other than taxes on RegSignal's income. Stripe may collect tax identifiers and billing addresses at checkout.
• Fees already paid are non-refundable except where these Terms, your order form or the law say otherwise: [Refund terms].

11. Confidentiality and security

Each party will protect the other's non-public information that it receives in connection with the Service with at least reasonable care, use it only for the purposes of these Terms, and disclose it only to people who need to know it and are bound by similar obligations, or where the law requires.

RegSignal protects Customer Data with the technical and organizational measures described in Annex 3 of the Data Processing Addendum and on the Trust page. SOC 2 Type I is in progress; RegSignal does not hold a SOC 2 report or any certification today.

12. Suspension and termination

• By you. You may stop using the Service at any time. An owner can delete the organization from the console, which deletes its data as described in the Data Processing Addendum. Paid subscriptions can be cancelled in the Stripe customer portal and end at the close of the current billing period.
• By us. We may end the beta or these Terms for convenience with [Termination notice period] notice. We may suspend access, a key or an organization immediately where needed to stop a breach of the Acceptable Use Policy, a security risk to the Service or other customers, non-payment, or where the law requires, and we will tell you why when we lawfully can.
• Effect. When these Terms end, access ends and your organization's data is deleted within [Post-termination deletion period], after an export window of [Export window]. Sections that by their nature should survive (including Customer Data ownership, AI output disclaimer, fees owed, confidentiality, limitation of liability and governing law) survive.

13. Warranties and disclaimers

Each party confirms it has the authority to enter into these Terms. During the beta, and except as expressly stated in these Terms, the Service, the Corpus and all Output are provided as is and as available, and RegSignal disclaims all implied warranties, including merchantability, fitness for a particular purpose, accuracy and non-infringement, to the extent the law allows.

14. Limitation of liability

Each party's total liability arising out of or relating to these Terms is limited to [Liability cap amount]. Neither party is liable for indirect, consequential or lost-profit damages. [Liability cap carve-outs, for example confidentiality, data protection obligations, indemnities and fraud, to be drafted by counsel.] [Indemnification commitments by either party, if any.]

Nothing in these Terms limits liability that cannot be limited under applicable law.

15. Changes to these terms

We may update these Terms. We will change the last-updated date above and notify organization owners by email or in the console at least [Notice period for changes to Terms] before a material change takes effect. Continuing to use the Service after that date means you accept the updated Terms. If you do not agree, you may stop using the Service and delete your organization.

16. Governing law and disputes

These Terms are governed by the laws of [Governing law], without regard to conflict-of-laws rules. The courts of [Venue / courts] have exclusive jurisdiction, except that either party may seek urgent injunctive relief in any competent court. [Dispute resolution mechanism, if any, such as negotiation or arbitration, to be decided with counsel.]

17. General

• These Terms, any order form, the Data Processing Addendum and the policies they reference are the entire agreement about the Service and replace earlier discussions about it.
• Neither party may assign these Terms without the other's consent, except to a successor in a merger, acquisition or sale of substantially all relevant assets, with notice.
• If a provision is unenforceable, the rest of the Terms remain in effect. A failure to enforce a provision is not a waiver.
• Notices to RegSignal go to [Legal contact email] and [Registered address]. Notices to you go to the organization owner's email address.