Last updated: June 2026
This page is practical platform guidance and should be read with the current in-app workflow.
Data we collect
AdhocX may collect profile details such as name, email, mobile number, role, age, gender, address, city, state, pincode, company details, branch details, supervisor details, vehicle preference, and approval status.
For riders, AdhocX may collect PAN, Aadhaar front/back, driving licence, selfie, payout or bank/UPI information, availability status, location data, no-show or penalty status, and assignment proof.
How we use data
We use data to create and verify accounts, approve riders and companies, match riders with nearby requirements, process bids and counters, manage assignments, verify OTP/location proof, support payments and payouts, send notifications, resolve disputes, prevent fraud, and improve platform reliability.
We do not sell user personal data. Data is used for platform operation, safety, compliance, support, analytics, and legitimate business needs.
Location data
Location may be collected during rider registration, availability/location tracking, requirement matching, branch setup, and assignment start/end proof. Nearby requirement matching uses rider and pickup/branch coordinates within the platform radius.
Location data helps verify work proof and route users to relevant jobs. Users should keep location information accurate and use the app only in a lawful and safe manner.
KYC and verification documents
KYC documents such as PAN, Aadhaar, driving licence, and selfie are used for identity, eligibility, safety, admin review, fraud prevention, and payout readiness. Document access is limited to authorized platform/admin workflows.
Users must not upload fake, altered, expired, or third-party documents.
Payments and third parties
AdhocX uses Razorpay or other configured payment providers for payment processing. Payment providers may process payment details according to their own terms and privacy practices. AdhocX stores payment metadata such as order IDs, payment IDs, verification status, amount, and related assignment/payment references.
AdhocX may use Supabase for backend data/storage, Firebase for messaging, Vercel or similar hosting providers for web services, and other operational tools needed to run the platform.
Notifications and FCM
AdhocX may send in-app notifications, foreground alerts, Android notifications, and Firebase Cloud Messaging pushes for nearby work, bids, counters, assignments, payments, payouts, penalties, support, and account updates.
Device tokens may be stored to deliver notifications to the correct rider or company profile. Users can manage device notification settings from their device where supported.
Data retention and rights
AdhocX may retain profile, KYC, assignment, payment, payout, notification, penalty, and support records as long as needed for platform operation, audit, dispute handling, fraud prevention, legal compliance, and business records.
Users may contact support@adhocx.in to request correction, account support, privacy questions, or reasonable access/deletion requests. Some records may need to be retained for verification, payment, dispute, safety, fraud prevention, or legal reasons.