Account information
Verified sign-in provides an email and optional display name. Public community fields are created separately and can be edited without exposing the account email.

Festly is designed to keep public profiles, private identity, store assignments, and payment-provider data in separate permission boundaries.
Verified sign-in provides an email and optional display name. Public community fields are created separately and can be edited without exposing the account email.
Posts, follows, favorites, and reports are stored to operate the social experience and enforce safety. Public actions are labeled; private moderation records are restricted.
Festly records a fixed set of aggregate beta actions without names, email addresses, account IDs, raw network addresses, user agents, referrers, full URLs, or query strings. Random identifiers live only for the current browser-tab session, Global Privacy Control and Do Not Track are honored, and the protected beta workflow removes records older than the configured retention period (30 days by default).
When commerce opens, Festly will minimize customer data shown to sellers. Payment credentials will remain with the payment provider and will not be stored in public browser code.
Festly does not generate public advocate links or rewards in this beta. If a seller-controlled program opens after legal review, Festly will document the product-specific participation record, terms version, approval state, and only the minimum attribution data needed to operate it.
Checking this browser...