Reach Operator Agreement

Effective: 2026-05-23 · Version 1.2 (added explicit standalone emergency / no-reliance / no-damages / no-consequential-damages callouts)

Plain English summary: If you sign up at inferlane.dev/reach/operator to operate a verified domain — for example, to let people call your support line in their browser — this is the contract between you and InferLane. It is in addition to (and incorporates) the Privacy Policy and Terms of Service. The most important thing to internalise: InferLane signals; you publish. You are the publisher. Calls flow browser-to-browser; nothing about a call's content (audio, transcript, captions) ever touches us.

Operator headline. Four bullets, all of which bind.

DO NOT ADVERTISE REACH AS AN EMERGENCY LINE. You must clearly disclose to your callers that Reach is not telephone service, does not route to emergency dispatchers, and cannot be relied on for time-critical contact. Reach is not 911 / 000 / 112 (Terms §5.1.1).
NO RELIANCE ON YOUR CONFIGURATION BY INFERLANE. Whatever you publish through the operator dashboard — endpoint descriptions, hours, recording policies, agent identities — is rendered verbatim and unverified. You are the publisher; you stand behind it (§3.1).
NO DAMAGES BEYOND THE CAP. InferLane's aggregate liability to you is the same AUD $100 / fees-paid cap as in the Terms of Service §7.
NO CONSEQUENTIAL OR INDIRECT LOSS OR DAMAGES. InferLane is not liable for lost profits, lost revenue, lost data, lost customers, business interruption, reputational harm, or any other consequential loss flowing from your use of the operator tier — even if InferLane has been advised of the possibility (§8).

1. Parties and acceptance

This Operator Agreement ("Agreement") is between you, the operator that signs up at inferlane.dev/reach/operator ("Operator," "you"), and the operator of Reach, InferLane ("InferLane," "we"). You accept this Agreement by clicking Create account on the operator sign-up form, by adding a domain, or by using any operator-tier feature.

If you are signing up on behalf of a company, you represent that you have authority to bind that company. The "Operator" is then the company; "you" includes you personally where context requires.

2. Domain ownership and verification

You may only add domains that you own or are authorized to operate. The DNS-TXT verification flow (_reach-verify.<your-domain>) is your representation that you control DNS for the domain. InferLane queries that record only.

If a domain you claimed has its DNS control transferred (sale, contract termination, internal team change), you must either transfer the publisher account to the new operator (contact legal@inferlane.dev) or remove the domain from your operator account. InferLane may also remove the domain on receipt of a credible counter-claim and will notify the original operator.
A verified domain can be re-verified by the same operator at any time (the "regenerate token" flow rolls a fresh TXT challenge).
InferLane does not verify your underlying ownership of the entity that owns the domain. The DNS-TXT challenge is the entirety of our check.

3. Responsibility split

This is the heart of the agreement. Read it carefully.

