// Sportaza is a meal planner and grocery-list generator: you drop recipes onto a weekly board and the app merges the ingredients into one aisle-ordered shopping list while keeping track of what is already in your larder.
[01] Information collected // inputs
None. We run no servers, so there is nothing for us to collect. The app never asks for your name, email address, phone number, contacts, location or payment details, and it has no code capable of sending them anywhere. The display name you can set on the chef record screen is optional, is stored only on your device, and is never transmitted.
[02] Local storage // on-device
Kept in OS-level local storage on your device, never uploaded:
- Planned meals — which recipe you assigned to which day and meal slot, and the number of servings.
- Grocery list lines — item name, quantity, unit, aisle, whether it is ticked off, and whether you added it by hand.
- Larder stock — item name, quantity, unit, aisle and an optional use-by date.
- Cook log — which recipe you marked as cooked, when, and for how many servings. The statistics, streak and badges on the chef record screen are calculated from this.
- Favourites — the recipes you have starred.
- Preferences — default servings, week start day, metric/imperial units, whether to subtract the larder, whether to show a snack slot, and whether the first-run tour has been completed.
- Chef profile — the display name and avatar mark you picked.
It all lives in a single local SQLite database (meal_mapper.db) inside the app's own sandboxed storage, which no other app can read. The 25 recipes shipped with the app are compiled into the binary — they are not downloaded, and we cannot change them after installation.
Uninstalling the app deletes every byte.
[03] Permissions // runtime
On Android the manifest declares INTERNET, and the app does not use it — Sportaza contains no networking code and issues no network requests. The permission is inherited from the standard Flutter project template and is listed here for completeness rather than because anything depends on it. The iOS build requests no runtime permissions at all: no camera, microphone, photo library, contacts, location, calendar, notifications or health data.
[04] Network // egress
Sportaza is fully offline. It has no HTTP client, no WebView, no socket code and no third-party network SDK. Planning, list building, larder tracking, statistics and badges all work with the device in airplane mode.
[05] Third parties // vendors
No analytics, advertising, attribution, crash-reporting or tracking service is integrated. The app is built with Flutter and uses these open-source packages purely for on-device functionality: flutter_riverpod (state management), sqflite and path (local database), fl_chart (the statistics chart), confetti (a celebration animation), share_plus (the system share sheet) and cupertino_icons. None of them contact a server on the app's behalf. The Share buttons on the recipe and chef record screens hand a short block of plain text to your operating system's standard share sheet — nothing is sent anywhere until you pick a destination app yourself, and that app's own privacy policy then governs the text you sent.
[06] Children // coppa/gdpr-k
Sportaza collects no personal information from anyone, including children under 13 (COPPA) or under 16 (GDPR-K). With no data collection, no profiling and no advertising, the app needs no parental consent mechanism and is safe for all ages.
[07] Your rights // you
Everything is on your device and under your direct control. Access: all stored data is visible in the app itself, on the Plan, Shop, Larder and Chef record screens. Correction: every entry can be edited or removed from the screen it appears on. Deletion: uninstalling Sportaza permanently removes the database and its contents, and because nothing is ever transmitted there is no copy elsewhere to delete. Since we never receive your data we cannot access, export or delete it on your behalf, and there is no account to close.
[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.