Privacy Policy
Last updated 4 October 2026
MISE is staff training, inventory and operations software for hospitality venues. This policy explains what we collect, why, who we share it with, and how to get it back or have it deleted. It is written to be read, not to be survived.
Operator: MISE SOFTWARES, ABN 71 803 015 212, 14 Attunga Avenue, Earlwood NSW 2206, Australia. Privacy enquiries: hello@trymise.io.
What we collect
| Your account | Email address, full name, and phone number if you give one. If you sign in with Google we also receive your profile picture. Passwords are handled by our authentication provider and never reach us in readable form. |
|---|---|
| Your venue | Venue and organisation name, country, timezone, your plan, and the customer and subscription identifiers issued by our payment provider. |
| Staff accounts | Username and display name only. No email address, no phone number. Passwords are stored as a salted one-way hash and cannot be read back, by us or by anyone else. |
| Learning records | Which menu items a staff member has mastered, quiz scores and history, streaks, and activity timestamps. |
| What you upload | Menus as PDFs, photos or text, photos of your venue, style notes, and your website address. |
| Enquiries | If you ask us to call you: name, email, phone, venue name, plan of interest and your message. |
| Page analytics | Which page was viewed, on which of our sites, and the referring page. |
| Free demos | You can build a demo app without an account at all: we then hold only the venue name you typed and the menu you uploaded. No email, no sign-in. The demo and everything in it is deleted after fifteen days unless you claim it into an account. |
| Error diagnostics | When something fails we record what broke: the message, the technical trace, and the address of the request. Passwords, keys and tokens are stripped out before any of it is written down. |
How our analytics work, precisely
We do not use cookies, and we do not use a third-party analytics service. We also do not store your IP address. To count unique visitors we take your IP address and browser user-agent, combine them with the current date and a secret value, and keep only a one-way hash of the result. The IP address and the user-agent themselves are discarded and never written down. Because the date is part of the recipe, the hash changes every day, so it cannot be used to follow you over time.
Why we use it
- To build and run your training app from the menus you give us.
- To let your staff sign in, and to show a manager how their team is progressing.
- To take payment and manage your subscription.
- To send you service email: receipts, and notices about your account.
- To understand which pages of our own site people read, in aggregate.
We do not sell your data, and we do not use it for advertising.
Who we share it with
Only the suppliers that make the product work. Each one receives the minimum it needs.
| Supabase | Database, sign-in and file storage. |
|---|---|
| Render | Hosting for our sites and our API. |
| Stripe | Payments. Card numbers go straight to Stripe and never touch our servers. |
| Resend | Sending transactional email. |
| Only if you choose to sign in with Google. | |
| OpenAI | Reads your uploaded menu PDFs and venue photos so they can be turned into text. |
| DeepSeek | Turns that menu text into the training content for your app. |
Leaving Australia. Everything we hold is stored and processed outside Australia, not only what the AI reads. Our database, sign-in and uploaded files live with Supabase in Tokyo; our API and our sites run on Render in Singapore; and OpenAI and DeepSeek process your menus and venue photos on their own servers abroad. Each supplier handles that data under its own terms. We say this plainly because Australian privacy law asks us to, and because a venue that cannot send staff or menu data overseas needs to know before it signs, not after. If that is your case, tell us before you upload anything and we will talk about what is possible.
Staff accounts belong to the venue
Accounts for waiters, bartenders and other floor staff are created by the venue owner or manager, and the venue decides who gets one and what happens to it. We hold that information on the venue's behalf. If you are a staff member and you want your record corrected or removed, ask your manager first, because they can do it directly. You can also write to us and we will help.
How long we keep it
- Demo apps are deleted fifteen days after they are created, along with their menus, staff accounts and progress.
- Active accounts are kept while the account exists.
- Error diagnostics are kept for thirty days and then deleted.
- On request we delete your data. Ask us and we will do it.
How we protect it
- Everything travels over HTTPS.
- Staff passwords are salted and hashed with scrypt, so they cannot be reversed.
- Our database enforces, row by row, that one venue cannot read another venue's data.
- We never see or store card numbers.
Your rights
Under the Australian Privacy Act you can ask what we hold about you, ask us to correct it, and ask us to delete it. Write to hello@trymise.io and we will answer within a reasonable time and at no cost. If you are not satisfied with how we handle it, you can complain to the Office of the Australian Information Commissioner at oaic.gov.au.
Changes
If we change this policy we will update the date at the top. If a change materially affects what we do with your data, we will tell account holders by email rather than leave it for you to find.