Privacy Policy.

The controller of your personal data is the operator of Breeq (“Breeq”, “we”, “us”), which provides the website at https://breeq.space, the Android application “Breeq: Brick Breaker & Earn”, and related features (the “Service”). You can reach us through Contact.

We have not appointed a statutory data-protection officer. If we later appoint one, or an EU or UK representative, we will publish those details on this page. This policy is meant to meet the transparency rules of the EU/EEA GDPR, the UK GDPR, the EU ePrivacy rules as implemented in France, and, where it applies, the California Consumer Privacy Act as amended (CPRA).

This policy covers personal data processed when you visit the site, create an account, play Story or Earn, publish a wall, buy gems, request a withdrawal, share a referral link, contact us, or use the Android app. It does not cover third-party sites you open from Breeq (Google, Stripe, Cloudinary, social networks, block explorers) except to the extent we send them data as described below.

Use of the Service is also governed by the Terms of Service. Capitalised terms not defined here have the meaning given there.

Account and identity

• username, display name, email address, password hash (we never store a plaintext password);
• Google account identifiers, verified email, and profile name or image Google sends us if you use “Continue with Google”;
• wallet address and a short-lived sign-in nonce if you use wallet / SIWE sign-in;
• a guest account created in the Android app before you add an email or Google sign-in, so a first session can start on the tutorial;
• role (player or admin), account timestamps, and linked sign-in providers;
• age-related flags only if we later ask you to confirm you are 18+.

Play and progress

• XP, player level, tutorial completion, Story chapter clears, star grades, hit counts, scores, and which pieces the Story has already explained;
• Earn maps you publish (title, slug, layout JSON, ticket price, difficulty snapshot, play and win counts, featured/hidden status);
• Earn runs (ticket, seed, score, locked payout, outcome, timestamps);
• ledger lines for every gem and ETH movement;
• paddle inputs of a Story, tutorial, or Earn run, with the level and the seed, so that run can be replayed in the game itself.

Push notifications

If you choose to turn them on, we keep that choice and send your account id to our notification provider (OneSignal) so a message can reach this browser or the Android app. The message is a title, a short text, and a link back to Breeq. We do not send your email address for this. You can turn notifications off in Account and in your device settings.

Photos and other User Content

If you choose a photo as a wall background, we receive the file you pick, compress it in the browser, and store a hosted copy (currently Cloudinary, folder for Earn skies). Gradient skies are identifiers, not photos. Usernames, titles, and layouts are stored so other players can see and play the wall. Do not upload photos of people who have not agreed, or any image that is illegal or that depicts a minor in a sexual or nude context.

Money and withdrawals

• gem and ETH balances (ETH stored as an integer in gwei);
• gem purchases: pack size, USD amount, discount, Stripe Checkout session id, status, and timestamps — not full card numbers;
• withdrawal requests: amount, destination address, status, optional transaction hash and operator notes;
• referral code, who referred you, which share button was used when we know it, and gems paid for that referral.

Stripe processes card data as an independent controller / processor under its own policy. We may receive a customer email, payment status, and identifiers needed to credit gems once.

Device, logs, and diagnostics

• IP address, user-agent (including a Breeq Android token, app version, and phone model when you use the app), approximate country from IP, locale, screen size, time zone, whether the device is touch-first, timestamps, and security logs;
• in the Android app, a one-way hash of the app-scoped Android install id, so the same phone can resume a guest account after the app is reinstalled. It changes if the phone is factory-reset. We do not use it for advertising, and we never store the raw id;
• crash or render-process events inside the Android shell, used to recover the app, not to build an advertising profile;
• sound, haptics, swipe, and theme preferences (cookies and, for theme auditioning, localStorage);
• play time: seconds a live board was running in Story, the tutorial, or Earn. Pause menus and end screens are not counted. We store the total on your account;
• when an OpenReplay project is configured, a session recording: a reconstruction of the pages you open, your clicks and scrolls, so we can replay a visit. The game canvas is not part of that recording. Once you are signed in, that recording is labeled with your email, or your username if the account has no email. Password fields are left out. Payment return parameters and the guest door token are stripped from the address before it is stored.

Contact

If you use the Contact form, we ask for a name, email, and message so we can reply. Treat anything you type as ordinary correspondence: do not send government-id images, card numbers, or seed phrases.

Data we do not collect today

We do not run third-party advertising SDKs, do not sell lists of players, and do not use your photos to train a public generative model. We do not ask for precise GPS. Haptics use the device vibrator only when you have that preference on.

