Your board stays yours.

What changed on 9 October 2026

This revision changes the companies that run this website for us, and adds statistics on the emails we send. Nothing changed in the app.

• New host: Cloudflare now hosts this website and runs its forms, the OutBrick Community and the storage for images in posts. Netlify did this until 9 October 2026.
• New database: Neon now runs the website’s database for us directly, still in the United States (US East). Until 9 October 2026, Netlify ran it with Neon.
• When you request a post translation, its text is processed by Cloudflare Workers AI and the translation is displayed. The request does not include your account details. Nothing is translated unless requested.
• Earlier records: our records were copied to the new services. Netlify still holds the earlier copy — form submissions sent before 9 October 2026, the former database and its request logs — which we keep only as a backup of the move. We will have it deleted once the move is confirmed, and in any case within the periods set out in this policy.
• Email statistics: we now count deliveries, opens and clicks for every email we send, without storing your address with them, and stop sending the newsletter to an address that bounces or reports spam. Details are under Email open and click tracking below.

What changed on 17 October 2026

This revision describes optional analytics in supported iPhone and iPad builds. It does not announce a new App Store release. The website analytics, email and community changes introduced on 8 October 2026 remain described below.

• Website analytics: Google Analytics can now measure visits to this website, but only if you accept it in the cookie banner. Nothing loads from Google until you do, and you can change your answer at any time.
• Newsletter open and click tracking: OutBrick News emails now record whether they were opened and which links were clicked, so that we can stop writing to people who no longer read them.
• Support cases, applications and newsletter topics: contact-form messages now become support cases that the team can reply to, applications keep the decision we made, and newsletter readers can choose topics. Each is kept in our database for a set period, listed below.
• Sign-in alerts: the community now remembers which browser and operating system you sign in with, so that it can warn you about a sign-in from a new one.

Optional TikTok connection

Only OutBrick’s publisher connects TikTok. With consent, Studio reads the name, avatar, app-specific ID, public videos and engagement counts. Tokens remain encrypted server-side until replaced or deleted.

Visitors can browse the public gallery without signing in. TikTok loads only after you choose Load. Revoke Studio access in TikTok; use Contact to request deletion. Private videos and posting are excluded.

Rewarded video advertising

This section is new as of 15 September 2026. Before that date OutBrick contained no advertising SDK at all, and this policy said so.

Eight optional rewarded video placements have separate daily caps, with up to 39 views a day in total. Videos start only when you choose; there are no banners or automatic interstitials.

The ads are served by Google (AdMob). When an ad is requested, the Google Mobile Ads SDK may collect and process, on Google’s own behalf as an independent controller, your device’s advertising identifier, device and app information, coarse location derived from your IP address, information about your interaction with the advertisement, and performance and diagnostic data. Google’s handling of that information is governed by the Google Business Data Responsibility and How Google uses information from sites or apps that use our services. Some of that processing is used for advertising measurement and personalisation, which Apple and applicable law describe as tracking.

Because of that, two consents apply. If you are in the European Economic Area, the United Kingdom or Switzerland, OutBrick shows Google’s consent form before any ad is requested, and you can reopen it at any time from Advertising choices in OutBrick Settings. Separately, iOS asks for your permission before the app may use the advertising identifier for tracking; saying no leaves every part of the game unchanged and simply makes the ads less relevant. You can change that answer at any time in Settings › Privacy & Security › Tracking.

Remove Ads, or owning the current season’s Brick Pass, stops ad requests. If a reward is offered without a video, its own eligibility and daily allowance apply; check the options shown in the game. Neither purchase makes lives, moves or boosters unlimited. Older versions may differ.

We do not sell or share your personal information for money.

Information stored on your device

The app stores progress, coins, boosters, settings and accessibility preferences locally and can sync the private save through your own iCloud account. Optional analytics sends the limited events described below, not your private iCloud save or a copy of the board. The developer does not receive face data or operate a game account system.

