GOOD STUFF GROUP LLC · BRICKIVA
Privacy Policy
Effective October 29, 2026.
Good Stuff Group LLC operates Brickiva. This policy explains the information used by the game, optional Google accounts, cloud features, advertising, and purchases. Contact wayne@goodstuffgroupllc.com with privacy questions.
Playing on your device
Brickiva stores your Sparks, upgrades, unlocked elements, settings, statistics, and saved run on your device. You can play without signing in. Android backup of this game data is disabled. Clearing app storage or uninstalling removes local data; a cloud backup you explicitly saved can be restored after signing into the same game account.
Optional Google sign-in
Google and Firebase authenticate your account. Brickiva receives an account identifier and email address. We do not receive your Google password or request access to your Gmail inbox, messages, or contacts. Authentication credentials and account sessions are handled by Google's authentication services.
Cloud backups and rankings
When you request a backup, Brickiva stores banked Sparks, upgrade levels, unlocked elements, and statistics in a private cloud record linked to your account. The current manual backup feature does not upload active-run checkpoints. A save revision and server timestamp help avoid conflicting updates.
If you choose Ranked before a run, submitted damage events, run identifiers, sequence numbers, timing information, completed-run summaries, and ranking aggregates are linked to your account. Public rankings show a player code, score, and rank; they do not display your email address. Cloud backups do not themselves submit leaderboard scores. Development leaderboards remain separate from production tables.
Optional advertising
When reward ads are enabled, Brickiva uses Google AdMob. Ads are optional: you choose whether to watch a video for the displayed run bonus. After the privacy check permits ad requests, the advertising SDK may preload an ad before you choose to watch it.
Google and its advertising partners may process device and advertising identifiers, IP address, approximate location derived from network information, app information, ad interactions, and diagnostics to deliver, measure, personalize where permitted, and protect advertising. Brickiva does not request precise-location permission. Advertising use depends on applicable privacy choices and restrictions. Google explains its processing in How Google uses information from apps that use its services.
Where required, a consent or privacy message is shown before advertising requests are allowed. Use Ad privacy choices in Settings when available to review or change those choices. If an ad cannot load or you skip it, your base earnings remain saved. Development and internal-test builds use test ads.
Purchases
Google Play handles purchase checkout; Brickiva does not receive full payment-card details. Purchase verification and recovery use the product, purchase status, purchase token, and linked game account. The backend retains recovery tokens in encrypted form and rechecks ownership after refunds or cancellations. Remove Ads owners receive the run bonus directly, without an ad impression. Purchase data is separate from ordinary cloud progression backups.
Before requesting ads, the game asks for an age group, stored only on the device. No birth date is collected. Ad requests are disabled for the under-13 selection; ages 13–15 use under-age-of-consent and non-personalized ad settings. The game is intended for ages 13 and older.
Service providers and security
Google Firebase and Google Cloud provide account and cloud services. Google AdMob and its listed partners provide advertising when enabled, and Google Play provides purchase processing. Their services may process information in countries outside your own. We use authenticated access controls and encrypted network connections. Production online services require Firebase App Check with Google Play Integrity to check app authenticity and device integrity. Temporary per-account and hashed network-address counters help limit abuse and expire after two days. Public ranking scores are visible to other players; private saves are restricted to their account. No service can guarantee complete security.
Retention and deletion
Local data stays on your device until cleared. Account-linked cloud records and submitted ranking records remain until removed as part of account-data deletion or service maintenance. Some purchase or security records may need to be retained for fraud prevention or legal requirements.
Use Settings → Delete Brickiva account to request deletion after verifying your Google sign-in. A retrying backend worker removes the sign-in account, cloud saves, and public/private ranking records. Local gameplay progress stays on your device and can be removed separately by clearing app storage. Minimal encrypted purchase recovery records and a hashed Google account binding remain to support ownership recovery and prevent reassignment; they are separate from cloud progression. A temporary deletion marker expires after 30 days. You can also request deletion by emailing wayne@goodstuffgroupllc.com from the email used for the game account and put Brickiva account deletion in the subject. We may ask you to verify ownership before deleting data. Do not send passwords or payment-card details. Signing out does not delete cloud records. A Google Play purchase or refund is managed separately through Google Play.
Audience and choices
Brickiva is intended for players aged 13 and older and is not directed to children under 13. Where local rules require a parent or guardian's permission for online services, that permission is required. If you believe a child has provided personal information to Brickiva without appropriate permission, contact us to request review and deletion.
You can play offline, decline optional sign-in or ranking uploads, choose whether to create a cloud backup, review available ad privacy choices, and request account-data deletion. Privacy rights and available options may vary by location; contact us with an access, correction, or deletion request.
Policy updates
We will update this page when the game's data practices change. Review the date on this page for the current version.
Brickiva support