KitchenSensAI
iOS app by VICTOR DAVID BELTRAN. Business · VICTOR DAVID BELTRAN
- Store rating
- 0 / 5
- Store rating count
- 0
- Download price
- Free to download
- In-app purchases
- Unknown
- Version
- 1.0.0
- Listing last refreshed
- 2026-09-07
View the original store listing
Store description excerpt
KitchenSensAI is a private, invite-only operations app for restaurant kitchens. Restaurants buy it for their own staff. There is no consumer sign-up, no purchase or subscription screen, and no paid content. Access is granted by a restaurant administrator (Guideline 3.1.3(c), enterprise services). The app is free, restaurants are invoiced outside the app, and no pricing or upgrade path appears in the binary. Please sign in rather than using the demo tour. The "Try the demo" button opens a no-account sample restaurant where account-specific controls are hidden, because there is no account to delete and no real people to report. chef@bamboo.local / KitchenDemo2026! (chef) manager@bamboo.local / KitchenDemo2026! (admin - Admin console) reviewer@bamboo.local / KitchenDemo2026! (staff - safe to delete) 1) AI CONSENT - response to the previous rejection (5.1.1(i), 5.1.2(i)) The earlier build sent data to a third-party AI provider without disclosing it in the app. Corrected: consent is now obtained in the app before anything leaves the device. a. Sign in as chef@bamboo.local, tap the Sensai assistant button. b. Type: how do I make salmon nigiri c. A disclosure appears BEFORE anything is transmitted. It names Groq (a US AI company) as the recipient, lists what is sent, lists what is never sent, and explains retention. d. Nothing is sent unless "Allow" is tapped. "Decline" keeps the assistant answering from on-device data, so refusing is not a dead end. e. The choice can be reviewed, withdrawn or re-granted any time in Settings > Sensai AI. Sent to Groq, only after consent: the typed question; summaries of matching recipes and menu items including a dish's build and plating steps; how many people are scheduled today by shift and role as counts only ("dinner: 2 sushi, 1 expo"); the last few messages of the conversation. Never sent: the user's name, email, PIN, password or account identifier; coworkers' names, including who is on the schedule; food-safety and temperature logs, checklists, waste logs, staff messages; training videos, quiz answers or completion history. PLEASE NOTE: schedule questions ("who is working tonight") are answered entirely on-device by a local engine. No network request is made and no disclosure is shown, because nothing is transmitted. If you ask a schedule question first you will correctly see an answer with no consent prompt. The disclosure appears on the first question that would require sending data off-device, which is why step b specifies a recipe question. The Groq API key is held server-side in a Supabase Edge Function and is not in the app binary. Users are never asked for an API key. Consent is stored per account, so on a shared kitchen tablet one person's answer never speaks for the next. 2) USER CONTENT CONTROLS (1.2) a. As chef@bamboo.local, open Messages. Press and hold a message from another person (e.g. Sofia Herrera). b. "Report message" files a report with the restaurant's man
Review coverage
AppRill has captured 0 reviews for this app. This is a collected sample, separate from the store rating count. Latest review capture: Not captured yet.
Recent captured chart positions
No chart positions have been captured for this app yet.
Chart position, rating count and review coverage do not establish downloads, revenue or profit. Understand the differences.