Security
Your recipes are your business.
A house spec and what it costs are worth protecting. Here is how we keep them safe, and who else handles them.
Each company kept apart
Every table checks which company a row belongs to before anyone reads it, in the database itself, so one company can never see another's recipes.
Access by role and location
An Admin chooses each person's role, sides and locations. Staff never see a cost, and a manager only sees their own locations.
Every change recorded
Each save writes a line to an audit log that nobody can change or delete, with who made it and when.
Keys locked away
The keys to your AI account and your Google Drive are locked before they are stored, and never reach a browser.
Sign-in you already know
Email and password, or a sign-in link sent to your email. Passwords are handled by our sign-in service, and we cannot read them.
A copy of your own
Every recipe downloads as a working Excel file, and can go to your own Google Drive on each publish, so you are never locked in.
Where it lives
The app runs on Vercel and keeps its data with Supabase, both in the western United States. Each service and what it handles is named in the privacy policy.
Found something that does not look right? Write to admin@gem15.app and we will look at it straight away.
Ready when your team is.
Bring your recipes, your prep and your menus into one place, and give every shift the same answers.