Last updated: 14 September 2026
Morsu is a cook-along app. It shows you a recipe one step at a time, with a picture and a voice reading each step aloud, so you can cook without stopping to read.
This policy explains what we hold, why, and what you can do about it. It was written by going through what the app actually stores rather than from a template.
Morsu is operated by Melvin Chau, 5432 Geary Blvd, Unit #547, San Francisco, CA 94121, United States. For anything in this policy, write to contactmorsu@gmail.com.
Your email address, so you can sign in and recover your account. If you sign in with Google or Apple we receive your email from them and never see a password.
A username, a display name, and which chef avatar you picked.
Photographs of food you have cooked, if you take them, along with any note or rating you leave on that cook.
Your cooking history — which recipes you started, which step you reached, whether you finished, and roughly how long it took. This is what lets you pick a recipe back up where you left off.
Progress — experience points and achievements.
Product events, like “cook started” or “recipe saved”, written to our own database so we can see which parts of the app work and which do not. These are tied to your account.
Crash and error diagnostics, when something in the app fails: the type of error, a message with personal details stripped out, and the technical trace showing where it happened. These are tied to your account, and they are on by default. You can turn them off at any time in Settings, under Diagnostics, and nothing further is sent from that moment.
We hold these for the same reason as product events: an error nobody reports is an error nobody fixes. They are never sold, never shared, and never used to advertise to you.
This is first-party only. There is no Google Analytics, no Firebase Analytics, no advertising SDK and no third-party tracker anywhere in Morsu. Our own database is the only place any of it goes.
We do not collect your location, contacts, calendar, or any health data. We do not track you across other apps or websites, we do not build advertising profiles, and we do not sell or rent personal information.
Morsu does not ask for your date of birth or your age. By creating an account you confirm that you are 13 or older.
It is used only for the in-app voice commands — “Chef, next step” — only while a cook-along is open, and only if you grant permission.
Your speech may be sent to Apple’s speech recognition service to be turned into text, so that the app can tell “Chef, next step” from anything else you say in your kitchen. The app first asks your phone to recognise speech on the device, and only falls back to Apple’s service when the phone cannot. Apple handles that recognition under its own privacy policy.
Morsu never records or stores audio. We receive the recognised words, act on the ones that are commands, and keep nothing.
| What | Why |
|---|---|
| So you can sign in, and recover the account if you forget | |
| Username, display name, avatar | So the app knows what to call you |
| Saved recipes | So they are there next time |
| Cooking history | To resume a recipe, and to show what you have made |
| Photos and notes | Because you chose to keep them |
| Product events | To find which parts of the app are failing people |
| Crash diagnostics | To find and fix what breaks, without waiting for someone to report it |
Photographs are optional, and we rely on your choosing to use them. The rest is what running the service requires.
Supabase hosts our database and handles sign-in. Cloudflare serves the recipe pictures and the narration audio. Google and Apple are involved only if you use them to sign in, or when you subscribe.
That is the entire list. Nobody else receives your information, and nobody pays us for access to it.
We would disclose information if the law genuinely required it, and we would tell you whenever we are permitted to.
Morsu Premium is billed by Apple, not by us. We never see your card details — Apple handles payment, tells us whether your subscription is active, and pays us. What we store is which plan you are on and when it renews or expires.
Apple charges you when you subscribe and again at each renewal until you cancel. You can cancel any time in your device’s subscription settings, and you keep access until the period you have paid for runs out.
For as long as your account exists.
Delete your account at Settings → Danger zone → Delete account. That removes your profile, your saved recipes, your cooking history, your photographs, your progress, and every report you have filed.
Deletion is permanent and we cannot undo it. Backups are overwritten on a rolling basis and are fully cleared within 30 days.
See what we hold. Ask at contactmorsu@gmail.com and we will send it to you.
Correct it. Most of it is editable in the app. Anything else, write to us.
Delete it. Settings → Danger zone → Delete account.
Turn things off. Photographs are optional. Microphone permission can be revoked in your phone’s settings and the app carries on working without it — you can step through the whole recipe by tapping.
If you are in the UK, the EU, California or another place with data protection law, you may also have rights to object, to restrict how we use your information, to receive a copy in a portable form, and to complain to your regulator. Write to us and we will help. We do not charge for this and we will not treat you differently for asking.
Morsu is for people aged 13 and over. By creating an account you confirm that you are 13 or older. No one younger may hold an account.
Morsu is deliberately built to be followed without reading, and children can and do cook. We think that is a good thing — with an adult. A younger child should be cooking alongside a parent or guardian, on the adult’s account. Hobs, ovens, knives and hot oil are not things to leave a child alone with, whatever an app makes easy.
If we learn that we hold information from a child under 13 we delete it. If you believe your child has created an account, write to contactmorsu@gmail.com and we will remove it.
Passwords are hashed by Supabase and are never visible to us. Everything travels encrypted. Database access is restricted per user by row-level security, so your records can only be reached by you — this is enforced by the database itself rather than by the app asking nicely.
No system is perfectly secure. If a breach affects you we will tell you, and the relevant regulator, within the time the law requires.
Our database and file storage are hosted in the United States. If you are outside the United States, your information is transferred there and held under the transfer protections our providers offer.
Any change is posted here with the date at the top updated. If a change matters to you, we will tell you in the app before it takes effect.
Melvin Chau 5432 Geary Blvd, Unit #547, San Francisco, CA 94121, United States contactmorsu@gmail.com
Written from an inspection of what the application actually stores. It is accurate as of the date above, but it is not legal advice — have a lawyer read it before publishing, particularly the children’s section.