1. Introduction
Freight Pro is a freight and logistics marketplace developed by Nihan Ali VP (Freight Pro Logistics Technologies Private Limited). It connects truck drivers, truck owners, transporters and shippers so that a shipper can find a truck for a route and a truck owner can find a load for a return trip.
This policy is published by Freight Pro Logistics Technologies Private Limited, developed by Nihan Ali VP, Freight Pro Logistics Hub, Outer Ring Road, Bellandur, Bengaluru, Karnataka 560103, India ("Freight Pro", "we", "us"). It covers the Freight Pro Android application, the Freight Pro web application and the servers that power them (together, the "Service").
By creating an account you agree to this policy. If you do not agree, please do not use the Service. Where Indian law applies, we process personal data on the basis of your consent and to perform the service you have requested, as described in the Digital Personal Data Protection Act, 2023 (DPDP Act) and the Information Technology Act, 2000.
The short version: we collect the phone number, profile details, vehicle details and marketplace listings you give us; we show listings to other users; we hide your phone number until you accept a request; we do not run advertising, analytics or location tracking; and you can delete your account and all of its data from inside the app.
2. Information we collect
We collect only the information needed to run the marketplace. The table below lists every category the app and API actually handle.
| Category | What it includes | Why |
|---|---|---|
| Account & sign-in | Mobile phone number in international format (e.g. +91xxxxxxxxxx), a one-time password (OTP) sent by SMS, and the verification status of your number. | To create your account and verify that you own the number. There is no email/password login. |
| Profile | Name, user type (driver, truck owner, transporter or shipper), optional company name, city, district, preferred app language (English/Malayalam), optional profile photo. | To show counterparties who they are dealing with and to personalise the app. |
| Vehicles | Vehicle type, registration number, load capacity, body type, optional vehicle photo, active/inactive flag. | To match loads with trucks. Registration numbers are partly masked for users who are not party to an accepted request. |
| Marketplace content | Truck availability posts (from/to locations, optional intermediate locations, available date, current-location text, capacity, body type, description up to 500 characters, contact preference, optional photo), return-trip posts, and load requests (message up to 500 characters, status). | To publish your listing and to deliver requests between users. |
| Saved items & settings | Posts you bookmark, language choice, notification on/off preference, an unsent post draft. | To remember your choices on your device and account. |
| Uploaded images | Profile, vehicle and post photos you choose to upload (JPEG/PNG/WebP, up to 5 MB per image). | To display your listing. Any photo you attach to a listing is visible to other users. |
| Technical & security data | IP address and request metadata handled by the API and by rate limiting, error logs, and OTP attempt counters. | To keep the Service available, prevent abuse and investigate faults. |
What we do not collect: we do not collect your precise GPS location, your contacts, your SMS inbox, your calendar, your photo library beyond the images you explicitly pick, your advertising identifier, or biometric data. "Current location" and "from/to" are free-text fields you type yourself; the app never reads the device GPS.
3. Personal information
The following categories identify you or can be linked to you, and are treated as personal data:
- Phone number — the account identifier. It is shown to other users only in limited cases (see section 9).
- Name, company name, city and district — shown on your public profile and on your listings.
- Profile photo — shown on your public profile when you add one.
- Vehicle registration numbers — shown in full to you and to users whose request you have accepted; partly masked for everyone else.
- Listings, requests and their messages — visible to the users they are addressed to, and listings are visible to anyone using search.
- Uploaded images — visible wherever the related listing or profile is visible.
Your phone number is not included in public profiles or in public post listings. It is released to the other party only after a load request between you has been accepted, so that you can call each other. You can also choose not to publish a contact preference at all.
4. Device information
The app itself does not read a device identifier. Two limited exceptions exist:
- Push notifications. If the build you installed uses Firebase Cloud Messaging, the app asks the operating system for notification permission and obtains a device push token from Google. The token identifies the app installation, not you. In the current release the token is only used locally to keep the notification channel alive and is not sent to our servers; if a future release registers it with our API, this policy will be updated first.
- Network metadata. Like any HTTPS request, calls to our API expose your IP address and standard HTTP headers (user agent, language) to our servers and to our hosting provider for the duration of the request. We use the IP address for rate limiting and abuse prevention.
We do not collect the advertising ID (GAID/IDFA), IMEI, MAC address, installed-app list, or device fingerprint.
5. Analytics and diagnostics
This release contains no analytics, attribution, advertising or crash-reporting SDK. Specifically, it does not include Google Analytics/Firebase Analytics, Crashlytics, Sentry, AppsFlyer, Meta SDK or any ad network.
Operationally, the API records:
- error logs for server-side failures (HTTP 5xx), which may contain a request path and an error stack trace but no request body or password;
- rate-limit counters derived from the IP address;
- SMS delivery logs in which phone numbers are masked (only the last three digits are stored in the log line).
These logs are used for debugging and security only, are not used for profiling or advertising, and are retained for 30 days.
7. Third-party services and SDKs
| Provider | Purpose | Data involved |
|---|---|---|
| SMS gateway / DLT operator Mapthrust Technologies |
Delivers the login OTP by SMS (India DLT-registered template). | Phone number, the OTP message, and delivery metadata. |
| Hosting & database MongoDB Atlas & Cloud Infrastructure (Asia Pacific / Mumbai Region) |
Runs the API and stores the marketplace database and uploaded images. | All data described in sections 2–4, stored on the provider's infrastructure. |
| Google Firebase Google LLC |
Optional: phone-number authentication and push notifications. Used only in builds configured for Firebase; the SMS build does not initialise it. | Phone number, Firebase installation/push token, and app-instance metadata (Google Privacy Policy applies). |
| Google Play | Distribution of the Android app and crash/vitals reporting performed by the operating system or the store. | Install and device data handled by Google as the store operator (Google Play Terms apply). |
These providers act as our processors and are bound to use the data only to deliver their service to us. We do not sell personal data and we do not share it with advertisers or data brokers.
8. Data storage and security
Data is stored on servers operated by MongoDB Atlas & Cloud Infrastructure in the Asia-Pacific (Mumbai, India) region. Cross-border transfers, if any, rely on statutory adequacy standards and contractual safeguards compliant with the Digital Personal Data Protection Act, 2023 (DPDP Act).
Security measures in the shipped product and API include:
- HTTPS-only communication; the release build blocks plaintext HTTP and does not trust user-installed certificate authorities.
- Short-lived access tokens (15 minutes by default) with rotating refresh tokens; failed refreshes end the session.
- OTPs are stored only as SHA-256 hashes, expire after a few minutes, allow a limited number of attempts, and are deleted after use or expiry.
- Authorisation checks on the server: you can only edit or delete your own profile, posts, vehicles and requests. Phone numbers are withheld on public endpoints until a request is accepted.
- Image uploads restricted by type and size, served from a separate path with content-type protection.
- Hardened API configuration: security headers, request-size limits, per-IP rate limiting, an explicit CORS allow-list in production, and a MongoDB instance that is not exposed to the internet.
- The production container runs as a non-root user.
No system is perfectly secure. If a breach affects your personal data, we will notify you and the relevant authority as required by applicable law.
10. Data retention
- Account and profile data — kept while your account exists.
- OTP records — deleted automatically within minutes of expiry, and immediately after successful verification.
- Listings, requests, vehicles, saved items and uploaded images — kept until you delete them or delete your account. Completed or cancelled posts remain visible to the parties involved until removed.
- After account deletion — your profile, listings, vehicles, requests, saved items, uploaded images and OTP records are deleted from the live database. Residual copies in encrypted backups expire within 30 days.
- Logs and security records — retained for 30 days for debugging and abuse prevention.
- Records we must keep by law — for example tax or lawful-request records, retained for the period required by law even after deletion.
11. Your rights and data deletion
Your rights
- Access and portability — see the profile, listings and requests in the app, or ask us for a copy of your data.
- Correction — edit your name, company, city, district, language and photo in Profile → Edit profile; edit or delete vehicles and listings at any time.
- Deletion — delete individual items, or delete your whole account (see below).
- Withdraw consent — turn off notifications in Settings, or delete your account. Withdrawing consent for essential processing means you can no longer use the Service.
- Grievance redressal — contact our grievance officer (section 14). We respond within the period required by applicable law.
- Complain to a regulator — you may lodge a complaint with the Data Protection Board of India or another competent authority.
How to delete your account
- Open the app and sign in.
- Go to the Profile tab.
- Tap Delete account at the bottom of the screen and confirm.
Deletion is immediate and permanent: your profile, truck posts (including return trips), vehicles, requests you sent or received, requests on your posts, saved items, uploaded images and OTP records are removed, and you are signed out. You can create a new account later with the same phone number, but the old data cannot be restored.
If you cannot sign in, you can request deletion by emailing privacy@freightpro.com from the phone number in question; we may ask you to verify ownership of the number first. The same instructions are published at https://fp.livetools.me/account-deletion.html.
12. Children's privacy
Freight Pro is a commercial transport marketplace intended for people who are at least 18 years old and legally able to enter into contracts. We do not knowingly collect personal data from children. If you believe a child has created an account, contact us at privacy@freightpro.com and we will delete the account and its data.
13. Changes to this policy
We may update this policy as the Service evolves — for example if we add a new third-party service or a new data category. The "Last updated" date at the top always reflects the current version, and material changes will be announced in the app before they take effect. Continuing to use the Service after an update means you accept the revised policy; if you do not, you may delete your account.
14. Contact information
Questions, requests or complaints about privacy can be sent to:
- App Name: Freight Pro
- Developer: Nihan Ali VP
- Package Name:
com.freightpro(Android) - Data controller: Freight Pro Logistics Technologies Private Limited, Freight Pro Logistics Hub, Outer Ring Road, Bellandur, Bengaluru, Karnataka 560103, India
- Privacy contact: privacy@freightpro.com, +91 80 4567 8900
- Grievance officer (India): Mr. R. Anandakrishnan (Chief Compliance & Grievance Redressal Officer), grievance@freightpro.com, Freight Pro Logistics Hub, Outer Ring Road, Bellandur, Bengaluru, Karnataka 560103, India
- Support in the app: Profile → Help → Contact support (support@freightpro.com)
We aim to acknowledge privacy requests within 24 hours and to resolve them within 15 working days as required by Rule 3(2) of the Information Technology (Intermediary Guidelines and Digital Media Ethics Code) Rules, 2021 and the DPDP Act, 2023.