PartyBook privacy policy
What the app stores, where it is stored, who can see it, and what you can ask us to do about it.
Last updated 2 November 2026
PartyBook is made by DevRocks, a sole proprietorship in India. Everything on this page, including any request or complaint, goes to partybook.support@gmail.com.
1. Two different people are involved
That distinction runs through everything below, so it comes first.
- The business using PartyBook — a hotel or caterer, and its staff, who hold accounts we issued.
- That business's own customers — the people whose names, phone numbers and delivery addresses staff type into an order. They have no account and never use the app.
In the language of India's Digital Personal Data Protection Act, 2023: for the second group the business is the Data Fiduciary and DevRocks is only a Data Processor. The business decides what is collected and why; we hold it on their instructions and use it for nothing else.
So if you are a customer of a shop that uses PartyBook and want your details corrected or removed, ask that shop — they control the record. We will help them act on it, and we will not alter another business's records on a third party's instruction.
For the business's own account data — staff names, usernames, roles — we are the Data Fiduciary, and sections 7 to 9 apply directly to you.
2. What is stored
- About the business
- Hotel name, its hotel code, and optionally an address and phone number. Per branch: name, address, phone number and bill-number prefix.
- About staff
- A username, a display name, a role (administrator or labour), whether the account is active, and whether a PIN change is due. Optionally a list of employee names, so an order can record who took it. When an administrator resets somebody's PIN we record who did it and when.
- About the menu
- Food item names and rates.
- About each order
- The customer's name, phone number, an optional second phone number and a delivery address. The items and quantities, rates and total, the delivery date and sitting, when it was booked and by which account, amounts paid and how, and — if cancelled — who cancelled it, when, why and any refund.
- About a subscription
- One date per branch: when it is paid up to. There are no plans to be on and no count of how many orders a branch has filed. Payment card and bank details are never seen by us or by the app; see section 5.
What is not collected at all: no location, no contacts, no photos, no device identifiers for advertising, no browsing or usage analytics. The app does not ask for those permissions, so it could not collect them if it wanted to.
3. Credentials, and why they cannot be recovered
PINs are not stored. A six-digit PIN never reaches our records in readable form. What is stored is a value derived from it using PBKDF2 with a per-account salt and 100,000 rounds, plus a secret held only in the app binary and on our server. That is one-way: nobody, including us, can read a PIN back out of it. It is why a forgotten PIN is replaced rather than recovered.
The branch cancellation code is stored the same way for staff to check against, alongside a copy that only that hotel's own administrators can read — so the owner can tell their staff what it is.
Under the Information Technology (Reasonable Security Practices and Procedures and Sensitive Personal Data or Information) Rules, 2011, passwords count as sensitive personal information. We hold none in a form that could be disclosed, exported or compelled.
4. Where it is stored
On Google Firebase — Firestore for records, Firebase Authentication for sign-in credentials, and Cloud Functions for the one operation the app is not permitted to do itself.
The database and those functions run in Google's
asia-south1 region, in Mumbai, India, so your records
are stored in India. Google may process limited operational data — service
logs, billing and abuse-prevention metadata — outside India as part of
running its platform. We do not choose or control that, and it does not
include your order records.
And on the phone
The app keeps an offline copy of the records it has seen, so it works without a signal, plus a stored sign-in session. Both live in the app's private storage.
On Android, we switch off Google's app backup and device-to-device transfer for PartyBook. That is deliberate: the offline copy holds customers' names, numbers and addresses, and we would rather it never be copied off the phone by the operating system. Removing the app removes it.
5. Who it is shared with
Nobody. We do not sell, rent or share your records. We do not use them to build profiles, to advertise, or to train anything.
There is no analytics in PartyBook. No advertising, no tracking, no crash-reporting service, and no third-party SDK beyond what is listed here. The app does not know how you use it.
| Who | What they process | Why |
|---|---|---|
| Google (Firebase) | Everything in section 2 | They host it. We are their customer, under their terms. |
| Razorpay | Only a subscription payment: the payer's own details and the amount | Collecting the yearly subscription fee. Razorpay never sees an order, a customer or a staff record. We never see card or bank details. |
We will disclose records if a law, a court or a lawful authority requires it. If that happens and we are permitted to tell you, we will.
6. Things that look like sharing and are not
- The Call button on a pending payment opens your phone's own dialler with the customer's number filled in. It does not place a call, and the number goes nowhere but your dialler.
- Printing or sharing a bill creates a PDF on your phone. Where it then goes — a printer, WhatsApp, email — is your choice, and after that it is outside PartyBook.
- The request forms for a hotel account or a PIN reset open your own email app with the details filled in. Nothing is sent until you press send there.
7. Why we are allowed to hold it
For a business using PartyBook: because you asked us to provide the service, and holding these records is how it works. You consent when you accept an account and the Terms of Service, and you can withdraw that consent by closing your account — see section 9.
For a shop's own customers: the shop decides, and is responsible for having a lawful reason. We act only on the shop's instructions.
8. Your rights
If you hold a PartyBook account, you can ask us to:
- Access — give you a copy of the records we hold about you and your hotel, and a summary of how they are processed.
- Correct or complete — fix anything inaccurate or incomplete. Most of this you can do yourself in the app.
- Erase — delete your hotel and its records. See Delete your account.
- Complain — raise a grievance and have it answered. See section 10.
- Nominate — name another person to exercise these rights on your behalf if you die or become unable to act. Tell us in writing and we will record it.
Email partybook.support@gmail.com from an administrator's address. We may ask you to confirm who you are before acting, because these requests can be used against an account rather than for it.
9. How long it is kept
While your subscription is live, for as long as you want it. Order history is the point of the product, and a cancelled order is deliberately kept rather than deleted so the record survives with its bill number intact.
After an account is closed or a deletion is requested, we delete the hotel and its records within 30 days. Backups then age out on their own within a further 7 days, after which nothing remains.
We keep daily backups for 7 days while an account is live, so an accidental deletion can be undone.
10. Grievances
If something here has gone wrong, tell us and we will answer.
| Grievance Officer | Suba R, DevRocks |
|---|---|
| partybook.support@gmail.com | |
| We reply within | 7 days, and resolve within 30 days of receiving the complaint |
If we do not resolve it, you can escalate to the Data Protection Board of India under the Digital Personal Data Protection Act, 2023.
11. If something goes wrong
If personal data we hold is exposed or lost, we will notify the Data Protection Board of India and the affected businesses without undue delay, telling you what happened, what was involved, and what to do about it.
12. Security, stated plainly
- Records are readable only by accounts belonging to that hotel, enforced on the server and not only in the app.
- Data is encrypted in transit, and encrypted at rest by Google.
- PINs and cancellation codes are stored one-way, as described in section 3.
- The app carries no administrative key. Changing another person's credential happens on a server, only for an administrator of that same hotel, and never for a hotel's only administrator.
- What we do not claim: a PIN is six digits, and a phone left unlocked on a counter is a phone anybody can pick up. PartyBook is built for a shared counter handset and its sign-in reflects that. Treat the phone as the key.
13. Children
PartyBook is business software. It is not intended for or directed at children, and accounts are issued to businesses rather than to individuals who sign themselves up.
We do not knowingly collect personal data from anyone under 18, which is how the Digital Personal Data Protection Act, 2023 defines a child. We do not track children, profile them, or show them advertising — we do none of those things to anybody. If you believe a person under 18 has an account, tell us and we will remove it.
14. Changes to this policy
If it changes in a way that matters, we will change the date at the top and tell the businesses using PartyBook by email.