Privacy Policy | Al-Qirsh

Privacy Policy

Al-Qirsh (“Al-Qirsh”, “the app”, “we”)

Version 1.0 — Effective date: 2026-09-13

Legal entity: Pending confirmation

Privacy contact: Pending confirmation

Support: Pending confirmation — Pending confirmation

Address: Pending confirmation

This policy describes the actual practices of the Al-Qirsh wholesale-ordering and field-operations application. It does not list data types the app does not handle.

1. Service identity

Al-Qirsh is a B2B application for approved wholesale customers and operations staff (sales representatives, delivery representatives, storekeepers, purchasing, sales management, and system administration). The backend is Supabase.

2. Developer / company identity

Display name: Al-Qirsh

Legal entity: Pending confirmation

3. Privacy contact

For privacy questions or access, correction, or deletion requests:

Pending confirmation

Pending confirmation

Pending confirmation

4. Types of information we collect

• Account data: name, mobile number, user ID, and operational role. An optional email may be stored for staff. Sign-in uses a technical email derived from the mobile number inside the authentication system.
• Customer business data: shop name, contact person, mobile, address, area, and classification when entered, plus the delivery addresses and their map coordinates saved by the customer or the representative.
• Precise location: staff device coordinates only during a work session the user starts explicitly: a sales representative's shift, or a delivery run sheet whose route the driver has started. One location point is recorded about every 5 minutes during the session, plus a point at operational events (route started, arrival at a customer, delivery outcome, visit started, order created, visit or session ended). Also the shop coordinates stored on the customer record and a location attached to a sale when available.
• App activity: orders and line items, the cart after submission, promo-code use, visits, in-app call-start records, and in-app notifications.
• Files and photos: catalog images, banners, and purchase attachments uploaded by staff from the gallery or a file — not a required camera, and not a Client-role upload.
• Operational financial data: order amounts, collection method, and a payment reference when recorded. We do not collect payment-card numbers and do not embed a payment SDK.
• We do not collect: advertising IDs, crash logs via an analytics/crash SDK, push-notification tokens (FCM), contacts, SMS contents, or the device call log.

The Client role does not track the customer’s device location. The device location is read once, only when the customer taps “Use my current location” while editing a delivery address, after an in-app disclosure and the operating-system permission; only the point the customer confirms on the map is saved as a delivery address. The location can also be chosen manually on the map without granting any permission.

5. How information is collected

• Entered by the user or a staff member in forms.
• Accounts are invited or created by an administrator — there is no public self-registration.
• Location is read from device location services after an in-app disclosure and the operating-system permission.
• Orders and operations are sent over HTTPS to our Supabase-hosted backend.
• Maps are rendered with the Google Maps SDKs, so map-view requests (the visible viewport) reach Google when a screen with a map is opened. Location tracking points are not sent to Google; they are stored directly on our servers.
• Run-sheet paths are drawn as straight lines unless a contracted or self-hosted routing server is configured.
• Google Maps or the device phone app open only if the user chooses to.

6. Purposes

• Account operation, authentication, and role-based access.
• Receiving, processing, preparing, and delivering wholesale orders.
• Customer management, field visits, and sales-shift supervision.
• Delivery routing and run sheets.
• Operational accounting, collections, abuse prevention, and security.
• Support and deletion requests.

We do not use this data for in-app advertising and we do not sell user data.

7. Location use

Precise location is used only for operations:

• Sales representative: after tapping “Start work day”, a location point is recorded about every 5 minutes for the duration of the shift through a foreground service with a visible notification, and recording stops when the shift is ended. Recording pauses during a break.
• Delivery representative: after tapping “Start route”, a location point is recorded about every 5 minutes, and recording stops automatically when the run sheet is completed or cancelled, or when the driver ends the session.
• A location point at operational events: route started, arrival at a customer, delivery outcome (delivered, partial, failed, refused, customer unavailable), route completed, visit started, order created, visit ended.
• Field-visit verification against the shop coordinates.
• Optional capture of the shop coordinates when creating a customer.
• Attaching a location to a sale when available.
• Showing the representative’s current position on their customer map and computing the straight-line distance to a customer on the device. This view does not create a tracking record.
• App customers: only after tapping “Use my current location”, the location is read once to place the shop pin on the map; the point the customer confirms is saved as a delivery address, and their representative is notified of the delivery-address change.

No staff location is collected outside an active work session, and a customer’s location is read only when they tap “Use my current location”. There is no 24/7 tracking. An in-app “location recording is active” bar with the last update time is shown for the whole session.

The Android app does not request background-location permission. Recording may continue while the app is minimized during an active session because of the visible foreground service, and stops if the user force-closes the app. A prominent disclosure is shown before the system permission prompt.

8. Account and authentication

Accounts are created or invited by the business. Sign-in is mobile number plus password. We do not use OTP. Session tokens are stored in on-device secure storage if the user chooses “remember me”. Passwords are sent over HTTPS and are not stored by the app.

9. Orders and business data

Submitting an order creates an order request pending processing, subject to the fulfillment workflow. Submission alone is not a completed sale. Orders are kept as operational and accounting records.

10. Service providers

We use service providers to operate the infrastructure:

• Supabase: authentication, database, file storage, and realtime updates.
• Google Maps for in-app map rendering (Maps SDK for Android and iOS, and the web interface). Google receives map-view data only; employee tracking history is never sent to Google.
• A routing service (OSRM) only if a contracted or self-hosted server is configured. The default build does not send stop coordinates to a public routing demo.
• Google Fonts for the interface typeface.

They process data to run the service, not for advertising on behalf of this app.

11. Sharing and processing

We do not sell data or share it with advertisers. We may disclose data if legally required. Opening WhatsApp, SMS, the phone dialer, or Google Maps is user-initiated.

12. Security

Traffic to the app backend uses HTTPS. The mobile app embeds only the public client key, not the service-role key. Row-level security is applied in the database. No electronic system is perfectly secure.

13. Retention

We keep data while accounts and operations remain active. Order, accounting, security, and field-work records are retained for legal obligations, disputes, and fraud prevention. There is currently no automatic purge of location history; any archiving or deletion of periodic location points is a documented management decision.

14. Deletion

A signed-in account holder can request deletion in the app: Account → Request account and data deletion. Instructions are also on the public page: https://alqirshgroup.com/delete-account

The request is reviewed and processed. Eligible personal data is deleted or anonymized. Transaction, accounting, tax, fraud-prevention, security, and dispute records may be retained where required. Disabling an account alone is not deletion. Access may end after processing completes.

15. User rights and contact

For access, correction, deletion, or questions: Pending confirmation

We may verify identity using the mobile number registered on the account.

16. Children’s privacy

The service is intended for wholesale business and institutional operations and is not directed at children.

17. Policy updates

We may update this policy when practices change. The effective date above is the current version. The in-app copy remains readable without a network connection.

18. Dates

Effective / last updated: 2026-09-13 — version 1.0