BB BBook
Home Privacy Terms Your Rights Contact
Raise a Concern
Privacy

Privacy Policy

What BBook collects, why we need each item, who can see it, and how long we keep it — in plain English, with nothing hidden behind vague phrasing.

Last updated: 12 November 2026 Version 1.0 Pending legal review

On this page

  1. Who operates BBook
  2. The data we process
  3. What we never collect
  4. What your ride partner can see
  5. Location and live GPS
  6. Who else handles your data
  7. How long we keep data
  8. Age policy (18+)
  9. Your rights
  10. Withdrawing consent
  11. How we protect your data
  12. Grievances and the Data Protection Board
  13. Legal status of this notice
  14. Changes to this notice

1 Who operates BBook

BBook is a bike seat-sharing platform for office commuters. A rider who is already travelling from home to work shares the empty pillion seat with a passenger going the same way, and the passenger contributes towards the fuel cost.

BBook is run by an individual, not a company. For the purposes of the Digital Personal Data Protection Act, 2023, the Data Fiduciary — the person who decides what is done with your personal data — is:

Data FiduciaryAnkit Kesarwani, an individual sole proprietor, operating as BBook
Registered address[REGISTERED ADDRESS — TO BE CONFIRMED]
Websitehttps://bbook-web.online
Privacy & grievance contactprivacy@bbook-web.online
Grievance OfficerAnkit Kesarwani

This notice covers the BBook Android app, this website at bbook-web.online, and the separate internal admin dashboard our team uses to review vehicle submissions and handle grievances.

2 The data we process, and exactly why

Below is every category of personal data BBook processes. If something is not in this table, we do not collect it.

