Purplezee

Privacy

Purplezee is operated by Purplezee LLC in New York City. This notice describes the current beta. Account-deletion requests are handled manually. Some retention schedules and request-handling procedures are still being finalized.

Accounts and creator content

Supabase Auth handles your email address, password, account verification and sign-in sessions. Purplezee stores your account ID, username, display name and optional profile image. Sign-in cookies keep your session separate from the gameplay statistics cookie described below.

New accounts require an age declaration: 13–17 with parent or guardian permission, or 18 or older. We store the declared age group, the guardian-permission declaration when applicable, the declaration version and the time it was submitted. We do not ask for a date of birth or a parent's contact details. These records are not part of your public profile. They are self-declarations, not verified proof of age or guardian permission, and do not grant permission for optional analytics. Older accounts are not assigned an age group automatically. You can separately confirm that you are now 18 or older on your profile. We store that declaration's version and time without changing your original signup record.

We store uploaded game files, images, game descriptions, visibility settings, content ratings, version information and upload-processing records. Your display name and profile image can appear beside games you publish. Ordinary public games can appear in discovery; ordinary unlisted games are available to anyone with their link. Mature games, including their images, previews and playtests, require a signed-in account with an 18+ declaration. Uploading alone does not publish a game.

You can edit your display name, replace or remove your profile image, unpublish games and delete games from your dashboard. Unpublishing retains the files and history. Game deletion removes related database records and starts file cleanup; failed cleanup remains tracked for retry. There is no self-service account-deletion or data-export tool.

For privacy questions or an account-deletion request, contact [email protected]. The owner verifies the request and reviews any preservation requirements before using the account-erasure process. That process removes the account and its owned content from active systems and removes account-attributed gameplay records for other creators' games while preserving summary play and duration totals without player identifiers. Earlier anonymous gameplay cannot always be linked back to an account. Reports, moderation records and minimal deletion evidence may remain. Older backups and provider records are not immediately erased.

Games run on separate browser origins and may keep their own saved state. They cannot read Purplezee's account cookies. Clearing Purplezee cookies does not clear every game's browser storage. Downloaded content and previously shared copies cannot be recalled.

Mature gameplay uses a necessary game-origin cookie to bind a launch to this browser. It is limited to a game version, cannot be read by game scripts, is partitioned by the browser's top-level site and expires after one hour. The delivery service checks that the associated sign-in session is still active. Games do not receive your sign-in tokens or readable account identifiers through this check. This does not enable optional analytics. If your browser blocks the cookie, mature gameplay cannot start; ordinary games do not need it.

Managed multiplayer

Managed multiplayer is restricted to platform test accounts and is not available in the public hosted beta.

When an admitted creator enables managed multiplayer, the platform uses a necessary, HTTP-only launch cookie lasting up to 30 minutes. It is separate from optional analytics consent. Games receive only random room-local player identifiers and room events, not your account identifiers, sign-in tokens or this cookie.

Operational records include room membership, authorization deadlines, connection generations, safety-budget accounting and cleanup status. The room service relays game messages but does not retain game payload history or automatically save a world. A creator's game can handle its received messages or browser storage independently.

Rooms last at most 15 minutes. Rich room details have an attempted deletion or redaction deadline seven days after that lifetime ends. Provider outages can delay execution, and minimal unresolved cleanup and safety records remain until cleanup is confirmed. Active deletion does not immediately erase provider recovery history or encrypted backups. Account-erasure and recovery procedures keep independent current fences so restoring an older copy cannot reopen an erased player's authority.

Gameplay analytics

Gameplay analytics are optional and off by default for both anonymous and signed-in visitors. If you opt in, we collect page views, successful launches, foreground session starts and ends, approximate playing time, fullscreen entry and copied game links for published games.

The preference cookie remembers your choice in this browser for up to one year. It is separate from signing in and does not sync with your account or other browsers. Browser storage and messages between tabs keep open tabs in sync. You can change your choice below, on a published game page or on your profile. Leave the box unchecked and save to decline or withdraw permission. Games and copied links still work.

Turning analytics off stops new optional collection and clears the analytics session cookie. It does not erase earlier records. Requests already sent may finish. If you turn analytics on while a game is running, gameplay collection starts at your next Play or Restart; saving does not restart the game.

