Last updated / effective date: September 27, 2026
BrickSnake: Snake & Brick (“BrickSnake,” “the game,” or “we”) is operated by SUNGSOON KWON (권성순), an individual developer based in the Republic of Korea.
App name: BrickSnake: Snake & Brick
Android package: com.bricksnake.game
Developer and privacy contact: SUNGSOON KWON
Email: bricksnake@naver.com
BrickSnake does not require account registration or sign-in.
This Privacy Policy explains how information is handled when you use BrickSnake and its online features.
Installing the game or selecting an age band does not itself constitute consent to optional online ranking or advertising.
BrickSnake may store:
selected age band
language
sound and gameplay settings
privacy and advertising choices
local game progress and scores
player profile information
randomly generated Player ID (UUID)
unsent or pending ranking results where online ranking is enabled
ranking status information where applicable
the original Privacy Recovery Code issued for your ranking record
The game asks for an age band rather than your full date of birth.
When online ranking is enabled and you choose to participate, BrickSnake may process:
nickname
selected country code
score
level
game mode
play date
daily challenge information
randomly generated Player ID (UUID)
play, execution, and submission identifiers
app version
submission and integrity-verification information
ranking position or ranking-status information where applicable
a verification value/hash derived from the Privacy Recovery Code
a one-time Deletion Request ID and privacy-request status where applicable
We use this information to:
provide online rankings and MY RANK
distinguish ranking records
determine whether a score qualifies for a retained ranking position
prevent duplicate or fraudulent submissions
protect the ranking service
verify submissions
handle privacy and deletion requests
The selected country code is a profile choice and is not verified residence, current location, nationality, or citizenship.
The Player ID is an app-generated identifier and is not a hardware identifier such as IMEI.
Linked records are not necessarily anonymous.
Do not use your real name, email address, phone number, or sensitive information as your nickname.
BrickSnake uses Google AdMob / Google Mobile Ads SDK and Google User Messaging Platform (UMP).
Depending on age, app settings, privacy choices, consent status, region, device settings, and service configuration, Google advertising services may process:
advertising, device, and app identifiers
IP address
approximate location inferred from IP
app and advertising interactions
diagnostic and performance information
privacy and consent choices
related device and operating-system information
BrickSnake does not request precise GPS location.
BrickSnake requests non-personalized advertising where applicable.
This does not mean that no personal information, device information, or device storage is used.
Advertising delivery, measurement, diagnostics, security, and fraud prevention may still involve processing by Google.
BrickSnake does not use online ranking records to create advertising profiles.
BrickSnake uses Google Play Integrity to help verify app and ranking-submission integrity and to prevent fraudulent or modified-client submissions.
Google may process information such as:
request hashes
app metadata
licensing status
app-recognition information
device-integrity signals
related attestation information
BrickSnake does not use Google Play Integrity as a player identity-verification service.
Online requests may generate minimum connection, error, verification, operational, security, and fraud-prevention records.
If you contact us, we may process:
your email address
your message
information or files you voluntarily provide
We use this information only as necessary to respond to the request and meet applicable obligations.
Do not send passwords, identity documents, payment information, or unnecessary sensitive information.
Even where separate verification is necessary, we request only the reasonable minimum information needed for the purpose.
Online ranking is optional.
BrickSnake uses different ranking visibility and retention ranges.
For each applicable ranking board or game mode, the public Global Ranking displays only:
Rank 1 through Rank 100
Other users may see:
rank
nickname
selected country/flag
score
level
game mode where applicable
play or record date
The public ranking does not display:
original Player ID (UUID)
Privacy Recovery Code
Recovery Code verification value/hash
Deletion Request ID
Ranking records from Rank 101 through Rank 1000 may remain stored on the server for:
ranking operation
ranking-position calculation
MY RANK
submission validation
related service management
These records are not displayed on the public Top 100 leaderboard.
An eligible user whose retained ranking is between Rank 101 and Rank 1000 may see the actual ranking position through MY RANK.
For each applicable ranking board or game mode, BrickSnake retains ranking records only within the applicable Top 1000.
If:
a newly accepted score does not qualify for the retained Top 1000; or
an existing ranking record is pushed below Rank 1000,
the ranking record may be not retained or deleted before the normal 365-day maximum retention period expires.
When a user has a valid accepted ranking submission but does not have a retained Top 1000 ranking position, MY RANK may display:
>1000
instead of an exact ranking number.
A user who has never completed a valid accepted ranking submission is not treated as “>1000” and may instead be shown as not registered, no ranking, not synchronized, or another applicable non-ranking status.
Removal of a ranking record from the retained Top 1000 does not necessarily mean that all separate privacy-request, security, integrity-verification, or temporary service-management information is deleted at the same time.
Those records follow their own purposes and retention rules described in this Policy.
Permitted local gameplay does not require online ranking participation.
Users who are eligible for local gameplay may continue to play locally without enabling Global Ranking.
Advertising and online ranking availability additionally depend on the age rules and settings described below.
Online ranking submission requires all of the following:
the user is aged 18 or over
Banner Ads are ON
Global Ranking is ON
ranking submission is not blocked by an administrator or other management state
If Banner Ads is OFF, Global Ranking cannot be enabled.
If Banner Ads is turned OFF after Global Ranking has been enabled:
new ranking submissions stop
locally queued ranking submissions are removed or cleared
retries are blocked
pending or late responses from earlier requests may be ignored
Turning Global Ranking OFF also:
stops future ranking submissions
clears locally queued ranking submissions
blocks retries or pending submission handling as applicable
Turning Banner Ads or Global Ranking OFF does not by itself delete ranking records already accepted by the server.
Existing ranking records remain subject to the Top 1000 retention structure, the maximum 365-day retention rule, and the deletion rules described in this Privacy Policy.
Rewarded Ads are not required for online ranking participation.
When online ranking registration is successfully completed for the first time, BrickSnake issues one Privacy Recovery Code linked to the Player ID (UUID).
The original Recovery Code is shown on the user's current device.
The user should keep a separate copy in a safe place in case the device is lost, replaced, or reinstalled.
The server does not store the original Recovery Code.
The server stores only a verification value/hash needed to validate the code.
The Recovery Code is not included in public ranking responses.
The Recovery Code is not included in ordinary logs.
The Recovery Code is not included in deletion-request emails.
The Recovery Code is used to identify existing ranking privacy records and handle privacy requests.
It is not a general game-progress or account-recovery credential.
The user can start a privacy deletion request from the PRIVACY screen.
After ownership verification, the user must explicitly confirm DELETE MY DATA.
The deletion or withdrawal request is received when that final confirmation is successfully accepted by the server.
The server issues a one-time Deletion Request ID linked to the Player ID.
The Deletion Request ID is valid for 30 days for request identification and verification.
This 30-day period is not a waiting period before deletion.
The game may prepare an optional email draft containing:
game name
Player ID (UUID)
Deletion Request ID
Sending the email is not required for the request to be received.
After acceptance:
the affected ranking information is excluded from public display
new ranking submissions for that privacy record are blocked
deletion and cleanup procedures proceed
This does not mean that every provider-controlled infrastructure copy is physically erased at the same instant.
On a new installation, the user may enter the separately saved Privacy Recovery Code.
The server verifies the code against the stored verification value and identifies the prior Player ID.
This identifies the existing privacy record and does not merge the prior Player ID into a newly created profile.
After successful verification, the user can explicitly confirm DELETE MY DATA and complete the same server-side deletion or withdrawal request process.
Email remains optional.
The Recovery Code itself is not sent by email.
If the Recovery Code has also been lost and automatic verification is not possible, contact:
bricksnake@naver.com
We will request only information reasonably necessary for a separate verification process.
A valid deletion or withdrawal request is processed without waiting for the normal ranking-retention period to expire.
Eligible adult users may separately control Banner Ads and Rewarded Ads through the app's privacy settings.
The app's Banner Ads ON/OFF setting is a game feature setting and is separate from Google UMP consent and other advertising privacy choices.
Turning Banner Ads ON does not override applicable:
privacy requirements
consent requirements
regional requirements
device requirements
service configuration requirements
Actual advertising requests are made only where permitted by the applicable Google UMP status and other relevant requirements.
Because Banner Ads ON is one of the app-level conditions for online ranking submission, turning Banner Ads OFF also prevents new online ranking submissions.
Turning Banner Ads OFF does not by itself delete ranking records already accepted by the server.
The Rewarded Ads setting is independent from Banner Ads and Global Ranking and is not required for online ranking participation.
Turning an advertising format OFF stops new advertising requests for that format.
It does not retroactively delete information already processed by an advertising provider.
Where available, users may manually open advertising privacy options to review or change applicable privacy choices.
Opening or changing those options does not by itself enable advertising or online ranking.
Gameplay cannot proceed.
Advertising and online ranking are unavailable.
Privacy-request and deletion channels remain available where needed to exercise privacy rights regarding historical or incorrectly created information.
Local gameplay only.
The following features are disabled:
Banner Ads
Rewarded Ads
other advertising
online ranking
Users aged 14–17 cannot enable Banner Ads, Rewarded Ads, or Global Ranking.
Eligible adult users may control Banner Ads, Rewarded Ads, and Global Ranking through the app's privacy settings.
For a newly selected adult age group:
Banner Ads start OFF
Global Ranking starts OFF
Rewarded Ads are controlled separately
Online ranking submission is available only when both of the following app settings are ON:
Banner Ads
Global Ranking
If Banner Ads is OFF, Global Ranking cannot be enabled.
Turning Banner Ads OFF after Global Ranking has been enabled stops new ranking submissions, clears locally queued submissions, blocks retries, and may cause late responses from earlier requests to be ignored.
Turning Global Ranking OFF also stops new ranking submissions and clears locally queued submissions.
Turning Banner Ads or Global Ranking OFF does not by itself delete ranking records already accepted by the server.
Rewarded Ads are independent from Banner Ads and Global Ranking and are not required for online ranking participation.
The app's Banner Ads ON/OFF setting is separate from Google UMP consent and other advertising privacy choices.
Turning Banner Ads ON does not override applicable privacy, consent, regional, device, or service requirements.
Actual advertising requests are made only where permitted by applicable Google UMP status and other relevant requirements.
Becoming an adult does not automatically enable Banner Ads, Rewarded Ads, or Global Ranking.
A stored OFF choice remains OFF.
If age is unknown or has not been selected, gameplay or online processing that depends on the age decision is deferred.
The game asks for an age band rather than a full date of birth.
Where available, users may manually open privacy-management options to review or change prior choices.
Opening or changing those options does not by itself enable advertising or online ranking.
If historical or incorrectly created server data exists for a child under 14, the user or the child's legal representative may use the available privacy-request channel to exercise applicable rights.
BrickSnake uses the following services.
Used for:
online-ranking storage and retrieval
backend functions
ranking validation
security
abuse prevention
related service operations
Used for:
app integrity verification
submission integrity verification
licensing and app-recognition checks
abuse prevention
Used for:
advertising
advertising delivery
measurement
diagnostics
fraud prevention
Used for:
advertising privacy messages
applicable consent and privacy-choice management
Used for:
support correspondence
privacy correspondence
data-rights requests
We use Google Cloud / Firebase for online-ranking storage and retrieval, backend functions, security, validation, and related service operations.
For customers billed in the Republic of Korea, the Google Cloud contracting/reseller entity is:
Google Cloud Korea LLC
Under the Cloud Data Processing Addendum (CDPA), Google acts as the processor of Customer Data; Google LLC and relevant global affiliates may be involved in that processing.
The primary location of our Cloud Firestore database and the primary execution region of ranking-related Cloud Functions are:
Seoul, Republic of Korea (asia-northeast3)
Supporting operations such as the following may involve processing outside the Republic of Korea:
security
maintenance
technical support
system telemetry
Cloud Logging
subprocessor activities
For the Google Cloud / Firebase processing described here, overseas processing or outsourcing is disclosed under Article 28-8(1)(3) of the Korean Personal Information Protection Act to the extent necessary to provide the optional online-ranking service.
Google Cloud does not provide a project-specific list of countries in which data is actually processed in its dynamic global environment.
We therefore conservatively disclose potential processing countries based on Google's official Google Cloud Platform Subprocessors information for the Google Cloud / Firebase services and common support and maintenance scope we use.
United States, Argentina, Australia, Austria, Belgium, Brazil, Bulgaria, Canada, Chile, Colombia, Czech Republic, Denmark, El Salvador, Finland, France, Germany, India, Indonesia, Ireland, Israel, Italy, Japan, Luxembourg, Malaysia, Mexico, Netherlands, New Zealand, Philippines, Poland, Portugal, Romania, Singapore, Slovakia, South Africa, Spain, Sri Lanka, Sweden, Switzerland, Taiwan, Thailand, United Kingdom.
This list does not mean that every user's personal information is actually processed in every listed country.
Some locations may relate only to technical support or other conditional service operations.
Data
Online-ranking information described in this Privacy Policy and minimum connection, error, verification, and security information necessary for service operation.
Timing and method
When online-ranking services, server requests, technical support, or related service operations occur, through encrypted communications such as TLS and Google Cloud infrastructure.
Recipients
Google, including relevant Google affiliates, and relevant subprocessors identified in Google's official Google Cloud Platform Subprocessors information.
Google Cloud data-protection contact:
https://support.google.com/cloud/contact/dpo
Relevant Google Cloud subprocessor names, processing locations, and activities are available at:
https://cloud.google.com/terms/subprocessors
Purpose
Ranking storage and retrieval, backend functions, security and abuse prevention, service maintenance, technical support, Cloud Logging, and related operations.
Retention
According to the game's retention rules and the service provider's necessary operational and deletion lifecycle.
Refusal and Effect
Users may:
keep Global Ranking OFF
keep Banner Ads OFF
decline to use online ranking
Because Banner Ads ON is one of the app-level conditions for online ranking submission, keeping Banner Ads OFF also prevents new ranking submissions.
Turning Banner Ads or Global Ranking OFF does not by itself delete ranking records already accepted by the server.
Online ranking will be unavailable, but permitted local gameplay is not affected.
Rewarded Ads are not required for online ranking participation.
Google Cloud Platform Subprocessors
https://cloud.google.com/terms/subprocessors
Cloud Data Processing Addendum
https://cloud.google.com/terms/data-processing-addendum
Google Cloud data-protection contact
https://support.google.com/cloud/contact/dpo
The CDPA's “up to 180 days” deletion period concerns Google's underlying-system deletion process after a deletion instruction.
It is not BrickSnake's maximum 365-day ranking-data retention period.
Google Play Integrity is a separate processing relationship from Google Cloud / Firebase.
The Google Cloud / Firebase potential-country list above is not presented as the processing-country list for Google Play Integrity.
For Google AdMob / AdSense, the contracting entity applicable to our billing country in the Republic of Korea is:
Google Asia Pacific Pte. Ltd.
Advertising-related processing may occur outside the Republic of Korea depending on Google services, infrastructure, user location, device settings, and service configuration.
The Google Cloud / Firebase potential-country list above is not automatically applied to AdMob or UMP.
For each applicable ranking board or game mode, ranking records retained within the applicable Top 1000 are kept for:
up to 365 days from the player's last accepted new ranking submission.
The 365-day period is a maximum normal retention period and does not guarantee that every ranking record will remain stored for the full 365 days.
A ranking record may be deleted earlier when:
it falls outside the retained Top 1000 for the applicable ranking board or game mode
a valid DELETE MY DATA or withdrawal request is accepted
deletion is otherwise required by applicable law
If a newly accepted score does not qualify for the retained Top 1000, the ranking record may not be retained.
Only a successfully accepted new ranking submission refreshes the 365-day retention reference date for a ranking record that remains stored.
The following actions do not refresh the retention date:
ranking reads
MY RANK reads
challenge issuance
failed submissions
rejected submissions
duplicate retries
retry attempts that do not result in a newly accepted ranking submission
After the 365-day period expires, ranking records and related ranking-management information that remain stored become eligible for deletion through the applicable cleanup process.
Recovery Code verification information and temporary deletion-request information are retained only as long as necessary for their privacy-request purpose.
Deletion Request IDs are valid for 30 days for request identification and verification.
The 30-day period is not a deletion waiting period.
The 365-day rule is BrickSnake's maximum normal ranking-retention period.
It is separate from Google Cloud's underlying-system deletion lifecycle.
Ranking-submission challenges are valid for approximately:
5 minutes
Expired challenge documents and request-limit records that are no longer needed are treated as subject to deletion through the applicable cleanup process.
Challenge expiration and physical deletion are separate events.
A challenge validity period is not the retention period of ranking data.
Google Cloud Logging retention currently includes:
_Default ordinary logs: 30 days
_Required infrastructure audit logs: 400 days
These periods are separate from ranking-data retention.
Operational logs are not intended to contain unnecessary ranking-profile personal information.
Scheduled Firestore backups are currently disabled.
Extended Point-in-Time Recovery (PITR) is currently disabled.
Limited provider-controlled infrastructure versions may temporarily remain after a live record is deleted as part of the provider's necessary system and deletion lifecycle.
General inquiry correspondence is retained after completion only where follow-up is necessary and for no longer than:
90 days
Deletion-request correspondence may be retained after completion or result notification only where necessary to confirm handling and for no longer than:
30 days
Verification materials and unnecessary attachments are deleted without undue delay after their purpose ends.
Retention of deletion-request correspondence does not delay deletion of the underlying ranking information.
Users can request deletion of ranking and related privacy records associated with their Player ID.
Privacy contact:
bricksnake@naver.com
The game provides a privacy deletion flow from the PRIVACY screen.
After server-side verification, the game may prepare an optional email draft containing:
game name
Player ID (UUID)
one-time Deletion Request ID
The deletion or withdrawal request is received when the user explicitly confirms DELETE MY DATA and that final confirmation is successfully accepted by the server.
Email is optional.
Opening, sending, or not sending the optional email draft does not determine whether the server has received the request.
The one-time Deletion Request ID is valid for 30 days for request identification and verification.
It is not a deletion waiting period.
For a lost, replaced, or reinstalled device, the saved Privacy Recovery Code can be entered on a new installation to identify the prior Player ID.
This identification does not merge the prior Player ID into a new profile.
After successful verification, the user can explicitly confirm DELETE MY DATA and receive a one-time Deletion Request ID.
If both the original device and Recovery Code are unavailable, contact us.
We may request only the minimum additional information reasonably necessary to identify the record and verify authority.
A verified deletion request may cover:
nickname
selected country code
score
level
game mode information
daily-challenge information
related identifiers
ranking-status information
related ranking and management information under our control
Uninstalling the game does not delete server records.
Google Cloud / Firebase international processing is described in Section 6 above.
Other service providers such as Google Play Integrity, AdMob, and UMP may also process information outside the Republic of Korea under their applicable service arrangements.
The Google Cloud / Firebase potential-country list is not automatically applied to those separate services.
Subject to applicable law, users may request:
access
correction
deletion
restriction of processing
objection to processing
data portability where applicable
withdrawal of consent
Users may also complain to a competent data-protection authority.
Contact:
bricksnake@naver.com
Privacy-request verification is limited to information reasonably necessary to:
locate the relevant record
verify ownership or authority
process the request
BrickSnake uses safeguards including:
HTTPS transmission
server-side validation
restricted database access
ranking-submission integrity verification
Android Keystore / AES-GCM encrypted storage for the device-side Privacy Recovery Code
The server does not store the original Privacy Recovery Code.
No electronic storage, transmission, or security method can guarantee complete protection against every possible incident.
Google Privacy Policy
https://policies.google.com/privacy
How Google uses information from sites or apps
https://policies.google.com/technologies/partner-sites
Google international data-processing information
https://policies.google.com/privacy/frameworks
Google data-retention information
https://policies.google.com/technologies/retention
Firebase Privacy and Security
https://firebase.google.com/support/privacy
Google Cloud Platform Subprocessors
https://cloud.google.com/terms/subprocessors
Cloud Data Processing Addendum
https://cloud.google.com/terms/data-processing-addendum
Google AdMob
https://support.google.com/admob/topic/9756841
Google Play Integrity
https://developer.android.com/google/play/integrity
NAVER Privacy Policy
https://policy.naver.com/policy/privacy.html
We may update this Privacy Policy when:
game functionality changes
online-ranking functionality changes
advertising functionality changes
service providers change
applicable legal requirements change
information-processing practices change
Additional notice or renewed consent will be provided where legally required.
Privacy contact:
bricksnake@naver.com