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 stale deployments 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 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.

Mixpanel is initialized after page load and uses cookie persistence when configured. Edgaze also supports an opt-out flag in local storage: `edgaze:disable_mixpanel`.

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.

Some Edgaze embeds may hide Calendly's 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.
• Mixpanel for product analytics 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

You can control cookies through your browser settings. You can also 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, analytics opt-out storage, demo run limits, or route recovery may fail or behave unexpectedly.

To opt out of Mixpanel tracking in browsers where local storage is available, set `edgaze:disable_mixpanel` to `true` in local storage. This opt-out is browser-specific and may not affect other analytics, performance, security, payment, or third-party embedded technologies.

No Universal Consent Tool Yet

Edgaze does not currently provide a full cookie preference center in the codebase reviewed for this policy. Where required by law, Edgaze may add consent controls, region-specific notices, or additional configuration for analytics and third-party embeds.

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 `[email protected]`.