Cookie Policy

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:

• PostHog for product analytics, page-view events, user identification where applicable, and optional session replay if configured.
• Vercel Analytics for site analytics.
• Vercel Speed Insights for performance measurement.
• Web vitals and internal performance signals.

PostHog analytics preferences. PostHog is our product analytics tool. Rejecting non-essential cookies disables PostHog 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 PostHog cookies or local storage identifiers and does not identify you as a person.

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, does not use third-party ad pixels, and does not store free-text form contents, file contents, or emails typed into product forms.

If you accept analytics, PostHog may use first-party cookies and browser storage, identify your account for session continuity, build person profiles where configured, and record sessions (with inputs masked) where enabled.

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

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 does 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.

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.
• PostHog for product analytics and session replay where configured.
• Cloudflare Turnstile for bot prevention and challenge verification.
• Calendly for scheduling embeds and booking flows.
• 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 Accept or Reject non-essential cookies, or open Manage 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, PostHog product analytics and optional session replay. Off until you allow it.
• Functional & embeds, third-party embedded tools such as Calendly scheduling. Off until you allow it.

Your decision is recorded in your browser under the edgaze:cookie-consent local-storage key and mirrored to the edgaze_consent cookie so it can be remembered across visits. The decision is versioned; if our categories change in a way that requires fresh consent, the banner reappears. 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, scheduling, payment, security, marketplace, or workflow technologies.

Contact#

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