iCloud progress sync

When iCloud is available, OutBrick automatically synchronizes progress through your Apple Account’s iCloud key-value storage. This includes level progress, coins and spending totals, boosters, streaks, rewards, purchases and unlocks, player name and avatar, gameplay statistics, and the colour-blind preference. Sound, music, haptics, notification settings, per-device retry counts, and detailed local play summaries are not included. The developer cannot access this private iCloud save. It is separate from an iCloud device backup. You can manage OutBrick’s iCloud access in your device’s Apple Account settings.

Camera and face data

The camera-free OutBrick update (build 18) removes the optional “Look at me (camera)” feature. That build does not request camera permission, start a face-tracking session, or collect or process face data. Earlier iOS builds, including version 1.0 (13), contain the optional feature described below. Updating the website does not change an older app already installed on a device.

Face information processed in earlier builds

In version 1.0 (13), the feature is off by default and requires the player to enable it in Settings and grant camera permission. On supported devices, Apple’s ARKit processes the front-camera input and provides a tracked face position and expression coefficients. OutBrick reads the face position and the left and right smile and outer-eyebrow-raise coefficients. It does not read or store a face mesh, depth map, face photograph, or video recording, and does not identify a person. Later development builds also used eye-direction, head-tilt and blink values and a temporary face-return event; these have all been removed from build 18.

Purpose and use of face data

Face information in earlier builds is used only to animate the mascots: looking toward the player and gently mirroring expressions. The later face-return event could trigger a local greeting, using a curated line or Apple’s on-device language model when available. Face information is not used for puzzle controls, scoring, progression, authentication, advertising, analytics, profiling, or model training. The whole game is playable without the feature.

Face data sharing and storage

OutBrick does not send face data, camera images, video, or face-derived animation values to the developer, third parties, servers, iCloud, Game Center, or an external AI service. The face-tracking calculations and animation values are processed locally in temporary device memory. The saved on/off preference is a setting, not a face record. OutBrick does not maintain a face-data database or save face data to files or backups.

Face data retention and deletion

Earlier builds continually replace temporary face values while the feature runs. The tracking session is stopped and its current values reset when the Home mascot stage stops or the app becomes inactive; renderer animation values settle back locally. No face-data history is retained on disk or on a server. Temporary in-memory state is released when the app terminates. To prevent further camera access in an older build, turn off “Look at me (camera)” in OutBrick Settings or revoke OutBrick’s Camera permission in the device’s Settings. There is no stored face dataset to request or delete. Build 18 removes the feature entirely.

Information sent to Apple services

If you choose to use Game Center, Apple processes the information needed for leaderboards, achievements, activities, and challenges under Apple’s policies. OutBrick submits gameplay scores and achievements and can display your Game Center name, profile photo, and friends’ leaderboard names and scores. Some leaderboard information is also displayed in the app’s widgets. If you buy or restore an in-app purchase, Apple processes the transaction and receipt. OutBrick does not see or store your payment card details.

Information we receive through support

You can reach us through the contact form on this website (described in the next section) or by emailing us directly. Either way, we receive the information you choose to include, such as your name, email address, device model, iOS version, app version, level number, and a description or screenshot of a problem. We use it to answer you and diagnose the issue. Please do not send passwords, payment details, government identifiers, or sensitive personal information.

Forms on this website

This section is new as of 24 September 2026. Before that date the website’s contact form only opened a draft in your own mail app and sent nothing itself; it now sends your message directly, and the site gained three more forms.

Contact, affiliate, job and newsletter forms send the information you submit to OutBrick only when you press the submission button. Cloudflare Workers handles the request, our owner-controlled Neon Postgres database stores the form record, and Resend delivers the applicable emails. Validation, a hidden anti-spam field and rate limits protect these forms; they are no longer processed by Netlify Forms or Akismet.

