Privacy Policy

1. Controller, scope, and definitions

1.1. This Policy applies to this deployment of Braains.io, including the website, accounts, account settings, authentication, multiplayer connections, chat, community submissions, feedback, virtual transactions, paid coin-package requests, and related legal pages.

1.2. The "Operator" is the administrator of this deployment and acts as controller for processing it determines. Public merchant information is maintained separately on the Merchant and Payment Information page.

1.3. This Policy does not control independent websites or providers, including Google, GitHub, Discord, or links opened outside the Service. Their own privacy policies apply to their processing.

1.4. The User Agreement / Public Offer governs use of the Service and paid digital features.

2. Processing principles

2.1. The Operator seeks to process information only for stated, legitimate purposes and to limit collection, access, and retention to what is reasonably needed for those purposes.

2.2. Personal information is not sold, rented, or shared for targeted advertising.

2.3. No internet service can guarantee absolute security. Users should use a unique password, keep purchase PINs private, and report suspected misuse promptly.

3. Information categories

3.1. Account and acceptance information. Username, email address, salted password hash for password accounts, account creation date, OAuth provider identifiers where used, email-verification status, and Agreement and Privacy Policy acceptance versions and times.

3.2. Profile and preference information. Profile picture, biography, social handles, optional PayPal contact email, marketing preference, previous usernames used to enforce change limits or continuity, staff role where applicable, and equipped or owned game cosmetics.

3.3. Authentication and security information. Random session and device identifiers, one-way hashes of session tokens, device/browser signals, IP addresses and network prefixes, session creation, expiration, activity and rebind times, anti-forgery tokens, failed login or purchase-PIN attempts, and temporary OAuth state values.

3.4. Device, network, and operational information. IP address used for routing or moderation, browser request headers, user agent, request timing, coarse country, region and autonomous-system number supplied by trusted infrastructure, server errors, rate-limit events, and security logs. The game does not request GPS or precise location.

Referral rewards also use keyed hashes of network and device identifiers, browser characteristics, and WebGL renderer information to detect linked accounts. Referral codes, reward status, frozen rewards, and coin transfers are recorded. Suspicious new rewards may be frozen without changing your existing coin balance; you can request review using the support contact below.

3.5. Gameplay and community information. Player identifiers, scores, game actions, room and presence state, chat messages, moderation records, high scores, virtual balances, inventories, and transaction history.

3.6. Uploads and submissions. Profile images, community skin files and metadata, creator information, votes and reviews, feedback category and message, optional reply email, ban appeals, and related account or hashed network context used to investigate abuse and duplicate submissions.

3.7. Purchase and virtual-transaction information. Coin package, amount, currency, claim code, payment-intent status and expiration, provider transaction or alert identifier, completion time, credited balance, promotion use, purchase-PIN hash and lock state, virtual-item purchases, seller proceeds, and service commission entries.

3.8. Payment-card information. The Service does not request or store full payment-card numbers, card security codes, or online-banking credentials. Those details are handled by the payment provider displayed at checkout.

4. Information sources

4.1. Information is provided directly when you register, update a profile, use chat, submit feedback, upload content, enter a purchase PIN, or start a coin-package request.

4.2. Technical and gameplay information is generated automatically when your browser connects, sends requests, joins multiplayer rooms, or interacts with Service features.

4.3. OAuth providers may supply an account identifier, verified email address, and basic profile details needed to authenticate you. The Service does not receive your provider password.

4.4. Payment providers may supply transaction identifiers, amount, currency, message, and status needed to match, fulfill, reconcile, or investigate a purchase.

5. Purposes and legal bases

5.1. Information is used to create and authenticate accounts, restore sessions, operate multiplayer gameplay, display player identity, deliver Virtual Content, process valid purchases, maintain transaction history, and provide requested features.

5.2. Information is also used to prevent fraud and abuse, enforce the Agreement, investigate technical and payment problems, moderate content, protect accounts, respond to requests, maintain reliability, and comply with legal obligations.

5.3. Where a legal basis is required, processing may rely on performance of the User Agreement / Public Offer, steps requested before entering that agreement, legitimate interests in operating and securing the Service, consent for genuinely optional processing, and compliance with legal obligations.

5.4. Optional marketing communication, if introduced and selected, should follow the recorded marketing preference. Withdrawing an optional preference does not affect processing necessary to provide or secure the Service.

6. Cookies and local identifiers

6.1. The Service uses first-party cookies that are necessary for authentication, account security, request integrity, device recognition, and OAuth sign-in. They are not advertising cookies.

