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

Data Retention Policy

Exactly how long each record lives, the purpose that justifies keeping it, and the method by which it is deleted or anonymised. Live GPS is never stored at all.

Last updated: 12 November 2026 Version 1.0 Pending legal review

On this page

  1. The principle we work to
  2. Retention table
  3. What happens when you delete your account
  4. What anonymisation actually means
  5. When we keep data longer
  6. These periods are not yet legally confirmed
  7. Questions and early deletion

1 The principle we work to

Personal data should not be kept because it might be useful one day. It should be kept for as long as it is needed for a stated purpose, and then removed.

BBook applies that in three tiers:

  • Live account data — kept while your account exists, because the service cannot run without it.
  • Transaction and safety records — kept for three years, because tax record-keeping, payment disputes and safety investigations genuinely need them. After an account is deleted, these survive only in anonymised form.
  • Operational records — notifications, logs, device tokens, website feedback — kept for shorter, fixed windows and then deleted.

This policy sits alongside our Privacy Policy, which explains what we collect and why.

2 Retention table

Each row gives what the record contains, the purpose that justifies keeping it, the period, and the method by which it is removed.

Record What it contains Purpose Retention period How it is deleted or anonymised
Account profile Name, mobile number, email, profile photo, role, verification status. To run your account, show your ride partner who they are travelling with, and handle support and grievances. Life of the account. After deletion: anonymised 30 days later. Deactivated immediately on deletion (sessions revoked, profile hidden). At the end of the 30-day grace period, identifying fields are overwritten or removed and the profile photo is deleted from file storage.
Home and office addresses Address text plus the coordinates derived from it. Proximity matching — office within ~200 m, home within ~1.5 km. Life of the account. Overwritten when you edit them. Removed when the account is anonymised; coordinates are cleared with the address.
Live GPS location Your device position while an accepted ride's screen is open. To show the live distance between rider and passenger. Not stored at all. Nothing to delete. It is exchanged over a private realtime channel between the two people on the ride and is never written to the database. It stops when the ride ends or the screen is closed.
Ride records Route endpoints, meeting point, seats, departure time, status, and which accounts were involved. To give both sides a record of the ride, resolve disputes, and support safety investigations. 3 years. Anonymised sooner if the account is deleted. Account references are replaced with non-identifying values when the account is anonymised, leaving a ride record with no name, phone, address or UPI ID. The record itself is deleted at the end of the 3-year period.
Booking records Booking reference, the ride it belongs to, request and acceptance timestamps, cancellation status. To show booking history, show who cancelled and when, and settle disputes. 3 years. Anonymised with the account; deleted at the end of the 3-year period.
Payment references Fare amount, payment status, booking reference, timestamps. No UPI PIN, password, card or bank details — we never receive those. Tax record-keeping and payment-dispute resolution. The money itself moves directly between the two users' UPI apps. 3 years, for tax and dispute purposes. The rider's UPI ID is removed when the account is anonymised; the amount, status and reference remain in anonymised form, then are deleted at the end of the 3-year period.
Vehicle verification records Bike model, registration number, what was submitted, and the admin decision with its date and outcome. To evidence why a verified badge was granted, refused or withdrawn, and to support safety and dispute investigations. 3 years from the decision. Retained through account deletion in a form tied to the decision, not to your identity, then deleted at the end of the 3-year period.
Notification records Title and body of in-app alerts, and whether they were read. To show your notification history so you can check what you were told and when. 12 months. Deleted on a rolling basis once 12 months old; deleted with the account at anonymisation.
Push notification device tokens The identifier your phone's operating system issues to the app. To deliver ride, booking and payment notifications to your device. Until logout, uninstall, or 90 days of inactivity. Deleted on logout and on account deletion. A token that stops working, or is unused for 90 days, is removed.
Consent records What you agreed to, which version of the notice applied, and when. To be able to demonstrate that consent was given, as a Data Fiduciary must. Life of the account, plus 3 years as proof of consent. Kept deliberately through anonymisation, stripped to the minimum needed to evidence consent, then deleted at the end of the 3-year period.
Grievance records Your complaint, the reference number, our correspondence and how it was closed. To handle your complaint, evidence that we handled it, and respond if it is escalated. 3 years after closure. Deleted 3 years after the complaint is closed. Retained even if you delete your account, since it is the record of a request you made to us.
Security and audit logs Privacy-relevant events: data exports, deletion requests, admin verification decisions, administrative access. To prove privacy requests were actioned and to investigate account misuse. 12 months, aligning with the one-year expectation in Rule 6 of the DPDP Rules. Deleted on a rolling basis at 12 months. Entries are kept pseudonymised where the log's purpose still works without your identity.
Website feedback Name, phone number, email, city, sector and message from the homepage feedback form. To read and reply to your feedback and to see where commuters want BBook to launch. 24 months. Deleted 24 months after submission, or sooner on request to privacy@bbook-web.online.

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

