FreshGuroo App Privacy Policy
This policy explains how FreshGuroo ("we", "us") handles information in these Android applications:
- FreshGuroo Customer (
com.freshguroo.freshguroo_customer): business-to-business fresh-produce ordering for store owners and authorized store staff. - FreshGuroo Driver (
com.freshguroo.freshguroo_driver): delivery trips, delivery evidence and cash, item and crate handovers for authorized drivers. - FreshGuroo Inventory (
com.freshguroo.inventory_app): stock, warehouse, dispatch, sales-visit and payment operations for authorized FreshGuroo staff.
Privacy, support and account/data-deletion requests can be sent to superadmin@freshguroo.com. Information collected depends on the app, your assigned role and the features you use. Driver and Inventory access is provisioned by FreshGuroo; downloading an app does not grant access to business data. Customer store approval and delivery serviceability are checked separately.
1. Customer app information
- Account and contact information: phone number, name, account and customer identifiers, authentication information, and email address when provided. Store owners may provide the names and phone numbers of authorized shopkeepers when linking stores.
- Business and delivery details: store name, business type, address, PIN code, GST information when provided, registration and approval records, and store coordinates you select or submit.
- Location: with your device permission, approximate or precise foreground location helps identify delivery serviceability and place your store on a map. Coordinates chosen on a map or supplied as part of a delivery address may be saved with the store. The Customer app does not request background location tracking.
- Photos and support content: store photos you choose or take, complaint descriptions and attachments you submit, ratings, feedback, and support correspondence. We do not need unrestricted access to your photo library to process selected uploads.
- Orders and payment records: products, quantities, invoices, delivery status, returns, payment method and status, transaction references, business-account balances, wallet adjustments and loyalty activity. The app does not ask for or store your UPI PIN or card security code.
- Device and technical information: an app/device identifier (including the Android app-scoped device ID where available), device model, operating system, app version, notification token, session and authentication records, and technical request information such as IP address. Update services also receive installation, release and patch identifiers.
- SDK usage and diagnostics: Google Maps collects SDK/device metadata, IP addresses, a Maps SDK-specific identifier, crash logs and crash metrics. Map interactions such as panning and zooming may also be collected when the app uses map camera features. These help Google measure usage, diagnose problems and improve its services.
Required and optional information: new-store registration requires a phone number, owner/contact and store details, a delivery address, the location-permission stage, and at least one store photo for verification. Email and GSTIN are optional. Complaints, complaint attachments, ratings and feedback are optional. Order and financial records are created when you use those features, and some authentication, device and SDK data is processed automatically when the relevant service is used.
Current payment features: the Customer release submitted to Google Play records payment claims and references, refund-wallet activity and loyalty points used on FreshGuroo orders. UPI payments open a separate payment app. This release does not include embedded HDFC checkout or collect card details, card security codes, bank-login credentials or UPI PINs. If a bank refund is arranged through support, the information needed to process it is handled for that request, not as a payment credential in the app.
2. Driver app information and location
- Driver account: name, phone number, driver and account identifiers, profile photo when provided, driving-licence number and expiry where recorded, assigned distribution centre, vehicle and trip details, and authentication/session information.
- Trip location: precise or approximate location, timestamps, accuracy, speed and heading where available. Current location and trip-location history support delivery tracking, arrival checks, dispatch coordination and delivery evidence. Location collection starts for an active trip and may continue while the app is in the background or the screen is locked, subject to Android permissions and operating-system limits. Tracking is stopped when the trip is ended or the driver signs out; previously recorded trip history remains subject to retention rules below.
- Operational evidence: delivery and failed-delivery records, returned items, crates, photos you capture or select, notes, timestamps, and coordinates attached to evidence. Delivery-evidence steps may require a camera photo; profile-photo selection may also use the system picker.
- Financial and work records: cash collected, payment references and proofs, cash/return/crate receipts, expenses, salary advances, payroll summaries and deductions associated with your work. These are business records, not permission to access your personal bank account or SMS inbox.
Authorized dispatch and operations personnel can view trip location and the delivery information needed for their work. Drivers see assigned customer contact and delivery details. Location is used for delivery operations, not advertising. You can revoke location permission or turn off device location in Android settings; doing so can prevent location-dependent trip or delivery actions from completing.
3. Inventory app information
- Staff account: name, phone number, email where provided, account identifiers, distribution-centre and role assignments, and authentication/session information.
- Operations and records: stock movements, grading and wastage, purchases, vendor and farmer details, uploaded agreements, customer/store details, orders, route and driver assignments, receipts, payment references and proofs, expenses, payroll actions and approval/audit records. Access is limited by the staff member's assigned permissions.
- Photos and documents: images or documents you select or capture for quality checks, wastage, receipts, vendor agreements and other supported work records. Selected files are uploaded when you submit the related action.
- Foreground location: location and accuracy at a sales visit help verify arrival near the store and record the visit. Device information and mock-location indicators are checked to protect the integrity of visit records. Inventory does not request background location permission or continuously track staff between visits.
Driver and Inventory also process app-scoped device identifiers, device model, operating system and app version, IP/request information, notification tokens and session records for authentication, security, notifications and operation of the app. Shorebird processes update-related installation, release and patch information. Neither staff app shows third-party advertising or uses the Android Advertising ID. Denying optional photo, document or notification access limits the corresponding feature; tasks requiring evidence or location cannot be completed without the required information.
4. Why we use information
We use this information to verify phone numbers, sign users in, recover access, register and verify businesses, associate authorized users with stores, check serviceability, fulfill orders, coordinate deliveries, reconcile payments and invoices, manage refund wallets and loyalty rewards, provide support, deliver notifications, prevent duplicate or abusive registrations, protect sessions, understand service usage and reliability, and maintain and update the app.
For Driver and Inventory, we also use information to allocate trips, verify arrival and delivery, coordinate stock and dispatch, reconcile cash and crates, manage returns and grading, record sales visits, administer work-related payments and approvals, and preserve an audit trail. Reassigning a trip does not transfer responsibility for another driver's previously recorded cash or liabilities.
5. Authentication and service providers
FreshGuroo Customer, Driver and Inventory use Google Firebase Authentication for supported phone-number verification flows, including OTP requests, resend and phone-based password recovery. Phone numbers supplied for authentication are sent to and stored by Google for spam and abuse prevention across Google services, including Firebase. Authentication/device information is also processed to deliver and verify SMS codes and protect sign-in. Depending on the device, verification may involve Google Play services, Play Integrity or reCAPTCHA. Firebase verification is exchanged for a FreshGuroo application session; it does not itself approve a store or grant a staff role.
We use service providers to operate the app:
- Supabase: authentication sessions, business records, database, storage and backend processing.
- Google Firebase Cloud Messaging: push-notification delivery using device/installation identifiers and notification tokens.
- Google Maps and device geocoding services: Customer uses Google Maps for maps and address/location features. These services may process coordinates, IP addresses and device/request information under their own terms. The Customer Maps SDK also sends the usage, identifiers and diagnostics described above to Google for service measurement, stability and improvement; this is not limited to information FreshGuroo saves in its database.
- OpenStreetMap and OSRM: Driver and Inventory show route-preview maps using OpenStreetMap tiles. Tile requests disclose the requested map area, IP address and request information to the tile service. Driver also sends route waypoint coordinates to the OSRM routing service at
router.project-osrm.orgto obtain road-following routes. Opening navigation in Google Maps or another map app passes the chosen destination to that service, under its privacy terms. - Shorebird: app update checks and delivery, using app, installation, platform, release and patch information.
- Payment, communications and delivery services: information needed to complete a user-requested payment, support interaction or delivery. If you open a UPI, phone, email or WhatsApp app, that service's privacy terms also apply.
See Firebase privacy information, Firebase phone authentication data handling, Maps SDK data disclosures, Google's Privacy Policy, Supabase's Privacy Policy and Shorebird's Privacy Policy.
For map tiles, see the OpenStreetMap Foundation Privacy Policy. Maps, routing and external navigation providers receive the data needed for their requests even when those requests are not saved as FreshGuroo business records.
6. Who can receive information
Authorized FreshGuroo sales, operations, support and delivery personnel receive the information needed for their work. Store owners and authorized linked-store users may see information for stores they are allowed to manage. Service providers process information for the purposes described above. We may also disclose information when required by applicable law or to protect users, prevent fraud, resolve disputes or enforce our agreements.
Google receives authentication phone numbers for cross-service spam and abuse prevention, and Maps SDK identifiers, app interactions, crash logs and diagnostics for analytics and service improvement, as described above. We do not sell personal information or share it with third parties for their independent marketing. The current Customer release does not show third-party advertisements or collect the Android Advertising ID.
7. Permissions and your choices
You can manage location, camera, photo/file and notification permissions in Android settings. In Customer, Location permission is required to progress through new-customer onboarding; denying it prevents that registration stage from completing. The Android system photo picker lets you select individual images without granting broad photo-library access. Customer camera access is used when you choose to take a photo; you can choose an existing image instead. Driver delivery evidence may require a live camera capture. Inventory uses photos and selected documents for operational records; available photo permissions depend on the Android version and installed app version. Selected photos are uploaded only as part of the action you initiate. OTP autofill uses supported Android/Firebase verification mechanisms; it is not general access to your SMS inbox. Denying an optional permission may limit the related feature, but you can still contact support.
The app stores session information and some preferences or unfinished registration information locally. Signing out or clearing app storage is not the same as deleting your server-side account. Uninstalling the app does not delete your business records.
8. Security and processing locations
We use encrypted network connections, authenticated sessions and access controls to protect information. No system can guarantee absolute security. Keep passwords and OTPs private and report suspected unauthorized access to support.
Our cloud providers may process information in India and other countries where they operate. Making the app available in India does not mean all data is stored only in India.
9. Retention, access and deletion
We retain account and business information while it is needed to operate your account and provide the services you request. Order, invoice and payment records may need to be kept for applicable accounting, tax or legal retention periods. Security and fraud-prevention records, and records connected to an unresolved dispute, may be kept for as long as that specific purpose requires. Retention depends on the record and applicable obligation rather than one fixed period for every type of data; where retention is necessary, access and use are restricted to that purpose.
You may request correction of your information, access to it, or deletion of your FreshGuroo Customer, Driver or Inventory account and associated personal data. Visit Request account and data deletion for the request channel, identity checks and information about records that may be retained. Driver and staff requests may involve employment, payroll, delivery evidence, safety, payment or stock audit records that must be retained for a specific accounting, legal or dispute-resolution obligation. Support will explain applicable exceptions. Deletion requests are reviewed by support; opening the page or uninstalling the app does not automatically delete data.
In Customer, open Profile > Privacy & Security > Request account deletion to reach the same support-assisted process. Users of any of the three apps can use the website or email above without signing in. Account deletion covers the login and associated personal data, subject to the specific retention exceptions above; merely disabling or freezing access is not account deletion. Support will explain any records that must be retained and the applicable reason when processing your request.
10. Children
FreshGuroo Customer, Driver and Inventory are intended for business owners, authorized business staff and drivers aged 18 and over, not children. If you believe a child has provided personal information, contact us so we can review and address the request.
11. Changes and contact
We may update this policy as the app or our practices change. The date above identifies the latest revision. For privacy, account or support requests, email superadmin@freshguroo.com.