Privacy Policy

1. Who we are

TearCraft is made and operated by Isaev LLC, a limited liability company registered in Wyoming, United States, at 30 N Gould St, Ste R, Sheridan, WY 82801. We are the data controller for everything described here.

For any privacy question or request, write to privacy@isaevlabs.com. We answer within 30 days.

2. What the game collects

Diagnostics and gameplay analytics. The game sends events to our own servers so we can see whether it runs well and which parts of it people use. Each event is linked to your game account and to a device identifier, and carries a session identifier, the game version and platform, your device model and operating system, the language your device is set to, hardware characteristics (memory, processor, graphics), performance measurements, and the gameplay action itself — that a world was opened, a tool was used, a session ended. If you installed the game from an advertising link, we also record the campaign labels that came with it, such as UTM parameters or a Google Ads click identifier. We also derive the country your request came from, and use it to pick the nearest game server for multiplayer; we do not store the IP address alongside these events.

The device identifier is the per-app identifier your operating system gives us — on Android an identifier scoped to this app, on iOS one scoped to apps from the same developer. It is not your advertising ID: our own analytics does not use the advertising ID. The advertising ID is used by the advertising service and by Google Analytics for Firebase — see the «Advertising» section and the Firebase paragraph below. The identifier is reset when the device is reset to factory settings, and on iOS also when you remove all of our apps.

Your game account. The first time the game starts, it creates an account for you automatically, linked to your device identifier, with an account identifier and a nickname the game picks for you; you can change the nickname at any time. Other players see your nickname — in shared rooms, in their friends list and as the author of worlds you publish. If you also sign in with Google, we receive and store your email address and the account identifier Google issues for our app. We do not receive your password and do not store your Google profile name.

Friends and multiplayer. If you use these features, we store your friends list, the friend requests and room invitations you send and receive, the players you have blocked, and the names of rooms you create. Your friends can see whether you are in the menu or in a game, and the code of the room you are in, so that they can join you.

Worlds and creations. Worlds you build are saved on your device; if you choose to publish one, its contents and the name you gave it go to our servers so other players can load it. Creations you make with the in-game creator are made on our servers, and once they pass moderation they are published to the shared catalogue; in the game, other players see a published creation without your nickname. How the creator works is described in the «The AI creator and moderation» section.

Voice input. If you choose to dictate a request to the in-game creator instead of typing it, the game records your voice for that request. How the recording is handled and how long it is kept is described in the «Voice input» section. The text of creation requests, typed or dictated, is processed by AI providers, as described in the «The AI creator and moderation» section.

Diagnostic captures. To understand crashes and rendering faults, and to see where players find the interface hard to use, the game can record short clips of the image it draws itself, at reduced resolution. It is off by default and is only ever enabled for a small number of Android devices during a specific investigation.

Firebase. The Google Play version includes two services from Google. Google Analytics for Firebase collects app usage events, including purchase events, and assigns its own installation identifier; it receives your device's advertising ID and your IP address, from which an approximate location can be estimated, and we use it, among other things, to measure our advertising campaigns in Google Ads. We pass it the same device identifier described above, along with your platform and device performance tier. Firebase Crashlytics receives a report when the game crashes: what failed, your device model, operating system and graphics processor, the device identifier, and a log of the last game events before the crash.

Server logs. Our API and game servers record IP addresses in their access logs. The logs rotate and are kept only for a limited time, to keep the service running and to protect it against abuse.

3. Voice input

The in-game creator lets you dictate a request instead of typing it. This is optional: you can always type the request instead.

• The game asks for microphone permission only when you tap the microphone button, and records only from that tap until you tap again — no longer than 60 seconds per message.
• The recording is sent over an encrypted connection (HTTPS) to our servers and linked to your game account, so that the result comes back to you.
• It is held temporarily in our file storage and turned into text by a speech-recognition model (Whisper) that runs on our own server. No third-party speech-recognition service receives it.
• The audio file is deleted as soon as the text is ready, or after the last unsuccessful attempt to recognise it.
• The recognised text becomes your message to the creator, just as if you had typed it, and is kept with your account until the account is deleted.