• Contact form: the topic, your name, email address and message, and — only if you fill them in — your device, iOS version and app version.
• Screenshots: if you attach them to the contact form or to your request page, up to three images per message. We remove location and camera data before storing them with Cloudflare; only the team, and you through the private link to your request, can see them. They are kept and deleted with your support request.
• Your request page: every email about a support request carries a private link, valid for a year, to a page that shows the request, our replies and anything you add. Anyone holding the link can open it, so please do not share it. Asking for the link again sends it only to the address on the request.
• “Was this helpful?”: answers on our help pages are anonymous: the page, yes or no, an optional reason and comment, the page’s language and the month. No name, email address or IP address is stored with them; a salted one-way hash of your IP address is kept for two days to limit repeated answers.
• Beta testing and the accessibility panel: sign-ups use the contact form with the topic set, and are handled like any other message. Taking part is voluntary, and you can leave at any time.
• Affiliate application: your name, email address, the links to your channels, an audience-size range, your country, how you would promote OutBrick, your preferred handle and the code proposed from it.
• Job application: the role, your name, email address, a link to your portfolio or profile, where you live and your time zone, and your note.
• Newsletter: your email address, the language you chose for the emails, and a record that you ticked the consent box. Sign-up is double opt-in: your address joins the list only when you press the button in the confirmation email, which works for 7 days. What we keep while you are subscribed, and how to change your topics or unsubscribe, is set out in the next two sections. Signing up or not changes nothing in the app.
• Emails we send you: after the contact form, an affiliate application or a job application, an acknowledgement email to the address you gave, with a copy of what you sent, and later the team’s replies, the decision on an application, a note when a fix you reported ships, and one short “Did we solve it?” email; for the newsletter, the confirmation email and then the welcome letters. They are sent through Resend, our email delivery provider, which acts as our processor under its own privacy policy. Resend receives the address, the language and the content of each email and keeps a delivery log; for newsletter subscribers it also stores the address, the date you confirmed and whether you have unsubscribed. Our Resend account sends from the EU (Ireland), and it can record opens and clicks, as explained under Email open and click tracking below.
• With each form we store the submitted consent and language, submission time and referring page address. Rate limits use a hash of the request IP address. Cloudflare also processes technical network information to deliver and protect the service; we do not describe those provider operations as anonymous.

We use these details only for the reason you sent them: to answer your message, to review and run your affiliate application, to consider you for a role, or to send the newsletter you asked for. We do not sell them, use them for advertising, or add you to a mailing list you did not sign up for.

Form submissions and their incoming emails are retained for up to 12 months after our last exchange unless an ongoing relationship or legal obligation requires longer. Support cases, applications and other database records follow the separate periods listed below.

You can request earlier deletion, a copy or correction through the contact form with the topic Privacy, or by replying to an email from us. We remove applicable records from our database and inbox and confirm the outcome, subject to any legal retention obligation.

What our website’s database keeps

Contact, application, newsletter and community records are stored in owner-controlled Neon Postgres, accessed through Cloudflare Workers. This replaced the former Netlify-hosted arrangement on 9 October 2026. The record types and retention periods are listed below; the migration did not create new permission to send emails.

• Support cases: when you use the contact form, we keep your message, name, email address, language and topic, the device, app and iOS versions you gave us, a case reference, the team’s replies, the case’s status, the version a fix shipped in, and your answer to “Did we solve it?” with any comment you add. We keep a case for 24 months after it is closed or resolved, then delete it.
• Affiliate and job applications: what you submitted and the decision we made. We keep an application for 24 months after the decision, then delete it.
• Newsletter subscription: your address and language, the date you confirmed, the topics you chose (new versions, tips and guides, events and seasons), how far you are through the welcome letters, the date you last opened or clicked a newsletter, whether we have asked you “Still want these?”, and whether we stopped writing to you after a bounce or a spam report. As the record of your consent, we also keep the page you signed up on (its path only), the version of the sign-up wording you agreed to and a reference to your sign-up form submission. We keep all of this while you are subscribed and delete it 30 days after you unsubscribe or are removed.
• Scheduled emails: emails due later — welcome letters, “Did we solve it?” requests and notices — wait in a queue with your address and language. Each is deleted no later than 90 days after it is sent or cancelled.

