Turtle Merge 3D · Privacy policy

1. Scope and operator

It From Bit Co., Ltd. (주식회사 잇프롬빗, “we”) explains how information is handled in the Steam and Android versions of Turtle Merge 3D. The Steam app ID is 3952050 and the Android app identifier is com.itfrombit.turtlegame.

This policy covers our game features, optional play data sharing and related customer support. Features and the information they require depend on the platform and version. Advertising, Google Play Games and Google Play purchasing apply to Android versions offering those features; the Steam version does not use mobile advertising. Separate processing by Steam, Google, Unity and other providers is governed by their policies.

2. Information and purposes

Game progress and settings: Progress, collected creatures, game currency, unclaimed rewards, settings and cached purchase entitlements are handled to run and save the game. A separate account with us is not required for ordinary play. Steam uses your Steam account for its platform features. Local saves and platform cloud saves are separate from optional play data sharing and information transmitted by advertising and purchase SDKs.
Optional play data sharing: Only after you agree to play data sharing, we collect the play records supported by your version: sessions, stage settings and results, scores, play duration, decks and creature activity, item use and inventory, draws and currency changes, reward collection, and, on mobile, rewarded-ad activity and revenue and purchased products, amounts and outcomes. We use these records to understand game use, difficulty, balance, currency supply and consumption, and advertising and purchase features, and to improve the game. Records include event times, app version, platform and input method. Unsent records are temporarily stored on your device and retried while sharing remains enabled.
Mobile analytics identifiers and connection security: Sharing uses randomly generated installation, session, play and event IDs, an installation authentication credential and a server-derived pseudonymous ID. We record when sharing first starts, a configured distribution-channel label, app version and platform. On first registration, Cloudflare supplies a country code derived from the connection; we do not request precise device location for this analytics feature. The connection IP address is used to create daily changing, keyed rate-limit identifiers. Our analytics database does not store the raw IP address. This analytics feature does not send names, email addresses, advertising IDs, Google Play Games account IDs, purchase receipts or store transaction IDs. Advertising, purchasing and other providers may handle their own information as described separately below.
Steam analytics authentication: When sharing is enabled, our service sends a Steam authentication ticket to Valve to verify the account and game ownership. It converts the verified Steam ID into a game-specific pseudonymous identifier using a secret key; the analytics database stores that pseudonym rather than the raw Steam ID. Records use random session, play, event and retention-enrollment identifiers. The same Steam account can be linked across devices and after sharing is enabled again. This analytics feature does not receive your Steam password, real name, email address or save files.
Optional daily visits and return measurement: After you expressly agree to the updated sharing notice, we observe days when the app is in the foreground and not paused, including visits without starting a game round. When a new retention group is created, the first observed visit after that agreement anchors it; it is not necessarily the purchase, installation or first-ever play date. We send at most one marker per UTC calendar day from that first day through day 30, including observation time, enrollment ID, platform and the game version at enrollment. We measure whether the account or installation returns on exactly day 1, 7 and 30. Each target day is finalized after it ends plus a 24-hour late-upload allowance; observations outside the allowed upload window may be excluded. Re-enabling sharing does not necessarily reset an existing group for the same Steam account. Existing play history is not backfilled, and older consent alone does not enable this new collection.
Steam platform features: Steam handles game ownership and DLC entitlements, achievements, leaderboards, cloud saves and Workshop features offered by the game. Leaderboards use Steam identifiers, display names, scores and ranks. These features and Steam's own usage statistics are separate from our optional analytics; turning off our sharing does not remove Steam records or disable those platform services.
Google Play Games leaderboards: In versions offering leaderboards, Google Play Games receives completed-game scores. The game uses player IDs, nicknames, scores and ranks to display leaderboards. Sign-in may be attempted automatically according to Google settings; ordinary play remains available without signing in.
Advertising: The Google AdMob SDK processes IP addresses (which may estimate approximate location), identifiers such as advertising ID and app set ID, interactions such as ad views and taps, and diagnostic and performance information. Purposes include advertising, measurement, analytics and fraud prevention. Processing can vary with consent, device settings and ad delivery mode.
Purchases and restoration: Google Play and Unity IAP process product and transaction identifiers, receipts, purchase history and status to support payment, purchase verification and restoration. Unity IAP may also process device and app identifiers, IP-derived approximate location, diagnostic, error and performance information for functionality and analytics. The game does not directly ask you to enter card or bank account numbers.
Customer support: Email support receives your sender address, message and any attachments you choose to provide. The website form sends your name, reply address, selected game and inquiry type, message, optional company, language and page URL. We use these to understand and respond to inquiries and resolve problems. Do not send unnecessary sensitive information, national ID numbers, passwords or card numbers.
Review account: When you sign in with a review account provided by us, the account name and password are sent to the authentication service. The issued session token is used to verify access. The connection IP address and a derived identifier are processed for login rate limiting and security. A review account is not required for ordinary play.

3. Services involved

