Security

How your business and customer data is protected

A plain-language account of the security posture around Nishop Booking — what is protected, how, and where the boundaries are.

The boundary

Two systems, deliberately separate

Understanding what is where makes the rest of this page obvious.

  • This website — static pages only. No database, no accounts, no payments, nothing to breach beyond the files themselves.
  • The platform — the existing application where accounts, bookings, customers and payments live, protected by OTP access and role-based permissions.

Nothing you type into forms on this website is stored by the site itself unless an endpoint has been configured for it.

This marketing site

  • Static HTML / CSS / JS — no backend
  • No login, no database, no payment logic
  • Forms validate locally until an endpoint is set
  • Served over HTTPS on the public domain

The live platform

  • OTP-verified sign-in for businesses and customers
  • Role-based access for organisation, staff and admin scopes
  • Payments handled by Razorpay
  • Booking and customer records behind authenticated access

Controls

The controls that matter for a booking platform

Booking platforms hold two sensitive things: who your customers are, and how money moves. These are the controls relevant to both.

Authenticated access

Phone-based OTP verification ties accounts to a real, reachable person and resists shared-password problems.

Role-based permissions

Organisation owners, staff and administrators each see the scope their role requires — nothing wider by default.

Payment isolation

Card and UPI details are entered on Razorpay's payment flow. The platform records payment status, not card numbers.

Data minimisation on this site

This website collects nothing by itself — no tracking scripts, no analytics beacons, no hidden form posts.

Clear policy surface

Privacy, terms, refunds and cookies are published in plain language so you can read what you are agreeing to.

Scoped access requests

If you need to know what data exists about your business, contact us — access and correction requests are handled directly.

For business owners

What you are responsible for on your side

Security is shared. These three habits cover most of what can go wrong in an account.

Guard your OTP

Never share one-time codes. Nobody legitimate will ever ask you for yours.

Invite only your team

Give access to people who need it, and remove it when someone leaves the operation.

Report odd behaviour

Something look wrong in your account? Contact us immediately rather than waiting.

Security questions

Have a security question?

Ask us directly — we would rather answer a specific question than publish a vague promise.