Data What we collect Why we need it Is it optional? Who can see it How long we keep it
Full name The name you type during onboarding. To show the other person on a ride who they are travelling with, and to identify your account in support and grievance handling. No — required to create an account. You, the BBook admin team, and your ride partner (first name only until a booking is accepted). Life of your account, then anonymised 30 days after deletion.
Mobile number Your 10-digit mobile number. So the rider and passenger can call each other to agree a pickup point once a booking is accepted. No — required to create an account. You, the BBook admin team, and your ride partner only after the booking is accepted. Life of your account, then anonymised 30 days after deletion.
Work email address The email address you enter at sign-in. To send the one-time password (OTP) that signs you in, and to send account and grievance correspondence. No — it is how you log in. You and the BBook admin team. The OTP email is delivered by our email provider. Life of your account, then anonymised 30 days after deletion.
Profile photo A photo you upload yourself. So your ride partner can recognise you at the pickup point. Yes — you can use the app without uploading a photo. You, the BBook admin team, and anyone who sees your ride or booking card in the app. Life of your account; deleted from storage on account deletion.
Role Whether you are using BBook as a rider, a passenger, or both. To decide which screens and matches to show you, and whether vehicle verification applies to you. No — the app needs to know which side of the ride you are on. You, the BBook admin team, and your ride partner. Life of your account.
Verification status Whether your account and vehicle have been reviewed by our admin team. To display the verified badge so the other person knows a review has taken place. No — it is generated by us, not collected from you. You, the BBook admin team, and anyone who sees your profile in the app. Life of your account; the decision record is kept 3 years.
Home address and its coordinates The address text you type or pick, and the latitude/longitude derived from it. To match you with people whose home is within roughly 1.5 km of yours, so the detour is realistic. No — matching cannot work without it. You and the BBook admin team. Your ride partner sees the agreed meeting point, not your saved home address, until a booking is accepted. Life of your account.
Office address and its coordinates The address text you type or pick, and the latitude/longitude derived from it. To match you only with people whose office is within roughly 200 m of yours. No — matching cannot work without it. You and the BBook admin team; the office area is shown on ride cards to people you are matched with. Life of your account.
Ride pickup and drop points The meeting point and destination attached to a published ride or a booking. So both people know exactly where to meet and where the ride ends. No — a ride cannot be published or booked without them. You, the BBook admin team, and your ride partner (the exact meeting address only after the booking is accepted). 3 years as part of the ride record; anonymised if you delete your account.
Live GPS location during an accepted ride Your device's live position while the ride screen is open. To show the live distance between rider and passenger so you know when your ride partner is arriving. Yes — you can decline the location permission; the live distance feature then will not work. Only the two people on that accepted ride, over a private realtime channel. Not stored. It exists only while the ride screen is open and stops when the ride ends.
Bike model The make and model you enter for your bike. So a passenger can identify the bike at the pickup point. No for riders; not collected from passengers. You, the BBook admin team, and passengers who see your ride. Life of your account; 3 years in the verification record.
Bike registration number The number plate you enter for your bike. So our admin team can review the vehicle, and so the passenger can confirm they are getting on the right bike. No for riders; not collected from passengers. You and the BBook admin team; the passenger sees it only after the booking is accepted. Life of your account; 3 years in the verification record.
Vehicle verification record The documents and details you submit for review, and our admin team's decision with its date. To run the admin review behind the verified badge, and to keep a record of why a decision was taken in case it is disputed. Yes — you may ride without submitting for verification, but you will not receive the verified badge. You and the BBook admin team. 3 years from the decision, for dispute resolution and safety.
Push notification device token An identifier your phone's operating system gives to the app. To deliver ride, booking and payment notifications to your device. Yes — you can decline notification permission or revoke it in your phone settings. You cannot see it; the BBook admin team and our push delivery provider handle it. Until you log out, uninstall the app, or 90 days of inactivity.
In-app notification records The title and body of alerts we have sent you, and whether you read them. To show your notification history in the app and to let you check what you were told and when. No — it is a by-product of using the app. You and the BBook admin team. 12 months.
UPI ID (riders only) The UPI ID you enter so the app can generate your payment QR code. To generate the QR code a passenger scans to pay you directly after the ride. Yes — but without it a passenger cannot pay you through the app's QR flow. You and the BBook admin team; the passenger sees it only after the booking is accepted. Life of your account; removed when personal data is anonymised.
Fare, payment status, booking reference and timestamps The agreed amount, whether it was marked paid, the booking reference, and the times the ride was published, booked, started and completed. To show both people the status of the ride and the payment, to settle disputes, and to meet tax record-keeping obligations. No — these are created by using the service. You, your ride partner (for your shared ride) and the BBook admin team. 3 years; retained in anonymised form if you delete your account.
Authentication session data The login session your device holds after a successful OTP sign-in. To keep you signed in without asking for an OTP on every screen. No — it is how login works. You and our database and authentication provider. Until you log out or the session expires; revoked immediately on account deletion.
Security and audit logs Records of privacy-relevant actions, such as a data export, a deletion request or an admin verification decision. To prove that privacy requests were actioned, and to investigate misuse of an account. No — we need these to show we handled your request. The BBook admin team. 12 months.
IP address and device metadata The network and device information our hosting providers receive when your app or browser connects. Handled by our hosting providers to route requests, apply rate limits and block abuse. No — it is inherent to any internet connection. Our hosting providers; the BBook admin team sees it only in provider logs. As per each provider's own log retention; we do not copy it into our database.
Website feedback form Name, phone number, email address, city, sector and your message, when you submit the form on our homepage. To read and reply to your feedback and to understand where commuters want BBook to launch. Yes — the whole form is voluntary. The BBook admin team. 24 months.

Scroll the table sideways on a small screen to see every column.

3 What we never collect

  • No UPI PINs, passwords, card numbers or bank details. The payment happens entirely inside your own UPI app. Money moves directly from the passenger to the rider. BBook never holds your money and never sees your payment credentials.
  • No passwords for app users. You sign in with a one-time password sent to your email, so there is no password for us to store.
  • No chat. BBook has no in-app messaging, so there are no message contents to store.
  • No call recording or interception. The tap-to-call button simply opens your phone's own dialler. We do not record, log, listen to or route your calls.
  • No stored live GPS trail. See Location and live GPS below.
  • No analytics, advertising or cross-site tracking on this website. See our Cookie Policy.

4 What your ride partner can see, and when

This is the rule that matters most to most people, so we will be precise about it.

Before a booking is accepted

A passenger browsing rides sees only:

  • the rider's first name;
  • the rider's profile photo, if one was uploaded;
  • the verified badge, if the vehicle has been reviewed; and
  • the bike model.

Only after the rider accepts the booking

These details become visible to the passenger:

  • the rider's phone number;
  • the bike registration (plate) number;
  • the exact meeting address; and
  • the rider's UPI ID, so the payment QR code can be generated.

