📄

RecipeMemoir privacy explainer: evidence and gaps

Private deliverable. Enter the hub password to continue.

That's not right. Try again.

← Back to the hub

RecipeMemoir privacy explainer: evidence and gaps

Claude Code (Opus 5.5), branch feat/privacy-explainer, merged to main (fast-forward, no force), released as v0.9.40.

Verdict on controls: RecipeMemoir has a FEW real, server-enforced content controls (imported-note gate, imported-photo hold with a family password, opt-in directory listing, pending-review hiding), but no site-level privacy control at all: every published site is public and indexable. So this log does not carry the "NO REAL PRIVACY CONTROLS" header, but the missing site-level controls are listed below.

Paths are relative to style-gallery/. API = functions/api/[[path]].js.

Where the explainer lives (the "share your site" steps)

  1. Homepage, "How it works" section, right after step 4 "Share your site" (index.html, block #who-can-see).
  2. Getting-started flow, /site/welcome, right after step 4 "See your site" ("your very own live address to share with anyone"), placed OUTSIDE the step card so it is visible even while that step is locked, i.e. before the person imports anything (site/welcome.html, block #who-can-see).

Exact text shipped (identical in both places)

Who can see your recipe site, and what you can control

  • Your site is public. Anyone with the link can open it, and search engines are allowed to list it. There's no private or password-protected site option yet.
  • Notes that came in with an import stay hidden until you approve them on Review your notes. Notes you write yourself show right away.
  • Photos that came from another website show a placeholder to visitors. Family can see the originals with a photo password you set. Once someone has unlocked them, changing the password or turning it off won't lock them out again.
  • Photos you upload or create yourself can be seen by anyone, so leave out anything you'd rather keep in the family.
  • Listing your site on Shared kitchens is optional, and you can unshare anytime.
  • Deleting a recipe takes it off your site, but a photo you added to it may still open at its old web address.

Evidence for each claim

Claim Evidence
Anyone with the link can open the site functions/u/[[path]].js:69-88: looks up the handle and serves the style page; the only refusal is if (db && !known) return new Response('Site not found', { status: 404 }) (line 88). No session/password check. Response headers lines 148-151 (Content-Type, Cache-Control only). Data endpoints the site reads are PUBLIC_OWNER ("anyone may call it, but ONLY for a collection that was named explicitly"): functions/api/lib/authz.mjs:17-21, 56-67; gate in API:916-919 (allowed = named).
Search engines are allowed to list it robots.txt: User-agent: * / Allow: /, no Disallow. /u/ responses carry no X-Robots-Tag (u/[[path]].js:148-151) and inject a <link rel="canonical"> but no robots meta (u/[[path]].js:122-133). sitemap.xml:36 lists https://recipememoir.com/u/annettethompson.
No private or password-protected site option No such setting or check exists in functions/ (audit of u/[[path]].js, authz.mjs, tenancy.mjs, API); site/settings.html holds only the AI-key form. The only password in the product is the family PHOTO password (below).
Imported notes hidden until approved API:434 (loadFullRecipe), API:1143 (recipe.js/collection.js payload), API:5773 (/api/site/recipe/:id): notes: r.notes_reviewed_at ? (r.notes ...) : null. Approval sets notes_reviewed_at: API:2780-2796 (POST /api/site/recipe/:id/notes-review, action keep). Owner UI: site/notes-review.html.
Notes you write yourself show right away Owner-edited overlay note always wins: API:455 and API:5795 (if (f.notes !== undefined) out.notes = f.notes || null;), comment API:432-433.
Imported photos show a placeholder to visitors API:6385-6396: for photo_third_party rows, if (kParam !== await familyKeyFor(row.collection_id, env)) return placeholderSvgResponse();. Payload URLs: demoPhoto API:558-565 emits ?k= only when photoCtx.authorized.
Family sees originals with a photo password you set POST /api/family/unlock API:1594-1618 checks shaHex('rmfp:'+id+':'+password) against the saved hash and returns the key; owner sets it via /api/family/settings API:1622-1650 (4 to 60 chars, "set a password before enabling"). Client stores it as cookie rm_fk for 180 days: styles/bind-photos.js:116. Viewer recognized via that cookie: API:862-864. UI: site/family.html.
Changing the password or turning it off won't lock them out The key is sha16('rmfk:' + collectionId + ':' + secret) (API:535-539): the password is not part of it. The viewer check (API:863-864) and the photo route (API:6393-6396) compare only the key, never the enabled flag or the password.
Photos you upload/create are visible to anyone /api/photo/ is PUBLIC (authz.mjs:34). A replaced/uploaded/AI photo (photo_data) is served with no audience check: API:6375-6388.
Shared kitchens listing is optional, unshare anytime POST /api/site/share API:3428-3440: needs a session, share requires rights_ok === true; share:false sets directory_shared_at = NULL. Directory lists only directory_shared_at IS NOT NULL: API:3395-3399. UI: site/index.html:89-99.
Deleting a recipe takes it off the site Shared public filter r.archived = 0 AND COALESCE(e.deleted, 0) = 0 (API:144-146) for lists; single-recipe reads return null/404 on delete: API:417 (if (!r \|\| r.edel) return null;), API:5741.
A photo you added may still open at its old address Photo route looks the recipe up by id only (FROM recipes r WHERE r.id = ?, API:6364-6372), with no deleted/archived/collection check; recipe ids are plain integers (API:6350-6352).

Controls that exist (server-enforced)

  • Imported-note gate (owner approves each note).
  • Imported-photo hold + family photo password.
  • Opt-in, reversible listing in Shared kitchens (with a photo-rights attestation).
  • Pending-review recipes (new link/video imports) hidden from non-members: API:847-855, filter applied API:997, 1186, 5742.
  • Edits require a signed-in session belonging to the collection (authz.mjs:124-145, API:887-899).
  • Shared shopping lists are read-only and reachable only by a 24 to 64 hex-char token (API:965-984). Not mentioned in the explainer (not part of the recipe site).

Controls that do NOT exist (so the explainer does not claim them)

  • No private, unlisted, or password-protected site.
  • No way to keep a site out of search engines (no noindex option, robots allows all).
  • No user-facing "hide sources" setting. Source links are blanked in collection.js/recipe.js payloads (API:575-578, 1140-1142) and hidden in the browser by styles/nosource.js, but /api/site/recipe/:id still returns source (API:5755) and JSON-LD adds isBasedOn (export-lib.js:168-171). Not claimed.
  • No family-access revocation (see the key derivation above).
  • No per-recipe visibility toggle.

Gaps found during the audit (not fixed here: this change was additive and text-only)

  1. Archived recipes still render by direct link. Single-recipe reads (API:412-417, 1186, 5740-5742) don't check archived, though the comment at API:1201 says they do. That's why the explainer says nothing about archiving.
  2. site/family.html:89 hint is false: "saving a new one signs out anyone using the old one eventually". The key does not depend on the password. Should be reworded or the key should include the password hash.
  3. Family photo password hash is publicly readable: /api/site/prefs is PUBLIC (authz.mjs:52) and returns any key (API:3454-3458), so ?owner=X&key=family_photos exposes the unsalted SHA-256 hash of a password that can be 4 characters. /api/family/unlock has no rate limit.
  4. Photo route ignores collection/deleted/archived/pending and ids are sequential, so every non-held photo across all users is enumerable.
  5. GET /api/site/recipe/:id/commentary (API:3935-3946) is not scoped to the named collection.
  6. RM_FAMILY_KEY_SECRET is not set in production; the family key falls back to RM_WRITE_KEY (API:528-536).

Files changed

  • style-gallery/index.html (explainer block after step 4 + 6 CSS rules)
  • style-gallery/site/welcome.html (explainer block after step 4 + CSS)
  • style-gallery/site/changelog.html, style-gallery/site/site.js (v0.9.40 entry and version bump)
  • test/privacy-explainer.test.mjs (new, 3 tests)
  • PRIVACY_LOG.md, HANDOFF.md (this log, handoff)

Tests

npm test: 549 pass, 0 fail (includes the 3 new tests: explainer follows the share step on the homepage and on /site/welcome, carries the honest-limit sentences and real settings links, and both copies match word for word).

Site validator (21 pages, live): http, mustContain, mustNotContain, overflow (320 to 1920), sticky, em dash, links all PASS. clipped FAIL only on the pre-existing decorative div.pattern-band banner of the styled browse pages (/site/browse.html, /u/annettethompson), same as the v0.9.39 run; not on any page changed here.

Visual check (headless Chromium, live site, 1280px and 390px): both blocks render cleanly, no overflow (scrollWidth equals viewport), screenshots in screenshots/privacy/.

Commits

  • f4c9ef2 feat: add a 'who can see your recipe site' explainer next to the share step
  • fa94f2d docs: privacy explainer log (evidence, controls, gaps) and handoff (also fast-forwarded to main)

main was fast-forwarded a5fc361 to f4c9ef2 with git push origin feat/privacy-explainer:main. No force push, no history rewrite, no production data touched, no secrets. Deployed with style-gallery/deploy.sh --production (deployment cd9e7753).

Live URLs checked (curl, browser user agent, redirects followed)


Pre-import + deletion (2026-11-21, v0.9.41)

Claude Code (Opus 5.5), same branch feat/privacy-explainer, fast-forwarded to main, released as v0.9.41.

Where it lives

  • /site/import: "Before you import: who will see it", #before-you-import, placed above the sign-in prompt, the Paprika file input (#file) and the sample-import button (#sampleBtn), so it is visible signed in or out.
  • /site/add: "Before you add a recipe: who will see it", #before-you-import, at the top of the page body above the link form ("Get the recipe"), the paste form ("Lay it out") and "Save to my recipes".
  • Both link to the full explainer at /#who-can-see (homepage, next to the "Share your site" step), which now has a second part, "Deleting things". The same full explainer is on /site/welcome next to step 4.

Exact text shipped

/site/import

Before you import: who will see it - Your imported recipes go on your public site right away. Anyone with the link can see them, and search engines are allowed to list them. There's no private site option yet. - Photos in your Paprika export show on your site for anyone to see. - Your notes come in only if you tick the box below, and they stay hidden until you approve each one. - You can delete recipes later and restore them from Trash, but deleting doesn't erase a recipe's photo from our storage, and there's no self-serve way to delete your whole account yet.

Who can see your site, and how deleting works

/site/add

Before you add a recipe: who will see it - Recipes you save here go on your public site right away. Anyone with the link can see them, and search engines are allowed to list them. There's no private site option yet. - A photo that comes with a recipe from a link or video shows a placeholder to visitors until you add your own. Family can see it with your photo password. - Photos you upload or create yourself can be seen by anyone. - You can delete recipes later and restore them from Trash, but deleting doesn't erase a recipe's photo from our storage, and there's no self-serve way to delete your whole account yet.

Who can see your site, and how deleting works

Full explainer (homepage #who-can-see and /site/welcome), replaces the v0.9.40 text

Who can see your recipe site, and what you can control - Your site is public. Anyone with the link can open it, and search engines are allowed to list it. There's no private or password-protected site option yet. - Photos in your Paprika export, and photos you upload or create yourself, can be seen by anyone, so leave out anything you'd rather keep in the family. - Photos that come with a recipe you add from a web link or video show a placeholder to visitors. Family can see the originals with a photo password you set. Once someone has unlocked them, changing the password or turning it off won't lock them out again. - Your Paprika notes come in only if you tick the box on the import page, and then stay hidden until you approve them on Review your notes. Notes you write yourself show right away. - Listing your site on Shared kitchens is optional, and you can unshare anytime.

Deleting things - Deleting a recipe, one at a time or with "Delete selected", takes it off your site and puts it in Trash on your site's homepage, where you can restore it. It isn't erased from our database. - Archiving a recipe on Duplicate Cleanup hides it from your site's lists and search, but it still opens by its direct link. "Delete forever" takes it out of your collection, but a backup copy stays in our database. - No kind of delete removes a recipe's photo from our storage, and the photo may still open at its old web address. Photos are set to be cached for up to a year, and visitors' browsers may keep copies for offline use. - There's no self-serve way to delete your whole account or site yet.

Evidence for each new claim

API = style-gallery/functions/api/[[path]].js; other paths relative to style-gallery/. Claims carried over from v0.9.40 (public site, search engines, no private option, family password limits, Shared kitchens) keep their evidence in the first table of this log.

Claim Evidence
Imported (Paprika) recipes are public right away Browser batch POST /api/import (API:1720) inserts with no pending_review (API:1739-1746). Background job insert: functions/api/lib/import-job.mjs:124-131 (no pending column, archived 0). Public reads filter only archived/deleted/pending: API:144-146.
Recipes saved on /site/add are public right away POST /api/add/save (API:2007) calls insertStagingRecipe(db, staging, collectionId, owner, false) at API:2029; the last argument is pendingReview (API:350, comment API:346-349). Same false for import-url (API:2108) and import-video/save (API:2273). site/add.html saves via /api/add/save. Correction to the v0.9.40 section: pending review exists as a mechanism, but no current add path sets it, so the "new link/video imports start pending" bullet under "Controls that exist" was wrong.
Paprika photos are public Both Paprika paths store recipes/{id}.jpg and set only has_photo = 1, never photo_third_party: API:1770-1771, lib/import-job.mjs:159. The placeholder hold applies only when tp is set (API:6393-6396).
Photos from a link/video show a placeholder API:2064-2065 (add/save), API:2127-2130 (import-url), API:2284-2285 (video): has_photo = 1, photo_third_party = 1; placeholder rule API:6393-6396.
Paprika notes only if you tick the box, then hidden until approved Checkbox #importNotes, site/import.html:110. Server: const importNotes = !!body.importNotes (API:1728), note stored only when true (API:1746); job path lib/import-job.mjs:63, 131. Hidden until notes_reviewed_at is set: API:434, 1143, 5773.
Delete puts it in Trash, restorable, not erased Soft delete only sets recipe_edits.deleted = 1: POST /api/delete API:2412-2425, POST /api/site/recipe/:id/delete API:2746-2758 (comment: "soft-delete (recoverable)"). Undo: POST /api/restore API:2428-2439. Trash UI in the styled site homepage drawer: styles/manage.js:52 (tab), 96-113 (Restore, Restore all); deleted recipes collected by styles/overrides.js:64-68. Recipe-page confirm: "You can restore it from Trash on your homepage." (styles/editor.js:406).
"Delete selected" does the same styles/manage.js:84-89: "Delete selected" sends the slugs through RMOverrides.del to /api/delete (soft), confirm "You can restore from Trash."
A deleted recipe comes off the site Lists: API:144-146 (COALESCE(e.deleted, 0) = 0). Single reads: API:417 (if (!r OR r.edel) return null), API:5741.
Archive hides from lists and search but opens by direct link Archive/restore API:3072-3082. Lists, search, facets, export filter r.archived = 0 (API:145, 705, 1247, 4947). Single reads never check archived: loadFullRecipe API:412-417, /api/site/recipe/:id API:5737-5742. UI: site/cleanup.html:145.
"Delete forever" removes it from the collection, a backup copy stays POST /api/site/recipe/:id/purge API:3889-3896 calls hardDeleteRecipeWithBackup API:679-696: writes the recipe and child rows to dedupe_deleted_backup (API:689), then DELETE FROM recipes (API:694). Button and confirm "A backup is saved": site/cleanup.html:505, 511. No code reads that backup back (its only reference is the write at API:689).
No delete removes the photo from storage The only env.PHOTOS.delete calls delete the uploaded import file and its manifest (lib/import-job.mjs:259-260). Nothing deletes recipes/{id}.jpg or recipes/thumb/{id}.jpg.
The photo may still open at its old address Photo route reads by id only, with no deleted/archived/collection check (API:6359-6372), then serves from storage (API:6397-6418).
Photos cached for up to a year Cache-Control: public, max-age=31536000, immutable on stored photos and thumbs (API:6407, 6417); edited photos max-age=86400 (API:6381).
Visitors' browsers may keep copies for offline use Service worker registered by the styled pages: styles/pwa.js:96. Photos cache-first up to PHOTO_CAP = 400 (sw.js:34-36, 54, 60); recipe text via /api/offline.json (cache-first) and recipe.js (network-first, offline fallback) (sw.js:26-29).
No self-serve account or site deletion No DELETE FROM users, collections or collection_members anywhere in functions/ (grep, 0 hits). The closest control is leaving Shared kitchens (API:3437), which does not take /u/{handle} down.

Not claimed (and why)

  • Database backups: wrangler.toml has no backup or Time Travel settings and there is no scheduled job, so the explainer says nothing about platform backups either way. The only backup the code makes is dedupe_deleted_backup on "Delete forever", which is stated.
  • The uploaded Paprika file: streamed to storage (lib/import-job.mjs:76) and deleted when the job finishes (259-260, best effort); a job that fails before finishing leaves the file in storage. Not in the explainer.
  • Other bulk deletes: Photo triage ("Delete selected WHOLE recipes", site/photo-triage.html:130) and low-confidence nutrition both soft-delete through recipe_edits, so the same rules apply, but those pages have no undo button of their own; restore is via Trash.

Additional gaps found (not fixed: this was a text-only change)

  1. Dedupe apply archives recipes by request-supplied id with no collection check (API:3676-3680); consolidate-undo un-archives the same way (API:3874).
  2. site/nutrition-lowconf.html:153 says "This can be undone" but that page has no undo; restore is the Trash drawer.
  3. A hard-deleted recipe's link/video photo loses its placeholder hold: the photo route can't find the row, so the if (row && row.tp) check is skipped and the original is served to anyone.
  4. /api/site/recipe/:id/delete writes recipe_edits without collection_id (API:2754); restore still finds it through EDIT_OWNED_BY (API:163-166).

Files changed

  • style-gallery/site/import.html, style-gallery/site/add.html (pre-import note + CSS)
  • style-gallery/index.html, style-gallery/site/welcome.html (explainer extended with "Deleting things", CSS)
  • style-gallery/site/changelog.html, style-gallery/site/site.js (v0.9.41)
  • test/privacy-explainer.test.mjs (3 new tests; block helper now reads the whole explainer)
  • PRIVACY_LOG.md (this section)

Tests

npm test: 552 pass, 0 fail. New: the full explainer states each deletion fact on both pages; the import note sits before #file, #sampleBtn and the sign-in prompt and states each claim; the add note sits before "Get the recipe", "Lay it out" and "Save to my recipes".

Site validator (21 pages, live): http, mustContain, mustNotContain, overflow (320 to 1920), sticky, em dash, links (69) all PASS. clipped FAIL only on the pre-existing div.pattern-band banner of the styled browse pages, unchanged.

Visual check, headless Chromium on the live site at 1280px and 390px: /site/import, /site/add and the homepage explainer render cleanly, no horizontal overflow.

Commits

  • 4c4f996 feat: pre-import privacy note on import + add pages; explainer covers deletion
  • 07e3b38 docs: PRIVACY_LOG pre-import + deletion section

main fast-forwarded 2b068ba to 4c4f996 and then to the log commit (no force, no history rewrite). Deployed with style-gallery/deploy.sh --production (deployment bf655628).

Live URLs checked (curl, browser user agent, redirects followed)

Published to Annette's hub. Rebuilt from the source markdown, so edit the source and rerun rather than editing this page.