개인정보처리방침

TierSnap Privacy Policy

Effective: August 11, 2026 · Last updated: August 31, 2026

TierSnap processes only the information needed to provide accounts, gameplay, rankings, clip submissions, the “Who’s at fault?” community, service operations, and advertising. The operator does not sell personal information for money. Only “Who’s at fault?” posts are reviewed by the operations team before publication. Posts and comments in the separate game-by-game free community may become public immediately and are then subject to user reports, blocks, and ongoing moderation. On iOS, TierSnap asks for App Tracking Transparency (ATT) permission before initializing the advertising SDK. Denying or restricting ATT does not remove gameplay or ads; every Google ad request is explicitly limited to non-personalized treatment.

Information we process

• Account and profile: Firebase user ID, sign-in provider, email supplied by that provider, nickname, nickname-reservation key, and, if selected by the user, a locally cropped square profile image. The server decodes and validates it, strips source metadata, and re-encodes it as a 512×512 WebP. The profile uses only a random image ID and revision, not the original filename, Storage path, or UID.
• Gameplay: app opens, game and mode, session times and duration, answered rounds, exact answers, score, streak, leaderboard entry, language, app version, and timestamps.
• Optional Firebase usage analytics: only after the user expressly enables Usage Analytics in Settings, Firebase Analytics processes a pseudonymous app-instance ID, automatic app and device dimensions such as app and OS version, language and coarse region, and a fixed set of interactions: app and Home views, game selection, quiz start, answer and completion, supported community views and successful creation actions, community-notification choice, and the start of the ad-removal checkout screen. Custom events use only allowlisted game and mode categories, answer outcomes, and bounded round, score, and streak counts. While usage analytics is enabled, a verified ad-removal purchase may also produce the store and Analytics SDK's in_app_purchase event with a product identifier, price or value, currency, quantity, and transaction information; TierSnap does not duplicate it as a custom revenue-completion event. Linked AdMob, Firebase, and the Mobile Ads SDK may also process ad impressions, clicks, exposure time, estimated revenue, and ad-unit, screen, format, and source dimensions as automatic Analytics events while that choice is on; TierSnap does not add manual advertising events or parameters. Analytics contains no Firebase user ID, email, nickname, advertising ID, post, comment, video or submission ID, content text, note, or purchase token. TierSnap does not set an Analytics User-ID or any custom user property.
• Aggregate answers: tier choices are added to per-video counters. Public distributions do not display an individual user's answer history.
• Quiz clip suggestions: YouTube ID and URL, game, tier, optional note, submission time, review status, app version, language, and the submitter's UID and nickname. Completed review records can include the reviewing staff member's UID and email, decision, reason, optional review note, and time. A separate owner-only Suggestion history stores the game, YouTube ID, tier, submission and status-update times, pending, approved, or rejected status, published game and clip IDs for approvals, and, for rejections, a server-approved fixed reason code and an operations-team-authored explanation shown to the submitter.
• In-quiz video problem reports: the current game and YouTube video ID, a fixed reason code (video not playing, wrong video, wrong tier, inappropriate, or other), required detail for “other” up to 500 characters, report and update times, processing status, and reporter UID. Reports are accepted only through a server function and sent through a private review workflow. Information provided to the operations team omits reporter UID, email, and profile data.
• “Who’s at fault?” reports and posts: the original report contains the reporter-selected game, YouTube ID, optional report note, community-guideline version, submission time, reporter UID and nickname, and review state. “My videos” uses a separate owner-only submission history containing the game, YouTube ID, submission and status-update times, pending, published, rejected, cancelled, hidden, or deleted state, an approved rejection category and operations-team-authored explanation where applicable, and a public-post reference where applicable. On approval, the operations team separately writes the public question, situation description, and two side labels. Those operations-team-authored fields are distinct from the reporter's original data; publication time and later visibility or deletion state are also processed.
• “Who’s at fault?” voting and safety: a user's choice and update time for each post; option totals without UIDs; reporter UID, target post and its video submitter UID, reason, optional report detail, time and status; blocked UIDs and block times; suspension state; and moderation records containing review-staff UID and email, decision, reason, optional note, and processing time. “View stats” for a published submission shows the same UID-free aggregate option totals used on other public screens; it does not reveal individual voters or their choices.
• Game-by-game free community: when enabled, the selected game, post title and body, comment body and reply relationship, creation and update times, state, public nickname, private account UID, and a community author key. These posts and comments may be visible immediately without prior approval, so users should not include personal information or contact details.
• Community comment notifications: on Android or iOS, when a user expressly enables notifications, the service links the user's Firebase ID with a Firebase Cloud Messaging registration token, platform, and token-update time. It sends a generic notification when another user comments on the user's post or replies to the user's comment, with routing data that opens the relevant game and post. Comment text is not included in push data, and the service does not notify a user about that user's own comment or reply.
• Game-community safety: reporter UID, reported post, comment, or author, a fixed reason, optional detail and time; account blocks and times; author suspension state; and operations-team action, reason, and time. Information provided for operations review omits reporter UID and email and contains only the reported author's nickname and community author key, fixed reasons, and the evidence needed for review.
• Attribution and operations: campaign or creator install-referrer fields, access/install timestamps, security events, technical service logs where applicable, and a deletion-safety marker containing the deleted Firebase UID, deletion state, and request/completion times.
• Advertising and device signals: consent choices, ad impressions, clicks, rewards and errors, plus device identifiers, device type, OS, coarse location inferred from IP address, app and ad interactions, crash, performance and other diagnostic data, and ad-performance signals processed by ad SDKs. If the user authorizes ATT on iOS, Google Mobile Ads may access the IDFA for more relevant ads and advertising measurement. When ATT is denied, restricted, or not yet determined, TierSnap resolves that status before ad-SDK initialization and applies an explicit non-personalized signal to every banner, interstitial, and rewarded request. ATT authorization does not override regional UMP consent or other privacy choices.
• App integrity: Firebase App Check uses Apple App Attest on supported iOS devices and falls back to DeviceCheck when App Attest is unavailable. Firebase installation identifiers, app and device attestation, and limited technical or diagnostic information may be sent to Apple and Google Firebase to reject counterfeit clients and automated abuse. TierSnap does not use integrity attestations for ad personalization or cross-app tracking.
• Tier Coins and reward verification: an account-linked Tier Coin balance and revision, the Korea Standard Time reward day and count, and single-request processing state. To credit completed quiz questions and offer a completed game's extra reward only once, the service privately processes the server-validated game-session identifier, Coins credited in that session, completion/reservation/credit state, and expiry time. When the Tier Coin shop is available, the service also processes the purchased background, button, or panel theme SKU, Coin price at purchase, independently equipped background, button, and panel choices, and request receipts that prevent duplicate deductions. When an ad starts, the server supplies Google Mobile Ads with a short-lived random one-time token as server-side-verification custom data. The token itself contains no Firebase UID, email, or nickname. The server verifies the ad network's signed transaction ID, ad unit, reward name and amount, completion time, and token, and processes token hashes, transaction receipts, and a private per-account cleanup index to prevent duplicate credit. If Android closes or restarts during an ad, the app may temporarily keep the raw token and request state in installation-only internal storage so it can safely resume the same request. This recovery record is excluded from device backup and migration and is removed as soon as processing reaches a terminal state. The app cannot directly read or write Firebase's raw-token or account-linked wallet records.
• One-time ad-removal purchase: when available, Google Play or the App Store processes the payment and purchase record. The TierSnap app checks purchase ownership on the device through the store SDK, but it does not send or store raw payment details such as card numbers, purchase receipts, or purchase tokens in Firebase.
• Anonymous community-ad operations metrics: UTC-day aggregate counts for banner and interstitial requests, impressions and clicks in the game-by-game and “Who’s at fault?” communities, plus post views, post or comment creation, and video-submission creation. Successful community-action counts may advance on-device ad-frequency progress, but a successful submission screen is not interrupted by an interstitial; an ad is attempted only at a later natural screen transition. These aggregates and their deduplication records contain no Firebase UID, email, nickname, game, post, comment, submission or YouTube video ID, author key, title, body, note, report detail, or other user or content identifier.
• Event notice: when enabled, the service processes an operations-supplied image, schedule, target platforms, destination link, accessibility label, and campaign configuration. Actual impressions, image-link actions, dismissals, and “do not show again today” selections are counted only as UTC-day aggregates without user or content identifiers; the server does not store each user's choice. Tapping the “do not show again today” text on the left side of the footer immediately closes the event notice and keeps that campaign hidden across app restarts for the same local date. The Close text on the right, the device Back action, and an image-link action do not create daily suppression and close the event notice only for the current app run. The campaign may appear again on the next local date if it remains active.
• Friend invites: when enabled, the service processes a random invite code; inviter and invitee account UIDs; the invitee's current profile nickname; accepted terms version and time; the number of distinct valid game sessions successfully completed during the campaign; provisional and final-review state; inviter totals; and abuse-prevention records. A prize recipient's TierSnap registration email is used for final review and prize delivery. It does not collect contacts or address books. The inviter sees the invitee's current profile nickname, game-session progress from 0–5, and completion status, but not the invitee's UID, code, email, content identifiers or content, or exact activity time. Community posts and their identifiers are not processed for referral qualification.
• On-device data: language, the usage-analytics choice, ad-frequency progress, one-time review-prompt state, community-notification choice, interrupted-session recovery state, short-lived Tier Coin ad-request recovery state, and the event campaign ID and device-local date selected for “do not show again today” may be stored locally. An ordinary event-notice dismissal lasts only for the current app run, while the daily-hide state lasts only through the selected local date. The usage-analytics choice and Tier Coin ad-request recovery state are excluded from device backup and migration.