The same rule applies in reverse. Until the rider accepts, they see only the passenger's limited profile. The passenger's phone number and exact meeting address become visible to the rider only once the booking is accepted.

Cancelling

If a booking is cancelled, the ride no longer appears in the other person's active list. We cannot, however, undo what the other person has already seen or written down. Share only what you are comfortable sharing with a fellow commuter.

5 Location and live GPS

Addresses you save

Your home and office addresses are stored, together with the coordinates derived from them, because proximity matching is the whole product: we only show you rides where the office is within roughly 200 m and the home within roughly 1.5 km of yours. The address text you type is sent to our mapping provider to be converted into coordinates.

Live GPS during a ride

Once a booking is accepted, the app can show how far apart the rider and the passenger are, so you know when your ride partner is arriving. To be exact about how that works:

  • Live position is exchanged only between the two people on that accepted ride, over a private realtime channel.
  • It is not written to our database. There is no location history, no trail and no map of where you have been.
  • It exists only while the ride screen is open and stops when the ride ends or the screen is closed.
  • You can refuse the location permission in your phone's settings. Everything else in the app still works; only the live distance feature does not.

6 Who else handles your data

BBook does not sell your personal data and does not share it for advertising. We do rely on service providers (Data Processors) to run the service. Each one receives only what it needs to do its job:

ProviderWhat it does for BBookWhat it receives
SupabaseDatabase, authentication, file storage and the realtime channel.Effectively all account, ride, booking and payment-reference data, plus your profile photo.
Google FirebasePush notification delivery (FCM) and hosting for this website.Your device notification token and the notification contents; web request metadata for the website.
ResendDelivers the login OTP email from the bbook-web.online domain.Your email address and the OTP message.
Ola MapsConverts the address text you type into coordinates.The address text you type.
RazorpayAn optional fallback payment route. It is in test mode only and is not used for live money today.Payment-related fields only if that route is used.
NetlifyHosts the separate internal admin dashboard.Web request metadata from admin users; application data is fetched from Supabase, not stored at Netlify.
NamecheapDNS for our domain.No personal data.
Data-processing agreements: pending

We want to be honest about this. Formal written data-processing agreements with the providers listed above have not yet been executed. Putting those contracts in place is an open item on our compliance plan, and we are not claiming otherwise.

We may also disclose data where we are legally required to — for example in response to a lawful order from a court or a competent authority.

7 How long we keep your data

In short: active data lives as long as your account does; records we need for tax, disputes and safety are kept for three years in a form that no longer identifies you.

When you delete your account

Pressing Delete Account in the app starts a two-stage process:

  1. Immediately. Your sessions are revoked, your open rides and bookings are cancelled, and your profile stops being visible to anyone else. You are, in effect, off the platform at once.
  2. After a 30-day grace period. Your personal data is permanently anonymised. The grace period exists so that an accidental or disputed deletion can be reversed before anything becomes irreversible.

Ride and payment records survive that anonymisation, but without your name, phone number, email, addresses or UPI ID. What remains is a bare record that a ride took place, for what amount, and when. We keep those for three years for tax, dispute-resolution and safety purposes.

Our full table of retention periods, and how each kind of record is deleted or anonymised, is in the Data Retention Policy.

8 Age policy: BBook is for adults only

BBook is an 18+ service. We do not knowingly onboard anyone under 18 and we do not process children's data. We do not run any profiling, advertising or tracking directed at children.

If you believe someone under 18 has created an account, write to privacy@bbook-web.online and we will remove the account and its personal data.

9 Your rights over your data

You can ask us to do the following with your personal data:

  • Access and export — get a machine-readable JSON copy of your data, from inside the app at Profile → Privacy & Data.
  • Correction — fix anything inaccurate, incomplete or out of date. Most fields you can edit yourself in the app.
  • Erasure — delete your account and have your personal data anonymised, as described above.
  • Withdraw consent — see the next section.
  • Nomination — nominate another person to exercise these rights on your behalf if you die or become incapable of doing so yourself.
  • Grievance redressal — complain to us about how we have handled your data, and escalate if we do not resolve it.