With your permission, a random browser-session cookie helps avoid duplicate counts. It expires after 30 minutes without analytics activity, with a maximum lifetime of 24 hours. It is restricted to this platform and is not shared with game frames. Clearing cookies or changing browsers does not erase previously stored events. Without a saved permission cookie, optional analytics stay off.

Events include the game and version, time, coarse device category, and an approximate playing duration where relevant. Page views can include the referring site's origin, without its path or query. If you are signed in, events may be associated with your account ID.

Gameplay analytics do not collect game content, keystrokes, player input, exact location, browser fingerprints, or advertising identifiers. Raw IP addresses and full browser descriptions are not stored in analytics. Short-lived, hashed network rate-limit keys help prevent repeated requests.

Creators can access event and session records for their own games, including account IDs when present. Purplezee operators can see platform-wide activity and operational records. Published pages show aggregate plays and likes. Local demos, staged previews and playtests do not collect these gameplay events.

Likes are separate. When you choose Like while signed in, we save your account ID and game ID to remember the like and prevent duplicates, even if optional analytics are off. This does not start a gameplay analytics session. Necessary security checks and abuse prevention also operate independently of this choice.

Declining or withdrawing permission stops new optional collection but does not erase earlier gameplay records. Automatic age-based deletion is not enabled. Game deletion removes that game's raw gameplay history and summary totals. The reviewed account-erasure process removes account-attributed raw gameplay on other creators' games while preserving summary plays and duration totals without player identifiers. Earlier anonymous records cannot always be linked back to an account.

Playtest feedback

A creator can share a private playtest link and ask for feedback. Ordinary playtests do not require an account; mature playtests require a signed-in 18+ declaration. We store the playtest, submission time, feedback type and the message you write. Feedback is available to the game's creator, not a public comment thread. Do not include sensitive personal information.

Revoking a playtest link stops new access but retains existing feedback. Deleting the game removes its playtests and feedback. There is no automatic age-based deletion schedule for feedback.

Reports and moderation

Website reports store your description, category, submission time and the reported game and creator identifiers and names. When signed in, your account ID is attached; you can also report public or unlisted games without an account. Reports and review notes are private to Purplezee operators, not visible to the reported creator or other users. Do not include passwords, private keys or unnecessary personal information.

Review and account actions record the operator, target, reason, time and outcome. Account or game deletion does not automatically erase reports, report text or moderation history. Account erasure removes the reporter's account association. A separate owner-reviewed process can delete an eligible closed website report and its linked review records after preservation requirements and related mailbox copies have been reviewed. Minimal case and deletion evidence remains. There is no automatic age-based deletion schedule for these records. Report text is not sent to an AI service.

Short-lived, purpose-specific hashed network counters limit submissions; raw IP addresses are not stored in the report database. Email reports are handled separately in the report inbox. Review and removal of related mailbox and owner-controlled forwarded copies are manual and also depend on the mail provider's controls. This process does not remove copies held by other recipients. Email reports are not automatically copied into the website queue.

Account verification

Account creation, sign-in and password recovery use Cloudflare Turnstile to reduce automated abuse. Cloudflare processes network and browser information for verification under its privacy policy. Verification tokens are sent to Supabase Auth for validation, not stored in gameplay analytics. Account upload-attempt counters expire at their hourly or daily boundary and are removed on later requests.

Creator billing

Paid checkout is currently unavailable. If enabled, Stripe will host checkout and payment management and receive your account identifier to associate a subscription with your account. Stripe collects the payment and billing information you provide there. Purplezee's billing system stores customer and subscription identifiers, status and renewal details, not full card details. Monthly upload usage is recorded separately from retained files.

Deleting games does not refund processing already used. Cancelling renewal does not delete games or billing records. Stripe's handling of payment information is described in its privacy policy.

Service providers and backups

Supabase provides authentication and database storage. Railway hosts the website and upload processing. Cloudflare provides game-file storage and delivery, account verification and report-email routing. Resend delivers account verification and recovery emails. These providers also process operational and security information needed to run their services.

Better Stack runs external availability checks to see whether the service responds. These checks do not track visitors.

Purplezee makes scheduled encrypted backups of account and application records and game files. Its regular backup snapshots use rolling 30-day retention; snapshots marked for preservation are retained separately. Live-data changes do not immediately remove older backup copies. This schedule does not set retention for provider-managed backups, operational or security logs, or report-mailbox copies. Provider-log and mailbox retention and deletion limits still require separate review. Limits on data stored in gameplay analytics are not a claim that hosting providers retain no request or network information.