Privacy Policy

Introduction#

This Privacy Policy explains how Edge Platforms, Inc. ("Edgaze," "we," "us," or "our") collects, uses, shares, stores, and protects information when you access or use Edgaze.

Edgaze is a platform for building, publishing, discovering, running, selling, and buying executable AI workflows and prompt products. Privacy on Edgaze includes ordinary account data, marketplace records, AI workflow inputs and outputs, execution logs, creator information, payment-related records, security data, and analytics data where enabled.

Scope#

This Policy applies to visitors, account holders, creators, customers, workflow publishers, prompt publishers, buyers, applicants, and other users of Edgaze.

It applies to the website, builder, templates, marketplace, legacy prompt products, hosted workflow runs, creator dashboards, checkout flows, payout onboarding surfaces, support channels, and related services.

Information We Collect#

We collect information depending on how you use Edgaze.

Account and Profile Data#

We may collect your name, email address, username or handle, profile information, avatar, bio, preferences, authentication identifiers, account status, and related settings.

Creator and Payout-Related Information#

If you publish or monetize Products, we may collect creator profile information, listing details, payout onboarding status, Stripe Connect account identifiers, payout eligibility signals, creator earnings records, pending-claim records, payout display records, refund records, dispute records, country information used for onboarding, and related compliance or accounting information.

Stripe may collect additional identity, tax, bank, verification, and compliance information directly under its own terms and privacy policy.

Workflow, Prompt, Listing, and Product Content#

We collect Creator Content, including workflow definitions, prompt text, product titles, descriptions, images, thumbnails, examples, demos, pricing, metadata, Edgaze codes, configuration, and related publishing materials.

Published listings, creator profiles, workflow pages, prompt pages, public templates, and marketplace metadata may be public.

Run Inputs, Outputs, and Execution Logs#

When a Product is run, Edgaze may collect and store Customer Inputs, runtime configuration, API key routing metadata, run status, timestamps, errors, run outputs, generated files, node state, trace data, execution events, duration, and related logs.

Run records may be used for access control, run limits, debugging, fraud prevention, abuse detection, support, creator analytics where available, marketplace integrity, and operational reliability.

Purchase and Payment Records#

We collect transaction, payment, refund, dispute, payout, and receipt information needed to provide the service, prevent fraud, support users, meet legal obligations, and maintain accounting records. Payment processors may provide transaction and account identifiers associated with these activities.

We do not intentionally store full card numbers. Payment processing is handled by Stripe.

Support, Reports, and Communications#

We collect information you send through support, bug reports, security reports, creator claims, takedown notices, refund requests, chargeback communications, application forms, and other messages.

Device, Browser, IP, and Log Data#

We may collect IP address, user agent, browser, device type, operating system, timestamps, URLs, referrers, request metadata, security events, rate-limit signals, bot-detection signals, approximate location derived from technical data, and diagnostic logs.

Cookies, Local Storage, and Session Data#

Edgaze uses cookies, local storage, session storage, and similar technologies for authentication, session management, routing, security, impersonation controls for admins where applicable, demo run limits, preferences, product analytics, and payment or checkout flows.

Analytics Data#

Where enabled, Edgaze uses product analytics and performance tools, including Mixpanel, PostHog, Vercel Analytics, and Vercel Speed Insights. These tools may collect page views, events, interaction data, device and browser data, approximate location, session identifiers, session recordings where configured, and performance data.

Your cookie preferences have four categories: necessary, analytics, functional, and marketing. Vercel Analytics and Vercel Speed Insights are cookieless. PostHog receives mirrored events, runs cookieless, and does not record sessions. Mixpanel, which is the session replay tool, and session replay itself run only after you accept analytics, and may then use first-party cookies and browser storage. Product events recorded on our servers are linked to your account only when you have accepted analytics; otherwise they are sent without account or persistent identifiers.

Advertising Measurement#

Edgaze advertises through Google Ads. The Google Ads tag loads only after you accept marketing cookies. When it loads, Google and Edgaze may use cookies and the ad click identifiers in the link you arrived from (gclid, gbraid, or wbraid, stored for up to 90 days) to measure whether an ad led to a conversion, such as signing up or completing a run. See the Cookie Policy for details and to change your choices.

Edgaze also records first-party product-page events (pseudonymous session identifiers, listing identifiers, funnel steps, run outcome signals, and aggregate selection metadata) to operate the marketplace, measure conversion, and provide creator analytics. Persistent anonymous identifiers are used only when analytics preferences are accepted. We do not sell this data, do not use it for third-party advertising (ad conversion measurement is limited to what is described above), and do not store message content, uploaded file contents, or emails entered into product forms as analytics properties.

