What we collect. What we don't.

Plain language for static pages, platform accounts, operational metrics, and security boundaries.

Current Status

Founder-preview — Stripe lab funding, Stripe checkout, and signed-in accounts

GLEE Phoenix is live in founder-preview: a platform for changing the world through intent, coordinated action, and public proof. Public lab funding at /fund is paid through Stripe Checkout, without a GLEE account. GLEE Platform account routes are visible at platform.gleephoenix.com for launch profiles, dashboard shell, intent requests, workspace objects, signed-in Fuel checkout, and paid-work billing. Stripe Checkout handles card entry for current signed-in platform card payments. Square is a fallback integration and may retain records of earlier payments. YouTube and Reddit provider connects start from signed-in platform sessions and store only consented account/profile/subscription metadata needed for the feature. This static public site does not collect form submissions, create sessions, start provider OAuth, or store raw payment details. Stripe, Square for earlier payments, and connected payment providers may process contribution or payment details when a supporter/customer uses those official rails.

Cloud + Local Boundary

Public platform, private control plane

GLEE Platform is the public cloud surface for accounts, launch profiles, workspace objects, updates, proof, signed-in provider connects, and Stripe-backed card payment flows. Individual payment features remain subject to their signed-in availability and launch controls. GLEE Ship/local is the private build and control environment. The public platform does not publish control topology, recovery procedures, admin paths, local machine details, or private credentials. That omission is intentional security design, not missing documentation.

What We Collect

Minimal, operational, and first-party by design

Public lab funding at /fund uses Stripe Checkout. Stripe collects the card and contact details. GLEE's public fund ledger records only the amount and Stripe's payment reference. If a lab payment is refunded, disputed, or needs checking, GLEE keeps Stripe's event record for it, which can include the payer's name and email, for accounting and dispute handling. Current paid Fuel card payments use signed-in GLEE Platform account routes and Stripe Checkout. Those processors handle payment fields. GLEE does not store raw card, bank, wallet, or payment credential data directly.

GLEE may retain only the fields needed to run, secure, improve, and verify the platform:

Public alias You choose — appears in the public supporter record if you choose public display

Contact email Collected only through an approved cashier or the GLEE Platform account flow — not collected by this static site

Support/Fuel amount and date For receipts, totals, supporter recognition, Fuel credit, and payment verification records

Account and session records Provider-created launch profiles, dashboard access, login/session identifiers, and account recovery state for GLEE Platform

Provider connections YouTube channel subscriptions and Reddit community subscriptions after signed-in consent; used for your private list and aggregate counts only

Platform objects Intent requests, workspace objects, saved Proof Runs, chat state, Fuel wallet/payment verification state, Stripe customer/payment references, and historical Square references needed for account billing

Operations and security events First-party route-level metrics, errors, abuse signals, audit events, and performance data needed to operate the service

Not intentionally collected for advertising or resale: browsing history across other sites, advertising identifiers, third-party tracking profiles, or data broker enrichment. GLEE does not sell supporter, account, or platform data.

The Public Supporter Record

What appears publicly

Lab funding payments at /fund are not linked to a GLEE account or name, so they create no supporter record; they appear only in the public fund totals. The supporter record is public only for contributors who choose public or anonymous display. Private contributors may be counted in totals without exposing personal identity. Public entries may contain:

Public alias You choose — public, anonymous, or private display

Supporter Number Your position in accepted contribution order if public display is enabled

Recognition class and honor tags Supporter credit only — no ownership, payout, or control

Approximate contribution date Public

Real name / email / payment details Never published — private always

This Site

No third-party tracking on this static site

No account cookies set by the static public site
No third-party analytics beacon intentionally allowed
No third-party embeds or content
No advertising networks
No user accounts or login on this static site; account sessions live on platform.gleephoenix.com
No YouTube or Reddit OAuth starts from the static site; provider connects require signed-in consent on GLEE Platform
GLEE Platform may collect first-party operational and security telemetry needed to run the service

This site is statically rendered HTML. GLEE does not intentionally create user sessions or run third-party tracking scripts on this static site. Account sessions, if created, live on the separate GLEE Platform Worker. The site is served through infrastructure providers such as Cloudflare, which may process limited request metadata for security, routing, abuse prevention, and service operation.

Your Rights

Data requests

Contributors and platform account holders may request deletion or correction of private GLEE-held data such as contact email, internal payment reference, or connected-provider records. Some payment records may need to remain with Stripe, Square for earlier payments, or connected payment processors for compliance, accounting, dispute handling, fraud prevention, or service operation.

Public supporter records are intended to be durable historical credit. If you do not want a public record, choose private or anonymous display before publication.

Data requests can be sent to the public contact listed in the site security/contact surfaces. Current status: SOFT_LIVE.

Updates

Policy changes

This privacy statement may be updated before Round Zero opens. The current version is always at this URL. Material changes will be noted in the build log.

Last updated: 2026-10-15 (current Stripe card checkout and historical Square records clarified)