Privacy Policy

Who this policy covers

This policy explains how the mobile game Weft (package identifier com.weft.game, published for Android on Google Play and for iOS on the App Store) handles information. Weft is made and published by an independent developer under the name Weft. In this document, “we” and “the game” both mean that.

It does not cover the storefronts themselves. Google and Apple collect their own data when you browse, download, or pay for an app; that is governed by their policies, not this one.

What we collect

Nothing. Weft has no user accounts of its own, no sign-up, no login, no forms, and no way to send a message from inside the game. We do not collect your name, email address, phone number, contacts, photos, location, advertising identifier, or device identifier.

The game has no social-network integration. There is no server behind Weft: we operate none, so there is nowhere for us to receive or keep anything.

Four components inside the game do send data, and none of them sends it to us: the advertising SDK (to Google), the analytics SDK (to Google), Google Play Billing (to Google), and the Unity in-app purchasing library (to Unity). Each has its own section below.

What the game stores on your device

To remember where you left off, Weft saves a small amount of data in the app’s own private storage on your device:

• Your progress — the number of the next level, and whether you have finished the tutorial.
• Your preference — the interface language you selected, if you changed it from the default.

This data stays with you

Both items above are written to storage that belongs to the application on your own device. They are never uploaded, never transmitted, and never shared — not with us and not with anyone else. They contain no identifiers and nothing that describes you as a person.

You can erase all of it at any time. Uninstalling Weft removes it completely; clearing the app’s data in your system settings does the same without uninstalling. The game also has a “Reset progress” button in its settings screen, which clears the saved progress.

Language detection

On first launch, Weft reads the language your device is already set to, so it can show the interface in English or Ukrainian instead of asking you. That reading happens entirely on the device and the result is not sent anywhere.

Permissions

Weft requests no runtime permissions: it never asks for your camera, microphone, location, contacts, files, or notifications, because it does not use any of them.

The Android build declares the standard INTERNET permission, together with ACCESS_NETWORK_STATE, the advertising identifier permission com.google.android.gms.permission.AD_ID and the Privacy Sandbox permissions ACCESS_ADSERVICES_AD_ID, ACCESS_ADSERVICES_ATTRIBUTION and ACCESS_ADSERVICES_TOPICS. None of them is requested from you at runtime, and they are used for three things only: the advertising, the analytics and the purchases described below. Everything else, including your progress through the levels, works entirely offline.

Advertising, and what Google receives

Weft shows advertising supplied by Google AdMob in three forms: a banner along the bottom of the battle screen, a full-screen ad shown occasionally after a won battle, and rewarded videos that you choose to watch for an in-game bonus. No ad interrupts a battle, and none must be watched to continue playing. A one-time purchase described below removes the banner and the full-screen ads for good.

Where the law requires it, the game asks for your consent before showing personalised ads, using Google’s consent form; you can change that choice later from the game’s settings screen.

The advertising is Google’s, not ours. We do not choose which ad you see, we receive no data about you from it, and no information about you passes through any system of ours — we operate none.

To select and measure ads, and to keep advertising honest, the Google Mobile Ads SDK inside the game may collect and send to Google your device’s advertising identifier and app set ID (and, where applicable, identifiers of accounts signed in on the device), technical information about the device and the app, your IP address, from which an approximate location may be estimated, information about how you interacted with an ad — app launches, taps, video views — and diagnostic figures about how the app itself runs — how long it takes to start, how often it hangs, how much energy it uses. Google encrypts this data in transit and uses it for advertising, for analytics, and to detect fraud. On Android the game therefore declares the com.google.android.gms.permission.AD_ID permission, and the Privacy Sandbox permissions the SDK brings with it. What Google does with all of this is covered by the Google Privacy & Terms — how Google uses information from sites or apps that use our services.

You can limit this yourself, on the device and without us: Android has Settings → Privacy → Ads, where the advertising ID can be reset or deleted entirely, and iOS has Settings → Privacy & Security → Tracking. Deleting the identifier does not remove the banner; it removes the personalisation.