Layer	InferLane's responsibility	Operator's responsibility
voice.json at your domain	Provides a synthesized voice.json file via the operator dashboard.	You upload that file to `https://<your-domain>/.well-known/voice.json` on infrastructure you control. You are responsible for keeping it served, correct, and accessible.
SIP signaling	Operates the signaling server at `voice.inferlane.dev`. Routes INVITEs based on the resolved manifest. Maintains uptime on a best-effort basis at v1.1 (no SLA — premium SLA tier may be offered in future).	Configure endpoints (hours, voicemail, recording policy) accurately. Keep at least one agent online during your declared hours if you want calls to ring; otherwise calls fall through to voicemail.
WebRTC media	Does not touch the audio stream. May provide TURN relay for symmetric-NAT callers (`no-log`).	The call's audio is between the caller's browser and your agent's browser. You are the publisher: anything said, recorded, or transcribed during the call is between you and the caller. InferLane has no copy.
Recording / monitoring / transcription	Honors your declared recording policy (`none` \| `consent-required` \| `business-disclosed`) at the protocol layer — Reach client surfaces show the recording flag to callers before connecting.	You are responsible for compliance with all applicable call-recording laws. The legal requirement varies by jurisdiction (one-party consent, two-party consent, mandatory disclosure, mandatory beep tone). InferLane does not, and cannot, enforce this on your behalf. If your endpoint records or transcribes, your declared `recordingPolicy` must accurately reflect that, and your agent must obtain whatever consent the law in their jurisdiction (and the caller's) requires.
Agent credentials	Generates the SIP username + a high-entropy plaintext password at invite time. Stores only the scrypt hash. Surfaces the plaintext exactly once.	Distribute the credential to your agent over a channel you trust. Revoke immediately if the agent leaves the team or the credential leaks.
Caller authentication / KYC	None. InferLane does not know who the caller is beyond what the caller's Reach client sends in SIP headers.	If your service requires caller authentication (e.g. banking, healthcare), implement it inside your conversation flow. Reach is not a know-your-customer layer.
Emergency calling (911 / 000 / 112 / equivalent)	Not supported. Reach is not a substitute for emergency calling and must not be advertised as such.	You must clearly disclose to your end users that Reach calls are not a path to emergency services. We recommend a disclosure on any page that surfaces a Reach calling button.
Voicemail content	v1.1: voicemail config is stored but voicemail capture is not yet implemented in the signaling server. When it ships (B-business future), recordings will be delivered to your configured email and stored on InferLane infrastructure for transit; retention is then 30 days unless you configure otherwise.	You are the data controller for voicemail content received via your endpoints.

3.1 InferLane does not vouch for what you publish

You are the publisher. Every endpoint name, description, hours block, recording-policy declaration, voicemail configuration, agent display name, and any other content you put into the operator dashboard is rendered, served, and surfaced verbatim by InferLane without audit, verification, or endorsement. InferLane does not warrant that your published configuration is accurate, lawful in your jurisdiction or in any caller's jurisdiction, suitable for any particular use, free from third-party claims, or compliant with any standard. You are responsible for the truth, lawfulness, and effect of what you publish.

In particular, InferLane does not:

Confirm that your declared recordingPolicy matches your actual recording practice.
Confirm that you have obtained any necessary consents for recording, monitoring, transcription, or AI-mediated answering of calls.
Confirm that you hold any licence, registration, regulatory approval, or insurance that may be required to operate the kind of service your endpoints describe.
Confirm that your declared business hours, voicemail availability, or estimated wait times correspond to what callers actually experience.
Confirm that your agents are who they say they are, or that they are authorised by you at the time a call connects.
Confirm that the goods, services, advice, or information your agents provide on a call are accurate, lawful, fit for purpose, or covered by any consumer guarantee owed by InferLane.

4. Operator obligations (operating practices)

These are minimum operating practices. Failure to comply is a material breach.

Do not impersonate a third party. Do not claim a domain you do not control. Do not configure a display name that suggests an affiliation you do not have.
Do not abuse the platform for outbound spam. Reach is for inbound calls to your verified domain. If a future feature enables outbound dialing, it will be governed by additional terms.
Disclose recording accurately. If you record, set recordingPolicy to consent-required or business-disclosed. Do not silently record on a none-policy endpoint.
Respect declared hours. If you publish hours, your endpoints should be staffed (by humans, AI receptionists, or voicemail) during those hours. Persistent unstaffed-during-hours patterns may result in suspension.
Keep agent credentials secure. Treat the generated REGISTER passwords as you would any production secret. Rotate (via revoke + invite) when an agent leaves.
Do not use Reach for prohibited content/use cases. See §4 of the Terms of Service and the Acceptable Use Policy.

5. Data — operator-tier specifics

The Privacy Policy §3.5.5 lists what InferLane stores about your operator account, publisher records, endpoints, and agents. In summary:

InferLane is the data controller for operator-account data (email, password hash, session cookie, audit log of dashboard actions).
InferLane is the data processor for operator-configured data (endpoint config, agent metadata, call-routing metadata).
You are the data controller for any call content (audio, transcripts, voicemail) — those never reach InferLane in the first place at v1.1.
You may export your operator data and revoke API access at any time via the dashboard. Account deletion purges within 30 days; pending call metadata still retained per the Privacy Policy retention schedule.

6. Pricing

The operator tier is free at v1.1. InferLane reserves the right to introduce paid features (e.g. signaling-uptime SLA, voicemail storage beyond default, premium agent seat counts) on at least 30 days' notice. Pricing for paid features will be disclosed in the dashboard with the ability to opt out before any charge.

7. Suspension and termination

You may close your operator account at any time via the dashboard (function lands in B-business.4) or by emailing legal@inferlane.dev.
InferLane may suspend or terminate a publisher (or your whole operator account) for material breach of this Agreement, the Terms of Service, or the Acceptable Use Policy. InferLane will give reasonable notice unless the breach poses an immediate risk (security incident, regulatory order, court order, ongoing abuse).
On termination: your endpoints stop accepting calls; the synthesized voice.json endpoint stops responding; cached agent registrations expire within 60 seconds; your data is purged on the schedule in the Privacy Policy.

8. Disclaimers, liability, indemnity

No warranty. As is. As available. The operator tier is provided "as is" and "as available." InferLane disclaims all warranties to the maximum extent permitted by law, including (without limitation) warranties of merchantability, fitness for a particular purpose, non-infringement, accuracy, availability, security, and any warranty arising from a course of dealing or usage of trade. Reach is a signaling and discovery layer — InferLane does not guarantee that any specific call will succeed, that a caller's WebRTC stack will negotiate successfully, that any TURN relay will be available, that your agent will be reachable, that any voicemail will be delivered, that any notification SMS will arrive, that DNS-TXT verification will succeed for any specific domain, or that any feature will continue to be supported in any future version.

The disclaimers in Terms of Service §5.3 (no reliance on third-party / publisher / claimant data), §5.4 (no identity verification), §5.5 (no availability guarantee), and §6 (no-warranty / as-is / as-available) apply to your use of the operator tier. The limitation-of-liability cap in ToS §7 and the force majeure clause in ToS §10.4 apply equally to this Agreement. Where this Agreement is silent and the ToS is not, the ToS controls.

In addition to the indemnity in ToS §8, you indemnify, defend, and hold harmless InferLane and its officers, directors, employees, contractors, and agents from and against any third-party claim, demand, action, proceeding, loss, liability, damage, cost, or expense (including reasonable legal fees) arising from or relating to:

Your publication of an inaccurate recordingPolicy, or your failure to obtain any call-recording, monitoring, transcription, or AI-disclosure consent required under applicable law in your jurisdiction or in any caller's jurisdiction.
Your use of a domain you do not lawfully control, or your continued operation of a Reach publisher after losing control of the underlying domain.
Your use of Reach in a regulated sector without obtaining the necessary approvals (e.g. operating a medical advice line without applicable medical-device or telehealth authorisations; operating a financial-advice line without a financial services licence; operating a gambling, alcohol, tobacco, or firearms line without the corresponding authorisation in each applicable jurisdiction).
Content transmitted during calls placed against your endpoints, including but not limited to defamation, fraud, intellectual-property infringement, unlawful disclosure of personal information, harassment, threats, or unlawful solicitation.
A caller's claim that an endpoint description, hours block, voicemail promise, recording-policy declaration, or any other text you published in the synthesized voice.json was misleading, inaccurate, or did not match the service they received.
A caller's claim that they reasonably believed an InferLane warranty applied to a transaction conducted via your endpoint when it did not (see ToS §5.2 — InferLane does not sell goods or services through Reach).
A claim by your agent, customer, or other third party arising from a missed call, voicemail not delivered, SMS notification not received, or any other availability gap.
A regulatory action against you arising from your operation of a Reach endpoint, including any STIR/SHAKEN, robocall, telemarketing, or do-not-call enforcement action; nothing in this Agreement transfers any such regulatory exposure from you to InferLane.
Taxes, duties, or fees assessed on any transaction you conducted via a Reach call or capability.

9. Dispute resolution; governing law

The dispute-resolution clauses in Terms of Service §10 (binding individual arbitration; no class action or mass arbitration; 30-day opt-out right) apply equally to this Agreement. The governing law is the law of New South Wales, Australia.

10. Changes to this Agreement

InferLane may update this Agreement. Material changes will be notified via a banner on the operator dashboard and by email to the account address at least 30 days before they take effect. Your continued use of the operator tier after the effective date constitutes acceptance.

11. Contact

Legal questions, disputes, account transfers: legal@inferlane.dev. Privacy / data subject requests: privacy@inferlane.dev.

Note on this document. This Agreement is intended to be plain, honest, and substantive. It is provided as part of the Reach by InferLane open-source project. It is not legal advice. If you are operating Reach for a business with material regulatory exposure (banking, healthcare, securities, alcohol/tobacco/firearms, gambling), retain qualified counsel in your jurisdiction before launch.