Haatro Privacy Policy (Version 1.0)

1. Information We Collect

• Account & Profile Data: Mobile phone number (+8801XXXXXXXXX, verified via SMS OTP), customer full name, optional email address, and preferred app language (en or bn), stored in Supabase Auth (auth.users) and public.profiles.
• Delivery Location & Address Data: Recipient name, contact phone number, locality details, optional landmark, and pinned delivery coordinates (latitude, longitude, and location_source: GPS or MAP_PIN) stored in public.addresses and snapshotted on placed orders.
• Order & Transaction Data: Ordered grocery product SKUs, variant quantities, server-validated unit prices in Taka (BDT ৳), delivery fees, applied coupon codes, and order status history. Version 1.0 uses Cash on Delivery (COD) exclusively; the app does not collect payment card numbers or mobile wallet PINs.
• Print & Xerox Service Documents: PDF or document files explicitly selected by the customer using the Android system file picker, along with print job settings (file name, byte size, page count, A4/Legal paper size, color mode, copies, and binding).

2. Location, Delivery Zone & Device Permissions

• Foreground Location Only (ACCESS_FINE_LOCATION & ACCESS_COARSE_LOCATION): Requested at runtime strictly when you tap “Use Current Location (GPS)” inside the Delivery Location & Address dialog to place your delivery pin and verify zone serviceability for your selected area. Background location is never requested or tracked.
• Zero Broad Storage Permission for Print Uploads: Print document selection uses the native Android system document picker without requesting READ_EXTERNAL_STORAGE or broad media permissions.
• Network Access (INTERNET & ACCESS_NETWORK_STATE): Used to communicate over HTTPS with the Supabase backend and load OpenStreetMap tiles. Camera, microphone, contacts, and advertising ID permissions are not used.

3. Third-Party Services & Data Sharing

• Supabase Backend (Auth, PostgreSQL & Storage): Hosts user authentication, profiles, addresses, warehouse inventory, orders, and private print files enforced by PostgreSQL Row Level Security (RLS) policies.
• OpenStreetMap & Nominatim: Delivery map tiles are fetched over HTTPS from tile.openstreetmap.org and coordinates are reverse-geocoded via nominatim.openstreetmap.org. No customer name, phone number, or account identifier is transmitted to OpenStreetMap.
• Assigned Delivery Riders & Authorized Fulfillment Staff: Your delivery address, pinned coordinates, and contact phone number are shared strictly with authorized Haatro hub staff and assigned delivery riders to fulfill and deliver your order.
• No Sale of Personal Data: Haatro does not sell, rent, or trade personal information to advertisers or third-party data brokers.

4. Data Security, Retention & 48-Hour Print Auto-Purge

• Encryption & Row Level Security: All API traffic is encrypted in transit via HTTPS/TLS. Database tables and storage buckets enforce strict Row Level Security (RLS) so customers can access only their own records.
• 48-Hour Automatic Print Document Deletion: Uploaded print documents are stored in the private print-documents bucket isolated by user ID (auth.uid()) and are permanently purged 48 hours after upload/delivery via scheduled server cleanup (public.cleanup_expired_print_documents).
• Account & Audit Retention: Profile details and saved addresses are kept while your account remains active. Upon account deletion, profile PII, saved addresses, and uploaded print files are permanently deleted, while completed historical order financial totals are retained in anonymized form for statutory accounting and audit compliance.

5. Your Rights & Account / Data Deletion

You can view, update, or permanently delete your Haatro account and personal data at any time. Inside the Haatro Android app, navigate to Account → Legal & Support → Delete Account & Data, type DELETE, and confirm. You can also review our public deletion instructions at /delete-account.