6.2. Blocking necessary cookies may prevent account registration, sign-in, session restoration, or secure account actions.

7. Public information

7.1. Usernames, profile pictures, selected profile fields, chat messages, scores, gameplay activity, approved skins, and creator names may be visible to other users.

7.2. Do not place private or sensitive information in a username, profile, chat message, skin submission, or public Discord channel.

8. Sharing and service providers

8.1. Information may be processed by providers supporting hosting, database storage, network delivery and protection, email delivery, OAuth sign-in, asset delivery, error investigation, and payment processing.

8.2. Payment providers may process the information needed to complete, reconcile, and investigate a displayed purchase. Google, GitHub, and Discord sign-in may be available. Each provider processes information under its own terms and privacy policy.

8.3. Information may be disclosed when reasonably necessary to comply with law, respond to a valid legal request, protect users or the Service, investigate fraud or abuse, enforce agreements, or establish and defend legal claims.

8.4. The Operator does not authorize providers to use Service information for unrelated targeted advertising.

9. International processing

9.1. The Operator and service providers may process information in countries different from yours because the Service is available over the internet and uses distributed infrastructure.

9.2. Where applicable law requires transfer safeguards, the Operator should rely on an available lawful transfer mechanism or provider safeguard appropriate to the processing.

10. Retention and deletion

10.1. Authenticated session records normally expire within seven days and may expire sooner after inactivity, logout, credential changes, role changes, account deletion, or a security mismatch. OAuth state values normally expire within ten minutes. Device cookies may remain for up to 30 days.

10.2. Account and profile records remain while the account is active. An account deletion request is normally scheduled for 14 days and may be canceled by signing in during that period.

10.3. Chat, gameplay, feedback, uploads, moderation, security, payment, and virtual-transaction records are retained only as long as reasonably needed for operation, moderation, fraud prevention, support, disputes, accounting, legal obligations, and backup integrity. Different categories may therefore have different retention periods.

10.4. Account deletion may not immediately remove information that must be retained for payment reconciliation, fraud prevention, security, legal claims, regulatory duties, or limited backup cycles. Public content may be anonymized or removed where reasonably possible.

11. Security safeguards

11.1. Safeguards include salted password and purchase-PIN hashing, hashed session and network identifiers, expiring and idle-limited sessions, secure cookie attributes, anti-forgery checks, input and upload validation, uniqueness constraints, request-size limits, rate limits, moderation controls, and periodic multiplayer-session validation.

11.2. Access is limited according to operational need, but no method of storage or transmission is completely secure.

11.3. Report a suspected account compromise or security issue promptly using Clause 15.4. Do not publicly disclose secrets or exploit details that could place users at risk.

12. Automated security controls

12.1. Automated controls may reject malformed requests, limit repeated actions, expire an unverified session, prevent duplicate votes or purchases, or temporarily lock a purchase PIN after repeated failures.

12.2. These controls protect accounts and Service availability. They are not used to build advertising profiles or make automated decisions intended to produce legal effects.

12.3. A user may request review through the contact methods in Clause 15.4 if a security control appears to have acted incorrectly.

13. Children's privacy

13.1. The Service is not intended for a person who cannot legally consent to account creation under applicable local law without parent or guardian permission.

13.2. A parent or guardian who believes a child supplied information without required permission should contact the Operator through Clause 15.4 and request review or deletion.

14. User choices and rights

14.1. You may update available profile fields, stop using the Service, log out of sessions, or schedule account deletion through Account Settings.

14.2. Depending on applicable law, you may request access, correction, deletion, restriction, portability, or a copy of personal information, and may object to or withdraw consent for certain processing.

14.3. The Operator may need to verify account ownership before fulfilling a request. A request may be limited where another person's rights, security, fraud prevention, payment records, or legal obligations require it.

14.4. Where applicable, you may complain to a competent privacy or consumer authority. Using the contact process first may allow a faster correction but is not required where the law provides otherwise.

15. Changes and contact

15.1. Policy changes will be identified by an updated effective date and version. Material changes may be announced in the Service or require renewed acknowledgment where appropriate.

15.2. Do not include passwords, purchase PINs, authentication cookies, full payment-card details, precise location, or unrelated sensitive information in a request.

15.3. Provide enough information to identify the account and request, such as username, optional reply email, relevant date, and a concise description. Identity verification may be required.

15.4. Verified request routes:

15.5. Refund and delivery requests are handled under Section 6 of the User Agreement / Public Offer.