Kitchen Support

How to write in

Email weekbox@crisperlatch.app with your iOS version, CrisperLatch version, and whether the snag is the recipe box, week rail, grocery list, Photograph this recipe capture, first-launch guide, Sunday / leftover / shopping nudges, or AI Allow / revoke.

Surfaces we can walk through

• Filing a recipe page into the box (camera, Photos, or Simulator still) and Accepting a draft
• Latching dinners from the box onto Mon–Sun slots under allergy / budget / taste chips
• Rebuilding and checking off the grocery list the week wrote
• On-device speech while you describe a recipe or pantry
• Allow DeepSeek for this latch / Settings → AI data sharing off
• Bundled CrisperLatch privacy page and the DeepSeek privacy link
• App Shortcut “Photograph this recipe”

Purchases

This build has no In-App Purchases. Apple refunds do not apply to CrisperLatch spend units because none exist on this tip.

What we cannot restore from the cloud

The ledger lives on this iPhone. If you delete the app or wipe local storage, we cannot rebuild recipes, week placements, grocery checks, or constraint cards from our servers.

Safety boundary for this kitchen job

CrisperLatch is not a dietitian, allergen lab, or restaurant concierge. Nested-agent OCR and week suggestions can be wrong — verify every Accept against the page you photographed and the chips you set.

Out of scope

We cannot recover deleted local data, promise perfect OCR, operate shared-family cloud sync on this tip, or reconfigure a tip whose app target still shows a placeholder bundle id — ASC must use the Feishu formal package name.

Contact

weekbox@crisperlatch.app