Your customers, menus and payments are the heart of your business. This page explains, in plain language, what we do to protect them today. It describes what is true now; we will not claim certifications we do not hold.
1. Your data stays yours and stays separate
Every catering business is a separate account. What one business records is never visible to another: this is built into how the product reads and writes data, and it is covered by automated tests that try to cross that line.
2. Who can see what inside your business
The owner decides what each team member can do. Roles such as sales, kitchen, store, accounts and events limit what people see and change, so a person in the kitchen does not see your payments unless you allow it.
3. Signing in
Passwords are stored only as one-way hashes, never as text. New accounts verify their email address, and a forgotten password is reset with a one-time code sent to the account's email. Sessions use secure cookies that scripts on the page cannot read, and they expire.
4. Payments
Card, UPI and bank details are entered with our payment provider, Razorpay, and are never stored by Platterly. If you connect your own Razorpay or UPI details so customers can pay you, those payments go to you.
5. A record of what changed
Important actions in an account are recorded with who did them and when. Owners and managers can review this in the Audit Log.
6. Protecting the service
- Traffic between you and Platterly is encrypted in transit (HTTPS).
- Data changes to the database are made carefully, with a backup taken first.
- Access to our systems is limited to the people who need it.
7. What we are still building
Security is never finished. We are working towards stronger operational monitoring and a formal review of our practices as Platterly grows. When we have something to report, such as an independent assessment, we will say so here.
8. Reporting a security problem
If you believe you have found a vulnerability or that your account has been misused, please write to [email protected] with the word "Security" in the subject. Tell us what you found and how to reproduce it. We will acknowledge your message, look into it promptly and keep you informed. Please give us a reasonable chance to fix a problem before sharing it publicly, and do not access other people's data while testing.