Sources of Information#

We collect information from:

• You directly, when you create an account, publish, buy, run, message, upload, or configure a Product.
• Automatic collection, through logs, cookies, local storage, analytics, security tooling, and runtime systems.
• Stripe and Stripe Connect, for payment, checkout, dispute, payout, onboarding, and account status events.
• Supabase authentication and database services, for account, session, storage, and platform data infrastructure.
• Third-party auth or integration providers, where you choose to use them or where they are part of a workflow.
• AI model and API providers, where needed to execute workflows or return outputs.

How We Use Information#

We use information to operate Edgaze, including to:

• Provide accounts, profiles, marketplace listings, builder features, legacy prompt-product access, dashboards, and hosted workflow runs.
• Execute workflows and prompt products.
• Process Customer Inputs and return Outputs.
• Maintain purchase access and ownership records.
• Process payments through Stripe and attribute creator earnings.
• Support Stripe Connect onboarding, payout eligibility, reserves, holds, refunds, disputes, and accounting records.
• Enforce run limits, BYOK requirements, account limits, and abuse controls.
• Prevent fraud, chargeback abuse, spam, scraping, credential theft, malware, and other misuse.
• Provide support, debug errors, investigate reports, and improve reliability.
• Analyze product usage, conversion, performance, and feature health.
• Maintain security, audit logs, legal records, tax/accounting records, and compliance evidence.
• Enforce Edgaze policies and comply with law.

AI and Model Provider Processing#

To execute workflows, Edgaze may send Customer Inputs, Creator Content, workflow configuration, node instructions, files, metadata, and related context to third-party AI model providers or API providers. Current model providers include OpenAI, Anthropic, Google, and Microsoft Azure (Azure AI Foundry, which hosts models such as Kimi and DeepSeek and powers the Composer assistant), where configured. Workflows may also call external APIs selected by creators or users, and Edgaze-managed data services such as Aviato, which returns person and company information for identifiers (for example a LinkedIn URL or email address) submitted in a run.

Those providers may process submitted information under their own terms, privacy policies, retention rules, abuse monitoring systems, and security practices. You should not submit sensitive data unless it is necessary for the Product and lawful for you to provide.

Outputs may be returned to Edgaze, displayed to users, stored in run records or logs, used for debugging and support, and retained as described in this Policy.

Google User Data#

When you connect your Google account to Edgaze, Edgaze may access Google user data that you explicitly authorize for use in workflows. Depending on the integrations you enable, this may include Google Calendar events, Google Docs documents, Google Sheets spreadsheets, Google Drive files, and permission to send email through Gmail. Google Drive access uses the limited drive.file permission: Edgaze can reach only files you pick or files the app creates, not the rest of your Drive.

Edgaze uses this data only to perform workflow actions that you configure or authorize. For example, a workflow may create or modify a calendar event, read or update a document or spreadsheet, save or read a Drive file, or send an email on your behalf.

Google user data may be processed and temporarily stored as necessary to execute workflows, maintain execution state, provide logs, troubleshoot failures, and operate the service. Access credentials and OAuth tokens are stored securely and are not exposed to workflow creators or other users.

Edgaze does not sell Google user data or use Google user data for advertising. Google user data is not used to train general-purpose AI models. Data is shared with service providers only where necessary to provide the requested workflow functionality and subject to applicable privacy and security safeguards.

You may revoke Edgaze's access to your Google account at any time through your Google Account permissions or by disconnecting the integration from Edgaze.

Creator Visibility and Dashboards#

Certain product, sales, usage, payout, and execution information may be visible to creators through creator dashboards, product analytics, purchase surfaces, support flows, or future reporting tools where the Platform makes that information available.

Edgaze also provides admin and operational tools that may allow authorized personnel to inspect transactions, runs, traces, logs, payout records, refund records, disputes, and Product data for support, security, accounting, and platform operations.

Do not assume that Customer Inputs, Outputs, or run logs are confidential from all operational review. Use Products accordingly.

Public Content#

Published workflows, prompt products, listings, creator profiles, public handles, Edgaze codes, descriptions, thumbnails, examples, templates, pricing, and public marketplace pages may be visible to anyone and may be indexed, cached, linked, or shared.

You should not publish confidential information, trade secrets, private credentials, regulated data, or third-party materials unless you have the rights and authority to do so.

