Cookie Policy

Last updated 17 October 2026

What this covers

This policy explains the cookies and similar technologies used on meetmarcelo.ai and in the Marcelo application, operated by Marcelo AI Inc. It is part of our privacy policy.

A cookie is a small text file a website stores in your browser. Browser storage (“local storage”) is a similar mechanism that keeps a value on your device without sending it with every request. Both are covered here.

Cookies we use

We use cookies for one purpose: keeping you signed in and keeping the service secure.

  • Authentication cookies. Set by our authentication provider, Clerk, when you sign in. They identify your session so that each page knows who you are, and they protect against a request being forged from another site. They are strictly necessary: without them you cannot sign in. They expire when the session ends or when you sign out.
  • Demo link cookie. If you open a demo link somebody sent you, a first-party cookie records which demo you are looking at so the pages that follow show the right one. It is set only when such a link is opened, and it holds no personal information.
  • Hosting cookies. Our hosting provider, Vercel, may set a cookie needed to route your request to the right server. It is strictly necessary and identifies nobody.

We do not use advertising cookies. No advertising network, social media pixel or cross-site tracker runs on the site or in the application.

Visits to our home page. The public home page of meetmarcelo.ai uses Google Analytics to count visits and see which parts of the page are read. Google Analytics sets its own cookies (named _ga and _ga_*) for this. It runs only on the public home page, never inside the Marcelo application.

Browser storage

The application keeps a small number of preferences in your browser’s local storage — for example which view of a screen you last used, or whether a notice has been dismissed. These values never leave your device and are not read by us. Clearing your browser’s site data removes them.

Error reporting

When something in the application fails, a report of the error is sent to our error monitoring provider, Sentry, so that we can fix it. The report describes what went wrong and the state of the screen; it is configured not to send personal details by default. This is done by the application itself rather than by a cookie.

Websites Marcelo hosts for customers

Marcelo builds and hosts websites for the businesses that use it. Those websites belong to those businesses, and any cookies on them — including Google Analytics or Google Tag Manager, where the business has connected them — are set under the business’s own cookie and privacy policies, not this one. This policy covers only meetmarcelo.ai and the Marcelo application.

Your choices

Apart from the analytics cookies on the public home page, the cookies we set are strictly necessary. You can block or delete cookies in your browser’s settings at any time; blocking the authentication cookies will prevent you from signing in. You can also stop Google Analytics with Google’s own opt-out browser add-on.

Changes

If we add a cookie or a tracking technology that is not described here, we will update this page before it goes live. The date at the top is the date of the current version.