# Celest Privacy Effective date: 2026-07-28 Contact: [Email Celest](mailto:founders%40celest.dev) Raw retention: at most 3 months Canonical URL: https://celest.dev/privacy Celest uses a deliberately small, first-party analytics boundary for its public website. The goal is to measure whether public resources lead to meaningful product exploration and conversations without creating visitor profiles. Short version ------------- - No analytics cookies - No local-storage identifier - No fingerprint - No raw IP address or raw user-agent string in Celest's analytics dataset - No sale or sharing for targeted advertising - No person-level website identification What Celest collects -------------------- Cloudflare hosts and protects the site and 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` - `landing.estate_review_open` - `estate_review.request_intent` - `landing.contact_intent` Each event includes only: - a fixed event name; - its page and placement; - one reviewed referring-source category; and - campaign labels selected from a finite public vocabulary when those labels are present in the URL. The analytics event does not receive a submitted name or website, generated content, artifact content, demo-session identifier, or other freeform user submission. Cloudflare Workers Analytics Engine supplies the observation time. The demo host does not load this analytics script. Machine-readable ---------------- - [Event manifest](https://celest.dev/analytics/manifest.json): the exact public website event contract. - [Markdown representation](https://celest.dev/privacy.md): this representation of the privacy notice. What Celest does not collect through analytics ---------------------------------------------- - 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; - 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; and - third-party advertising, retargeting, session-replay, or identity-resolution pixels. How Celest uses the signal -------------------------- Celest uses aggregate measurements to answer a narrow set of questions: - whether people and agents can reach canonical resources; - which public paths lead to team-demo exploration, Estate Review interest, or contact intent; and - whether the public 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. Measurement is not authority ---------------------------- Analytics does not create a customer record, score a person, grant access, or trigger automated outreach. AI crawlers and MCP ------------------- Celest keeps discovery crawls, user-directed retrieval, and explicit MCP activity separate. User-agent strings can be spoofed, so Celest does 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. It retains the operation name and requested MCP pathname, which identifies the corpus endpoint or a particular scoped resource endpoint. It does 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. Celest does not send the analytics events described here to Google Analytics, Google Tag Manager, RB2B, or another advertising or identity-resolution provider. Choices and updates ------------------- Because this analytics model creates no durable browser identifier, there is no analytics profile for a visitor 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, Celest will update this notice and the public analytics manifest before expanding collection. Privacy questions or requests can be sent by [emailing Celest](mailto:founders%40celest.dev).