Third-Party Services and Sharing#

We may share information with service providers and third parties that help operate Edgaze, including:

• Stripe and Stripe Connect for payments, checkout, disputes, refunds, creator onboarding, payout rails, accounting, and compliance.
• Supabase for authentication, database, storage, and backend infrastructure.
• Vercel for hosting, analytics, performance monitoring, and deployment infrastructure.
• Microsoft Azure for the workflow runtime, run-stream cache, and hosted AI models.
• Cloudflare Turnstile where enabled for bot prevention and abuse protection.
• Mixpanel where enabled for product analytics and session replay.
• PostHog where enabled for mirrored product analytics events (no session replay).
• Google Ads, after marketing consent, for advertising conversion measurement.
• Resend for transactional email.
• Calendly where you book a call through an embedded scheduler.
• AI/model providers such as OpenAI, Anthropic, Google, and Microsoft Azure where needed for workflow execution.
• Integrations you choose to connect, such as GitHub, Slack, and Google (Gmail, Calendar, Docs, Sheets, and Drive), to perform the workflow actions you authorize.
• Edgaze-managed data services used by workflow steps, such as Aviato for person and company enrichment from identifiers submitted in a run.
• Webshare, a proxy provider, which relays the request when a workflow step fetches a YouTube transcript, or reads a web page that blocked Edgaze's own servers. It sees the address being fetched and the response, not your account details.
• External APIs selected by Creators or Users in workflow configurations.
• Support, security, logging, storage, and infrastructure providers where used.
• Professional advisors, auditors, insurers, payment partners, banks, processors, regulators, law enforcement, or courts where required or appropriate.
• Successors or counterparties in a merger, acquisition, financing, restructuring, asset sale, bankruptcy, or similar corporate transaction.

We may also share information to enforce terms, protect rights and safety, prevent fraud or abuse, respond to lawful requests, investigate disputes, or protect marketplace integrity.

Cookies and Similar Technologies#

Edgaze uses necessary cookies and similar technologies for authentication, session security, admin controls, checkout flows, bot prevention, and essential platform operation.

Edgaze may use analytics cookies or browser storage after you accept analytics, and advertising cookies after you accept marketing. Browser storage may also support return paths, demo run tracking, device-based demo limits, preferences, and recovery from outdated app versions.

You may control cookies through browser settings, but disabling cookies or storage may break authentication, checkout, security checks, or platform features.

Data Retention#

We retain information as long as reasonably needed for the Platform, marketplace access, hosted runs, creator dashboards, support, accounting, tax, legal, fraud prevention, security, dispute handling, audit, backup, and compliance purposes.

Some records, such as payment records, purchase history, payout records, refund and dispute records, audit logs, security records, and evidence needed for legal or accounting purposes, may be retained after account deletion or product removal.

We do not promise permanent retention or immediate deletion of every copy, backup, log, or derived record.

Security#

We use reasonable administrative, technical, and organizational safeguards designed to protect information. No system is perfectly secure. Unauthorized access, provider failure, software bugs, user error, credential compromise, or other incidents may occur.

You are responsible for protecting your account, devices, browser sessions, API keys, credentials, and third-party accounts.

International Transfers#

Edgaze primarily operates and processes data in Singapore and Southeast Asia: our database, application hosting, and workflow runtime run in Singapore, and our run-stream cache runs in Malaysia. Our service providers may also process, store, or transfer information in other countries, including the United States. Those jurisdictions may have data protection laws different from those where you live.

User Rights#

Depending on your jurisdiction, you may have rights to request access, correction, deletion, portability, objection, restriction, or withdrawal of consent for certain personal data.

These rights may be limited by law, security needs, payment and accounting records, fraud prevention, dispute records, backup systems, technical feasibility, legal claims, or legitimate business needs. To make a request, contact support@edgaze.ai.

Children#

Edgaze is not intended for children under 13, or a higher age where required by law. We do not knowingly collect personal information from children in violation of applicable law. If you believe a child has provided information to Edgaze, contact us.

Sensitive Data#

You should not submit sensitive personal data, protected health information, financial account credentials, government identifiers, secrets, private keys, passwords, regulated data, or confidential third-party information unless it is necessary, lawful, and appropriate for the Product you are using.

Changes to This Policy#

We may update this Privacy Policy as Edgaze evolves. Changes become effective when posted unless a later effective date is stated. Continued use of Edgaze after the effective date means you acknowledge the updated Policy.

Contact#

For privacy requests or questions, contact support@edgaze.ai.