EdgazeDocsEdgaze Docs
BuilderBilling & RunsAPI ReferenceMCPLegal & TrustChangelog
DocumentationAPI Reference
Home
Legal & Trust Center
Core Platform
Terms of ServicePrivacy PolicyCookie PolicyAcceptable Use PolicyPlatform Status and Beta DisclaimerContent Disclaimer
Marketplace & Payments
Payments OverviewMarketplace FeesCreator EarningsPayout SystemRefund PolicyChargeback PolicyPricing Limits
Creator Rules
Creator TermsCreator GuidelinesWorkflow Run PolicyInfrastructure Cost EstimationModel CatalogCreator Subscription Policy
Trust, Safety & IP
Community GuidelinesFraud and Abuse PolicyDMCA and IP Takedown PolicySecurity and Responsible Disclosure

Platform status

Checking platform status
Theme
Legal & Trust Center / Core Platform

Cookie Policy

How Edgaze uses cookies, local and session storage, analytics, ad measurement, embeds, security tools, and payment technologies.

Explains how Edgaze and third-party services use cookies, local storage, session storage, analytics, embedded scheduling, security tools, and payment technologies.
Applies to Visitors, Users, Creators, Customers.

Overview#

This Cookie Policy explains how Edge Platforms, Inc. uses cookies, local storage, session storage, pixels, SDK storage, embedded third-party technologies, and similar browser technologies on Edgaze.

It should be read with the Privacy Policy. The Privacy Policy explains broader data handling; this policy focuses on what may be stored in or read from your browser.

What We Mean by Cookies and Similar Technologies#

Cookies are small files placed on your browser or device. Local storage and session storage are browser storage mechanisms that can keep information on your device. SDK storage, pixels, scripts, iframes, and embeds may also collect or store identifiers, preferences, event data, or security signals.

Edgaze uses these technologies directly and through service providers.

Categories We Use#

Strictly Necessary Technologies#

These support core platform operation, authentication, security, routing, checkout, fraud prevention, and reliability.

Examples include:

  • Supabase authentication and session behavior.
  • Return-path storage used after sign-in or checkout flows.
  • Admin impersonation security cookies where applicable.
  • Cloudflare Turnstile proof cookies or related bot-prevention signals where Turnstile is used.
  • Stripe checkout, embedded checkout, Connect, and payment-related browser technologies.
  • Storage used to recover from outdated app versions or route transitions.

Disabling these technologies may break sign-in, checkout, demo runs, anti-abuse checks, or other platform features.

Analytics and Performance Technologies#

Edgaze uses analytics and performance tools to understand product usage, page performance, conversion, reliability, and feature health.

Current code uses:

  • Mixpanel for product analytics, page-view events, user identification after you accept, and session replay after you accept.
  • PostHog for mirrored product analytics events. PostHog does not record sessions.
  • Vercel Analytics for site analytics.
  • Vercel Speed Insights for performance measurement.
  • Web vitals and internal performance signals.

Mixpanel analytics preferences. Mixpanel is our product analytics and session replay tool. Rejecting non-essential cookies disables Mixpanel analytics cookies, local storage persistence, identity tracking, person profiles, and session replay.

If you reject (or have not yet chosen), Edgaze may still collect basic cookieless product analytics to understand aggregate usage and keep the platform reliable. Cookieless analytics does not store Mixpanel cookies or local storage identifiers, does not identify you as a person, and does not record sessions. PostHog may receive the same cookieless events.

Edgaze also runs first-party product-page telemetry (session storage for same-visit funnel stitching; optional persistent anon id in local storage only when you accept analytics). This powers marketplace operation, creator analytics, and conversion reliability. It does not sell data and does not store free-text form contents, file contents, or emails typed into product forms. Google Ads measurement is separate and covered under Marketing Technologies.

If you accept analytics, Mixpanel may use first-party cookies and browser storage, identify your signed-in account for session continuity, and record sessions (with inputs masked), including for logged-out visitors. Known bots and crawlers are excluded. PostHog may receive mirrored events and does not record sessions.

Your choice in the cookie preference center is the canonical browser record for optional analytics.

Older browser flags edgaze:disable_mixpanel and edgaze:disable_posthog are still treated as a reject decision.