We operate optional play data analytics using Cloudflare. Advertising and purchase SDKs may also transmit information directly to their providers without passing through our analytics service. Turning off play data sharing does not turn off the separate processing needed by those services.

Valve · Steam: Valve provides the Steam platform, including account authentication, ownership, achievements, leaderboards, cloud saves and Workshop services used by the game. We verify Steam authentication tickets and ownership through Steam's service when authenticating optional analytics or a deletion request. Steam handles its account, purchase and platform data under Valve's privacy policy.
Google AdMob · Google Play: These services support advertising, consent-related choices, payment and purchase records under Google’s applicable policies and service terms.
Google Play Games: In versions using Google Play Games, Google provides sign-in and leaderboards. Its SDK automatically collects analytics and diagnostics for stability and product improvement, and gamer identity (nickname and avatar) when a Play Games profile is created or updated. Data is transmitted using HTTPS and may be processed internationally under Google's policies.
Unity IAP: We use Unity IAP for store connections, purchase status and restoration, and purchase-related diagnostics and analytics. Its own data processing is separate from the standalone Unity Analytics feature.
FormSubmit · NAVER Mail: If you use the website inquiry form, FormSubmit forwards your inquiry to our company email, received through NAVER Mail. Direct email does not use the FormSubmit form. We access the inquiry to handle your request.
Cloudflare: We use Cloudflare Workers and D1 to receive, authenticate, store and analyze optional play data on our behalf, and Cloudflare Workers for review-account authentication and connection security. Data is transmitted over HTTPS. Cloudflare may process connection information, including IP addresses, to provide and secure its services. Access to our analytics is restricted to the developer; the records are not published as player profiles.

4. Play data sharing, advertising and privacy choices

Play data sharing is off until you expressly agree in the app. You can decline and still use every game feature, and change the choice in Settings. The updated daily-visit and return measurement requires new express agreement; a previous grant alone does not start collection or upload in the updated client. This choice is separate from advertising privacy consent, Google Play Games settings and Steam's own data processing.

Turning sharing off stops new collection and uploads on this device and removes its unsent analytics records, including pending daily-visit markers and local retention enrollment. On Android it also removes the local installation identity; later agreement creates a new installation identity. Steam's account-derived pseudonym can remain the same after agreement again. If local deletion fails, collection remains off while deletion is retried. This does not remove game progress or immediately delete previously uploaded records. Server retention and explicit deletion are described in sections 5 and 6.

You may choose to watch a rewarded ad through the reward options presented in the game. Where an ad-removal product is available, its description explains the benefits provided without ads.

A privacy message is displayed when Google requires consent or privacy choices. If an advertising privacy option is shown in the app settings, you can use it to reopen the applicable choices. Declining personalized advertising may not stop all processing needed for basic ad delivery, security or fraud prevention.

Android settings allow you to reset or delete your advertising ID. Menu names vary by device and Android version. Deleting this ID does not delete other identifiers, purchase records or support inquiries.

You can manage Google Play Games sign-in and profile visibility in Google settings. Other players' access to leaderboard data follows your profile visibility settings.

5. Retention and deletion

You can remove local game saves by clearing app storage, removing save files or uninstalling, depending on the platform. This may erase your progress. Operating system backups, Steam Cloud, store purchase records and data held by external services are managed separately.

Individual play-event records remain eligible for scheduled deletion 30 days after server receipt. Existing mobile installation-linked gameplay analysis follows that 30-day period. Separately, the minimal linked return-measurement record stores the pseudonymous account or installation ID, first observed visit and enrollment date, enrollment ID, platform, initial game version, expiry and day-1/day-7/day-30 return flags. This compact record becomes eligible for finalization and removal at the start of the UTC date 32 days after the first observed visit's UTC date; we describe this as up to 32 days from that first shared visit. It does not extend the 30-day play-event retention.

Installation, authentication and minimal abuse-prevention or deletion-revocation records become eligible for cleanup after 31 days without authentication, once their related play records and upload state have been removed. Scheduled deletion and finalization run in batches, so a backlog or service failure can delay completion beyond the stated thresholds. Uninstalling or turning sharing off does not itself request deletion of already uploaded records.

Before linked analysis records are removed, we may combine them into statistics grouped by date, platform and game version without account, installation, player, session, event or enrollment identifiers. Finalized return statistics are kept for 90 days after their own finalization; adding later finalized statistics does not renew an earlier batch's period. Other existing anonymous daily totals follow their 90-day finalization-based cleanup. These totals cannot be linked back to an individual; an individual deletion request cannot identify or remove one person's part after finalization. Connection rate-limit identifiers expire at the end of the applicable hour or day and are removed by subsequent authentication or scheduled cleanup. These application-database rules are separate from Cloudflare's infrastructure information under its own policy.

We delete support emails and attachments under our control without undue delay once the inquiry and necessary follow-up are resolved. Records that must be retained by law are kept separately for the required period and deleted when that period ends. This rule does not delete records independently held by external providers.

Retention and deletion by Valve, Google, Unity and other services depend on the information, service settings and provider policies. We cannot directly delete every record held by those providers.

