Privacy policy
Last updated 20 November 2026
Nimbuu runs digital loyalty cards for cafes and salons in India. This page says what we keep, why, who sees it, how long we keep it and what you can do about it. It is written for India's Digital Personal Data Protection Act, 2023.
Who we are
"Nimbuu", "we" and "us" mean the team that runs Nimbuu. For anything on this page, write to privacy@nimbuu.in.
Who decides what happens to your data depends on which part of Nimbuu it is:
- Your card at a shop. The shop decides why it keeps your card: to run its own loyalty card. The shop is responsible for that data, and Nimbuu runs the card for the shop.
- Your Nimbuu login. Your phone number and the codes we send to check it work across every shop where you have a card. Nimbuu decides how that works and is responsible for it.
- Owner and staff accounts. Shop owners, managers and counter logins have their accounts with Nimbuu, and Nimbuu is responsible for them.
What we keep
Customers
- Your phone number.
- Your name and birthday, only if the shop adds them.
- Your language, English or Hindi.
- For each card: the balance and its history, meaning each stamp or point added or used, the date, the outlet, the bill amount and bill number if the shop enters them, and any note staff typed when changing your balance.
- When you said yes or no to the card's notice and to messages, with the date.
- A list of the codes and messages sent to you: what kind and when, not the text.
Shop owners and staff
- An email address, or a username for a counter login, and a name if one is added.
- A password, kept only as a hash that nobody can read back.
- Your role, your outlet and when you last logged in.
- The shop's details: its name, outlets and their addresses, logo, colour, card rules and rewards.
- A record of changes made by hand: balance changes and their reason, staff changes, and API keys made or revoked, with who made them and when.
The pilot sign-up form
- Your business name, your name, your WhatsApp number, the type of business, the area, and when you sent the form.
Technical data
- Our logs say what the service did, for example "a stamp was added to card 123". Phone numbers and codes are masked in them.
- To stop abuse, we count requests for a short time, at most a day: for example per IP address, per phone number for codes, per username for logins, and per card at the counter. The counts then expire.
Why we use it
- To run your card: show your balance, add stamps or points and give rewards.
- To check it's you: we send a 6-digit code to your phone when you join, open your card on a new phone, take a reward that needs a code, or delete your card.
- To send messages for the shop, only if you said yes: a welcome with the link to your card when you join, a note after each visit, when a reward is ready, before your balance expires and on your birthday. You can turn them off any time. When a shop makes your card at the counter, we may send you that one welcome before you have said yes. These messages have not started yet: they will go out on WhatsApp once we connect it, and only to people who said yes.
- To prevent fraud and abuse: limits on codes and requests, a code before some rewards, and codes only to Indian (+91) numbers.
- To keep the shop's accounts right: a card's history is never changed. Corrections are added as new entries.
- To run owner and staff accounts, and to reply to pilot sign-ups.
Who sees it
- The shop your card belongs to: your number, name, birthday, balance and history at that shop. The shop can download its list of members. Other shops never see your card there, even if you have a card with them too.
- Software the shop connects: if a shop connects its billing software or website to Nimbuu, that software can read the shop's own cards.
- Our service providers, only to run Nimbuu: our hosting provider (servers in India), the SMS provider that sends codes, WhatsApp (Meta) for messages once we use it, and an email provider for owners' password emails. Each gets only what it needs, for example your phone number and the code. WhatsApp may handle a message outside India.
- The authorities, when the law requires it.
We don't sell your data. We show no ads and use no analytics or third-party trackers.
Cookies
We use only the cookies the service needs. Our fonts and files come from our own server, so our pages don't call other companies' servers.
- nimbu_card keeps you logged in to your card for 90 days, renewed when you use it. Before that, for ten minutes after we send a code and again after you type the right one, it remembers that step, with a hash of your number and never the number itself.
- nimbu_lang remembers whether you read the card in English or Hindi, for a year.
- sessionid keeps owners and staff logged in: 14 days, 12 hours for a counter login, or 30 days with "Keep me logged in on this phone".
- csrftoken stops other websites from sending a form in your name. It lasts a year.
- messages carries a one-time notice, like "Saved.", to the next page in the dashboard or counter app, and is deleted once shown.
The card widget on a shop's own website keeps a 30-minute key in that browser tab only, not in a cookie. Closing the tab clears it. The shop's website may use its own cookies; its own policy covers those.
Where we keep it
On servers in India.
How long we keep it
- Codes: a code works for 5 minutes. Its record, which holds a hash and never the code, is deleted after a day.
- One-time request records that stop a stamp being added twice: deleted after a day.
- The list of codes and messages sent: 90 days.
- Records of what the shop's own software was sent: 30 days.
- Logins: as long as the cookies above say. Ended ones are deleted every day.
- Your card: as long as you keep it. When you delete a card, we delete your name, birthday and language there, unlink your phone number, and clear any balance. The shop keeps the entries of past visits, so its accounts still add up: dates, amounts, outlets, bill numbers, which staff login added each one, and any note staff typed when changing your balance. No name, number or birthday stays attached to them. Staff are asked never to write your name or number in a note. The record of your yes and no answers and the list of messages sent stay too, also without your details; the list goes after 90 days.
- Your phone number: deleted when you delete your last card, or your whole Nimbuu account.
- Owner and staff accounts: while the shop uses Nimbuu. Write to us to close one.
- Pilot sign-ups: until we no longer need them to contact you about the pilot, or sooner if you ask us to remove you.
- Logs: only as long as we need them to fix problems and keep the service safe.
Your rights
- Get a copy: on your card, open Account, then "Your data". The download has your number and, for each card at every shop, your name, birthday, language, balance, history with any staff notes, your yes and no answers, and the messages sent. That is everything we keep about you, apart from which staff login added each entry and security data: login keys, the code in your card's QR and records of codes, which hold only hashes.
- Correct it: change your language on your card, and write to us to fix anything else.
- Delete it: on your card, open Account to delete one card, or all your cards and your Nimbuu account.
- Withdraw consent: turn off "WhatsApp messages" on your card's Account page. It stops the next message.
- Nominate someone to act for you if you die or can't: write to us with their name and how to reach them.
- Complain: write to privacy@nimbuu.in. We reply as soon as we can, and within 90 days at most. If you are not happy with our answer, you can complain to the Data Protection Board of India.
Owners and staff: write to us for a copy of your data, a correction, or to close your account. A shop owner can also switch off a staff login from the dashboard.
Children
Nimbuu is not meant for anyone under 18. If we learn that we hold a child's data without a parent's consent, we delete it.
How we keep it safe
- Every page uses a secure (https) connection.
- Each shop sees only its own cards, and staff can only do what their role allows.
- Codes, passwords and API keys are kept only as hashes.
- Our logs mask phone numbers and codes.
- If a breach affects your data, we tell you and the Data Protection Board of India, as the law requires.
Changes to this policy
When we change this page, we change the date at the top. If a change affects how we use your data, we tell shops first, and ask customers again where the law needs it.
Contact
Write to privacy@nimbuu.in with any question about your data or this policy.