Privacy

OrderWalk is a phone-first app for counting what a restaurant has on hand and turning that into vendor orders. Hackwise Labs LLC operates it from the United States.

Questions about this policy go to [email protected].

When you sign in, we store the email address for that restaurant.

For the restaurant we store the restaurant record, vendors, storage lists, items, counts, units, pack sizes, notes, prices, par levels, order history, and team members.

A team member has an email, a display name, and a role. An invite stores the invited email, name, and role until it is accepted or it expires after 14 days. When team mode is on, a count or a completed order can store the name of the person who did it.

A photo you add is stored with the item. A barcode you save is stored with the item.

We also store the choices you make here: theme (dark, light, or system), whether you use par levels, and which one-time tips you have dismissed. Those sit on this device and, once you are signed in, on the account.

Restaurant data is hosted in Supabase. That includes the database, the sign-in account, and item photos. Photos go in a private bucket. They are not published as a public web address.

There is no password. You enter an email and tap Email me a link. Supabase emails a 6-digit code and a one-time sign-in link to that address. Type the code in the app. On iPhone, if OrderWalk is on the Home Screen, type the code from the email there. The link opens Safari and leaves that app signed out. Opening the link in the browser also signs you in. The sign-in session stays on this device so you remain signed in.

A manager can share an order with a link. Anyone with the link can open it without signing in. The page shows the list name and the lines still to order: item name, quantity, unit, and notes.

The link does not show prices, photos, barcodes, pars, order history, or the team. Lines that are checked off, have a quantity of zero, or have a blank name are left off.

Stop sharing turns that link off. New link replaces it, and the old link stops working. A link that was turned off says it is no longer active.

The app keeps a copy of the signed-in kitchen on the device so it can open offline. That copy includes lists, items, counts, prices, order history, queued edits, and photos waiting to upload. It is stored in this browser and tied to the signed-in account.

Signing out removes that account's copy from the device. Theme, par, and tip choices are also stored in this browser. Deleting the account, or leaving the team, removes that copy, the queued edits, and the choices saved in this browser.

The demo kitchen is sample data in the tab you have open. It is not saved to an account or to the device database.

If you turn reminders on for this phone, we store a push subscription for that device: the push address, the two keys the phone uses to receive the message, the account, and the restaurant. We also store the reminder itself: all lists, or which storage list or vendor, which days, the time, and the restaurant time zone.

We use that only to send the reminder to phones that still have reminders on. A count reminder can go to anyone on the team. An order reminder goes to owners and managers, and only when that vendor order still has lines and has not been sent. All lists waits until any vendor still has lines. A counter cannot create or change a reminder.

Turning reminders off on this phone stops delivery here. Signing out removes this phone's subscription. If the phone's push service says the subscription is gone, we delete it. The demo shows a sample and does not subscribe or send.

On an iPhone, push reminders need OrderWalk on the Home Screen and iOS 16.4 or later. A phone that cannot receive a push still shows a dismissible banner in the app when a reminder is due or was missed that day.

Error monitoring and anonymous usage counts stay off unless a deployment is configured to send them. Monitoring needs a public Sentry address. It also stays off during development and on the demo. When it is on, a sample of crashes is sent to Sentry. Emails, prices, item names, share links, and account ids are removed first. Reloading after a crash leaves the offline copy on this device.

Usage counts need Plausible, with a site domain, or Vercel. They send an event name only: a count was saved, an order was sent, or the demo was opened. They do not include who you are, what you ordered, or which page you were on.

While both are off, OrderWalk does not send crash reports or usage counts.

We do not sell personal information or restaurant data. We do not use it for advertising.

If you scan a barcode that is not already on an item, the app can ask Open Food Facts for a product name and picture. That request sends the barcode to world.openfoodfacts.org. You can skip it and type the name. Share links do not include photos or barcodes.

Backup in Settings downloads your data to this device. You get a JSON file of lists, items, the catalog, and pars, and a CSV of every item. That download is not uploaded by the app. Order history and photos are not in those files.

The owner deletes one restaurant in Settings, under Delete account. The page names that restaurant. It deletes the lists, items, counts, prices, order history, team memberships, share links, reminders, and item photos stored for it. Download a backup first. Type DELETE to confirm. If another restaurant remains, the sign-in stays. If it is the only one, the sign-in is deleted too.

A manager or a counter sees Leave this team for the restaurant they have open. That removes only their membership in that restaurant and their reminder subscription for it. It does not delete the restaurant, the lists, the items, the counts, the prices, the order history, the share links, or the owner's account. If another restaurant remains, the sign-in stays. If they have no other restaurant, their own sign-in account is deleted too.

After either one, this device drops the offline copy and the queued edits, then signs out. The demo has no account to delete.

If you cannot finish it in Settings, email [email protected] from the account address and ask us to delete it.

Signing out by itself removes the account's copy from this device. It does not delete the restaurant. Removing a teammate ends their access. It does not delete the restaurant.

OrderWalk is for restaurant work. It is not directed at children.

If this policy changes, this page and the effective date change with it.