The device record used for community sign-in alerts is described in the community section below.

Email open and click tracking

This section was added on 8 October 2026 and updated on 9 October 2026, when we began keeping statistics on every email we send. Resend, which sends our emails from the EU (Ireland), records whether each email was delivered and opened and which of its links were clicked. It adds a tiny invisible image that is fetched when the email is displayed, and routes each link through Resend before it takes you to the page. This applies to every email we send: the newsletter, support replies, and account and community emails.

For OutBrick News, our newsletter, opens and clicks also tell us which readers no longer read the letters. If 120 days pass without you opening or clicking any newsletter, we send one email asking “Still want these?”. If you do not answer within 14 days, we take you off the list. We do not use it to build a profile of you, and nobody but Resend receives it.

Our legal basis is our legitimate interest in not emailing people who no longer read our letters. You can object at any time: unsubscribe with the link in every newsletter, or change your topics on the preferences page it links to.

Opens are approximate. Some mail apps, such as Apple Mail with Mail Privacy Protection, load images in advance, so an email can count as opened when you never read it; if your mail app blocks images, an open is never recorded.

Since 9 October 2026 we also keep statistics on every email we send, to see how each kind of email performs. Each event Resend reports (delivered, opened, clicked, bounced, marked as spam and the like) is stored with the email type, its language, Resend’s reference for the message and a keyed one-way code made from your address, never the address itself. For a click we keep only the link’s site, page path and campaign tags; the rest of the link is dropped. For the newsletter we also record, the same way, when you sign up (with the page you signed up on), confirm, unsubscribe or save your preferences. These records are deleted after 400 days. We read them only as totals per email type, language and link, never to profile individuals, and we do not share them with anyone. Our legal basis is our legitimate interest in knowing whether our emails arrive and are useful.

If an email to you bounces permanently, you mark one as spam, or Resend blocks delivery to your address, Resend tells us. From then on we stop sending you the newsletter, and we cancel every email of any kind still waiting in our queue for you; a spam report also unsubscribes you at Resend. If you unsubscribe with Resend’s own unsubscribe link, you leave our list too and your queued letters are cancelled.

The OutBrick Community

This section is new as of 7 October 2026. The OutBrick Community is the forum, support forum, FAQ and search on this website. Anyone can read it without an account; you need one only to post, vote, follow threads or report a post. The community is separate from the app, and nothing you do in it is linked to your game progress.

• Your account: a display name, which is public; your email address, which is never shown to anyone else; the language you chose; an optional bio; your email preferences; and your role, such as member or moderator. You can sign in with a one-time link sent to your email address, or with Apple, Google or Facebook. If you use one of those, we store the user id that company gives us for you and the email address it shares with us; we never see your password. Apple’s Hide My Email relay addresses work like any other address.
• What you do in the community: your threads and posts, including earlier versions of a post you have edited, your votes, the threads and categories you follow, how far you have read each thread, your notifications, the reports you make, and any moderation action taken on your posts or your account.
• Bug reports: a bug report can also include your device model, iOS version, app version and the assistive technologies you use. Each of these is optional, and only what you choose to fill in is stored.
• Devices you sign in from: the browser and operating-system family you sign in with, such as “Safari on macOS” — never your IP address or a device identifier — so that we can email you when your account is used from a new one. This record is deleted with your account.
• Signed-in sessions: for each browser you sign in on, when the session started, when it expires and the browser’s user agent, so the sign-in can be recognised. The token that keeps you signed in is stored only as a one-way hash.
• IP addresses: the community’s database does not store them. To slow down spam and abuse, the community briefly keeps a salted one-way hash of your IP address to count requests, and records older than two days are deleted.
• Public posts: everything you post — threads, replies, your display name and your bio — is public. Anyone can read it without an account, and search engines index it. Please do not post your own or anyone else’s personal information.