FormSubmit states that it retains form submissions for 30 days. This archive is separate from our support mailbox and may remain after we delete the email. You can contact us directly by email instead of using the website form.

Where information must be retained by law, we will distinguish the legal basis, information and period concerned. Information under our control is deleted or destroyed so that it cannot be recovered when its retention purpose and obligations end.

Review progress is kept only in app memory, separately from normal saved progress, and is discarded on sign-out or app exit. Review sessions remain valid for up to two hours. The authentication service does not store plaintext passwords or log passwords, session tokens or request bodies. Cloudflare’s policies govern retention of information handled by its underlying services.

Deleting the app does not delete Google Play Games scores or profile data. You can delete this game's Play Games data or your profile through Google's official deletion process linked in section 3. Google's retention and deletion policies apply.

6. Access, correction and deletion requests

You can contact the privacy email below to request access, correction, deletion, restriction of processing or withdrawal of consent. Legal representatives may also make requests under applicable law. We will explain the scope of the request and any minimum information needed to verify it.

Include the game name and what you are requesting. For purchase issues, we may ask for an order reference when needed. Do not send passwords, analytics authentication credentials or identity document copies in your initial message.

In Steam, use “Delete my records” in the play-data settings to request deletion of linked server play records and any active return-measurement record for the verified account. The app stops collection, clears pending local records and shows whether the server request completed; retry if it reports a failure. Minimal revocation and abuse-prevention information follows the 31-day rule in section 5. Already finalized anonymous totals remain until their scheduled expiry because they cannot be linked back to you. This does not delete Steam achievements, leaderboards, cloud saves, purchases or other Valve-held data.

For access or deletion requests, including Android records, contact the privacy email below. Analytics uses a pseudonymous Steam account or installation ID rather than your name or email, so an email address alone may not locate a record. Clearing the Android installation identity or reinstalling can also prevent us from linking a request to an earlier installation. We will explain the minimum verification information and any limits. Do not send passwords, authentication tickets or analytics credentials. Provider-held records may require a separate request to that provider.

We will explain the outcome for information we control, or why a request cannot be completed and the applicable process. Steam account and purchase information, Google account or Play purchase information, and information held by Unity may require a separate provider process. A data deletion request is separate from purchase cancellation or a refund.

7. International processing

Google and Unity state that they process information through global infrastructure, including in the United States and other countries outside the Republic of Korea. Information described in section 2 may be transmitted over networks when the relevant advertising or purchase service operates. The purposes are those described in sections 2 and 3; retention and deletion follow section 5 and the applicable provider policies.

Website inquiries are transmitted through FormSubmit to our NAVER Mail inbox when you submit the form. FormSubmit’s public privacy policy does not specify every processing country. Direct email to our contact address bypasses FormSubmit. The linked Google, Unity, FormSubmit and NAVER policies explain their privacy contact channels and applicable processing practices.

You can ask our privacy officer about overseas processing or request restriction or withdrawal of consent. Use the available in-app advertising privacy choices or contact the relevant provider for information it controls. Restricting processing needed for a feature may prevent that advertising, purchase, restoration or inquiry feature from working. Declining personalized advertising does not necessarily stop all overseas processing.

Optional play data, return-measurement records, Steam or installation authentication information, review-account authentication and connection information may be transmitted over HTTPS and processed outside your country through Cloudflare's global infrastructure. Steam authentication also uses Valve's service. The purposes and information are described in sections 2 and 3, and retention in section 5. Declining or withdrawing play data sharing stops future transmissions for our optional analytics without restricting game features.

8. Security and children

Our optional play-data and review-account services use HTTPS. Steam analytics authentication verifies a Steam ticket and game ownership and stores a keyed pseudonym. Mobile analytics authenticates installations and stores a hash of the installation credential rather than the credential itself. According to their official disclosures, advertising and purchasing SDKs encrypt transmitted data using TLS or equivalent transport protection. We restrict access to analytics and support information to what is needed for handling it and apply access controls.

The game is designed primarily for teenagers and adults. Content age ratings and the intended primary audience are different criteria. A parent or guardian may contact us about concerns involving a child’s information.

9. Contact and complaints

Privacy officer: SEO SEUNGWAN (서승완), It From Bit Co., Ltd. (주식회사 잇프롬빗). For privacy inquiries or requests, email fibonacci618@naver.com.

In Korea, privacy concerns can also be raised with the KISA Privacy Infringement Report Center (118 within Korea; privacy.kisa.or.kr) or the Personal Information Dispute Mediation Committee (kopico.go.kr).

fibonacci618@naver.com

10. Changes

This policy first took effect on 2026-09-24 and was updated on 2026-10-25 to cover Steam alongside Android, new express consent for daily-visit and return measurement, and the separate 30-day play-record, up-to-32-day linked return-record and 90-day anonymous-total periods. The current policy is available in English and Korean; other language routes display the current English policy until their translations are updated. We will update this page when features, providers or information handling change. Important changes will be announced here and, where necessary, within the app.