Each right, and exactly how to use it, is set out on Your Privacy Rights. The short version: use Profile → Privacy & Data in the app, or email privacy@bbook-web.online.

10 Withdrawing your consent

You can withdraw consent at any time, and you do not have to withdraw all of it at once:

  • Location. Revoke the location permission in your phone's settings. The live distance feature stops working; nothing else breaks.
  • Notifications. Revoke the notification permission in your phone's settings, or log out, and we stop sending pushes to that device.
  • Profile photo and UPI ID. Remove them in the app. The photo is deleted from storage; without the UPI ID the QR payment flow will not work for you.
  • Everything. Delete your account from Profile → Privacy & Data, or email us.

Withdrawing consent is not retroactive: it does not undo processing that already lawfully happened, and it does not erase the anonymised ride and payment records we are required to keep. Some data is genuinely necessary to provide the service at all — your name, mobile number, email and addresses — so withdrawing consent for those means closing your account.

11 How we protect your data

Described plainly, and only what is actually in place:

  • Encryption in transit. All traffic between the app, this website, the admin dashboard and our backend runs over TLS (HTTPS).
  • Encryption at rest. Data stored in our database and file storage is encrypted at rest by our hosting provider.
  • Row-level access control. Our database enforces row-level security policies, so a signed-in user's queries can only reach the rows they are entitled to see — for example, their own profile and the rides and bookings they are party to.
  • Role-based admin access. The admin dashboard is restricted to accounts explicitly linked to an admin role. Admin-only operations run through controlled database functions rather than open table access.
  • Audit logging of privacy actions. Privacy-relevant events — exports, deletion requests, verification decisions — are logged so we can show what was done and when.
  • OTP login, no stored passwords. App users sign in with a one-time password sent to their email. There is no user password in our systems to leak.
  • Minimised contact sharing. Phone numbers, plate numbers, meeting addresses and UPI IDs are released only after a booking is accepted, as described in section 4.

No system is perfectly secure. If a personal data breach occurs, we will notify affected users and the Data Protection Board of India in the manner and within the timelines the DPDP Rules require once those provisions are in force, and we will tell you what happened and what to do about it. Breach-related queries also go to privacy@bbook-web.online.

12 Grievances and the Data Protection Board

If you are unhappy with how we have handled your personal data, raise it with us first:

Grievance OfficerAnkit Kesarwani
Emailprivacy@bbook-web.online
Online formRaise a privacy concern — you will receive a reference number
Our response targetWe aim to respond within 30 days of receiving your complaint

If we do not resolve your grievance, you may approach the Data Protection Board of India once it is operational and accepting complaints. The Board is being constituted under the Digital Personal Data Protection Act, 2023; we will update this page with its filing route as soon as that route exists.

13 The legal status of this notice

We would rather be accurate than impressive, so:

  • The Digital Personal Data Protection Act, 2023 is law.
  • The DPDP Rules were notified on 13 November 2025 with a phased commencement. Rules 1, 2 and 17–21 took effect on notification. Rule 4, on consent managers, follows about 12 months later. Rules 3, 5–16, 22 and 23 — which carry most of the substantive duties, including the prescribed notice format, security safeguards, breach reporting, and retention and erasure obligations — follow about 18 months later, around 13 May 2027.
  • BBook is building to align with these requirements ahead of those deadlines. That is the honest description of where we are.
What we are not claiming

BBook is not certified, not government approved, and we do not claim to be fully DPDP compliant. These pages are not legal advice and are pending review by qualified Indian privacy counsel. Where a fact is still to be settled, we have left a visible placeholder rather than invent one.

14 Changes to this notice

When we change what we collect or how we use it, we will update this page, change the version number and the "last updated" date at the top, and — for changes that materially affect you — notify you in the app or by email.

This is Version 1.0, last updated 12 November 2026.

12 November 2026 · Version 1.0 Back to top
BB BBook

A bike seat-sharing platform that connects verified office professionals travelling along similar daily routes — trusted, convenient, and affordable.

Product

How It Works Features Safety Benefits

Company

For Investors Contact Us Give Feedback

Legal

Privacy Policy Terms & Conditions Cookie Policy Data Retention Your Privacy Rights Raise a Privacy Concern Contact
© 2026 BBook. All rights reserved. Operated by Ankit Kesarwani, sole proprietor, trading as BBook.