Terms
Terms of service
The content of these terms is pending legal sign-off. The structure below is final; the wording inside each section is supplied separately and is not drafted by design.
Not yet in force. Nothing here binds anyone. No terms of service have been approved for Call Marlin. Every section below is an empty slot showing what that section has to cover and who owns it. A pilot today is governed by the pilot agreement you actually sign, not by this page.
1. Who these terms are between
Content pending Owner: Legal / DPO
Must name the legal entity, its registered address and company number, and define “you” — the business, not the caller. It also has to state how these terms sit against a signed pilot agreement, and which one wins where they differ.
2. What the service is
Content pending Owner: Legal, with Founder / product
Must describe the service in terms narrow enough to be true: it answers calls, holds a conversation, captures a request, and performs the follow-up actions configured for that deployment. It must not describe capability the product does not have.
3. Pilots, and what a pilot is not
Content pending Owner: Legal, with Founder / product
Must define the pilot: its scope, its duration, what ends it, what happens to configuration and data afterwards, and the fact that a submitted request on the website creates no obligation on either side.
4. What you are responsible for
Content pending Owner: Legal
Must cover the customer’s side: accuracy of the workflow rules and limits they configure, the authority to grant the system access, staffing the escalation path they nominate, and acting on unknown-outcome alerts when they appear.
5. Acceptable use and prohibited sectors
Content pending Owner: Legal / DPO, with Founder / product
Must state which uses are out of scope without a separate review. Healthcare, financial advice, recruiting decisions and emergency or safety-critical lines all need explicit treatment rather than silence. Outbound calling, if it is not offered, has to be excluded in words.
6. Call recording and caller notification
Content pending Owner: Legal / DPO
Must allocate responsibility for telling callers they are speaking to an automated system and, where applicable, that the call is recorded. It has to interlock with the retention slot in the privacy notice, which is also empty.
7. Charges, billing and taxes
Content pending Owner: Finance / commercial, with Legal
Must set out currency, billing period, the usage unit and how it is measured, included allowance, overage, telephony pass-through, setup and custom-work rates, payment terms, taxes and what happens on non-payment. Every one of those is unset — pricing shows the same slots waiting.
8. Third-party systems and connectors
Content pending Owner: Legal, with Engineering
Must state who carries the risk when a connected system or an automation connector fails, changes its interface, or writes something unexpected — and must match the failure behaviour published on integrations.
9. Service levels, and the absence of them
Content pending Owner: Legal, with Engineering
Must say plainly whether any availability or response commitment exists. No uptime, latency or accuracy figure has been measured, so this section either commits to something measured or says there is no commitment. It may not imply one.
10. Data protection
Content pending Owner: Legal / DPO
Must reference or incorporate the processing terms: roles, instructions, sub-processor consent, security measures, breach notification, audit and deletion on termination. Depends on the privacy notice, which is not written.
11. Confidentiality and intellectual property
Content pending Owner: Legal
Must cover both directions, and say explicitly whether customer call content may be used to improve or train any model. That answer materially affects whether a business can adopt the product, so it cannot be left to inference.
12. Warranties and disclaimers
Content pending Owner: Legal
Must disclaim what the product genuinely does not do, in the same words the rest of the site uses: no diagnosis, no pricing, no duration estimate, no safety advice, and no confirmation of an outcome a connected system has not confirmed.
13. Liability
Content pending Owner: Legal
Must set the caps and exclusions, and handle the specific case a customer will ask about: a booking that was missed, duplicated or written wrongly. Depends on section 7, since caps are usually expressed against charges.
14. Term, suspension and termination
Content pending Owner: Legal
Must give notice periods both ways, the grounds for suspension, what happens to call records and configuration on exit, and how a number is released back. Ending must be as easy as starting.
15. Changes to the service and to these terms
Content pending Owner: Legal
Must say how a change is notified, how much notice a material change gets, and what a customer may do if they do not accept it. The version and last-updated slots at the top of this page are the fields that carry it.
16. Governing law and disputes
Content pending Owner: Legal
Must state the governing law, the forum, and the escalation route before formal proceedings. Depends on section 1 and on the launch market, neither of which is fixed.
While this page is empty
The things a terms page would normally pin down about behaviour — what the agent may do, where it stops, what is logged, who can see it — are written and published on data handling and controls, with a register of every unconfirmed item. That page is not a contract and does not pretend to be one. For a pilot, the document that matters is the pilot agreement you sign.
Need to see the contract before you go further?
Say so in your pilot request. You will get the current draft position, including which sections above are still empty.