3 What happens when you delete your account

Pressing Delete Account in Profile → Privacy & Data runs two stages.

Stage 1 — immediately

  • Your login sessions are revoked, so the account cannot be used.
  • Any rides you have published and any open bookings are cancelled, and the other side is notified.
  • Your profile stops being visible to other users and disappears from matching.

Stage 2 — after a 30-day grace period

  • Your personal data is permanently anonymised: name, mobile number, email, profile photo, home and office addresses and UPI ID are removed or overwritten.
  • Ride, booking and payment records remain in anonymised form for the rest of their three-year period.

The grace period exists so that an accidental deletion, or one made in the middle of a dispute, can be undone before anything becomes irreversible. If you want your data anonymised sooner than 30 days, email privacy@bbook-web.online from your registered address and we will action it.

4 What anonymisation actually means

We use the word carefully. When a record is anonymised:

  • the identifying fields — name, phone number, email, home and office addresses, profile photo and UPI ID — are removed or overwritten, not merely hidden from a screen;
  • what survives is the shape of the transaction: that a ride took place between two accounts, on a route, at a time, for an amount, with a status; and
  • we do not keep a separate key that would let us re-attach your identity to those rows.

Two honest caveats. First, anonymisation is applied to our own database; copies that have already passed through a provider's systems are governed by that provider's own retention. Second, no anonymisation is mathematically perfect — a small enough dataset can in principle be narrowed down. We keep the surviving fields minimal for exactly that reason.

5 When we keep data longer

We may keep specific data beyond the periods above where we are required or clearly entitled to:

  • to comply with a legal obligation, a tax requirement, or a lawful order from a court or competent authority;
  • to defend or pursue a legal claim, or to deal with an ongoing dispute, for as long as it is live;
  • to investigate a safety incident, fraud, or serious misuse of the platform; or
  • where you have specifically asked us to keep something, for instance while a grievance is open.

Where we do this, we keep only the data the specific reason needs, and delete it when the reason ends.

6 These periods are a business decision, not yet legally confirmed

Read this before relying on the numbers above

Every period in the table is a business decision we have taken, based on the retention we believe tax, dispute-resolution and safety purposes require. They are pending confirmation by qualified Indian legal counsel and may change once reviewed.

On the legal framework: the Digital Personal Data Protection Act, 2023 is law, and 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 the substantive duties including security safeguards, breach reporting and the retention and erasure obligations — follow about 18 months later, around 13 May 2027.

We are building to align with those requirements ahead of the deadlines. We are not claiming to be certified, government approved or fully DPDP compliant. The 12-month log retention above is set with the one-year expectation in Rule 6 in mind; it will be reviewed against the final position when those rules commence.

7 Questions, and asking us to delete something early

If you want to know what we hold, have something corrected, or have data deleted sooner than the periods above:

  • In the app — Profile → Privacy & Data for a JSON export of your data, or to delete your account.
  • By email — privacy@bbook-web.online, from the address registered on your account so we can confirm it is really you.
  • By complaint — the grievance form, which gives you a reference number.

We aim to respond within 30 days. Statutory timelines will apply once the relevant Rules commence. Your full set of rights is explained on Your Privacy Rights.

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.