Purposes and service providers

We use this information to authenticate users, prevent duplicate nicknames, run quizzes and rankings, restore sessions, review quiz clip suggestions, show each user their own quiz suggestion history, show users their separate “Who’s at fault?” submission status, pre-moderate and publish those posts, provide anonymous voting results, and process their reports and blocks, publish game-by-game free-community posts and comments immediately when the feature is enabled, process reports and blocks, hide or restore content, and suspend or unsuspend authors, receive in-quiz video problem reports, prevent duplicate or excessive reports, and fix broken or incorrect quiz videos, display a user-selected profile image, send new-comment and new-reply notifications when the user enables them, enforce community safety, improve reliability, serve and measure ads, maintain Tier Coin balances and Korea Standard Time daily limits, verify signed ad completion, buy and equip cosmetic themes, prevent duplicate or altered reward and deduction requests, provide event notices and anonymous event measurement, issue friend-invite codes, verify the five-valid-game-session campaign requirement, show invitee profile nicknames and requirement progress to their inviters, finalize rankings, and deliver prizes when enabled, provide required-update notices, and answer support requests. We use Google Firebase, including App Check with Apple App Attest or DeviceCheck, optional Firebase Analytics when enabled by the user, Cloud Messaging only after community-notification opt-in, and Storage for event images and server-normalized profile images; Google Sign-In; Sign in with Apple; Google Mobile Ads and UMP; Unity Ads through mediation; the Google Play and App Store payment services; and the embedded YouTube player. Opening a quiz or community video loads the YouTube iframe and media resources and may autoplay the video. YouTube may process IP address, device and browser information, request referrer, playback and interaction data, and cookies or similar storage under the Google Privacy Policy and YouTube Terms of Service. These providers may process information in countries outside Korea.