Analytics, and what Google receives

To learn where players get stuck or stop playing, Weft uses Google Analytics for Firebase. The game reports when a level starts and how it ends — won, lost, or abandoned — with the level number and how long it took, which features have been unlocked, and whether a rewarded video was watched. None of these records carries your name, an account, or anything you typed; there is nothing to type.

Alongside our events the Analytics SDK collects, according to Google’s own disclosure: a random app-instance identifier it assigns to this installation, your device’s advertising identifier, your IP address in masked form (used only for a coarse location), in-app purchase events, and app lifecycle events such as sessions and screen views. The data is encrypted in transit and stored by Google; we see it only as aggregated reports and keep no copy of our own. What Google does with it is covered by the Google Privacy & Terms — how Google uses information from sites or apps that use our services.

Where the law requires consent, analytics honours the same consent form as the advertising, and no analytics data is collected before you have answered it. The advertising identifier can be reset or deleted in your device settings, as described above; that also breaks the link between past and future analytics records.

Purchases

Weft is free to play in full. It offers optional in-app purchases — packs of crystals, a starter bundle, and a one-time “remove ads” option — sold through Google Play Billing on Android.

The payment is handled entirely by Google. We never receive your card details, your name, your email, or your billing address; Google’s own privacy policy governs that. What the game receives from Google Play is a purchase receipt — the product bought and an order token — which it checks on your device and then uses to deliver what you bought. The receipt is kept in the app’s private storage so that the purchase can be restored; it is not sent to any server of ours, because we operate none.

Purchases are tied to the Google account that made them. If you reinstall the game or change phones, the “remove ads” purchase can be restored through Google Play on the same account. Refunds are handled by Google Play under its own rules.

The purchase flow inside the game is run by Unity In-App Purchasing, a library made by Unity Technologies, the maker of the engine Weft is built on. According to Unity’s own disclosure, that library collects and sends to Unity: an installation identifier and other device identifiers, device information, session identifiers, your country, your purchase history in the game, and crash and diagnostic data about the app. It does not collect your name or email, and Weft passes it no account of yours. Unity uses this to operate the purchasing service and for its own analytics; the data is encrypted in transit and is not shared by Unity with third parties. Unity’s handling of it is described in the Unity Privacy Policy.

Children

Weft is not directed to children. Its target age group on Google Play is 13 and over. We do not knowingly collect personal information from anyone, children included — there is no mechanism in the game by which such information could be collected.

The advertising described above is served by Google AdMob under the settings we have chosen for this app in Google’s console. If you believe a child has used the game on your device, resetting or deleting the device’s advertising identifier — as described in that section — removes the history the personalisation was built on.

Your rights

Privacy laws such as the GDPR (European Economic Area, United Kingdom, Switzerland) and the CCPA (California) give you rights to access, correct, export, or delete the personal data a company holds about you.

We hold none. There is no database, no account, and no copy of anything from your device on any server of ours, so there is nothing for us to hand over, correct, or erase on request — and nothing that we could transfer to another country or sell. Your progress lives on your device and is under your control; deleting it is described in the section above.

There are four exceptions, and none of them is held by us: whatever the advertising SDK and the analytics SDK send to Google, the record of your purchases on Google Play, and what the Unity purchasing library sends to Unity. For the first, the advertising identifier can be reset or deleted in your device settings; the second is your Google Play order history, managed with Google; for the third, Unity states that its purchasing library offers no in-app way to request deletion — requests go to Unity under the Unity Privacy Policy. Rights over any of these are exercised with Google or Unity directly. You are welcome to write to us at the address below to confirm any of this.

Changes to this policy

If the game changes in a way that affects this document, we will update this page and move the effective date at the top. The page you are reading is always the current version; there is no separate archive of older ones.

Contact

Questions about this policy, or about anything Weft does with data, go to [email protected]. One inbox, read by the person who builds the game.