Privacy notice

○Content pending Owner: Legal / DPO

Must state: the legal entity name, its registered address and company number, the governing jurisdiction, and which party is controller and which is processor for each category of data. Where the business using Call Marlin is the controller of its callers’ data, this section has to say so plainly.

○Content pending Owner: Legal / DPO, with Engineering

Must list, by category: what a caller provides during a call, what the system generates about the call, what the pilot request form collects, and what the website collects from a visitor who does nothing but read. Six form fields are collected today — name, email, business name, industry, optional website, optional call-volume range — plus an optional marketing preference.

○Content pending Owner: Legal / DPO

Must give a purpose and a lawful basis per category, and must keep the marketing preference separate from the basis for replying to a pilot request. The form treats those as two different things; this section has to as well.

○Content pending — launch blocker Owner: Legal / DPO, with Engineering

Must state what happens to microphone audio and to transcripts: whether they are stored at all, in what form, who can reach them, and what a caller is told before recording starts. No wording here may claim that audio is never stored unless that has been verified against what the running system actually does.

○Content pending — launch blocker Owner: Legal / DPO, with Engineering

Must give a retention period per category, with the criterion used to set it and what happens at the end of it. No period is stated anywhere on this site today and none is estimated here. This slot also gates the live demo’s microphone permission dialog.

○Content pending Owner: Legal / DPO

Must name each sub-processor, what it does and where, and how a change to the list is notified. Speech processing, model inference, telephony carriage, email delivery and any automation connector in the path all belong on that list.

○Content pending Owner: Legal / DPO

Must state the processing locations and the mechanism for any transfer out of the governing jurisdiction. Depends on section 1 and on the launch market, neither of which is fixed.

○Content pending Owner: Legal / DPO

Must set out the applicable rights, the route to exercise each, the identity checks applied, and the response window committed to. The working route today is the request form, described accurately as a general intake on data handling and controls rather than as a published data-protection contact.

○Content pending Owner: Legal / DPO, with Engineering

Must list every cookie and storage key actually set, with its purpose and lifetime, and describe the consent mechanism if any non-essential one is used. Engineering has to confirm the real list before this can be written — a copied cookie table is worse than none.

○Content pending Owner: Legal / DPO, with Engineering

Must cover the demo specifically: that it runs on sample business data, makes no real bookings and contacts no third parties; what happens to audio captured during a session; and what ending a session does. This has to agree word for word with the permission dialog the demo shows.

○Content pending Owner: Legal / DPO

Must state the position on data from children, including the case of a child calling a business that uses the product.

○Content pending Owner: Legal / DPO

Must say how a change is notified, how much notice is given for a material one, and where previous versions can be read. The version and last-updated slots at the top of this page are the fields that carry it.

○Content pending Owner: Legal / DPO

Must give a named contact address, the escalation route inside the company, and the supervisory authority a complaint can be taken to. All four depend on section 1.