Cookie Policy
one short-lived cookie, and no tracking.

We set one cookie, and only when you connect an MCP client (such as an AI app) to your account:

• __Host-alertmcp-consent — set by our API server while you approve the connection, so the approval page only works in the browser that started it. HTTP-only, secure, expires after 10 minutes and is deleted as soon as you approve.

Signing in with Google, GitHub or Apple may set cookies on their own sites; those are covered by their policies.

The dashboard keeps a few items in your browser’s local storage. They stay on your device and are not sent to us except for your sign-in token:

• authToken — your sign-in token, sent with each request to our API. Removed when you sign out.
• persist:alertmcp — your signed-in state and profile (name, email, avatar), so the dashboard loads without a flash.
• alertmcp.active-workspace — the workspace you last opened.
• alertmcp.sidebar-collapsed — whether the sidebar is collapsed.
• alertmcp.dashboard.v2 — sample data for the demo dashboard, only if you try the demo.

After an update, a short-lived entry in session storage (alertmcp:chunk-reload-at) stops the page from reloading in a loop.

The site loads its fonts from Google Fonts, which receives your IP address and browser details when you visit but sets no cookies. We do not use analytics, advertising or social media scripts.

Signing out removes your token. You can clear everything above at any time in your browser’s site settings. Questions? Email legal@alertmcp.com.