← Back to Radiant Blocks

Privacy policy

Radiant Blocks by FaithAppBox

Effective September 12, 2026. Updated October 17, 2026 for Apple Build 44: the combined age/reporting choice, optional App Store update notices and verified account-deletion requests.

This policy covers the Radiant Blocks browser game, Android app, and iPhone and iPad app. Some features differ between editions, as described below. For privacy questions, contact support@faithappbox.com.

Your game and optional account

Your board, preferences, scores and Scripture Collection are saved on your device. You can play without a FaithAppBox account. Local game storage remains until you clear it or it is removed by your device or browser.

If you choose to sign in, our account service, Supabase, processes your email address and email verification code, or your password if you use password sign-in, to authenticate you. Your account has a user ID. We use your email address and user ID for account management, sign-in and cloud saves. Cloud saves store your board, scores, Radiance, Scripture reading progress and settings so you can recover or continue your game. These records are linked to your account.

If you choose to create a public player profile, its nickname, optional website photo, high score and verse count appear on community leaderboards. Android builds through 24 do not connect rankings. Starting with Android and Apple Build 25, you can sign in and explicitly join from Menu → My profile. Use a nickname instead of your real name. Sharing from each Android or Apple installation starts off; you can pause new uploads from that device in My profile. Pausing does not remove earlier public results or change sharing on other devices. Your account links the same public profile across supported editions. Photos can be managed on the website. Developer testing pauses native-app uploads and excludes runs marked as development runs from later score uploads.

iPhone and iPad ads and related data

The iPhone and iPad app uses Google AdMob (the Google Mobile Ads SDK) for banner, full-screen and optional rewarded ads. The ad service connects to Google even when you play without signing in. Development builds use demonstration ads; the release configuration uses production ads.

Google's advertising SDK may collect the following information:

Google's SDK declares advertising, including third-party advertising and developer advertising or marketing, and analytics as purposes for location, identifiers, interactions, advertising data, performance data and other diagnostics. Crash data is used for analytics. Location, identifiers and interaction data may be associated with device or app identifiers. We do not send your FaithAppBox email address, account user ID or saved Scripture reading progress to the ads SDK.

For all players in the current iOS edition, we request child-treated, non-personalized ads. In Build 44, an explicit 18-or-older confirmation in the first reporting popup can establish the age group when no advertising age choice is already saved. It does not grant advertising consent. Skipping reports does not confirm adult age; unknown or under-18 ages retain under-age protections. Existing choices are preserved, and age group can be changed from Advertising privacy in the menu. No date of birth is collected, and the choice stays on the device, separately from reporting consent. Google's child-treatment setting disables personalized advertising and prevents transmission of Apple's advertising identifier (IDFA). Google's publisher first-party ID is also disabled. Other permitted SDK identifiers, advertising data and diagnostics may still be processed. This edition does not request permission to track you across other companies' apps and websites.

Google's User Messaging Platform (UMP) receives the app identity, the under-age-of-consent flag and technical connection information to determine which privacy requirements apply. It stores applicable advertising choices on your device. Ads are requested only when UMP indicates they are permitted. Open Menu → Privacy & analytics to view ad privacy status and, when required by Google, use “Ad privacy choices”. You can keep playing if ad privacy setup fails.

Apple Build 44 supports optional Firebase gameplay analytics and crash reporting, described below. It also supports optional account-linked community rankings. Reports start off and joining rankings requires a separate choice; neither is enabled by advertising consent. Older iOS previews may have fewer features.

Read Google's iOS Mobile Ads data disclosure, Google's age-restricted advertising information and Google's privacy policy for more information.

On Apple Build 44, open Menu → Privacy & analytics → Advertising privacy to change your advertising age group, refresh privacy information, or change consent when Google requires a privacy-options form. UMP updates at launch and determines whether ads may be requested. Under-18 / undisclosed-age users are not asked for advertising consent. Eligible adults can consent, decline or manage purposes in the applicable Google message. These choices do not enable or disable optional reporting, and previously loaded ads are discarded when choices change.

Android ads and related data