• Directly from you — sign-up, account settings, editor uploads, checkout, withdrawal forms, Contact, and play inputs.
• Automatically — cookies, server logs, the Android WebView cookie jar, and game events needed to save progress and settle a run.
• From others — Google (sign-in profile), Stripe (payment result), Cloudinary (hosted image URLs), a referrer’s link, and blockchain networks if we send or confirm a withdrawal.

We process personal data only when a legal basis applies:

• Contract (GDPR Art. 6(1)(b)) — creating and securing the account; providing Story, the editor, and Earn; crediting gems; recording the ledger; processing withdrawal requests; sending transactional notices.
• Legitimate interests (Art. 6(1)(f)) — keeping the Service safe (fraud, cheats, chargebacks, multi-accounting); debugging; improving difficulty proofs and economy settings; establishing, exercising, or defending legal claims; product analytics (page views, sign-up, device, country, app version, phone model, and play time) in PostHog, and session replay in OpenReplay when that project is configured. You may object (Section 10). We do not use legitimate interests to override a child or to send you marketing you did not ask for.
• Legal obligation (Art. 6(1)(c)) — tax, accounting, sanctions screening, responding to a binding order, and consumer-law record keeping.
• Consent (Art. 6(1)(a) and ePrivacy) — optional push notifications, if you turn them on; optional cookies that are not strictly necessary, if we later add them; sharing to a social network you click; certain photo uses beyond operating the wall, if we ever ask. You can withdraw consent without affecting processing that happened before withdrawal.
• Vital interests / public task — only if we must, for example to report CSAM or an imminent threat.

We do not use your data for automated decisions that produce legal or similarly significant effects solely by automated means, other than ordinary game rules (tickets, proofs, run expiry, anti-abuse blocks). Integrity holds and withdrawal refusals can be reviewed if you contact us.

We use first-party cookies and similar storage. We do not currently set third-party advertising cookies. Browser storage on the Android WebView is the same Service, persisted by the app.

Strictly necessary

• authentication and session cookies set by our sign-in stack (Auth.js), including CSRF protection;
• a short-lived SIWE nonce cookie (breeq.siwe-nonce) while a wallet sign-in is in progress.

Functional preferences (up to 12 months)

• breeq-theme — light or dark appearance;
• breeq-sound — sound on or off;
• breeq-haptics — vibration on or off;
• breeq-swipe — paddle swipe mode.

These preference cookies are first-party, not used for advertising, and exist so the Service remembers a choice you made. You can change the underlying setting in the game header or account page; that overwrites the cookie. You can also delete cookies in the browser, which may sign you out.

Product analytics

When a PostHog project key is configured, the browser loads PostHog to record page views and, once you are signed in, to tie them to your account id. PostHog may store a first-party cookie and a localStorage entry for that. We do not create a person profile for a visitor who has not signed in, and we do not turn on session replay. You can block it with your browser; the game still runs.

Session replay

When an OpenReplay project key is configured, the browser loads OpenReplay and records the visit as a reconstruction of the pages, clicks, and scrolls. The game canvas is left out. A Story, tutorial, or Earn run is replayed from the paddle inputs stored with your account, inside the game itself. It is not a video file. A signed-in recording is labeled with your email, or your username when the account has no email. Password fields stay out of the recording. OpenReplay may keep a first-party token in localStorage so one visit stays one session. You can block it with your browser; the game still runs.

Referral attribution (30 days)

Visiting a share link /r/… sets an HttpOnly breeq-ref cookie (SameSite=Lax) so a later sign-up can credit the inviter. It is not an advertising tracker for third parties. If you do not want it, do not use an invite link, or clear the cookie before you register.

Partner attribution (30 days)

A partner campaign link (/p/…) sets an HttpOnly breeq-partner cookie (SameSite=Lax). It records which partner sent you and, when the partner includes it, the email address they hold for you. When you sign in or create an account, we copy those two values onto your account so we can see which players arrived from that partner. The cookie is then removed. If you do not want this, do not use the partner link, or clear the cookie before you sign in.

Local and session storage

The browser may hold a theme audition key, a short-lived skip-to-shop intent, and similar client state needed to finish a flow after Stripe redirects you back. That data stays on the device unless a screen-sync feature we add later says otherwise.

We do not sell personal data. We share it with processors and other recipients who need it to run the Service:

• Hosting and delivery — the platform that serves breeq.space (currently Vercel) and related CDNs;
• Database — MongoDB (account, game, ledger);
• Sign-in — Google, if you choose Google; your wallet software, if you choose SIWE;
• Payments — Stripe, for gem Checkout, receipts, and fraud signals;
• Images — Cloudinary, for hosted wall photos and variants;
• Product analytics — PostHog (EU cloud unless we configure another host), for page views, sign-up, device, country, Android app version, phone model, and play time. The person profile uses your account id, username, and email once you are signed in;
• Session replay — OpenReplay (their cloud unless we configure another ingest host), to replay a visit. Once you are signed in, the recording is labeled with your email, or your username if you have no email;
• Notifications — OneSignal, if you turn push on, to deliver the message to your browser or the Android app. They receive your account id and the device's push token;
• Blockchains — a public ETH network if we execute a withdrawal; the destination address and amount become public;
• Other players — username, published walls, public play counts, and whatever the live board shows;
• Professional advisers and authorities — where needed for law, tax, or a dispute;
• A buyer — if we transfer the Service, under a contract that continues this level of protection.

If you tap X, Facebook, WhatsApp, Telegram, or Copy, that network receives whatever the share URL and your device send. That is your act, not our sale of data.

We may process data in the EU/EEA, the United Kingdom, the United States, and other countries where our processors operate. Where a transfer leaves a jurisdiction that requires safeguards, we rely on an adequacy decision where one exists, and otherwise on Standard Contractual Clauses (and the UK addendum where required), plus supplementary measures our processors publish. A copy of the relevant clauses can be requested through Contact to the extent we are allowed to share them.

• Account, progress, maps, runs, and ledger — for the life of the account, then deleted or irreversibly anonymised within a reasonable period after closure, unless a longer legal hold applies.
• Purchase and withdrawal records — at least as long as tax, anti-fraud, and accounting law require (often five to ten years).
• Contact messages — as long as needed to answer you and keep a limited record of the correspondence.
• Security logs — typically up to 12 months, longer if an incident is open.
• Cookies — as stated in Section 6, or until you delete them.
• Backups — rolling windows; deletion on the live system may take until the backup expires.

We may keep a record of banned identifiers (email, wallet, payment fingerprint) so the ban can be enforced.

EEA, UK, and similar laws

Subject to the limits in those laws, you may:

• access a copy of your personal data;
• rectify inaccurate data (much of this you can already edit in Account);
• erase data (“right to be forgotten”), which may require closing the account and may not reach public chain records or legally required books;
• restrict or object to processing that relies on legitimate interests;
• receive data you provided in a structured, commonly used format, and transmit it;
• withdraw consent where consent is the basis;
• complain to a supervisory authority.

Our lead concern for EU players is typically the French authority, CNIL (cnil.fr). You may also contact the authority of your EU/EEA member state or, in the UK, the ICO.

California and similar US state laws

We do not sell personal information and we do not share it for cross-context behavioural advertising. We do not use or disclose sensitive personal information to infer characteristics, beyond what is needed to run an account you asked for. California residents may request know/access, delete, and correct, and may use an authorised agent. We will not discriminate against you for exercising a privacy right. If a future feature ever looks like a “sale” or “share” under CPRA, we will provide a Do Not Sell or Share control before that feature goes live.

To exercise any right, use Contact from the email on the account, or another method that lets us verify you. We may ask for information reasonably necessary to confirm identity and will answer within the statutory period (generally one month under GDPR, 45 days under CPRA, extendable as those laws allow).

The Service is not directed to children under 13, and we do not knowingly collect their personal data. If you believe we have, contact us and we will delete it. Players under 18 must not use paid or Earn features. We may delete an under-age account and associated User Content when we learn of it, without restoring spent gems except where the law requires.

We use reasonable technical and organisational measures (hashed passwords, TLS in transit, access-controlled admin tools, atomic balance writes, webhook secrets). No method is perfectly secure. You must keep your password, email, and wallet keys confidential. Blockchain payments you receive are public. If we become aware of a breach that must be notified, we will notify the competent authority and affected people as the law requires.

Please do not upload special-category data (health, political opinions, religious beliefs, sexual life) or biometric templates. A photo of a face on a wall is User Content you chose to publish, not a biometric identification system we run. We do not currently require ID documents; if a withdrawal review asks for them, we will tell you why, who sees them, and how long they are kept, before you send them.

The Service does not change behaviour in response to a browser’s “Do Not Track” signal today, because we do not run a third-party ad graph. If we add non-essential trackers, we will honour Global Privacy Control and similar opt-out signals for those trackers where required.

We may update this policy. The “Last updated” date will change, and we may give in-Service or email notice for material changes. The updated policy applies from posting unless a later date is stated. If you do not agree, stop using the Service and request account closure.

Privacy requests and questions: breeq.space/contact. Operator: Breeq, https://breeq.space. We may add a postal address, company registration, and VAT number here when they exist.