Security, in plain words
This is what the Food Order Chat does to keep restaurant sites and customers safer. It is a product description, not a certification, and not a claim of SOC 2 or ISO certification.
- The site is served only over HTTPS, with strict transport security and a tight Content Security Policy.
- Pages cannot be framed by other sites. Browsers are told not to sniff file types, not to send referrers, and not to use camera, location, or payment APIs here. The microphone is allowed only on this site, for optional voice typing in your browser.
- What you type in the chat is shown as plain text, not as HTML, so a pasted script cannot run in the page.
- Inputs have length limits. Restaurant lookups are checked on the server, limited to 8 per 10 minutes per IP, and only accept a plain name and town.
- No secret keys are placed in the chat’s public files. The lookup uses free public map sources and does not need an API key in the browser.
- Food orders, names, and addresses are not stored on our servers. Call, text, and email handoff happens on your own device.
- When Rebecca, our AI assistant, calls a restaurant for you, the call is started by our server. She only calls a US or Canada number from the restaurant’s public listing (not a number you type, and not a premium or high-cost international number). Calls and restaurant searches are rate limited, and the calling key stays on the server. One $5 payment can start only one call. The live “Listen” link is listen-only, unguessable, and is given only to the customer who placed that order.
- The chat never takes payment for food. Customers pay the restaurant at pickup or delivery.
The same summary is in SECURITY.md. Read full policy.
Restaurants can buy the chat for their own site on the Food Order Chat listing.