The iOS app requests ATT permission before advertising SDK initialization. Only authorization permits IDFA access; denial or restriction causes every Google ad request to use explicit non-personalized treatment. Authorization may still result in non-personalized ads depending on UMP consent, region, age, and platform rules. Users can revisit ad privacy options in the app and ATT permission in iOS Settings. See Google's advertising data guidance for more information.

Retention and deletion

Account-linked records are retained while the account is active or as needed to provide the service. In Android, use Delete Account below the profile card on Home; in iOS, open Settings → Delete Account. Review the scope and confirm. This removes the Firebase Auth user, profile, every profile-image Storage object and its private ownership/operation/cleanup indexes, owned nickname reservation, UID-linked leaderboard and play records, creator attribution, pending quiz clip suggestions, the complete owner-only quiz Suggestion history, the separate owner-only community My videos submission history, and reported pending, public, or hidden community-post content linked to the video submitter, the user's individual community ballots and reports, the user's block list, references to the user in other block lists, suspension and UID-keyed anti-duplicate records. Community review records are scrubbed of reporter, content-reporter, or reviewing-staff UIDs, review-staff email, nicknames, the reported video and game, free-form report notes, rejection explanations, and other report-source content linked to the deleted account. Because they are authored separately by the operations team rather than supplied by the reporter, the operations-team-authored public question, situation description, and side labels, together with non-identifying decision and processing timestamps, may remain as operational records. Operationally required review-staff fields in hidden-post or suspension records may be replaced with a fixed “[deleted]” marker that does not identify a person. If the submitter deletes their account, completed clip-suggestion reviews are scrubbed of submitter UID, nickname, optional submission note, and rejection explanation; if the reviewing staff member deletes their account, they are scrubbed of that staff member's UID, email, free-form review note, and rejection explanation. In-quiz video problem reports are scrubbed of the deleting reporter's UID and free-form detail, and their per-user duplicate-prevention, idempotency, and quota records are removed. UID-free game/video identifiers, fixed reason codes, status and timestamps, and anonymous reason aggregates may remain to improve video reliability. In the game-by-game free community, deletion removes the user's public and hidden posts and comments, private reported-content evidence, UID-to-author-key mapping and nickname, reports submitted by the user, report groups targeting that user's content or author identity, both directions of blocks, suspension state, guideline acceptance, quotas, idempotency records, and community-notification tokens. Self-deleted content disappears publicly immediately and is never restored. If it had already been reported, a private evidence copy may be retained only for the period needed to complete safety review; it is removed or de-identified after review, and author-linked evidence is removed immediately when account deletion completes. Only moderation records without a UID, email, or content snapshot may remain. Community-notification registration tokens are retained only while notifications are enabled. Disabling the setting unregisters the token, invalid tokens may be removed after a delivery response, and account deletion removes every notification token linked to the account. After a user casts a final vote on a published “Who was at fault?” case, the service may expose one server-owned announcement discussion for that case. Its title and body are derived only from the reviewed public case and do not include vote counts or voter identity. If the source case is hidden or deleted, the room becomes inaccessible immediately and its thread, report evidence, and reporter-linked indexes are removed by a serialized cleanup. Non-identifying video, decision, and timestamp metadata such as the YouTube ID or URL may remain. The deleted user's choice is subtracted from verifiable option and total vote counts. If an anonymous aggregate is missing or malformed and cannot be safely verified, the individual ballot is still deleted but that anonymous aggregate may remain to protect data integrity. Remaining anonymous aggregate answer, score, campaign, and community-vote counts, plus non-identifying moderation reason counts, decisions, and timestamps, may remain where needed for service integrity, safety, or dispute handling. Anonymous daily community-ad and community-event counts are retained for 90 days. Random operation records used only to prevent duplicate counting, together with non-identifying configuration-operation and audit records, are retained for 7 days. Expired records are removed in bounded batches during later metric-recording or private operations calls. None of these records contains a UID, email, nickname, game or content identifier, or content text. A current profile image is retained until replacement, direct deletion, or account deletion. Replacement and direct deletion remove the prior Storage object and private ownership/cleanup indexes. A temporary Storage failure may retain a private account-linked retry index until object deletion succeeds; full account deletion verifies image-object deletion before removing that metadata and Firebase Auth. Tier Coin balances, revisions, Korea Standard Time daily reward counts, purchased background, button, and panel theme SKUs and prices, and independently equipped background, button, and panel choices are retained while the account remains active and are removed on account deletion. An unused or reserved completed-game reward record is retained for up to 24 hours after game completion; a credited marker is retained for 14 days to prevent duplicate credit. Cosmetic purchase/equip request receipts are retained for 14 days to prevent duplicate processing. On the server, a raw one-time ad-start token and its begin-request record have a 30-minute validity window and are removed together by scheduled cleanup, normally within one hour of issuance. A verified callback's token hash and signed ad-transaction fields may be retained for up to 24 hours to retry a grant after a temporary server failure. A successful begin request becomes a raw-token-free reuse-prevention marker for 14 days; cancelled requests do not create separate cancellation receipts. Token hashes, verified ad-transaction replay receipts, and their private per-account cleanup index are retained for 90 days. Android's installation-only recovery record is removed immediately when grant, cancellation, or expiry is confirmed. On the next app launch, any record more than seven days old is removed before use; it is also removed with app deletion and is excluded from backup and device migration. Account deletion removes the account's wallet, daily counts, completed-game reward records, pending requests, operations, transaction index, cosmetic inventory, equipment, purchase records, and cosmetic operation indexes; a global replay receipt containing only a token hash and transaction ID, without UID, email, or nickname, may remain for up to 90 days from the transaction. Event images and settings; the accepted terms version; account-linked invite codes and relationships; valid game-session progress; provisional and final-review state; confirmation order; and abuse-prevention records are retained while needed to provide, review, and safely operate those features. Community posts are not tracked for referral qualification. An inviter receives the invitee's current profile nickname and requirement progress, but not the invitee's UID, email, content, or exact activity time. Account deletion removes or de-identifies the deleting account's invite code, relationship, progress, and request records. Deleting an account before prize fulfillment can cancel participation under the official rules because the service can no longer retain the account link needed for review and delivery. Minimum records required for fulfillment, disputes, or legal obligations may be retained for the applicable period, and UTC-day aggregates without a UID, email, or content identifier may remain for service quality and integrity. These features remain disabled until the applicable account-linked deletion process is available. An ad-removal purchase belongs to the Google Play or App Store account used to buy it, not to a TierSnap account. Deleting a TierSnap account does not automatically refund the purchase or delete the store's purchase record. The purchase can be restored on the same platform with the same store account that made it; Android and iOS purchases are not shared or restorable across platforms. Once the purchase is verified, all advertising formats, including banners, interstitials, and rewarded ads, are removed. Features such as nickname changes or revives that otherwise use an ad are made available without viewing one under the applicable app policy, but Tier Coin credit whose condition is actually watching an ad is unavailable. App notices and event information are not advertisements and may still appear. Optional Firebase usage analytics is off after a new install and is processed only while the user has expressly enabled it in Settings. Turning it off or deleting the account on the current device stops collection and resets local Analytics data and the pseudonymous app-instance ID. Previously uploaded events do not contain a TierSnap account UID and cannot be looked up or linked by that account; installation-level events and de-identified aggregates may remain or be deleted under the Google Analytics property's applicable retention and deletion settings. As a limited exception, a minimal deletion-safety marker containing the Firebase UID, deletion state, and request/completion times is retained for the life of the service so stale app requests or delayed server work cannot recreate deleted data. It contains no profile, post, ballot choice, or other usage content.

If in-app deletion is unavailable, email support@brainrottedgames.com from the account email. We may verify ownership and normally complete a valid request immediately or within 30 days after verification.

Your choices, children, and contact

You may request access, correction, deletion, restriction, or withdrawal of consent. TierSnap is not directed to children under 14. Firebase usage analytics is a separate, default-off choice in Settings and is not inferred from advertising, account, or notification consent. You can turn it off at any time without losing gameplay or account features. If you believe a child's information was processed without appropriate consent, contact us so we can investigate and take appropriate action. For privacy questions or requests, email support@brainrottedgames.com.