Mukaase privacy policy
Last updated
The short version
Mukaase runs on your phone. Your pantry — every item, date, quantity, receipt line and photo — is stored on your device and, if you are signed in to iCloud, in your own iCloud account. We have no server it could be copied to, and no way to read it.
What we do receive is small and separate from your pantry: whether you bought a plan, which screens you used, and a report when the app crashes. None of it carries the name of a single thing in your kitchen.
This page says exactly what that means, and where it stops.
Who we are
Mukaase is made by Floresys LLC, a New York limited liability company, registered office c/o Republic Registered Agent Services Inc., 54 State Street, Ste 804, Albany, NY 12207, USA. You can reach us at support@floresys.com about anything on this page.
We are responsible for the data described under *What we receive*. We are not a holder of your pantry data at all, for the reason in the next section.
Your pantry is yours, and we never hold it
Everything you put into Mukaase — item names, quantities, dates, places, your shopping list, the lines read off a receipt, the cropped photo Mukaase keeps as evidence of a printed date, and anything you added by speaking — is written to your device.
If you are signed in to iCloud, that data also syncs to your own iCloud account, in Apple's private CloudKit database. That is your storage, not ours. We hold no key to it, we operate no console that reads it, and we keep no copy. Apple's handling of your iCloud account is covered by Apple's privacy policy, not by this one.
If you join somebody else's pantry. A shared pantry is the one part of Mukaase that is not private to you. It lives in the iCloud account of whoever started it, and everybody in it can read and change what is there. If you accept an invitation to one, the name on your Apple account and everything you add to that pantry become visible to the other people in it — in their iCloud, still not in ours. This version of Mukaase has no button for inviting anybody, so you can be invited but cannot invite, and most people will never be in a shared pantry at all.
Mukaase runs no server of its own. There is no Mukaase account, no email address to register, and no password.
What never leaves your phone
- Receipt photos. A receipt is read in memory and the image is discarded once the lines have been parsed. No receipt image is sent anywhere, and none is saved to disk.
- Camera frames. Barcodes and printed dates are read on the device by Apple's Vision framework.
- Your voice. When you add an item by speaking, the audio is transcribed on the device. No audio and no transcript is sent to us, and none is sent away for transcription.
- The date-evidence crop. The small photo of a printed date is stored with its item, on your device and in your iCloud, the same as the rest of your pantry. It never reaches us.
What we receive
Three companies process data for us. Each one gets a narrow slice, and together they are the whole of what we can see.
| Who | What they receive | Why | Where they process it |
|---|---|---|---|
| RevenueCat | Your purchases and whether a plan is active, and an anonymous app user ID that RevenueCat generates for your install | To unlock what you paid for, and to restore it on a new phone | United States (AWS) |
| PostHog | Product events — a fixed event name and a few fixed properties — and the same anonymous app user ID | To see which parts of the app people reach, and where they stop | United States (us.i.posthog.com) |
| Sentry | Crash reports, app hangs and performance data, and Sentry's own random installation ID | To find and fix the crashes you would otherwise just live with | United States (ingest.us.sentry.io) |
The identifiers. The main one is an anonymous app user ID that RevenueCat generates for your install, reused as PostHog's identifier so that a purchase and a usage funnel agree about which install they describe. It is not your Apple ID, not your iCloud account and not your name. Sentry keeps its own separate random installation ID, so that one install's crash reports can be grouped together.
Two device-level values also travel, and we would rather name them than let the paragraph above imply more than it should. Both are added by the SDKs themselves, not by Mukaase's own code. RevenueCat's SDK attaches your device's *vendor identifier* — Apple's per-developer device ID, which changes when you delete every app from the same developer — to its own API requests. Sentry attaches a one-way hash of that same identifier combined with your device model, which is how it tells one install's crash reports from another's.
No advertising identifier is involved anywhere. Mukaase does not read the IDFA, does not ask for tracking permission, and cannot be used to target you with advertising. Nothing above is combined with data from other companies' apps or websites.
What a product event contains. Each event is a fixed name from a fixed list — a paywall opened, a permission was granted, the first pantry was ready — plus at most a few properties from a fixed list of their own. Most are a fixed word or a true-or-false. Four are numbers, and we would rather name them than round them into the sentence above: how many lines a receipt turned out to have, how many items your first pantry ended up with, how long a receipt took to get into the pantry, and how long it took from allowing the camera to that first pantry being ready. Automatic screen capture, automatic tap capture and session replay are all switched off. No item name, no date, no place and no free text is ever sent as a property — nothing that says *what* is in your kitchen, only how much of it there was and how long something took.
Crash reports are stripped before they are sent. When something fails deep in the app, the error can quote the record it failed on — and in rare cases that record is a pantry item's name or a household member's name. Mukaase removes that detail on your phone before the report leaves it. What we get is what broke and where: the error's domain and code, and the stack trace.
We do not track you. No advertising, no ad networks, no data brokers. Nothing we collect is combined with data from other companies' apps or websites, and nothing is sold or shared for advertising. The app's privacy manifest declares no tracking and no tracking domains.
There is no analytics switch in this version. Mukaase offers no setting that turns the product events above off — we checked the whole app rather than assuming, and the only switches in it are one for reminders and two for whether an item has a best-before date. So the only ways to stop the events are to stop using Mukaase or to delete it. If that matters to you, write to us at support@floresys.com; we would rather be told than assume nobody minds.
How long they keep it. We set no retention period of our own, because none of this is ever on a machine of ours to delete. What the three companies publish about their own retention, read on 14 September 2026:
- RevenueCat keeps purchase records for as long as our account with them is open, and for six years after it closes. A deletion request is actioned when it is made. (<https://www.revenuecat.com/privacy-policy>;, *How long we keep your information*.)
- PostHog publishes no fixed period for product events. They are kept until the project or the person they belong to is deleted, and deletions of event data are processed in batches rather than instantly. (<https://posthog.com/docs/privacy/data-storage>;.)
- Sentry keeps error reports no longer than 90 days — 30 days on its entry plan, 90 on its paid ones. (<https://docs.sentry.io/security-legal-pii/security/data-retention-periods/>;.)
We would rather give you the vendors' published numbers than a period of our own that nothing enforces. Where a number above depends on which plan we are on, we have stated the longest it can be rather than the shortest.
When Mukaase talks to Open Food Facts
When you scan a barcode Mukaase has not seen before, it sends the barcode number to Open Food Facts over HTTPS to look up the product's name, brand, category and size. The request carries the barcode and an identifying line for the app (Mukaase/1.0 (support@floresys.com)), and nothing else — no identifier, no cookies, nothing about you or the rest of your pantry. The answer is kept on your phone for 30 days so the same barcode is not looked up twice.
Open Food Facts is an independent open-data project with its own privacy terms, and its product data is published under the Open Database License.
Permissions Mukaase asks for
- Camera — to read receipts, barcodes and printed dates.
- Microphone and speech recognition — to add items you say out loud. The transcription happens on the device.
- Notifications — for expiry reminders, which your phone schedules locally. Mukaase operates no server and sends no push messages of its own in this version.
Each is asked for at the point it is first needed. You can refuse any of them; the app keeps working, without the one feature that needed it.
What the App Store privacy labels say
Apple asks us to declare what the app collects, and the labels on Mukaase's App Store page are the answer. Seven categories are declared:
- Purchase History, User ID, Product Interaction, Other Usage Data — declared as *Data Linked to You*, because they travel with the anonymous app user ID above. We hold no name or email to link them to.
- Crash Data, Performance Data, Other Diagnostic Data — declared as *Data Not Linked to You*.
Every other category Apple lists — contact information, health, financial information, location, contacts, user content, browsing history, search history, and photos or videos — is declared not collected, and this page is written to mean the same thing.
Getting a copy of your data, and getting rid of it
A copy. Settings → Data → Export my data writes everything in your pantry to a JSON file and opens the system share sheet on it, so you can save it to Files or send it to yourself. The date-evidence photos are left out of that file; they stay on your phone.
Getting rid of it. Mukaase has a Delete everything button: open Our Home from the avatars at the top of your pantry, then Account, then Delete everything. It asks you to confirm, and then:
- Your pantry, your receipts and your date-evidence photos are removed from this phone.
- The copy in your own iCloud goes too. Mukaase deletes its own iCloud storage for this device outright, rather than leaving it for you to find in Settings. If you delete while signed out of iCloud, or while iCloud is restricted on this phone, Mukaase can't reach that copy; sign back in and choose Delete everything again to remove it.
- Any expiry reminders already queued or sitting on your lock screen are cleared, because a reminder names the item it is about.
- The app's own settings are wiped and Mukaase starts again as if you had just installed it.
What Delete everything does not reach, said plainly rather than left to be assumed:
- The purchase, product and crash records described under *What we receive*. Those sit with RevenueCat, PostHog and Sentry, not on your phone. Delete everything cuts this install loose from the identifiers they use and stops new records being made; it does not reach back and delete the ones already sent. For those, write to support@floresys.com — and please read the next paragraph first, because it affects what we can find.
- A shared pantry you joined rather than started. That pantry lives in the other person's iCloud account, not yours. Delete everything removes your copy of it and stops your phone syncing with it; what you had already added to it stays there for the people who did not just delete their own. If you want something you contributed taken out of somebody else's shared pantry, ask them — we cannot reach it either.
Two other routes exist and still work, whether or not you use the button:
- Deleting the app removes the copy on your phone.
- Your iCloud copy can also be removed from Settings → your name → iCloud → Manage Account Storage → Mukaase.
We usually cannot tell which records are yours. We hold no name, no email and no account for you. What our processors hold is keyed to an anonymous identifier your phone generated, which you have no way of reading and we have no way of connecting to you. If you have bought a plan, tell us and we can usually find that purchase from your App Store transaction. For product analytics and crash reports we generally cannot, and we will tell you so plainly rather than guess.
We are not being coy about this, and it is not a policy choice we could reverse on request: Mukaase has never asked you for a name, an email address or a password, and it never sends one. The identifier our processors hold is a random one your phone generated. The app does not show it to you anywhere, so there is no string you could quote at us to prove which records are yours. That is the cost of an app that asks you for nothing, and we would rather state it than imply a lookup we cannot perform.
If you are in the UK or the EEA
All three companies named under *What we receive* process in the United States, so data about your use of Mukaase leaves the UK and the EEA. Each of them publishes how it handles that transfer: PostHog is certified under the EU-U.S. Data Privacy Framework and its UK extension, and relies on the EU Standard Contractual Clauses where the framework does not apply (<https://posthog.com/privacy>;); Sentry's data processing addendum covers its transfers (<https://sentry.io/legal/dpa/>;); RevenueCat's does the same (<https://www.revenuecat.com/dpa>;). Read 14 September 2026.
There is no way to turn the product analytics off, and that is the honest state of this app today. We looked rather than assumed: Mukaase has three switches in the whole app — one for reminders and two for whether an item has a best-before date — and none of them concerns analytics. So the only ways to stop Mukaase sending product events are to stop using it or to delete it. If that is not good enough for you, write to support@floresys.com, say so, and we will both tell you what we can actually delete and count you among the people asking for a switch. We would rather record that than pretend a control exists.
Your rights, and where each one is actually answered. You have the rights the UK GDPR and the GDPR give you — access, correction, erasure, restriction, objection and portability. Three things shape how they work here:
- Your pantry is in your own iCloud rather than with us. Access and portability are answered by Settings → Data → Export my data; erasure by Delete everything, by removing the app, or through Apple. We cannot answer a request about data we have never held.
- What we do hold is the purchase, product and crash records above. Ask us and we will do what we can — bounded by *We usually cannot tell which records are yours*, in the previous section. That is a real limit, not a refusal dressed up as one.
- Objection to the analytics specifically runs into the missing switch. Say so anyway; it is the clearest signal we can be given that one is needed.
Children
Mukaase carries a 4+ rating on the App Store. That rating is Apple's judgement that nothing in the app is unsuitable for a young reader — no violence, no mature themes, no gambling, and nothing a user can post for strangers to see. It is not a statement that the app is *for* children, and we do not intend it as one.
Mukaase is a pantry app made for the person who does the shopping. It is not directed to children, we do not market it to them, and we do not knowingly collect data from them. We also do not ask anybody their age, because we ask for no personal details at all — so if you are a parent whose child has been using Mukaase and you want what it sent removed, write to support@floresys.com and read *Getting a copy of your data, and getting rid of it* above, which explains honestly what we can and cannot find.
Changes to this page
When this policy changes, we update the page and the date at the top. We hold no email address for you, so this page is the only place a change appears. Please check it when you next think of it.
Contact
Floresys LLC, c/o Republic Registered Agent Services Inc., 54 State Street, Ste 804, Albany, NY 12207, USA