Cloudflare Workers runs the community API, Neon Postgres stores its records, Cloudflare R2 stores uploaded images, and Resend delivers community emails on our behalf. Optional sign-in with Apple, Google or Facebook is handled under that provider’s policy and shares the account identifier and email described above. We do not sell community data or use it for advertising.

Cloudflare handles network and request details, such as request time, requested address, IP address and browser information, to deliver the website, protect it and investigate problems. Any provider logs follow Cloudflare’s applicable policies and our configured logging settings. We use operational diagnostics to investigate errors, not to build advertising profiles.

Emails. We email you sign-in links when you ask for one, a confirmation when you add or change your email address, a welcome when you join, and notifications: replies to you, mentions of your name, new posts in threads and categories you follow, a status change on your bug report or idea, your answer being marked as the solution, new OutBrick releases, and moderation notices about your posts or your account. You can switch each kind of notification off in your community settings, and every notification email has a one-click unsubscribe link.

Security emails. We also email you when your account is signed in to from a new browser or operating system, when a passkey is added, when your account is deleted, and with the download link for your data when you ask for one. These cannot be switched off while you have an account, because they protect it.

How long we keep it. Your account and what you post stay for as long as you keep the account. A session ends when you sign out, or after 30 days without a visit. Sign-in links stop working after 20 minutes.

Your choices and rights. In your community settings you can change your name, bio, language and email preferences, download everything we hold about your account as a JSON file, and delete your account yourself. You can also edit or delete your own posts at any time. Deleting your account blanks your name, email address and bio, removes your sign-in links, sessions, follows and notifications, and signs you out. Your posts stay, shown as written by a Former member, so the conversations they belong to still make sense. To have specific posts erased as well, ask us through the contact form with the topic set to Privacy, or reply to any community email, and we will remove them and confirm when it is done.

What stays after deletion. Your votes, the reports you made and the edit history of your posts stay attached to the blanked Former member account. Removing them would change vote counts and leave gaps in threads, and moderators need the record of what was reported and changed to handle disputes and repeated abuse fairly. None of it is linked to your name or email address any more.

Who can join. You must be at least 16 to create a community account, or older if the age of digital consent where you live is higher. The game itself is rated 4+ and needs no account.

Community features

These OutBrick Community features are live, except reply by email, which is not switched on yet; until it is, none of its data is collected.

• Images in public posts are stored in Cloudflare R2. Each image needs alt text; embedded location and other metadata are removed during upload. The image is public like the post to which it belongs.
• Reply by email: you will be able to answer a notification email to post your reply. Resend receives and processes the incoming email on our behalf, and we post its text as your reply, under your account.
• Passkeys: if you sign in with a passkey, we store only its public key and a credential id. The private key never leaves your device or password manager, and no fingerprint or face data is ever sent to us.
• Translation on request: if you ask for a post to be translated, the text of that post is sent to Cloudflare Workers AI, which runs an open translation model on Cloudflare’s own network, and the translation is shown to you. Translations are saved so that the same post is not sent twice. Nothing is sent unless someone asks for a translation, and your account details are never part of it.
• Weekly digest: an optional weekly email summarising what happened in the community. It is off unless you switch it on, and it has the same one-click unsubscribe as every notification email.

Optional in-app analytics

On supported iPhone and iPad builds, App analytics in OutBrick Settings is off by default. We do not configure the Firebase Analytics SDK or queue gameplay events before you explicitly opt in. Declining does not change levels, rewards, purchases or access to the game. The choice applies to this installation, separately from this website’s cookie banner.

