// VinciTu is an offline sliding-tile puzzle game in which you restore the Seal of Nine Fortunes one nudged shard at a time.
[01] Information collected // inputs
None. VinciTu has no account system, no sign-in and no registration. You are never asked for a name, an email address, a phone number, an advertising identifier or any other identifier. The keeper name and sigil you may set in the Chronicle are free text you invent for yourself — they are written to your device’s local storage and are never transmitted anywhere.
[02] Local storage // on-device
Kept in OS-level local storage on your device, never uploaded:
- Seal records — for each level you have cleared: the star rating, your best move count, the best time left on the incense, and how many times you have cleared it.
- Endowment tiers — the tier you have reached on each of the four permanent upgrade tracks.
- Laurels — which of the thirteen accolades you have earned, and the date each was earned.
- Keeper record — the keeper name, sigil and founding date you chose, your Ember balance, and lifetime Embers earned and spent.
- Daily offering state — the date you last claimed the daily offering and how many you have claimed, so the offering resets once per day.
- A suspended level — the board state of a level you left mid-run, so you can resume it.
- Settings — your ward marks, calm motion, show moves and confirm spend toggles, plus a single first-launch flag that records whether you have seen the intro.
Uninstalling the app deletes every byte.
[03] Permissions // runtime
VinciTu requests no runtime permissions. It does not ask for the camera, microphone, location, contacts, photos, storage or notifications, and it will never prompt you to grant any. The Android manifest declares the standard INTERNET permission, which ships in the default Flutter application template; the game contains no networking code and makes no use of it. The iOS build declares no usage-description keys at all.
[04] Network // egress
VinciTu is fully offline. It contains no HTTP client, no socket code and no backend, so it contacts no servers — not ours, not anyone’s. It plays identically on a plane, in a tunnel or with the radio switched off. The one outward-facing action in the app is the share button in the Chronicle, which hands a short summary of your own progress to your device’s system share sheet. That only happens when you tap it, and you choose the destination; the app never shares anything on its own.
[05] Third parties // vendors
No analytics SDK, no advertising SDK, no crash reporter and no attribution or A/B-testing service is integrated — there is no Firebase, no AdMob, no Crashlytics, no Sentry and no equivalent. The app is built on Flutter with a small set of open-source packages (flutter_riverpod, sqflite, shared_preferences, gap, collection, intl, flutter_animate and share_plus). These are local libraries for state, storage, formatting and animation; none of them transmit data off the device. There are also no in-app purchases and no billing library.
[06] Children // coppa/gdpr-k
VinciTu is suitable for all ages. Because it collects nothing from anyone, it collects nothing from children — there is no personal information for a child to disclose, no profile to build and no content shared with third parties. This holds regardless of the user’s age, so the app does not need to, and does not, verify age. It contains no advertising, no in-app purchases, no chat and no user-generated content visible to anyone else.
[07] Your rights // you
Everything VinciTu stores is on your own device and under your control. You can erase all of it at any time by uninstalling the app, or by clearing the app’s data from your device settings (Settings › Apps › VinciTu › Storage › Clear data). There is no server-side copy, no backup we hold and no account to close. We cannot access, export, correct or delete your data on your behalf for the simple reason that we never receive it — so there is no request to make. If you have a question about any of this, write to us at the address below.
[08] Changes // changelog
If this policy changes, the updated field at the top of this page will be revised. Material changes are also noted in the app's release notes.