Thin Walls is a puzzle game operated by Ratchet Media, LLC ("we", "us"). This policy explains what information the game uses, why, and what you can do about it. We have tried to keep it short and plain. It covers the Thin Walls apps for iPhone, iPad and Android and the web version of the game.
- You can play ordinary puzzles as a guest. Purchases require a linked Apple account on Apple devices or Google account on Android.
- Your progress is saved on your device. When you're online, a copy is also kept on our server under a random game account ID. Backups cannot guarantee recovery of an unlinked guest account.
- If you play the daily building, your display name and move count can appear on a public leaderboard.
- No ads or cross-app tracking. Cloudflare hosts our service. Apple and Google provide sign-in and purchases on their platforms. We do not sell information.
1. Information saved on your device
The game saves your progress in your device's storage (browser storage on the web, app storage in the apps). This includes your buildings, stars, rent, collectibles, outfits, settings such as volume and accessibility options, and a backup copy if you ever choose between two saves. Some device settings stay local; progress also backs up when connected. The iOS app stores its session and Apple account identifier in Keychain. Keychain entries can survive app removal. Android stores its session and Google account identifier encrypted with Android Keystore, outside device backups. Use account deletion in Settings to remove the account and clear the game's device data.
2. Cloud save and the guest ID
When your device can reach our server, the game backs up your progress automatically. You can start as a guest:
- Our server creates a random guest player ID. It is not based on your device, your phone number or anything about you.
- Your device gets a secret session token that proves it owns that guest ID. We store only a scrambled (hashed) form of the token, plus when it was created and last used.
- We store your game progress (the same save data described above, minus a few device-only settings) and when it was last updated.
- We give you a starting display name like "Landlord 4821". You can change it in Settings. Please don't use your real full name or anything personal.
Ordinary puzzles work offline and back up after reconnection. Purchases, premium spending, and verification of some rewards require a connection.
3. Daily leaderboard
When you finish the daily building, the game sends your solution so the server can check it. We store the number of moves and the time you submitted for that day's puzzle, linked to your game account ID. The leaderboard shows the top players' display names and move counts publicly to other players. Your guest ID is never shown.
4. Codes, invites, reminders and rewards
- Promo codes: when you redeem a code, we record which code, when, and the reward, so each code can only be used once per player.
- Founder numbers: if you claim a Founding Landlord number, we store the number and when you claimed it.
- Invites: we store your invite code, who invited whom, the relevant timestamps, and which handcrafted buildings an invited player completed. These records let us verify the ten-building reward and prevent duplicate rewards. Other players do not see your guest ID.
- Inbox gifts: we store a grant when you claim a gift, so the same gift is not added twice.
- Reminders: optional reminders are scheduled only on your device. We do not receive a notification token or store your reminder choices on the server.
5. Hosting, IP addresses and logs
Our server runs on Cloudflare (Cloudflare Workers and the Cloudflare D1 database). Like any website or online service, Cloudflare receives your device's IP address and basic request details (such as the time, the address requested and your browser or app type) in order to deliver the game and protect it from abuse. Cloudflare acts as our service provider. Its operational logs follow the retention settings of the service.
Our own server code also limits how many guest accounts can be created from one address per hour, which stops spam. It keeps a small counter labeled with a one-way scrambled code (a hash) made from the IP address, never the address itself. Old counters become eligible for removal after about a day. Removal happens during cleanup triggered by later requests, so inactive counters can remain longer.
6. What we don't do
- No advertising and no ad networks.
- No tracking across other apps or websites. Optional first-party game analytics requires your permission.
- No chat and no way for players to message each other.
- We don't sell your information or share it for advertising.
- We don't ask for your location, contacts, photos, camera or microphone.
7. Linked accounts, purchases and support
On supported Apple devices, Sign in with Apple can link your game account for recovery. We store Apple's account identifier and encrypted authorization credentials for account management. The app does not request your Apple name or email.
On Android, Google sign-in links your game for recovery. We store Google's account identifier and the account's purchase environment. We use your verified Google email to identify approved purchase testers. We do not store that email or a Google refresh token.
Apple or Google handles payment on its platform. Our service verifies purchase evidence and stores product and transaction identifiers, Google purchase tokens, purchase dates, and delivery or refund state. We do not receive payment-card details from either store.
We also store balances, inventories, reward claims, and action requests to prevent duplicate delivery and recover interrupted actions. These records are associated with your game account while that account exists.
If you email support, we receive your email address and the information you include. Support diagnostic reports are sent only if you share them. Do not send passwords or complete signed purchase receipts.
8. Why we use this information
The necessary records above run the game: saving and restoring your progress, linking accounts, delivering purchases and processing confirmed refunds, running the daily leaderboard fairly, verifying invite progress, delivering inbox gifts, honoring codes and founder numbers, keeping the service secure and preventing cheating and abuse. Where privacy laws ask for a legal basis, we rely on providing the service you asked for and our legitimate interest in keeping it secure and fair.
If you choose Allow analytics, we also use optional game observations to improve tutorials, difficulty, features, purchase reliability and retention. We collect sessions, active play time, puzzle summaries, tutorial steps, help, waits, resource blocks, feature use, and shop or account outcomes. We link these observations to a random identifier associated with your game account. Reports can join this identifier to verified purchase and reward records. We record occurrence time, local hour, weekday, UTC offset, game version, platform, language and a bounded distribution label. Bounded loss counts and delivery-delay categories help us assess collection reliability. These counters do not contain crash logs. These linked records are personal data. They are not anonymous.
We use your consent for this optional analysis. Refusal leaves the full game available. No optional history is collected before a confirmed grant. We do not collect advertising identifiers, raw text, touch coordinates, board replays or precise location. Active time stops in the background and after two minutes without interaction. Long thinking pauses may be undercounted. An unexpected ending remains unknown. It does not prove a crash or uninstall.
Settings provides Stop and erase analytics. Withdrawal stops collection and clears queued observations on this device immediately. When offline, the device saves a pending request and sends revocation before any upload after reconnecting. The status states when server confirmation is pending. Another offline device may not learn of withdrawal immediately. The server rejects its uploads after revocation commits. Withdrawal erases linked game-database analytics. Operators must erase controlled export copies through the documented cleanup procedure. The game does not confirm external-copy erasure.
9. How long we keep it
- Optional analytics: raw observations expire at 90 days, and derived daily features expire at 13 calendar months. Routine maintenance removes expired records. The expiry dates do not trigger automatic deletion by themselves. Controlled exports are restricted, short-lived and included in erasure. Offline device queues hold at most seven days, 1,000 events or 2 MiB. Account switching discards the previous queue. Account deletion also erases linked analytics. Verified financial and security records retain their separate policy below.
- Cloud save, display name, codes, founder number, invite relationships, verified completions and gift claims: until account deletion or service cleanup. There is no automatic inactivity expiry in the current service.
- Daily leaderboard results: kept so past leaderboards stay accurate, until you ask us to delete them.
- Cloudflare request logs: retained according to the provider settings. In-game account deletion does not erase email correspondence.
- Limited purchase records remain after account deletion to prevent repeat redemption. The game-account link and private offer snapshot are removed. Retained records include purchase-request and transaction identifiers, product and purchase dates, delivery/refund state, and settlement history. These records have no automatic expiry. They are not described as anonymous.
- Public-name safeguards: reports keep the reported name, reason, account links and creation time while open. Deleting the reporter's account removes the reporter link but leaves the unresolved report for review. Resolution clears the name, reason and reporter link. We retain the report ID, target, disposition and timestamps until target-account deletion. Deleting the target removes its reports and name restriction. Hidden-name preferences remain until cleared or either account is deleted.
- Deletion confirmation receipt: we retain a hash of the calling session token so a later retry can confirm deletion. The receipt has no expiry and contains no guest ID, bearer token, or game data.
Reminder schedules stay on your device until they are delivered, replaced, cancelled in Settings, or removed with the app.
Link your game with Apple on Apple devices or Google on Android before changing devices. Apple and Google game accounts remain separate. A public display name cannot prove ownership of an unlinked guest save.
10. Deleting your data and your rights
You can permanently delete your game account inside the game. Open Settings → Cloud save → Delete account, tap Delete my account, and confirm. This removes the cloud save, leaderboard results, invite and completion records, claimed rewards, sessions, Apple or Google identity linkage, Apple credentials, and the player record. It also removes Thin Walls data from that device. Unresolved reports about other players remain without your account link. The limited purchase records and deletion receipt described above remain. Deletion does not undo campaign usage or reuse a Founder number. The deletion cannot be undone. The game creates a new guest only if you choose Start a new game afterward.
If the game cannot confirm that deletion finished, it keeps the device data and lets you retry. The server's durable deletion receipt makes that retry safe even if the first request succeeded but its response was lost. If the server confirms deletion but device cleanup is interrupted, the game records that confirmation and finishes device cleanup when you retry or reopen the game.
After deleting the account, our service attempts to revoke Apple authorization. If Apple does not confirm revocation, the app explains how to disconnect Thin Walls in your Apple account settings. Deletion does not request a purchase refund.
You can also email support@ratchetmedia.com about account deletion.
Depending on where you live (for example under the GDPR in the EU, the UK GDPR, or California and other US state laws), you may have the right to access the data we hold about you, correct it, delete it, receive a copy, or object to or restrict how we use it. Email us to make a request. We will not treat you differently for using these rights. We do not sell or "share" personal information as California law defines it. You can also complain to your local data protection authority.
11. Children
Thin Walls is intended for a general audience. It is not offered in the App Store Kids Category. We do not ask players to enter their age. Please keep personal information out of public display names.
If you are a parent or guardian concerned about a child's information, contact support@ratchetmedia.com about access or deletion.
12. Security
Everything sent between the game and our server is encrypted in transit (HTTPS). We store only a hash of session tokens, and our server never accepts a player ID from your device to decide whose data it is. No system is perfectly secure, but we work to keep your data safe and to collect as little as we can.
13. International players
We are based in the United States. Cloudflare runs a global network, so your data may be processed in the United States and other countries.
14. Changes to this policy
If we change this policy, we'll update the date at the top. For bigger changes to the information we use, we'll update the policy before the change goes live and mention it in the game or the store release notes.
15. Contact
Ratchet Media, LLC
Email: support@ratchetmedia.com