After opt-in, Google Analytics for Firebase helps us understand game performance and purchase paths through reports. Events can include sessions and screens, level starts and outcomes, elapsed time, difficulty, move budgets and moves used, goals remaining, bounded resource balances, booster use, offer views and selections, purchase requests and outcomes, and rewarded-ad loading, impressions, earned rewards and successful grants. Verified new purchases may include the product identifier, actual amount and currency, and a locally hashed transaction identifier for deduplication. Raw transaction identifiers and receipts are not sent by this instrumentation.

Events are linked to a pseudonymous app-instance identifier, so this is not anonymous collection. Under Apple’s privacy classifications, analytics identifiers and associated events are disclosed as linked data. We do not attach your name, email, iCloud or Game Center identity. Reports may include app/OS/device information and coarse location such as country derived by Google from network information; Google Analytics 4 does not log or store IP addresses. The game does not request GPS for analytics.

We do not send raw boards, hidden-brick information, player-entered text, names, email addresses, iCloud saves, Game Center account identifiers, full receipts or precise location to this analytics service. Analytics collection of the advertising identifier (IDFA) and vendor identifier (IDFV), Google signals and advertising personalisation is disabled. Advertising SDK consent remains separate and follows the advertising section of this policy.

You can turn App analytics off in OutBrick Settings. This stops new analytics collection and resets the local analytics identifier and our local transaction-deduplication ledger. It does not remotely delete information already received by Google or OutBrick, and does not undo earlier lawful processing. Use the privacy contact and rights described in this policy for a data request; do not send payment details or a full receipt.

Google Analytics is provided by Google Ireland Limited and Google LLC. Where EU or UK law applies, the basis for optional app analytics is your consent. Google may process data outside your country, including in the United States, under its applicable data-processing and transfer terms. Aggregate reporting is the purpose; these events are not used by us to personalise advertisements.

The Google Analytics property used by this app and website has event and user data retention set to 14 months. Reset on new activity is enabled for user data, so new activity can restart that user-data retention period. Standard aggregate reports are separate and may remain available beyond the individual event retention window. Turning analytics off does not remotely delete past data.

Google Analytics for Firebase

Performance and crash diagnostics

Apple MetricKit performance and crash diagnostics are separate from optional gameplay analytics. The App analytics switch does not control those existing diagnostic reports, Apple’s own App Store diagnostics or advertising consent. We use diagnostics to investigate crashes, hangs and performance problems, not as consent to collect optional gameplay analytics.

Website analytics

This section describes analytics on this website only. It has a separate browser consent choice from optional App analytics in the game.

With your consent, this website uses Google Analytics 4, provided by Google Ireland Limited and Google LLC, which process the data on our behalf as our processor. Until you press Accept in the cookie banner, nothing is loaded from Google and no analytics cookie is set: Google’s consent mode starts with every kind of storage denied. If you decline, or never answer, the site works exactly the same.

• What is measured: the pages you view, the page that brought you here, your type of device and browser, your approximate country and city, which Google works out itself, and clicks on App Store buttons, sending the newsletter or contact form, and links to our social channels.
• Links in our emails: links to pages on this website carry utm_source, utm_medium and utm_campaign tags naming the email they came from, so that Google Analytics can count visits from each email. The tags name the email, not you, and Google Analytics reads them only if you have accepted analytics.
• What is not: Google Analytics 4 does not log or store IP addresses. Google signals and ad personalisation are switched off, so the data is not combined with your Google account or used for advertising.
• Why: to understand which pages help people, and to improve the site.
• Legal basis: where EU or UK law applies, your consent. Withdrawing it stops future measurement; it does not undo what was measured before.
• The Google Analytics property used by this app and website has event and user data retention set to 14 months. Reset on new activity is enabled for user data, so new activity can restart that user-data retention period. Standard aggregate reports are separate and may remain available beyond the individual event retention window. Turning analytics off does not remotely delete past data.
• Where: Google may process the data outside your country, including in the United States.