We use voice recordings only to turn your request into text. We do not use them for advertising, do not sell them or share them with third parties, and do not use your voice to identify you.

You can withdraw microphone permission at any time in your device's system settings; you can still type requests to the creator.

4. The AI creator and moderation

The in-game creator makes creatures, vehicles, buildings and blocks from your requests with the help of AI models run by third-party providers, who process the data on our behalf. We currently use models from Anthropic (Claude); for some tasks we may use models from Google (Gemini) instead. They receive:

• the text of your request — typed, or recognised from your voice — and your follow-up messages about the same creation, to generate it and, before work starts, to check the request against our community rules;
• images of the finished creation and what kind of object it is, so that an AI moderator can check it before it is published to the shared catalogue. People on our team review what the AI moderator rejects or is unsure about.

Your voice is not sent to them: recordings are turned into text on our own server, as described in the «Voice input» section, and only that text goes on. The providers are not given your email address or your sign-in details. They handle what they receive under their own terms and privacy policies — so please do not put personal information in a request, yours or anyone else’s: the creator does not need it.

Requests and the conversation about a creation are kept with that creation on our servers, so that it can be changed later and moderation decisions can be explained and reviewed. If you delete a creation, they are deleted with it. If you delete your account, unpublished creations are deleted too, and published ones stay in the catalogue without the link to you, as described on the account deletion page.

5. Reports and blocking

When you report a creation or a player in the game, we store who sent the report, what it is about (the creation, or the player’s nickname), the reason you chose, your comment if you wrote one, and the game version and language. Moderators receive the report through a private channel in the Telegram messenger and use it only to review it and keep the game safe. We do not tell the reported player who reported them.

If other players report you, the reports and our decision are kept so that repeated breaches can be recognised. If your account is suspended, we store the date the suspension ends.

When you block a player, we store that you blocked them, so that their creations are hidden from you and they cannot join your rooms or send you friend requests. Unblocking them in Settings → Help → Blocked players deletes that record.

If you delete your account, blocks are deleted with it; reports you sent are kept for moderation with your name removed from them.

6. This website

The site sets no cookies, runs no analytics and no advertising trackers, and writes nothing to your device. Our hosting provider keeps ordinary server logs for a short period to protect against abuse. Fonts are served by Google Fonts, which receives the request needed to deliver them.

7. What we do not do

• We never ask for access to your device’s location (GPS or the location permission), camera, photos, contacts or files. An approximate location is only estimated from your IP address, as described in the «What the game collects» and «Advertising» sections.
• We do not use your worlds, your voice requests or your nickname to target advertising.
• We do not sell your personal information.

8. Advertising

The game may show ads supplied by Google AdMob. To select, show and measure ads and to protect against fraud, AdMob receives your device's advertising ID, your IP address — from which an approximate location, such as the city or region, can be estimated — technical information about the device, and how you interacted with the ad. Google's use of that data is governed by Google's own privacy policy.

AdMob works as a mediation platform: an ad request may be passed on to one of its partner networks — Unity Ads, Mintegral, Pangle, DT Exchange (Digital Turbine), Liftoff Monetize (Vungle), InMobi or AppLovin. Some of these networks come with software from the wider group they belong to — Pangle, for example, is operated by ByteDance, the company behind TikTok. The network that serves the ad receives the same kind of data for that request as AdMob does and processes it under its own privacy policy; where we ask for your choice about personalised advertising, that choice is passed on to these networks too.

In the European Economic Area, the United Kingdom and Switzerland we ask for your choice about personalised advertising before any ad is shown, and you can change that choice at any time in the game's settings. Everywhere else you can limit ad personalisation, and reset or delete the advertising ID, in your device settings.

Ads are chosen from what the advertising service knows about the device, not from what you build: we do not pass your worlds, your voice requests or your nickname to the advertising partner.

9. Purchases

The game may offer paid items, including the TearCraft Premium subscription. The payment itself is handled entirely by Apple or Google: we never see your card number, your billing address or any other payment detail, and our servers do not keep a record of your purchases. Whether a subscription is active is checked on your device, through the store. When you buy something, the game records the product, its price and the currency in our analytics and in Google Analytics for Firebase; Unity, whose purchasing library (Unity IAP) the game uses, receives these purchase events too. A subscription renews automatically through your store account until you cancel it in the store.

