This policy explains what information the B2Czone apps and related services collect, how we use it, and how you can contact us.
01
Who this policy covers
This policy describes how B2Czone handles personal information for people who use our mobile apps (B2Czone user and B2Czone locals) and our public website.
Customers book services through the B2Czone user app. Locals receive job requests and manage work through the B2Czone locals app. The website is mainly informational; sign-in and booking happen in the apps.
02
Information we collect
[Customer] Phone number used to sign in (OTP). Optional profile fields such as name, gender, and email when you add them.
[Customer] Saved addresses you create in the app: label, address text, optional map coordinates, and any extra fields you save with the address.
[Customer] When you post a job, we store the service type, the address text you provide, map coordinates for that job, optional notes, budget, and status/timestamps as the job moves through our system.
[Customer] Job-related records: offers from locals, messages in job chat, ratings, and complaints linked to the job.
[Customer] App usage events (job created, offer received, job completed) sent to our servers for operational analytics. No advertising data is collected.
[Local] The same account basics as customers plus locals profile data: service category, years of experience, verification status, and aggregate rating fields we show on your profile.
[Local] Last map coordinates you report while using the app for availability and matching, stored on your locals profile.
[Local] Optional Firebase Cloud Messaging (FCM) device token when you send it to us, used for job notifications on supported devices.
[Local] Job offers you send, job chat you participate in, platform fee payment records created through Razorpay (order and payment identifiers and amounts), and ratings or complaints involving you.
Both roles: short-lived OTP codes for login, stored until used or expired. Server-side and in-app analytics events (event name, related identifiers, app version, platform, timestamps).
03
Customer and locals accounts
Accounts are separate per role: the same phone number can exist once as a customer and once as a locals provider because each role is its own account.
You sign in with a one-time code (OTP) sent by SMS through our messaging provider; we store your phone number.
You can update profile fields in the app where the product supports it. You can request account deletion from the app; when you do, we delete your account row and remove or detach related data our deletion flow is built to handle.
04
Location usage
Job postings include the service location you choose (latitude, longitude, and address text). That location stays on the job record for matching, fulfilment, and history.
To find nearby locals, our servers use distance-based matching with expanding search rings up to 5 km from the job.
Locals: we store the last coordinates you report for matching and job alerts while you use the product. If you revoke location permission, features that depend on location may not work.
Maps inside the apps rely on the map provider on your device (for example Google Maps or Apple Maps). Those providers process location under their own policies when you use map features.
05
Notifications
We send transactional messages about jobs and bookings using the contact and device data described above.
Customers: we send booking and job updates via SMS to your registered phone number.
Locals: we may send push notifications through Google Firebase Cloud Messaging using the FCM token stored on your locals profile when you provide one.
SMS is used for OTP login codes through our SMS vendor. Message and data rates from your carrier may apply.
06
Payments
Locals (service providers) pay a platform fee after completing a job. This fee is processed by Razorpay. Payment details are entered in the Razorpay checkout; we do not receive or store your full card number or UPI PIN.
Our database stores Razorpay order identifiers, and after a successful payment the Razorpay payment identifier, plus the amount and status.
Razorpay processes payments under its own terms and privacy policy in addition to this notice.
07
How we use and share information
We use the data above to operate the marketplace: authenticate you, post and match jobs, show offers, enable chat, take payments, send notifications, improve reliability, and investigate abuse or technical problems.
We share data with service providers strictly where needed to run the product: Razorpay for payments, our SMS provider for OTP, Expo and Google FCM for push delivery, and cloud or hosting vendors that store our database and files.
We may disclose information if required by law, regulation, or valid legal process.
We do not sell your personal information to data brokers for their own marketing lists.
08
Data retention
We keep information while your account exists and for as long as needed to provide the service, resolve disputes, and meet legal obligations.
When you delete your account through the app, we run our account-deletion process to remove your user profile and the categories of linked data that process is designed to delete.
Analytics and operational logs may be kept for troubleshooting and product improvement for a period our team configures in production.
09
Your rights and choices
You can access and update much of your profile information directly in the app.
You can request deletion of your account from the app; that triggers the deletion flow described above.
You can turn off push notifications in your device settings; some SMS messages (such as OTP) are required to sign in.
For other questions or requests about your data, contact us at the email below.
10
Changes
We may update this policy from time to time when our practices change. We will post the new version on this page and adjust the "Last updated" date.
Contact
Questions about this policy or your data: email us at info@b2czone.com.