Napkin is a meal journal for iPhone and Android: you log the restaurants you eat at, keep a wishlist of ones to try, and share — if you choose — with small private groups called Tables. This page explains what data Napkin handles and what happens to it. The short version: your data exists to power your journal. No ads, no data sales, no tracking.
1.What we collect
- Account. Your email address and password, handled by Supabase Auth (passwords are stored hashed, so we never see them), or the name and email Apple or Google share when you sign in with them, plus your display name and, if you add one, a profile photo.
- Things you make. Restaurant logs — ratings, written notes, dates, tagged companions — the photos you attach, wishlist saves, lists, your Table memberships and activity, comments, and emoji reactions.
- Location — optional, foreground only. If you allow it, your coordinates are used to find restaurants near you and to sort saved spots by distance. They serve the search in front of you and nothing else: we don't record where you've been or build a location history. Restaurant coordinates come from Google, not from tracking you.
- Search text. What you type into restaurant search is sent to Google Places to return results.
- Imports. When you import a link, a saved video or a screenshot, Napkin reads it to find the restaurants in it. On iPhone, on-screen text and speech in a video are read on your device, and the video itself is never uploaded; Android imports links, shared text and screenshots, not videos. When you share a link to Napkin, the link itself reaches our server. To identify the restaurants, the public post or page you link (its caption, and the on-screen text and speech we read from it) is sent to Anthropic. Your own content (a screenshot you pick, the on-screen text and speech of a saved video, or text you paste) is sent to Anthropic only if you allow it: Napkin asks the first time. Google Maps links are never sent to Anthropic. You can withdraw that permission in Settings → privacy → Imports.
- Usage events. First-party events like "logged a meal", tied to your account id and stored in our own database. There is no third-party analytics SDK in the app.
- Crash and error reports. If the app crashes or hits an error, Sentry receives technical details (device model, system and app version, the error) so we can fix it. They are not linked to your account.
2.How we use it
- To run the app: your journal, feed, wishlist, Tables, and profile.
- To show what you make to the people you chose — Tablemates, tagged friends, or anyone, if your profile is public.
- To find restaurants: search text (and, for nearby search, transient coordinates) goes to Google Places. What you import goes to Anthropic: the public posts and pages you link, and your own screenshots, videos and pasted text only when you choose to import them, beside a line in the app saying an AI reads them.
- To keep user images safe: before an avatar or meal photo is published, a standardized JPEG copy is sent to Google Cloud Vision SafeSearch to check for adult, violent, or sexually suggestive content. Rejected images are not published.
- To see which features get used, via our own usage events.
- To email you about your account — password resets, replies when you write to us.
We never sell your data, never show ads, and never share your data with advertisers or data brokers.
3.What's public, what's private
- Profiles are public by default. Yours can be found and browsed unless you switch it off in Settings → Privacy.
- Your logs are public while your profile is. Anyone can then see the places you log, your ratings and any review you write, on your profile and elsewhere in Napkin, and a log with both a rating and a written review also appears on that restaurant's page. Make your profile private and your logs are visible only to you, the Tables you share them with, the friends you tag and the people you share a supper with.
Tables are never public. A Table has no public page, never appears in search, and only its members see its feed. A log you share to a Table still shows on your profile while your profile is public, without saying which Table.
4.Third-party services
A small set of providers runs Napkin. Each gets only what its job requires, and none of them get data for advertising.
| Service | Purpose | Data shared |
|---|
| Supabase | Database, sign-in, and photo storage. Hosted in EU-West. | Account data and the content you create. |
| Google Places | Restaurant search and restaurant details. | Your search text; transient coordinates for nearby search. |
| Google Cloud Vision | Safety-checks avatars and meal photos before publication. | The standardized JPEG being checked. Google says online Vision images are processed in memory, not persisted to disk, not used to train Cloud Vision, and not shared publicly or with another third party. |
| Anthropic | Identifies the restaurants in what you import: the public posts and pages you link, and your own screenshots, videos and pasted text only when you choose to import them, beside a line in the app saying an AI reads them. | A post's caption, the on-screen text and speech read on your device, the screenshot you picked, or the text you pasted. Never your name, email or account, and never the video. Under Anthropic's commercial terms this data is not used to train its models. |
| Sentry | Crash and error reports. | Technical details of a crash or error. Not linked to your account. |
| Vercel | Hosts these pages and Table invite links. | Standard web request data (such as IP address and browser) when you open a page or an invite link. |
| Apple and Google | App Store and Google Play distribution. | Nothing from inside Napkin. |
5.How long we keep it
For as long as your account exists. Your search text and location aren't stored as a history: they serve the request in front of you, and that's it. Screenshots you import are kept privately with your account so an import can be finished later, and text read from a public post is kept so the same post imports faster next time. When you delete your account, your data goes with it.
6.Deleting your data
Profile → Settings → delete account (at the bottom of Settings). The request immediately freezes new uploads and signs you out. Your logs, photos, imported screenshots, wishlist, comments, Table memberships, and account are then deleted irreversibly; storage cleanup is recorded durably and retries if a provider call fails. If you'd rather we handle it, or you can't get into the app, email jackyieong@mainrichinternational.com.
7.Your rights
Wherever you live, you get the GDPR-style basics:
- Access — ask for a copy of the data we hold about you.
- Correction — fix your account data (most of it is editable in the app).
- Deletion — see section 6.
- Objection and restriction — ask us to stop or limit a particular use.
- Portability — ask for your content in a machine-readable format.
Email jackyieong@mainrichinternational.com and we'll respond within a month. Data is hosted in the EU (see section 4); if you're in the EEA or UK, you can also complain to your local data-protection authority.
8.Children
Napkin is for people aged 13 and over — or older, if that's the minimum age where you live. We don't knowingly collect data from children below that age; if you believe a child has an account, email us and we'll delete it.
9.Changes to this policy
If this policy changes, the new version appears here with a new effective date. Meaningful changes get flagged in the app.
10.Contact
Napkin is built and run by one person — Jacky Ieong. Email jackyieong@mainrichinternational.com and you'll be writing to the developer, not a ticket queue.