Skip to content
Request access
Product

Gate before you collect, Trace after, Watch while you rely on a site, Matters when it counts.

  • Gate
  • Trace
  • Watch
  • Matters
  • Get the API
  • Pricing
Solutions

By what you are building or checking.

  • Training data collection
  • RAG and AI search
  • Common Crawl and existing corpora
  • Dataset building
  • Due diligence
  • Law firms
  • All use cases
India and EU

The rules each check reads, and where they are heading.

  • India
  • EU
  • Profiles
  • Where the law is heading
Resources

How it works, receipts, and who we are.

  • How it works
  • Receipts and verification
  • Why RightSignal
  • About
  • FAQ
  • Contact
Legal/API terms

Schedule 3 to the RightSignal Terms of Service

API Terms

These API Terms are part of the Agreement between RightSignal and the Client. Words defined in the Terms of Service have the same meaning here.

Version
1.0
Last updated
11 November 2026
Sections
6
Reading time
4 min

Contents

  1. 01Access
  2. 02API keys
  3. 03Modes and limits
  4. 04Decisions through the API
  5. 05Receipts, requests and logs
  6. 06Changes, availability and suspension
All legal documents

01Access

1.1

Right to call the API: The Client may call the API at api.rightsignal.legal only with an API key issued to its organisation, only within its Plan, and only as the Agreement and the API reference allow. If the API reference and these API Terms conflict, these API Terms govern.

02API keys

2.1

Issue of keys: A key is either a live key for Live Mode or a test key for Test Mode, and it carries the scopes chosen when it was made. Only a signed-in Authorised User can make, rotate or revoke a key in the app, and a key can never do so. RightSignal shows the secret part of a key once and stores only a salted and keyed hash of it, so a Client that loses a key must make a new one.

2.2

Protection of keys: The Client must keep each key secret, use a separate key with the narrowest scopes for each system, and never put a key in a web page, a mobile app, a public repository or a page address. The Client must revoke a key at once if it may have been exposed and must tell RightSignal at security@rightsignal.legal. When the Client rotates a key, the old key keeps working for the grace period chosen at rotation, which is 24 hours unless the Client chooses another period of up to 7 days.

2.3

Responsibility: Everything done with a key is done by the Client. The Client is responsible for it, and for any Fees that it gives rise to, until the Client revokes the key.

03Modes and limits

3.1

Test Mode and Live Mode: A test key works in Test Mode only, where Decisions carry test seals and are made without the AI models. A live key works in Live Mode, where Decisions are sealed with RightSignal's service key and Receipts are locked as clause 11.2 of the Terms describes. The Client must not use a Test Mode Output for real Collection or present it as a Live Mode Output.

3.2

Rate limits and quotas: Each key has a rate limit set by the Client's Plan, and every request counts towards it, including a request for the status of a check. Where an answer says how long to wait, the Client's software must wait at least that long. Clause 4.6 of the Terms governs quotas and spending limits, and the Client must not try to get round a limit by spreading requests across keys or organisations.

04Decisions through the API

4.1

Handling of Decisions: Each Decision states its Outcome and outcome group, the Profile, the version of the RightSignal Algorithm, when it was made, when it expires and whether the AI reader took part. The Client's software must keep these with the Decision, must not act on a Decision after it has expired, and must not serve a bundle answer beyond the time that the answer allows. The software must treat a hold, an unknown value, an error or an unavailable API as a reason not to collect, and must never treat any of them as a collect.

4.2

Notice and presentation: Each Decision carries a short notice, and the Client must show that notice wherever it shows the Decision to anyone outside its organisation. The Client must not show a Decision under any description that clause 3 of the Acceptable Use Policy forbids.

05Receipts, requests and logs

5.1

Receipts: The Client may fetch its Receipts through the API and should keep its own copies. It may verify a Receipt with the standalone verifier under clause 3.3 of the IP and Confidentiality Schedule, and clause 11.1 of the Terms states what verification shows.

5.2

Requests and the audit log: The Client must send only what the API reference asks for, which means public web addresses that contain no personal data, passwords or secrets. RightSignal records each authenticated request and each failed attempt to use a key in an audit log that holds the organisation, the key or user, the method, the route, the status, a request identifier, the originating address and the time. The log never holds a request body, a query string or a secret, and the owners of the Client's organisation can read it in the app.

06Changes, availability and suspension

6.1

Changes to the API: RightSignal may add routes, fields and values to a version of the API at any time, and the Client's software must tolerate additions. RightSignal will give at least 30 days' notice before it removes or changes a route or field in a way that would break software written to the API reference, unless an urgent change is needed for security, to prevent misuse or to meet Applicable Law. A new version of the RightSignal Algorithm may change the Decisions that the API returns, and that is not a change to the API.

6.2

Availability and suspension: Clause 4.7 of the Terms applies to the API, and no service levels apply unless an Order Form states them. RightSignal may revoke a key or suspend API access under clause 18.3 of the Terms, and the keys of a suspended organisation stop working until the suspension ends. The rest of the Terms, including clauses 7 to 9 and 15 to 17, applies to every use of the API.

Read with this

  • The agreementRightSignal Terms of ServiceVersion 1.0 · 29 min
  • Schedule 1 to the RightSignal Terms of ServiceIP and Confidentiality ScheduleVersion 1.0 · 8 min
  • Schedule 2 to the RightSignal Terms of ServiceAcceptable Use PolicyVersion 1.0 · 3 min
  • Schedule 4 to the RightSignal Terms of ServiceData Processing AgreementVersion 1.0 · 10 min
rightsignal
RightSignal Legal

Know what a website allows before you collect, and keep the proof.

Product

  • Gate
  • Trace
  • Watch
  • Matters
  • Pricing

Solutions

  • Training data collection
  • RAG and AI search
  • Common Crawl and existing corpora
  • Dataset building
  • Due diligence
  • Law firms
  • Scraping and data services
  • Model builders

Law

  • India
  • EU
  • Profiles
  • Where the law is heading
  • How the algorithm works
  • Not legal advice

Get the API

  • Developer overview
  • Documentation
  • API terms
  • Security

Resources

  • How it works
  • Receipts and verification
  • About
  • Why RightSignal
  • FAQ
  • Contact
  • Request access

Legal

  • Terms of service
  • IP and confidentiality
  • Acceptable use
  • Privacy policy
  • Data processing agreement
  • Subprocessors
  • Cookie notice

For website owners

  • Crawler and site-owner policy
Not legal adviceRightSignal Algorithm 1.3.6

Not legal advice: RightSignal provides evidence and decisions under the RightSignal Algorithm. It does not provide legal advice or a legal opinion, and nothing it produces states that any collection or use is lawful. A decision may not be correct, complete or current, because websites change and a reading can miss wording. You operate your own crawlers and you alone decide what to collect and how to use it. Take advice from your own advocate. The full notice is at rightsignal.legal/legal/not-legal-advice and the terms are at rightsignal.legal/legal/terms.

© 2026 Manraj Singh Chandpuri, trading as RightSignal, Chandigarh, India, who conceived, designed and built RightSignal. RightSignal is for businesses and professionals only and is not for anyone under 18.