Refunds follow the rules of the store you bought in. Start there — we cannot reverse a charge made by a store.

10. Why we are allowed to process this

Where the GDPR or UK GDPR applies, we rely on our legitimate interest in keeping the game working and free of faults for diagnostics and analytics; on performing our agreement with you for accounts, published content and the creator; on our legitimate interest in keeping players — many of them teenagers — safe, for moderation, reports and blocks; and on your consent where consent is required, including for voice input, which never starts on its own.

11. Who else receives data

We share data only with providers who run part of the service for us, and only as far as they need it:

• Apple and Google, as the stores that distribute the game;
• Google — for sign-in and, in the Google Play version, for Google Analytics for Firebase and Firebase Crashlytics;
• Google — as the advertising partner supplying ads through AdMob — together with AdMob’s mediation networks: Unity Ads, Mintegral, Pangle, DT Exchange, Liftoff Monetize, InMobi and AppLovin;
• Unity — for purchase events, through the Unity IAP purchasing library;
• our hosting and file storage providers;
• Anthropic and, for some tasks, Google — as AI providers that generate creations and help moderate them;
• Telegram — the messenger through which our moderators receive reports.

We also disclose data where the law requires it. We do not sell it to anyone.

12. Where the data is stored

Our main servers are in the European Union, in Frankfurt, Germany. To give players in some regions a faster connection, some multiplayer game sessions may be hosted on servers outside the European Union, closer to those players; such a server processes what the game session needs, such as your nickname, what you do in the room and your IP address. Encrypted backups of our database are kept with a hosting provider outside the European Union. Some of the providers listed above, including the AI providers, are based in the United States. Where data is transferred outside the EEA or the United Kingdom — including to countries for which the European Commission has not adopted an adequacy decision — we use the safeguards the law provides for such transfers, such as the European Commission’s standard contractual clauses, or another lawful basis for the transfer.

13. How long we keep it

• Analytics events — two years, then deleted automatically.
• Account data — until you ask us to delete the account.
• Published worlds and creations — until you or we remove them.
• Voice recordings — deleted as soon as they have been turned into text; the recognised text is kept with your account.
• Creation requests and the conversation about a creation — for as long as the creation exists.
• Reports — for as long as we need them for moderation and to recognise repeated breaches.
• Blocks — until you unblock the player or delete your account.
• Diagnostic captures — for as long as we need them to investigate the problem, then deleted; we aim to keep them no longer than 60 days.
• Purchase events — as part of analytics events; the store keeps its own record of your purchases.
• Server logs with IP addresses — for a limited time, as the logs rotate.
• Encrypted database backups — 30 days, rolling.

14. Your rights

You can ask us to show you what we hold about you, correct it, delete it, or send you a copy in a portable form. You can also object to the processing we base on legitimate interest, including analytics — write to us and we will stop it for you.

Write to privacy@isaevlabs.com. If you have not linked a Google account, include the nickname shown in the game under Profile, otherwise we cannot find your data.

Deleting an account has its own page, with the full list of what is removed, what stays and how long it takes: /delete-account.

If you are in the EEA or the United Kingdom you may complain to your national data protection authority.

If you are a California resident, you have the rights described in the CCPA and CPRA, including the right to know and the right to delete. We do not sell personal information for money. Showing personalised ads counts as 'sharing' under those laws: you can stop it by declining personalised advertising in the game's settings, or by writing to us.

15. Children

TearCraft is intended for players aged 13 and over. It is not directed at children, and we do not knowingly collect personal information from anyone under 13. If you believe a child has given us personal information, write to privacy@isaevlabs.com and we will delete it.

16. Security

Traffic between the game and our servers is encrypted in transit. Access to stored data is limited to the people who need it to run the service, and backups are encrypted. No system is completely secure, and we do not claim otherwise.

17. Changes

When this policy changes we publish the new version here with a new effective date. If a change materially affects what we collect or why, we will say so in the game as well.

18. Contact

Isaev LLC, 30 N Gould St, Ste R, Sheridan, WY 82801, United States. privacy@isaevlabs.com, +1 307 357 5613.