The current Android test edition uses the Google Mobile Ads SDK to load Google's demonstration ads. These are test ads and earn no income. The SDK connects to Google to request test ads, including when you play without signing in. In Android Build 25 and later, ad requests wait until Google’s User Messaging Platform (UMP) indicates they are permitted. Earlier test builds initialize test ads on startup.

Google's SDK collects and shares data with Google for advertising, analytics, and fraud prevention, security and compliance. This includes:

The Android app requests child-treated, non-personalized ads and disables the Android advertising ID. Other SDK identifiers may still be used. Ad-related SDK data is separate from the optional reporting described below. Test ads earn no income, and these builds do not use production ad units.

Read Google's Mobile Ads data disclosure and Google's privacy policy for more information about Google's handling of this data.

Android advertising privacy, starting with Build 25

Advertising privacy asks whether you are 18 or older, or under 18 / prefer not to say. We store this age-group choice on your device, not a date of birth. It is separate from the adult confirmation for optional reporting. Child-treated, non-personalized test-ad settings stay enabled for everyone in this edition.

Google UMP receives the app identity, the under-age-of-consent flag and technical connection information to determine which privacy message applies. It stores advertising choices on the device. Under-18 / undisclosed-age users are marked under the age of consent and are not asked for advertising consent. Eligible adults in the EEA, UK and Switzerland can consent, decline or manage purposes in the applicable Google message.

Open Menu → Privacy & analytics → Advertising privacy to change your age group, refresh privacy information, or change advertising consent when Google requires a privacy-options form. Turning optional reports off does not withdraw advertising consent. Declining advertising consent does not change local gameplay, account access or reporting choices; Google determines which ads, if any, may be requested. A privacy-service error does not block gameplay. Previously loaded ads are discarded when advertising choices are changed.

Optional Android, iPhone and iPad gameplay and crash reporting

Starting with Android Build 22 and Apple Build 10, gameplay analytics and crash reports are optional and off until an adult allows them. Apple Build 44 offers one first-run popup with “I'm 18+ — Allow & play” and “Play without reports”. Allow confirms age 18 or older and enables both disclosed reporting categories. Play without reports keeps both off and is available to everyone, including younger players. Existing saved choices are retained; separate reporting controls remain in the menu. Earlier Android and Apple builds may show separate reporting and age choices. Change reporting choices in Menu → Privacy & analytics at any time.

If enabled, Firebase Analytics processes a random app identifier, device information, approximate region and gameplay events such as active play time, scores, outcomes, powers, ad results and counts of Bible-feature interactions. These counts do not prove a verse was read or understood. Firebase Crashlytics processes a random installation identifier, device and operating-system details, app version, crash stacks and limited technical diagnostics to help locate failures. Android Build 24 and Apple Build 12 and later also support native crash diagnostics and a limited number of validated locations for packaged JavaScript errors. Android additionally reports supported WebView exit information.

Our reporting code does not add your name, email, account ID, password, sign-in code, individual verse text, selected answers or screen recordings to reports. Firebase advertising personalization and advertising-ID collection are disabled. Developer reports are labelled separately. Reporting preferences stay on your device and are not copied into cloud saves.

Turning analytics off stops future analytics collection and resets its local analytics data. Turning crash reporting off deletes reports waiting for upload; reports already sent are not recalled by this switch. Enabled crash reports may upload after you reopen the app. Google processes previously received information under its service retention practices. See Firebase privacy and security information.

Optional iPhone and iPad app update notices

Apple Build 44 can check the App Store for a newer eligible version. The app uses the App Store account's storefront region and asks Apple's lookup service for this app's public version and operating-system requirement. These requests include normal network information such as your IP address; we do not add your saved board, FaithAppBox account or optional reports to them. Checks are independent of optional gameplay reporting.

Update notices offer Update now and Later outside active gameplay. Update now opens the verified App Store listing. Offline play remains available. Development and TestFlight builds skip the public-store check.

Optional browser usage analytics

In the browser game, Google Analytics is off until an adult chooses “Allow” in the beta welcome or Privacy & analytics menu. Children can keep analytics off and still play the complete game. Choosing “Play without analytics” does not affect gameplay or saved progress. Global Privacy Control and browser Do Not Track preferences keep analytics off.

