Rome TD: Fire and Bricks · Apple App Store
Last updated: September 30, 2026
This policy describes what Littoral Games (“we”) does with information in connection with Rome TD: Fire and Bricks, a tower-defense game (the “Game”), distributed on Apple App Store. This page is the privacy policy linked from the App Store listing. It is written to match the App Privacy label on that listing, which declares four data types — Identifiers, Usage Data, Coarse Location and Purchases, all linked to you, all used only for analytics, and none used for tracking.
We have kept this document short on purpose. A privacy policy that lists everything a game might one day do is not more protective — it is less accurate. This one describes what the Game actually does today. If that changes, we update this page and the store declarations before shipping the change.
Littoral Games develops and publishes Rome TD: Fire and Bricks. Privacy questions and data requests: privacy@littoralgames.com.
The Game sends us the following events, and nothing else:
Every event also carries the session it belongs to, the release channel and your device's UTC offset. Every event carries a pseudonymous in-app identifier: a random value the Game generates on first launch and stores on your device. It is not an advertising identifier, not a hardware identifier and not an account — but it is stable across sessions, so we treat it as identifying and declare it as such on both stores. Clearing the app's data or uninstalling the Game discards it; the next launch generates a new one.
Purchases. If you buy the one-time unlock, Apple processes the payment. We receive only which product was purchased and whether your purchase is active or restored. We never see your card number, billing address or Apple ID. The purchase itself runs through Unity In-App Purchasing, a component made by Unity Technologies. When a purchase starts, succeeds or fails, that component sends Unity a record of it: the product, price and currency, the transaction identifier and store receipt, a Unity installation identifier and Apple's identifier for vendors (IDFV), and technical device details such as the device model, operating-system version and language settings. Unity receives this under its own privacy policy (https://unity.com/legal/game-player-and-app-user-privacy-policy).
Email you send us. If you write to support or to the address above, we process your address and your message so we can reply.
Data on your device. Your save, settings and unlock are stored locally; the save itself is never uploaded. The progress snapshots above send us a summary of it, including whether you own the unlock.
Connection data and approximate location. The server that receives the events above records the IP address your device connects from, stores it with those events, and resolves it against a regularly updated IP database to derive an approximate location — country, region and city level. This does not come from your device: the Game requests no location permission and uses no GPS or Wi-Fi positioning. We use it to see which countries our players are in. It is stored next to the pseudonymous identifier above, so we treat it as part of your analytics record, and we declare it on both stores. It is not used for advertising, profiling or any automated decision about you. How long we keep it is in section 7.
The Game does not show ads. There is no ad network, no attribution or measurement SDK, and no advertising identifier is read — no IDFA, no Android Advertising ID, no OAID, and no App Tracking Transparency prompt, because nothing here would need one.
There is no crash or performance reporting SDK, no Firebase, no Google Play Games Services, and no third-party analytics SDK. The only third-party component that sends data is Unity In-App Purchasing, and only about purchases (section 2). Unity's own Analytics, Ads, Crash Reporting and Performance Reporting services are switched off in the project.
There is no account and no login. We never receive your name, email address (unless you write to us yourself), phone number, postal address, contacts, photos, camera or microphone input, device location, health data, biometrics, browsing history, search terms, or any text you type. The Game requests no device permissions — no location permission, so nothing here uses GPS or Wi-Fi positioning. The only location signal we hold is the estimate derived from your IP address at our server, described in section 2.
One reason: analytics. We look at how far players get, where they stop, and which towers they build, so we can balance the levels. We do not use this data for advertising, for marketing, for profiling, or to make automated decisions about you, and we do not sell it.
| Recipient | What they get | Why |
|---|---|---|
| Our own analytics service | The events above, the IP address they arrive from, and the approximate location it resolves to | It is our own deployment of ThinkingData analytics software, running at
ta2.cisgames.cn. It processes the data on our instructions and for no purpose of
its own, which is why the Play Data safety form records this as collection rather than
sharing. |
| Unity Technologies | The purchase records described in section 2 (product, price, transaction and receipt, a Unity installation identifier and Apple's identifier for vendors (IDFV), device model and system details) | Sent by Unity In-App Purchasing, the component that runs the purchase. Unity uses it under its own privacy policy, so the Play Data safety form records this as sharing. |
| Apple | Distribution and payment data they handle themselves | To deliver the Game and process the one-time purchase, under their own privacy policies. |
There is no other recipient. No ad network, no analytics vendor's shared cloud, no data broker, no attribution partner. We do not sell personal information and we do not disclose it for cross-context behavioural advertising.
Our analytics receiver runs in mainland China (Ningxia region). If you play outside China, the events described in section 2 are transferred there, together with your IP address and the approximate location derived from it. They contain no name, no email address and no message content — beyond that, only the pseudonymous identifier and the gameplay fields listed above. Traffic we control uses HTTPS. Unity processes its purchase records, and Apple processes distribution and payment, in their own regions under their own terms.
Write to privacy@littoralgames.com to ask what we hold, to get a copy, to correct it, or to have it deleted. Tell us the approximate date and the device you played on so we can locate the records — because there is no account, that is the only way we can find them. We reply within the period applicable law requires.
Depending on where you live you may also have the right to object to or restrict processing, to portability, to withdraw consent, and to complain to your supervisory authority. In the EEA and UK we rely on our legitimate interest in understanding and balancing our own game; you can object to that at the address above. In California and similar US states: we do not sell or share personal information as those laws define it, and we will not discriminate against you for exercising your rights.
Uninstalling the Game removes the local data on that device and stops any further events. We cannot delete records held by Apple or Unity — use their own privacy tools for those.
The Game is for a general audience. It is not directed to children, is not listed as Designed for Families or Teacher Approved, and we do not knowingly collect data from children under 13. If you believe a child's data reached us, write to us and we will delete it.
We use measures appropriate to a game of this size: HTTPS on the links we control, limited access to the analytics system, and no storage of payment or contact data in the first place. No method of transmission or storage is completely secure.
If the Game starts collecting something new, we change this page and the store declarations before that version ships. The date at the top changes with it.
Littoral Games · privacy@littoralgames.com
The Google Play version of this policy is at /android/. Chinese versions are linked at the top of this page.