Cookie Policy

1.What we use, in one paragraph

Deliverd sets the cookies it needs to sign you in, remember which organisation you are working in, and prove to the origin serving a report that you are allowed to read it. Those cannot be switched off without breaking the product.

The only optional thing we set is Google Analytics, on these public marketing pages, and only after you accept. It never runs inside the product and never on a published report.

These pages also count visits and measure their speed with Vercel Web Analytics and Speed Insights, which set no cookies and store nothing in your browser, so there is nothing for you to accept or decline.

Change your mind any time on the cookie settings page.

2.Three places, three different rules

Deliverd runs on more than one hostname, and which cookies you meet depends on where you are.

• These marketing pages — the only place any optional or third-party cookie exists.
• The product, where you sign in and publish — strictly necessary cookies only, no analytics, no third parties.
• Published reports, served from a separate origin — one short-lived viewer cookie and nothing else. No analytics, no third-party scripts, and a content security policy that blocks outbound requests by default, so a report cannot quietly load a tracker either.

3.Strictly necessary cookies

These are set because the service cannot work without them, so they do not require consent and cannot be turned off in our settings. Blocking them in your browser will sign you out and stop reports from opening.

4.Analytics cookies

We use Google Analytics to see how many people reach these pages and which ones they land on. Nothing is requested from Google — not even the script, which would disclose your IP address — until you press Accept.

With your consent, we also record a few interactions on these pages, so we can tell which parts help people get started:

• clicks on a sign-up button, and where on the page it was
• copying a code sample
• the words typed into the docs search
• whether a docs search found nothing
• that the contact form, the chat assistant's form for reaching a person, or the guide request at /ebook was sent (never what was in it)
• reaching the pricing section
• which of the two buttons at the top of the home page was clicked
• whether the developer or the business starting point on the home page was followed
• how far through the home page walkthrough a visitor stepped
• clicks on a plan's button, and which plan
• clicks on a button to book a governed AI pilot, and where on the page it was
• clicks on a comparison page's sign-up button, and which comparison
• that the partner application was sent (never what was in it)
• that the chat assistant was opened (never what was asked)

None of these carries anything you typed into a form, except the words you type into the docs search. The contact form and the partner application record only that they were sent.

Declining is one click, exactly like accepting, and you can withdraw consent later without penalty. We do not use advertising cookies, we do not build profiles, and we do not track you across other sites.

5.What is stored that is not a cookie

Two choices are stored in your browser’s local storage rather than in a cookie, and are listed here so that a reader auditing what we set finds nothing unexplained:

Neither leaves your browser. Because they are stored per browser, a different browser or a private window will ask you again.

6.How to change your mind

Use the cookie settings page. The change applies immediately — accepting loads analytics on your next page view, and declining stops it at once: nothing further is sent, the _ga cookies are deleted, and the page reloads so the script is gone too.

Every browser can also block or delete cookies for a site, and clear local storage with them. That will clear your stored choice too, so we will ask again next time.