If you allow analytics, Google Analytics uses a random browser identifier in cookies and receives information about your browser, device, approximate location, referral website, visits and game events. Events include actual play, rounds, scores, replays, skin milestones, power-ups, whether a verse was opened or a question answered, and performance measurements. An opened verse does not prove it was read or understood.

We do not send your name, email, photo, account ID, individual verse text or reference, answers you selected, or account authentication details to Google Analytics. Our browser analytics does not use session recordings, personalized advertising or Google advertising signals. Full referral paths and URL query strings are excluded from our event configuration.

Google processes this information to provide aggregate reports that help us improve game quality and understand return visits. See how Google uses information from sites and apps.

Browser analytics choices

You can change your choice in Menu → Privacy & analytics. Turning analytics off stops our tracking and clears this game's Analytics cookies; the page may reload to complete that change. It does not delete previously collected reports. Analytics cookies are configured to expire after 90 days without a rolling extension. Your choice is saved locally until you change it or clear browser storage.

Guest measurements describe browsers, not verified individual people. Different devices, cleared cookies, blockers and opting out affect the totals. We do not reconstruct activity from before analytics was enabled. The browser analytics setting does not control the Android or iOS ads SDK.

Community safety and moderation

Custom nicknames and profile photos are reviewed before public display. Until approved, rankings use a neutral player label. Moderators can reject content and suspend public profiles. See our Community Rules.

Reports include the selected player, reason, optional details, visible profile information, submission time and a reference number. Signed-in reports are linked to the reporting account; guests can also report. A one-way account or connection identifier limits report abuse. Reports are private to authorized moderators, not shared with the reported player. Do not put passwords or unnecessary personal information in reports.

Guest blocks are stored on the device. Signed-in blocks are also stored with the account to hide the player across devices. Unblocking removes the stored block. Moderation records are retained while a concern is investigated and as needed to prevent repeated abuse; contact support for access or deletion requests. They are not sent to optional gameplay analytics.

Service providers and security

Our hosting and account service providers process the information needed to deliver the game, authentication and cloud saves. Technical connection information may be processed for service operation and security. Information sent by the app to our online services and Google's ads SDK is encrypted in transit using HTTPS/TLS.

Google handles ads SDK, UMP, Firebase reporting and browser analytics data according to its applicable service and privacy policies. Public player profiles and leaderboard entries can be viewed by other players.

Account and data deletion

You can request deletion of your FaithAppBox account and associated data without opening the game. In the Android, iPhone or iPad app, open the FaithAppBox account screen from the game menu and choose “Request account deletion”. On the website, verify your account email using a one-time code, choose what to delete and submit the form. No support email is required to submit a request. If you cannot access your account email, contact support@faithappbox.com for help. Never email a password or sign-in code.

We complete verified deletion requests within 30 days and email you when finished. Account deletion removes the sign-in account and linked cloud saves, public profiles, photos, leaderboard entries and reading records where present. A FaithAppBox account can be used across games, so deleting it also removes its other FaithAppBox cloud saves. You may instead request deletion of only your Radiant Blocks data while keeping the account.

Account and cloud-save records are retained while you use the account until deletion is requested. The deletion form records your verified account ID and email, chosen scope, verification time and request status; it does not store your verification code in the request. After a verified deletion request, we remove records from active services. Your contact email and request correspondence are deleted when we close the request; minimal identifiers needed to prevent restoration of deleted data are kept for up to 30 days after completion. Routine hosting logs expire within 7 days. Residual database recovery copies may remain for up to 30 days, and completed deletions are reapplied if a backup is restored. Google's data retention is governed by its own policies.

Deleting your online account does not remotely erase local copies on your devices. Clear Radiant Blocks app storage and browser site data to remove those copies. Uninstalling the app alone does not delete the online account. The deletion request page explains the steps and retention details.

Children and families

Children can play without creating an account. Optional browser analytics and Android, iPhone and iPad reporting are intended for adults who choose to allow them. Android and iOS ad requests use Google's child treatment setting. A parent or guardian with questions about a child's information or a deletion request can contact support@faithappbox.com.

Policy updates

We will update this page when the game's data practices change. The date above identifies the latest update.