Beta program

1. What the beta is

The beta is the period before general availability in which design partners use RegSignal on real work and help shape it. The Terms of Service, including their beta terms, the Data Processing Addendum and the Acceptable Use Policy apply throughout.

The beta runs until [Beta end date] or until general availability is announced. Fees during the beta: [Beta commercial terms].

2. What design partners get

• The console and the API: the signals feed, impact inbox, product profiles, Ask with citations, tasks and approvals, the deadline calendar, audit log, members and roles, and API keys.
• Coverage of 21 jurisdictions: 20 national and regional markets plus WTO notifications, from 101 configured official sources of which 96 are active, with about 900 signals in the corpus at the start of the beta.
• Multilingual search across publications in their original language, and on-demand translation of signal summaries into 15 languages.
• Integrations: signed webhooks, Slack and Microsoft Teams notifications, Jira and ServiceNow connectors, an MCP server for AI assistants, and TypeScript and Python SDKs.
• Plan limits set for your organization, visible under Settings and through GET /v1/billing/plan.
• A direct line to the team building RegSignal, and early sight of the roadmap. [Any additional partner benefits, such as pricing commitments after the beta, to be confirmed.]

3. What we ask of you

• Use RegSignal on real regulatory monitoring work, with at least one product profile that reflects what you sell.
• Tell us when something is wrong: a misclassified document, a missing source or jurisdiction, an impact match that makes no sense, or an answer whose citation does not support it.
• Join short feedback conversations at a cadence we agree with you. [Expected time commitment, if any.]
• Name one contact person for the beta, and keep the organization owner's email current.
• Expect change. Screens, endpoints and limits may move during the beta.
• Do not rely on RegSignal as your only source of regulatory information, and do not submit special categories of personal data.

4. How feedback works

• Channels: email to [Beta contact email], in-product feedback where the console offers it, and scheduled calls.
• Be specific: a signal id, profile id or the question you asked lets us reproduce the issue. Avoid pasting confidential document text into email when an id will do.
• What happens next: we read every item, reply to tell you whether and when we will act on it, and tell you when a fix ships.
• Use of feedback: we may use your suggestions to improve RegSignal without obligation to you. Feedback does not change who owns your Customer Data.
• Publicity: we will not name you as a customer or partner, or publish your logo or quotes, without your written permission.

5. Data handling during the beta

• Beta organizations run on the same production infrastructure and controls described on the Trust page: data stored in Supabase in AWS us-west-2 (Oregon), services on Render in Oregon.
• You own your Customer Data. Documents you submit are visible only to your organization and never join the shared corpus.
• RegSignal does not use Customer Data to train or fine-tune models. Language-model processing is done by Anthropic; search embeddings are computed in RegSignal's own services.
• Retention defaults apply unless an owner changes them: internal documents kept until deleted, Ask history 365 days, audit events 730 days, usage events 400 days, webhook delivery logs 90 days. Each nightly purge records a deletion receipt.
• We do not plan to reset or migrate away beta data. If a change ever requires it, we will tell you in advance and give you time to export.
• SOC 2 Type I is in progress. RegSignal does not hold a SOC 2 report or any certification today, and the beta has no service level agreement.

6. Accuracy and how we measure it

Classifications, summaries, impact assessments, answers and translations are generated with language models. They are informational, not legal advice, and should be verified against the official source each signal and citation links to.

Method. Labels come from publisher metadata that settles the document type (for example the Federal Register document type, GOV.UK content types, recall feeds and legislation series), not from hand labelling. The datasets are frozen by hash, and each run records the commit, models and dataset versions. Classification uses the production prompt and model on the first 4,000 characters of each document. Retrieval questions are generated from each document's own key points, so hit rates are an upper bound for questions customers write.

Limits. The subset over-represents recalls, rules and consultations; guidance, standards and enforcement documents have little labelled support. The corpus is still small, so results should be re-measured as it grows rather than extrapolated. The full evaluation report is available on request at [Beta contact email].

7. How to leave

1. Export anything you want to keep through the API (for example your internal signals, profiles and impact matches).
2. Revoke your API keys and remove webhooks and connectors so no further requests or deliveries happen.
3. An owner deletes the organization under Settings. This deletes every organization-scoped record from the primary database at once; deleted data leaves backups within 7 days.
4. If you prefer, email [Beta contact email] and we will delete the organization for you and send a deletion receipt stating what was deleted and when it leaves backups.

You can leave at any time and do not need to give a reason. If you tell us why, it helps. Paid subscriptions, if any, can be cancelled in the Stripe customer portal.

8. Contact

Beta questions: [Beta contact email]. Privacy: [Privacy contact email]. Security issues: the address in /.well-known/security.txt.