Server-side events. Some product events (for example a workflow run starting or finishing, a workflow being created or published, a checkout starting, or a purchase completing) are sent to Mixpanel and PostHog from Edgaze's servers rather than your browser. They are tied to your account only when your browser's edgaze_consent cookie records that you allowed analytics in the current version of the preference center. Otherwise, including when you have not chosen yet, they are sent anonymously: with no account ID, device identifier, or person profile, and a new random ID for each event. Events that do not come from your browser, such as payment confirmations from Stripe, scheduled jobs, the workflow runtime, and calls through the Edgaze MCP server, are always sent anonymously. This does not change the records Edgaze keeps in its own database to operate the platform, such as run history and creator dashboards.

Vercel Analytics and Vercel Speed Insights are cookieless. They measure aggregate traffic and page performance without setting cookies or storing identifiers on your device, so we treat them as strictly necessary and they run without a separate consent step.

Security, Abuse Prevention, and Demo-Limit Technologies#

Edgaze may use browser signals and storage to prevent abuse, enforce demo limits, verify bot challenges, detect stale sessions, reduce duplicate actions, and protect hosted workflow infrastructure.

Examples include:

  • Cloudflare Turnstile scripts and proof cookies for verification where enabled.
  • Device or browser signals for demo run limits.
  • Local storage used for one-time or limited demo-run checks.
  • Logs and request metadata used with server-side abuse controls.

Platform Preference and Workflow Technologies#

Edgaze may use local storage or session storage for product experience details such as:

  • Returning users to the page they intended to visit after authentication.
  • Remembering user-initiated purchase or run intent during redirects.
  • Draft support for feedback or bug forms.
  • Builder, demo, marketplace, or workflow runtime UI state.
  • Temporary client-side caches that improve responsiveness.

These storage items are not a substitute for server-side records and may be cleared by your browser.

Payment and Payout Technologies#

Stripe and Stripe Connect may use cookies, scripts, frames, redirects, device signals, and browser storage to process payments, prevent fraud, support embedded checkout, operate Connect onboarding, comply with legal obligations, and secure payment flows.

Stripe controls its own payment technologies under Stripe's terms and privacy policy.

Scheduling and Calendly Embeds#

Edgaze uses Calendly scheduling in some places, including an inline widget on the contact page and a popup scheduling widget on the invest page.

Calendly embeds load scripts and assets from Calendly domains and may set or read cookies, local storage, or similar technologies for scheduling, availability, routing, analytics, fraud prevention, preference, and session purposes. Calendly may collect information such as scheduling details, browser data, IP address, referral data, and interaction data under Calendly's own terms and privacy policy.

Because Calendly is a third party that can set its own cookies, these embeds fall under the Functional & embeds consent category. Calendly's scripts and stylesheets do not load until you allow that category; until then you'll see a short notice with a one-click option to enable scheduling. Some Edgaze embeds may hide Calendly's own GDPR banner for a cleaner in-product experience. Hiding that banner does not mean Calendly sets no cookies or uses no similar technologies.

Marketing Technologies#

Edgaze uses Google Ads to measure which ads bring people to Edgaze. This falls under the Marketing consent category, which is off until you allow it.

  • Before you allow marketing, Edgaze does not load Google's tag (gtag.js), sends nothing to Google Ads, and stores no ad click identifiers. If you arrive from an ad, the click identifier in the page address (gclid, gbraid, or wbraid) is only held in memory for that page and is stored only if you allow marketing before leaving it.
  • After you allow marketing, Edgaze loads Google's tag from googletagmanager.com with Google Consent Mode set to grant ad storage and ad user data. Ad personalization stays denied, and Edgaze does not use Google Analytics. Google may set its own first-party conversion cookies, such as _gcl_aw and _gcl_au.
  • Conversions. With marketing allowed, Edgaze tells Google Ads when an account is created and when a workflow run completes, using the account ID or run ID only as a de-duplication key. A session-storage flag (edgaze:ads-conv:…) stops the same conversion being sent twice.
  • Click identifiers. With marketing allowed, ad click identifiers are stored in the edgaze:ads-click-ids local-storage key and the edgaze_ads_click cookie for up to 90 days, and copied to your account when you sign up so a later sign-up can be attributed to the ad click.
  • If you withdraw marketing, Edgaze updates Consent Mode to denied, deletes the edgaze:ads-click-ids key and the edgaze_ads_click cookie, and expires Google's _gcl_ cookies. A tag already loaded on the open page stays loaded until you leave or reload it, but with consent denied it no longer sets ad cookies.

