Last updated 2026-10-14 · applies to the Mise hackathon build submitted to Build, Ship, Shape 2026
Whatever you tell it through Alexa+: what's in your pantry, what you cooked, substitutions you made, and recipe or shopping preferences. If you use the simulated fridge or barcode-scan demo, it also handles a simulated device reading or a scanned barcode. If you use the demo checkout, it handles the items in a cart and a fictional stored payment instrument — never a real card number or real payment credential; the demo does not accept or process either.
On the demo server, in memory, behind the interfaces that a real deployment would back with a
database. It does not currently persist to a database — a server restart clears it. There is no
account linking yet: a single shared demonstration account (DEMO_USER) owns
everything behind account-bound surfaces. That account is a configuration flag, not a
verified identity, so this build should not be pointed at anything you consider sensitive.
It doesn't sell or share what you tell it with any third party. The one outbound lookup it can make — checking a barcode against Open Food Facts — sends only the scanned barcode, nothing that identifies you. It doesn't use anything you report to train a model; the server has no model of its own, and the only language model involved is Alexa+ itself, carrying on the conversation.
Real account linking (OAuth with PKCE), persistent storage, and a real connected fridge or barcode scanner are planned but not yet built — see BLOCKED.md in the repository for exactly what's missing and why. This policy will be rewritten, not quietly extended, before any of that handles a real person's data outside a demo.
Open an issue on the GitHub repository.