Your player · Updated 30 October 2026
Player privacy.
Swezeebra is an independently operated private project offering browser games. This notice explains the shared player account and optional sign-in. Contact the project operator at [email protected].
Information we use
- Your chosen display name, avatar settings, internal player identifier, game progress, cosmetic selections and verified game results.
- For wallet sign-in: the public wallet address and a server-verified signed challenge. We never ask for your seed phrase or private key.
- For Facebook sign-in, when available: Facebook’s app-scoped account identifier, verified on our server. We request only the basic public profile permission and fetch the identifier. We do not import your Facebook name or photo, email, friends, messages or posts. Your Swezeebra name remains the one you choose.
- If you enable social features: your bio and sharing choices, friend relationships, messages, invitations, notification read positions and any reports you submit. If used, we also store your uploaded profile image, opt-in online presence, community topics/replies and moderation records.
- Limited abuse-prevention records and technical connection information processed by our hosting provider. Provider sign-in uses short-lived state and verification records to prevent forged or replayed login responses.
Why we use it
We use player information to provide the account, saved progress and social functions you request. Optional account linking and social sharing are your choices. Necessary security and abuse controls protect the service and its players. Where applicable, the legal bases are providing the requested service, consent for optional linking and sharing, and our legitimate interest in maintaining a secure service. You can withdraw an optional choice; this does not undo processing already completed.
We do not sell Facebook data, use it to target advertising, or make automated decisions with legal or similarly significant effects about you. Facebook login does not authorize us to publish to your Facebook account. A separate sharing link opens Facebook so you can decide whether to post there.
Sessions and retention
An essential Secure, HttpOnly cookie grants access to your player for up to 180 days from session creation. Logging out revokes the current session. Browser storage keeps player-scoped progress copies and pending changes. Clearing it does not delete server records.
Account/profile information, linked sign-in identifiers and retained personal bests remain while the player is kept, unless removed through a verified data request. OAuth verification flows expire after five minutes; expired flows are removed during later sign-ins and daily cleanup after the feature is installed. Provider access tokens are used temporarily on the server for identity verification and are not saved in your player record or sent to browser code.
Social messages are available for 90 days; reports for up to 180 days. Invitations expire after seven days. Shared result links expire after 90 days or can be revoked earlier. Daily cleanup removes expired social records. Public scoreboards have their own bounded retention periods, described in the scoreboard notice. Account deletion, sign-out and provider removal are different actions.
Community topics and posts have no automatic age expiry. Moderation can hide them from view; verified deletion requests are reviewed for erasure. Community reports are retained for up to 180 days and moderation audit records for up to 365 days. An uploaded profile image remains until replaced or removed. Opt-in online presence is shown to accepted friends only while recent (90 seconds); turning it off clears the current shared activity.
What other people can see
Your chosen name is visible when you join multiplayer or publish a score. A social profile is optional; a friend link can reveal its name, avatar and bio, with statistics only if enabled. Publishing a result link is a separate choice. Your private saves, session credentials, wallet address and provider identifier are not exposed through the social profile. Community posts are visible to other signed-in members; disabling a social profile does not automatically delete earlier posts. Uploaded profile pictures appear with your player and can also be retrieved by anyone who has their image URL. Messages are not end-to-end encrypted. Blocking prevents further contact through the service.
Providers and international processing
Cloudflare hosts the site and account services and processes ordinary connection data. Optional Facebook login opens Meta’s service and sends the information necessary to authenticate, including the app identifier and return address. Meta’s own data practices apply on that service. These providers may process information outside your country, including outside the European Economic Area, under their published terms and safeguards.
See Cloudflare’s privacy policy and Meta’s privacy policy. Other website features, such as market widgets and aggregate analytics, are described in the site privacy notice. This login integration does not install Meta Pixel or a Facebook advertising SDK.
Your choices and data requests
Edit your chosen profile in the player hub. You can turn off your social profile, revoke a result link, log out, or request access, correction, export, restriction or deletion of your information. Where applicable, you can object to processing and complain to your local data-protection authority. Contact [email protected]; the operator handles requests manually and verifies control of the relevant account before changing or disclosing private information.