BIDUAGOAndroid app
Legal

Privacy Policy

Last updated: November 2025 · Effective immediately for the BIDUAGO mobile app (Android & iOS) and biduago.com.

Information in different app workflows

The relevant inputs depend on the utility you use: ride routes, seats and bookings; linked children, school assignments and boarding records; vehicle details and expenses; INR wallet entries and dispute evidence; or identity and payout-account details for the relevant check. Submit only information you are authorised to provide. Provider-backed verification and OCR are separate methods, and text extraction alone is not proof of authenticity.

What we believe

BIDUAGO collects only what we strictly need to run the service — find you cheap fuel, plot your route, send roadside help, and pay out your Fuel Coins. We do not sell your data. We do not run ad networks. We comply with the Digital Personal Data Protection Act, 2023 (DPDP Act) of India.

Photo uploads — how we protect you

When you contribute a station photo, your phone's camera typically embeds GPS coordinates, device serial, lens info, capture time, and sometimes thumbnails of nearby photos into the image metadata (EXIF / IPTC / XMP / ICC). Leaving that data on a public image is a real privacy risk.

Here is what BIDUAGO does the moment a photo arrives at our server:

  1. The file is magic-byte sniffed — we reject anything that isn't a real JPEG, PNG, WebP, HEIF, or AVIF, even if the filename says otherwise.
  2. We refuse images larger than 8 MB or with pixel dimensions above 5000 × 5000 — this blocks pixel-bomb attacks.
  3. The image is fully decoded and re-encoded using sharp. This neutralises any embedded shell-code, polyglots, or malformed sections.
  4. ALL metadata is stripped — EXIF, GPS coordinates, device fingerprints, IPTC, XMP, and ICC profiles. The output is a clean JPEG with zero ancillary data.
  5. The file is saved under a server-generated UUID (e.g. 35fe0d1a-…jpg). The filename you chose on your device is never persisted.
  6. The original bytes are discarded immediately after a successful re-encode.
  7. Files are served with X-Content-Type-Options: nosniff and Cross-Origin-Resource-Policy: cross-origin headers so browsers cannot be tricked into executing them.

Account & API security

  • • All write endpoints require a signed JWT bound to your phone number.
  • • Anonymous reads are limited to public station data (price, hours, address).
  • • Per-account rate limits on uploads (20 / minute) prevent abuse.
  • • Passwords (where used) are hashed with bcrypt. We never see your plaintext.

Location data

Location is processed transiently in memory to return nearby stations. We do not store your minute-by-minute location history. When you contribute a station pin, we store only the coordinates you tapped on — not your phone's actual position.

Vehicle data

When you add a vehicle, we fetch RTO/Vahan public records to pre-fill make, model, registration year, and fitness status. Insurance & PUC expiry dates you enter are stored only on your account for the sole purpose of sending you renewal reminders.

Encryption

All API traffic uses TLS 1.2+. Personal data at rest is encrypted using PostgreSQL transparent disk encryption. Backups are encrypted with AES-256.

Your DPDP Act rights

Under the DPDP Act 2023, you have the right to: access your data, correct it, erase it, withdraw consent, and nominate a successor. Use the in-app Profile → Privacy → Export my data or Delete my account controls — both complete within 7 working days.

Contact

Privacy questions, takedown requests, or DPDP grievances: privacy@biduago.com. Our Data Protection Officer responds within 72 hours.