Crumb

Privacy Policy

Last updated: 12 July 2026

Crumb is a photo-first food diary. You snap the meal in front of you, score it out of ten, and it pins where you were standing — building a personal, mostly-private atlas of everywhere you have eaten. This policy explains exactly what data Crumb handles, where it lives, and who can see it.

The short version. Crumb has no ads, no third-party analytics, no tracking, and no data sales. Crumb runs in one of two modes. In Local mode (no account) everything you create stays on your device. If you choose to create an optional account, your data syncs to our backend so it can be backed up and shared with friends you approve. In both modes, when Crumb looks up nearby restaurants it sends your location to the OpenStreetMap Overpass API.

1. Who we are

Crumb ("Crumb", "we", "us") is an iOS application. If you have any question about this policy or your data, contact us at greg@willownook.co.uk.

2. Two modes: Local and Account

Crumb works fully without an account. Understanding which mode you are in tells you where your data lives.

Local mode The default. You have not signed in. All of your data is stored only on your device in the app's local storage. We do not receive it, and it is not backed up by us. If you delete the app, this data is gone.
Account mode Optional. You sign in with your email address using a one-time code (no passwords). Your crumbs, photos, and profile then sync to our backend (hosted on Supabase) so they persist and can be shared with friends you approve.

3. What data Crumb handles

Data	Why	Where it lives
Precise location (while using the app)	To pin each meal where you were standing and to find restaurants near you. Your coordinates are sent to the OpenStreetMap Overpass API to look up nearby venues.	Local The pin is stored on-device. Account The pin is stored in your account. In both modes, the coordinates go to Overpass for the venue lookup.
Photos (camera & photo library)	Your meal photos and optional menu photos.	Local On your device only. Account Uploaded to a private storage bucket in our backend.
Your crumb content: dish name, score, note, tags, price, place, reactions, and to-try lists	This is the diary itself — the entries you create.	Local On your device only. Account Stored in your account.
Account details: email address, @handle, profile name, and profile emoji	Account mode only. Your email is used solely to send the one-time sign-in code and identify your account. Your handle, name, and emoji identify you to friends you approve.	Account Stored in our backend. Not collected at all in Local mode.

4. Location and the OpenStreetMap Overpass API

Crumb requests location access only while you are using the app ("when in use"). We never track your location in the background. When you capture a meal, Crumb sends the coordinates to the free OpenStreetMap Overpass API to fetch a list of nearby restaurants, cafés, and shops so you can pick where you are. Crumb identifies itself to Overpass but does not send your identity, email, handle, or any account information with that request. Overpass is operated by third parties under the OpenStreetMap project; venue data is © OpenStreetMap contributors (ODbL). You can decline location permission and enter the place manually instead.

5. Who can see your crumbs

Local mode Nobody but you. Your data never leaves your device.
Account mode Your crumbs are visible to you and to mutual friends you have accepted. Crumb is not a public feed — there are no public profiles and no followers. You find friends by searching their exact @handle and sending a request they must accept. A pending request only reveals your name and handle, never your content.
Blocking and reporting. You can report a user or an individual crumb for review, and you can block another user. A block severs the friendship in both directions and makes each of you invisible to the other. These rules are enforced on the server, not just in the app.

6. What we do not do

No advertising and no ad networks.
No third-party analytics or tracking SDKs.
No tracking you across other apps or websites.
No selling, renting, or sharing your data with data brokers.
No uploading your contacts or address book.

We use your data only to run the app for you.

7. Service providers

In Account mode, our backend is hosted on Supabase, which stores your account data, crumbs, and photos on our behalf and sends your sign-in emails. Supabase acts as our data processor. In both modes, restaurant lookups are served by the OpenStreetMap Overpass API as described above. We do not use any other third parties to process your data.

8. Retention and deletion

Local mode Your data lives on your device until you delete individual crumbs, reset the app, or uninstall it.
Account mode Your data is kept while your account exists. You can delete your account from Profile → settings → Delete my account. This permanently removes your profile, crumbs, and photos from our backend. You can also sign out on a single device without deleting anything.

9. Children

Crumb is not directed to children under 13, and we do not knowingly collect data from them.

10. Your rights

Depending on where you live (for example under UK GDPR), you may have the right to access, correct, export, or delete your personal data. In Account mode you can delete everything yourself using the in-app account deletion. For any other request, contact us at greg@willownook.co.uk.

11. Changes to this policy

If we change this policy we will update the date at the top and, where appropriate, notify you in the app.

12. Contact

Questions about this policy or your data? Email us at greg@willownook.co.uk.