You can change your answer at any time with this button, or from the Privacy choices page.

Cookies and browser storage

Reading this website sets no cookies unless you accept analytics. The OutBrick Community uses two first-party cookies, both strictly necessary for signing in, and neither is used to follow you around the web. Everything the site keeps in your browser is listed here.

• Session cookie: set when you sign in to the community. It holds a random token that keeps you signed in, cannot be read by scripts on the page (it is HttpOnly), and lasts 30 days, renewed while you keep visiting. Signing out removes it.
• Sign-in cookie: when you start signing in with Google or Facebook, a cookie that lasts at most 10 minutes ties the sign-in to the browser that started it, so nobody else can finish it. It is removed as soon as the sign-in completes.
• Your analytics choice (ob-consent): your answer to the cookie banner, kept in your browser’s local storage for 12 months so that the banner does not ask again on every page. It is stored whichever answer you give.
• Google Analytics cookies (_ga, _ga_<container-id>): first-party cookies that let Google Analytics recognise a returning browser, kept for about 13 months. They are set only after you accept analytics. You can delete them at any time in your browser settings.

Retention and deletion

We keep support correspondence only for as long as reasonably needed to respond, maintain records, or resolve a recurring issue, subject to legal obligations. Delete My Data in OutBrick Settings resets this device’s progress and local play summaries and requests removal of its iCloud save, including any recovery copy in build 18. iCloud changes require service availability and may take time to reach other devices; a device that still has an older save can sync it again. Apple controls any separate device backups, purchase records, and Game Center data. This action does not delete screenshots or videos you chose to save to Photos or share. No face-data files are created by the tracking feature. For requests about information in a support message, use our privacy choices page or the contact form.

Your OutBrick Community account is kept and deleted as described in the community section above.

On the website, each kind of record has its own period, set out in the sections above: form submissions, support cases and applications, the newsletter, scheduled emails, email statistics and website analytics.

Your rights

You can ask us for a copy of the personal information we hold about you, ask us to correct or delete it, and object to or restrict how we use it. Where we rely on your consent, you can withdraw it at any time. Ask through the contact form with the topic set to Privacy. If you are in the European Economic Area, the United Kingdom or Switzerland, you can also complain to your local data protection authority.

Some of this you can do yourself, without asking us:

• Your community data: download everything we hold about your account from your community settings, straight away or as a link we email you that works for 24 hours, and delete the account yourself.
• The newsletter: every newsletter links to a preferences page where you can choose your topics, change the language or unsubscribe.
• Website analytics: change your answer at any time on the Privacy choices page.
• Game data: Delete My Data in OutBrick Settings, described under Retention and deletion.

Children

OutBrick is rated 4+. Optional app analytics is off by default and is not required to play; its pseudonymous data is described above. Please avoid including children’s personal information in support messages. The game has no public chat and no account registration. Rewarded advertising is described above; where Apple or applicable law requires child-directed treatment, that restricts advertising to non-personalised ads and prevents use of the advertising identifier.

The OutBrick Community on this website is separate from the game and is not meant for children: you must be at least 16 to create an account, or older if the age of digital consent where you live is higher. If you believe a child has created an account, tell us through the contact form and we will delete it.

Third parties and changes

Apple services, App Store purchases, Game Center, iCloud sync and iCloud backups operate under their own terms and privacy policies. Google provides rewarded advertising and, only after opt-in in supported builds, app analytics as described above. Website hosting, forms, the community, Resend emails and website analytics are described in their separate sections. If you sign in with Apple, Google or Facebook, that company handles sign-in under its own terms. We update this policy and the app’s App Store privacy information when applicable practices or partners change. The effective date above identifies this revision.

Contact

Questions about this policy? Use the OutBrick contact form or visit User privacy choices.

OutBrick decides how the personal information described in this policy is used, which makes it the controller under data protection law. By post: OutBrick · P.O. Box 330279.