Useful signal,
without visitor profiles.

What we collect

Cloudflare hosts and protects this site. Like any delivery and security provider, it receives ordinary request information needed to serve traffic and defend the service. Celest uses aggregate edge information to understand route availability, request volume, and crawler activity.

On Celest pages, a small script records only reviewed high-intent actions: landing.team_demo_open opens the Day One team experience, landing.estate_review_open opens the Estate Review product, estate_review.request_intent starts an Estate Review request, and landing.contact_intent starts a general contact email. Each event contains a fixed event name, its page and placement, one reviewed referring-source category, and campaign labels selected from a finite public vocabulary when they are present in the URL. It never receives a submitted name or website, generated content, artifact, or demo-session identifier. Cloudflare Workers Analytics Engine supplies the observation time. The demo host itself does not load this analytics script.

The exact public event contract is available in the analytics manifest.

What we do not collect

• Analytics cookies, local-storage identifiers, or persistent visitor IDs
• Device or browser fingerprints
• Raw IP addresses or raw user-agent strings in the Celest analytics dataset
• Full referrer URLs, query strings, or search terms
• Email addresses, names, company names, form text, or clipboard contents through analytics
• Submitted display names or company URLs from the Day One journey
• Demo or session identifiers
• Generated content, artifact content, or receipt content
• MCP questions, tool arguments, resource contents, or tool results
• Third-party advertising, retargeting, session-replay, or identity-resolution pixels

How we use the signal

We use aggregate measurements to answer a narrow set of questions: whether people and agents can reach the canonical resources, which public paths lead to team-demo exploration, Estate Review interest, or contact intent, and whether the Learn MCP surface is useful. A click that opens an email client is only contact intent; Celest treats an email actually received and qualified by a founder as the business outcome.

AI crawlers and MCP

Celest keeps discovery crawls, user-directed retrieval, and explicit MCP activity separate. User-agent strings can be spoofed, so we do not describe a crawler as provider-verified without additional network evidence.

For the public Learn MCP server, Celest counts successful initialization and calls to the ask and similar tools. We retain the operation name and requested MCP pathname, which identifies the corpus endpoint or a particular scoped resource endpoint. We do not retain the question, query, arguments, retrieved passages, or result. MCP clients may send Celest-Analytics: omit to suppress these operation counts.

Retention and providers

Raw first-party event observations are retained for no more than Cloudflare Workers Analytics Engine's current three-month window. Celest may retain longer-lived aggregate counts that cannot reasonably be used to reconstruct a person's browsing activity.

Cloudflare is the hosting, security, and analytics infrastructure provider for this public site. We do not send the analytics events described here to Google Analytics, Google Tag Manager, RB2B, or another advertising or identity-resolution provider.

Your choices

Because this analytics model creates no durable browser identifier, there is no analytics profile for you to retrieve or delete from a cookie ID. Browser content blockers may prevent the optional landing-page event request without affecting the site. Celest does not sell this information or use it for cross-context behavioral advertising.

If this model changes, we will update this notice and the public event manifest before expanding collection. Questions or privacy requests can be sent to [email protected].