1. Who we are and what this covers
Tokenwala (“Tokenwala”, “we”, “us”) is a software platform operated by [legal entity name], [registered address], India. It lets event organizers and outlets (“Organizers”) run closed-loop digital tokens and prepaid passes for their own event or outlet, lets stalls and counters (“Stalls”) accept them, and lets guests (“Guests”, “you”) top up and pay.
This policy explains what personal data we process through the Tokenwala mobile apps, the web wallet, the organizer web app and this website (together, the “Services”), why, and the choices and rights you have. It is written with the Digital Personal Data Protection Act, 2023 (“DPDP Act”) and the rules made under it, and the Information Technology Act, 2000 and its rules, in mind.
2. Our role and the Organizer’s role
Two kinds of party decide how your data is used:
- Tokenwala as Data Fiduciary for your Tokenwala account: your phone number, name, profile photo, devices, security settings, sign-in records, and the operation, security and improvement of the platform.
- The Organizer as Data Fiduciary for the event or outlet you join: your pass at that event, your top-ups, payments, refunds and any information the Organizer asks for. For this data Tokenwala acts as the Organizer’s Data Processor, processing it on their behalf and under their instructions, under a written agreement.
Payment gateways (such as Razorpay or Cashfree) that the Organizer connects process your payment details under their own privacy policies. Tokenwala never receives your full card number, UPI PIN or bank credentials.
3. What we collect
| Category | Examples | Source |
|---|---|---|
| Account | Mobile number (verified by one-time password), name, optional profile photo, preferred language and theme | You |
| Passes and ledger | Passes you hold, balances, top-ups, payments, refunds, transfers, gifts, donations, receipt codes, timestamps, the stall and event involved | Created when you use the Services |
| Payment references | Gateway order and payment IDs, payment method type (e.g. UPI, card), amount, status, refund status | The Organizer’s payment gateway |
| Family and sub-passes | Names you give sub-passes, daily limits, blocked items and time rules you set | You (as parent or guardian) |
| Security | A public key for device-bound payment approvals, a salted hash of your payment PIN, Quick Pay settings, failed-PIN counts, device identifiers, app version, IP address | Your device and our servers |
| NFC bands and cash cards | Band or card identifier linked to a pass; whether it is active or blocked | The counter that assigns it |
| Stall and organizer data | Business or stall name, contact person, phone, email, UPI/bank details for payouts (held by the Organizer), menu items and prices, staff members and roles | Organizers and Stalls |
| Support | Problems you report on a transaction, messages to us, and our replies | You |
| Technical | Crash reports (only if enabled), diagnostic logs, rate-limit counters keyed to a hashed IP address | Your device and our servers |
Biometrics stay on your phone. When you approve a payment with Face ID or a fingerprint, your phone’s operating system checks it locally and only tells the app “approved”. We never receive or store your face or fingerprint data.
No location tracking, contacts or microphone. The “₹80 received” voice alert is text-to-speech played on the stall’s phone; nothing is recorded. The camera is used only to scan QR codes when you choose to.
4. Why we use it
- To provide the Services: create your account, issue and run passes, process top-ups, payments and refunds, show balances and receipts, and let Stalls and Organizers see the payments made to them.
- To keep money safe: verify approvals, enforce Quick Pay caps and PIN locks, detect unusual activity (for example many rejected payments or PIN failures), freeze lost phones and bands, and reconcile our ledger against gateway and cash records.
- To meet legal duties: keep transaction records, respond to lawful requests from authorities, handle grievances and meet tax and accounting rules.
- To communicate: one-time passwords, payment and refund notifications, low-balance and spend alerts you turn on, service messages, and, only if you opt in, WhatsApp receipts.
- To improve the Services: fix bugs and understand aggregate usage. We do not sell personal data and we do not use it for third-party advertising.
5. Consent and legitimate uses
We process your personal data on the basis of your consent, which you give when you create an account and accept this policy, and which you may withdraw at any time (see Your rights). Withdrawing consent does not affect processing already done, and we may need to keep some records afterwards where the law requires.
Some processing relies on the legitimate uses recognised by Section 7 of the DPDP Act — for example, where you voluntarily provide data for a specific purpose such as a top-up, or where we must comply with a law or court order.
6. Who we share it with
- The Organizer of an event or outlet you join: your name, masked phone number, pass, top-ups, payments, refunds and any problem you report at that event.
- Stalls you pay: your first name or pass label, masked pass number, amount, items and time.
- Payment gateways connected by the Organizer (for example Razorpay, Cashfree) to take top-ups and process refunds.
- Service providers who help us run the Services under contract, including cloud hosting and database ([e.g. Supabase, region]), SMS/OTP delivery, push notifications, email, and crash reporting (only if enabled). If you opt in: WhatsApp Business messaging, Apple Wallet and Google Wallet passes.
- Authorities where required by law, court order or to protect the rights, property or safety of users or the public.
- A successor if Tokenwala is merged or acquired, subject to this policy.
We do not sell or rent personal data.
7. Where data is stored
We aim to store production data in India ([Mumbai region]). Some service providers may process limited data outside India. Any such transfer will follow Section 16 of the DPDP Act and any restrictions notified by the Government of India.
8. How long we keep it
- Ledger and transaction records are kept for as long as needed for refunds, disputes, reconciliation and the record-keeping periods required by tax, accounting and payment laws ([e.g. 8 years]), even after an account is deleted. The ledger is append-only, so corrections are recorded as new entries.
- Account data is kept while your account is active and deleted or anonymised within [30 days] of a verified deletion request, except what must be kept as above.
- Security logs and rate-limit counters are kept for [90 days] unless needed for an investigation.
- Crash reports are kept for [90 days].
9. Your rights
Under the DPDP Act you may:
- Access a summary of the personal data we process about you and the processing activities (the app’s data export gives you a copy of your account and transactions);
- Correct, complete or update inaccurate or incomplete data;
- Erase your data, subject to the retention duties above (use “Delete account” in the app, or see how to delete your account without it);
- Withdraw consent at any time, with the same ease with which you gave it;
- Nominate another person to exercise your rights in the event of your death or incapacity;
- Seek grievance redressal from us, and then, if unresolved, complain to the Data Protection Board of India.
For data an Organizer controls, we will pass your request to that Organizer and help them respond. Before deleting an account with a balance, please ask for a refund where the event allows it; balances on deleted accounts follow the Organizer’s leftover policy.
10. Children
Under the DPDP Act a child is anyone under 18. Children should use Tokenwala only through a family sub-pass created and managed by a parent or lawful guardian, or with an NFC band or cash card the guardian obtains. By creating a sub-pass, the guardian gives verifiable consent for the limited processing needed to run it (a label, limits, payments and alerts). We do not knowingly create accounts for children, track them, monitor their behaviour, or show them targeted advertising.
11. Security
We use reasonable security safeguards, including encryption in transit, access control at the database row level, signed and time-limited payment codes, device-bound approval keys, hashed PINs, encrypted storage of gateway keys, rate limits, audit logs and nightly reconciliation. No system is perfectly secure. If a personal data breach occurs, we will notify the Data Protection Board of India and affected users as required by the DPDP Act and its rules.
12. Cookies and this website
This website does not use advertising or tracking cookies and loads no third-party analytics. The web wallet and organizer app store a sign-in session and preferences in your browser’s local storage so you stay signed in; clearing site data signs you out.
13. Changes to this policy
We will post updates here and change the date at the top. For material changes we will notify you in the app before they take effect and, where the law requires, ask for your consent again.
14. Grievance Officer and contact
For questions, requests or complaints about personal data, contact our Grievance Officer:
[Name], Grievance Officer, [legal entity name], [address]
Email: hello@tokenwala.co [replace with a dedicated grievance address]
We will acknowledge your request within [48 hours] and aim to resolve it within [30 days]. If you are not satisfied, you may approach the Data Protection Board of India.