Privacy Policy
Last updated November 12, 2026
KitchenSlate is booking, membership and billing software for shared commercial kitchens. It is provided by Poor Vida LLC (“we”, “us”). This policy explains what information KitchenSlate holds, why, who else handles it, and the choices you have. It covers kitchenslate.app, every kitchen’s own address on it (such as yourkitchen.kitchenslate.app), and the forms and calendars kitchens put on their own websites.
Who is responsible for your information
Each kitchen that uses KitchenSlate (a “Kitchen”) decides what it collects about its members, applicants and visitors, and what it uses it for. For that information, the Kitchen is responsible and we handle it on the Kitchen’s behalf, following its instructions and this policy. We are responsible for information about the Kitchens themselves and their staff as our customers, and for how KitchenSlate itself works. If you are a member of a Kitchen, the Kitchen is usually the first place to ask about your information; you can also contact us.
What KitchenSlate holds
| Information | Examples | Why |
|---|---|---|
| Account | Your name and email address; your password, stored only as a one-way hash; whether you use two-step sign-in (its secret and backup codes are stored encrypted) | To let you sign in and keep your account secure |
| Sign-in activity | When you signed in, and the IP address and browser of each signed-in session | To keep you signed in, let you sign out everywhere, and spot misuse |
| Your business, as a Kitchen member | Business name, contact details, address, what you make, your plan and rates, door code, calendar colour and logo | So the Kitchen can run your membership |
| Bookings and the calendar | The times, kitchens and equipment you book, and what for | To book kitchen time and show the Kitchen’s calendar |
| Documents | Files you or the Kitchen upload, such as insurance certificates, licences and food-handler cards, and their expiry dates | So the Kitchen can keep its compliance records |
| Applications, contracts and policies | Your application answers, signed agreements and acknowledgements | So the Kitchen can onboard members and keep signed records |
| Billing | Invoices, charges and payments, and the reference Stripe gives each payment. Card and bank details are entered on Stripe’s own pages; KitchenSlate never sees or stores them | To bill and record payment for kitchen time, storage and membership |
| Messages | Messages between members and the Kitchen in the app | To let you talk to the Kitchen |
| Website visitors | Name, email, phone and answers given on a Kitchen’s application or tour-booking form on its own website | So the Kitchen can follow up |
| Technical | Records of errors the app hits, kept for 30 days, and a record of changes staff make in the Kitchen’s account | To fix problems and let the Kitchen see and undo changes |
We do not use KitchenSlate’s information for advertising, we do not sell or rent it, and we do not share it with anyone for their own marketing. KitchenSlate uses no advertising or tracking cookies.
Sign in with Google
Where a Kitchen offers it, you can sign in with your Google account instead of a password. KitchenSlate asks Google only for your name, email address and profile picture (the “openid”, “email” and “profile” permissions), and uses them only to recognise you as someone who already has a KitchenSlate account, matched by your email address. It never creates an account from Google, and it keeps only the identifier Google gives your Google account, so it can recognise you next time. It does not keep the access tokens Google issues, and it never reads or changes anything else in your Google account, such as your email, calendar or files.
KitchenSlate’s use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements. You can remove KitchenSlate’s access at any time at myaccount.google.com/connections; you can still sign in with your password.
Email and calendars
KitchenSlate sends emails on a Kitchen’s behalf, such as invitations, password resets and tour confirmations. They come from a KitchenSlate address in the Kitchen’s name, and replies go to the Kitchen. We send no marketing email. Calendar links (for Google, Apple or Outlook Calendar) are private addresses: anyone with a link can see what it shows, so keep yours to yourself; a new link can be made at any time, which stops the old one working.
Who else handles information
We use these service providers to run KitchenSlate. Each handles information only to provide its service to us:
| Provider | What for |
|---|---|
| Cloudflare, Inc. | Hosting the app, storing uploaded files, and sending email |
| Neon, Inc. | The database that holds KitchenSlate’s records |
| Stripe, Inc. | Card and bank payments, where a Kitchen accepts them (Stripe’s own privacy policy applies to what you enter on its pages) |
| Google LLC | Sign in with Google, only if you use it |
We may also disclose information if the law requires it, to protect the safety or rights of people or of KitchenSlate, or as part of a sale or reorganisation of the business, in which case this policy continues to apply to it.
Cookies and storage in your browser
KitchenSlate sets only the cookies it needs: one that keeps you signed in, and, if you choose, one that remembers a device you trust for two-step sign-in. Your browser also remembers which Kitchen’s sign-in page you last used and a few display choices. None of these are used to track you across other websites.
How long information is kept
Information is kept while a Kitchen uses KitchenSlate, so it can keep its membership, billing and compliance records. Error records are deleted after 30 days. Demo kitchens and everything in them are rebuilt from scratch regularly. When a Kitchen leaves, it can take a full copy of its records, and we delete them on request, except where we must keep something by law. Backups are overwritten on a rolling basis.
Security
Information travels encrypted. Each Kitchen’s records are kept apart from every other Kitchen’s by the database itself, not just by the app. Passwords are stored only as one-way hashes. Kitchens can require two-step sign-in for their staff. No system is perfectly secure; if a breach affects your information, we will tell the Kitchens concerned and, where the law requires, you.
Your choices and rights
You can see and correct most of your information yourself in the app. You can ask for a copy of your information, ask for it to be corrected or deleted, or ask how it is used, by writing to the Kitchen you belong to or to us at privacy@kitchenslate.app. We answer within 30 days. Some information may have to be kept, for example invoices a Kitchen must keep for tax purposes. Depending on where you live, you may have further rights under privacy law, and you can complain to your local data protection authority.
Children
KitchenSlate is for businesses and is not meant for children. We do not knowingly collect information from anyone under 13.
Changes to this policy
If we change this policy, we will update the date above, and tell Kitchens of significant changes before they take effect.
Contact
Poor Vida LLC, Texas, USA — privacy@kitchenslate.app