MeatLife uses no cookies. There are no tracking cookies, third-party cookies, conversion pixels, ad SDKs or advertising identifiers. The app uses local device storage only, to function — and none of it leaves your device.
| Technology | Purpose | Leaves the device? |
|---|---|---|
localStorage | Keep your records and preferences between sessions | No |
| Service Worker + Cache | Store the app's own files so it works offline | No |
None of this is sent to any server — ours or third-party. Details in the Privacy Policy.
The app registers a service worker that stores a copy of its own files (HTML, icons) in the browser cache. That is what lets MeatLife open without a connection. The cache holds application files only — never your records — and is replaced with every new published version.
The app loads no fonts, scripts, images or any resource from external servers: everything ships embedded. The only third-party interaction happens when you buy or restore a subscription, at which point Google Play Billing takes over — payment data never passes through the app.
In addition, when confirming a subscription the app sends our own server three pieces of information — package name, plan subscribed to, and the purchase code (purchaseToken) issued by Google. It is not a third party, and involves none of your records; it is described in full in section 5 of the Privacy Policy.
Any of these paths erases your records permanently. Since we keep no copy, they cannot be restored afterwards — export a backup first if you want to keep your history.