MergeYards
English

MergeYards: Privacy Policy

Last updated: 19 October 2026 · App: MergeYards (com.mergeyard.game) · Developer: BLN Design and Architecture

This text is a translation. If the versions differ, the Turkish version prevails.

In short: MergeYards is a merge game made for children. The game itself does not collect your real name, e-mail address, location, contacts or advertising ID. It only collects technical information and in-game actions so the game runs well on every phone. The nickname the game gives (from a ready-made list) is stored with the progress save. This collection can be switched off completely in the game’s Settings, behind a parental gate. The ad software for the game's optional rewarded ads (Google) processes device and network information (IP address) to serve an ad, and for players 13 and over may also process the advertising ID (section 5).

1. Who collects the data

MergeYards is made by BLN Design and Architecture, an independent developer. Data controller: BLN Design and Architecture. Contact: info@mergeyards.com

2. What is collected

WhatExampleWhy
Device technical data Phone model (e.g. “SM-M127F”), screen size, screen density (DPI), screen refresh rate, operating system, app version; the approximate country taken from the device’s language/region setting (e.g. “TR”; no IP address, city or location is used) and the time-zone name (e.g. “Europe/Istanbul”) So the game is the right size and runs smoothly on different screens and phones
Performance data Frames per second, duration of the slowest frame, memory usage To find and fix stutters
In-game actions Coordinates of the point touched on the screen, drag gestures, which cell an item was dropped on, completed levels, in-game rewards and in-game currency earned; session length, the level where the session ended and the hours since the previous session (a counter) To measure whether the game is understandable and playable (for example, to see if a child cannot merge a box)
Nickname A nickname of up to 12 characters that the game gives from a ready-made list (e.g. “Happy Fox”). No name is typed on a keyboard; it is not a real name. It is stored with the progress save and with the technical row written when the game starts. To save progress and to tell sessions from different devices apart. The player can pick another ready-made name with the dice button.
Account ID (browser version) An anonymous Firebase ID created when the game opens. If a Google account is optionally linked with the “Make progress permanent” button, Google also tells us that account’s name and e-mail address. This option is shown only to players aged 13 and over; in under-13 child mode (and while no age has been chosen) there is no Google account linking. So that game progress is not lost and one person’s different sessions can be joined together. Signing in is not required; if you do not link an account, no name or e-mail is collected.
Installation code An 8-character code generated randomly by the app itself To link the rows of the same session together

About the installation code

This code is not derived from the phone’s hardware. It is generated randomly when the app is first opened, stored only in the app’s own folder, and disappears when the app is uninstalled. It is not an advertising ID and cannot be matched with other apps or advertising companies.

3. What is NOT collected

Real name and surname (the nickname the game gives comes from a ready-made list)E-mail address (only if you link a Google account)
Location dataPhone contacts, address book
Advertising ID (AAID): the game itself does not collect it; for players 13+ the ad software may process it (section 5)IMEI, MAC address, serial number, SIM data
Photos, microphone, cameraAudio or video recordings

4. Where data is stored and who can see it

Data is sent over an encrypted connection (HTTPS) to our database on Google Firebase (Cloud Firestore). The database can be read only by the developer; no player can see another player’s data. Data is not sold to third parties and is not shared for advertising or marketing. The only exception is the service providers acting on our behalf: Google (Firebase; hosting and database) and Cloudflare (visit counting). They process the data solely to provide the service to us, not for their own purposes.

Website (mergeyards.com) visit counting

The landing page uses Cloudflare Web Analytics for aggregate visit counts. It sets no cookies and creates no device or person identifier; it only reports page views, browser type and country-level totals, so no consent banner is shown. The browser version of the game (/oyna/) loads the same counter only under the age rule: it is loaded only when the player has explicitly selected 13 or older ("13+"); it is never loaded while age is unknown or the player is marked as under 13 ("child"); the store (Android) build has no counter. As a service provider, Cloudflare technically processes your IP address while serving the request; we only receive aggregate figures that cannot be traced to a person, and the IP address never reaches us and is not stored by us. Details: the Cloudflare Web Analytics privacy notice.

The browser version also records in its session start row which link you came from: the short source tag in the address (the ?k= value, e.g. “site”) and only the domain name of the referring site (e.g. “mergeyards.com”; no page path, search text or personal data). This does not identify a person; it is used to see, in aggregate, which channel brings players.

5. Ads and purchases

Purchases: in the Google Play store version (once released), in-game currency (Gilt packs) can be bought with real money. Payment is handled entirely by Google Play; card, account and billing details never reach us. We only receive, without identity, which pack was bought, the result (completed/cancelled), the result of the purchase check (valid/invalid) and this month's total spending (from pack prices, in cents); taps in the store screen are recorded like other in-game actions. In under-13 child mode the purchase screen is behind the parental gate and a monthly spending cap applies. The browser version has no purchases.

Ads: the game has optional rewarded ads: the player chooses to watch one and gets an in-game reward only after watching it to the end; there are no forced interstitial ads. The ad network is Google AdMob in the Android version (certified for Google Play's Families program). The browser version currently shows no real ads; its ad button only opens the test mode of Google H5 Games Ads. To serve an ad, the ad software sends device and network information (IP address, device model, language) directly to Google; this information does not reach us. In the under-13 child mode (and while no age has been chosen) ad requests are tagged as child-directed, are not personalized, do not use the advertising ID and are limited to the most suitable content rating (G). For players 13 and over the advertising ID (AAID) may be processed by the ad software; personalized ads are used only if ad permission is turned on in Settings and, where required (EU/UK), after the consent screen. We only receive, without any identifier, which screen requested the ad, how long the wait was and the result (watched / closed early / did not open). Details: Google's advertising privacy notice (policies.google.com/technologies/ads).

6. Children

Age question: on first launch the game asks for the year of birth from a neutral list (an “I'm not sure” option is included). The year and month of birth are not stored and not sent. The age group (“under 13” or “13 and over”) is kept on the device and the game is set up accordingly; for under-13 players the month they turn 13 is also kept only on the device and is never sent to the server, the cloud save or a transfer code. When that month comes, the switch to “13 and over” happens only after the parental gate question is answered. If a Google account is linked, the age group (only “under 13” / “13 and over”) travels with the cloud save; telemetry carries only a coarse age group. In under-13 child mode there is no Google account linking.

MergeYards is designed for children aged 6-20. The game has no chat, no friend adding, no messaging with other players and no user-generated content. No personal information is requested from the child; there is no box for typing a name, and the nickname is given from the game’s ready-made list. Settings that are destructive or require an adult decision (turning off data collection, resetting progress) are behind the parental gate.

In the Google Play store version (once released), in under-13 child mode (and before an age has been chosen) the country, time zone, phone model (only a coarse device class instead), precise screen density and browser source fields are not collected. In that version nothing is sent until a parent answers “Yes” to the question behind the parental gate on first launch.

7. Parents’ rights

8. Retention period

Session records carry no identity (only a random installation code). Session records and transfer codes older than 30 days are deleted on the server by a regularly run deletion job (within 30 days at the latest); only aggregate figures that cannot be traced to a person are kept for development.

9. Changes

If this policy changes, the “Last updated” date on this page changes. If there is a significant change, players are informed in the game.

Privacy · Terms of use · Account deletion · Press kit · For families · Home