Google processes this information under its own terms and privacy policy.

Third-Party Providers#

Depending on the page or feature, browser technologies may be provided by:

  • Supabase for authentication and platform data infrastructure.
  • Stripe for checkout, payments, Connect onboarding, fraud prevention, and payout-related flows.
  • Vercel for analytics, performance insights, and hosting infrastructure.
  • Mixpanel for product analytics and session replay where configured.
  • PostHog for mirrored product analytics events (no session replay).
  • Cloudflare Turnstile for bot prevention and challenge verification.
  • Calendly for scheduling embeds and booking flows.
  • Google Ads for ad conversion measurement, only after you allow marketing.
  • AI/model or external API providers indirectly, when a workflow opens or calls third-party services.

Third-party providers may process information under their own policies. Edgaze does not control all cookies or storage used by third-party scripts, embedded widgets, or payment flows.

Your Choices#

Cookie Preference Center#

Edgaze provides a built-in cookie preference center. When you first arrive, a small banner lets you Allow all optional categories, keep Essentials only, or open Preferences for category-by-category control. You can reopen it anytime from the Cookie preferences link in the site footer or by visiting /cookie-preferences.

You can choose per category:

  • Strictly necessary, always on; cannot be disabled. Includes cookieless performance measurement (Vercel Analytics and Speed Insights).
  • Analytics & performance, Mixpanel product analytics and session replay after you allow it. Off until you allow it. Rejecting this category keeps cookieless events only.
  • Functional & embeds, third-party embedded tools such as Calendly scheduling. Off until you allow it.
  • Marketing, Google Ads conversion measurement and ad click identifiers. Off until you allow it.

Allowing everything turns on every optional category; Essentials only (or Reject all in the preference center) turns them all off.

Your decision is recorded in your browser under the edgaze:cookie-consent local-storage key and mirrored to the edgaze_consent cookie for up to 180 days so it can be remembered across visits and so Edgaze's servers can respect it. The decision is versioned; if our categories change in a way that requires fresh consent, the banner reappears. Adding the Marketing category was such a change, so earlier decisions are asked again and never count as consent to marketing. Clearing your browser storage resets your choice and shows the banner again.

Browser controls#

You can also control cookies through your browser settings, and clear local storage and session storage through browser developer tools or privacy settings.

Blocking cookies, JavaScript, third-party scripts, local storage, iframes, or embedded widgets may prevent Edgaze features from working. For example, sign-in, checkout, Stripe Connect onboarding, Calendly scheduling, Turnstile verification, demo run limits, or route recovery may fail or behave unexpectedly.

Changes#

We may update this Cookie Policy as Edgaze adds or changes analytics, advertising measurement, scheduling, payment, security, marketplace, or workflow technologies.

Contact#

For questions about cookies or privacy, contact support@edgaze.ai.

Was this useful?

Your response helps us improve the documentation.

Also in the docs

  • Builder
  • Billing & Runs
  • API Reference
  • MCP
  • Legal & Trust
  • Changelog

Related policies

Back to Legal & Trust Center
Privacy Policy

How Edge Platforms, Inc. collects, uses, shares, stores, and protects information across Edgaze.

Terms of Service

The core terms for using Edgaze: product use, publishing, marketplace transactions, hosted AI runs, platform limits, and legal responsibilities.

Security and Responsible Disclosure

How to report Edgaze security issues and the boundaries for good-faith vulnerability reporting.

Open Workflow BuilderOpen Workflow StudioBrowse workflow templatesVisit the marketplaceLearn about creators
On this page
OverviewWhat We Mean by Cookies and Similar TechnologiesCategories We UseStrictly Necessary TechnologiesAnalytics and Performance TechnologiesSecurity, Abuse Prevention, and Demo-Limit TechnologiesPlatform Preference and Workflow TechnologiesPayment and Payout TechnologiesScheduling and Calendly EmbedsMarketing TechnologiesThird-Party ProvidersYour ChoicesCookie Preference CenterBrowser controlsChangesContact
© 2026 Edge Platforms, Inc. All rights reserved.