1Introduction

Tayyar ("we", "us") provides a delivery management platform used by businesses to manage staff, orders, couriers, and deliveries. This Privacy Policy explains what personal information is collected through the Tayyar web dashboard, mobile applications, and related services, and how that information is used, shared, retained, and protected.

Please read this policy carefully. By creating an account or using Tayyar services, you acknowledge the practices described here.

2About Tayyar

Tayyar is a business-to-business delivery operations platform operated under the Yusr brand. Businesses (tenants) use Tayyar to organize branches, employees, delivery couriers, customer orders, trips, shifts, and financial settlements. Tayyar acts as the technology platform; each business controls its own staff accounts, customer records, and operational data within its isolated workspace.

3Scope and applicable services

This policy applies to the Tayyar web application, the Tayyar Android and iOS mobile applications, backend APIs, push notifications, and the public order-tracking pages. It does not govern data practices of third-party websites or apps linked from Tayyar.

4Data controller and business contact

Tayyar is operated under the Yusr brand. For privacy questions or requests, contact us at support@yusr.site.

5Information we collect

We collect information you or your business provide, information collected automatically during use of the services, and limited information from third-party services (such as push delivery and maps).

6Account and identity information

When an account is registered, we store the username, display name, email address, phone number, assigned role, branch assignment, and authentication credentials (passwords are stored hashed, never in readable form). Login records the sign-in time. Accounts are isolated per business workspace, and access to staff records is restricted by role.

7Business and organization information

Businesses provide their name, branches, delivery zones, schedules, and configuration. This information is used to operate the workspace and is visible to authorized staff of that business only.

8Employee and courier information

Businesses manage employee and courier profiles including display name, contact details, role, branch, shift and attendance records, performance metrics, and financial records (gains, transactions, settlements). Shift status (on-shift, in-turn) and presence state are processed to coordinate deliveries.

9Customer and delivery recipient information

Orders contain the delivery address, geographic coordinates, and the recipient's phone number entered by the business or an integrated ordering system. There is no separate customer account; recipient information exists only inside the order record and is visible to authorized staff of that business and the assigned courier.

10Order and delivery information

Orders include items, totals, delivery fees, payment method, status history, assigned courier and trip, timestamps, proof-of-delivery attachments, and audit metadata (who created, updated, or settled each record). For record integrity, orders cannot be deleted through the application; corrections are made by updating the order or its status.

11Precise and approximate location data

The mobile apps collect precise GPS location (coordinates, accuracy, speed, bearing, battery/charging state, and timestamps) from couriers during active work. Location is used for live shift tracking, trip breadcrumb trails, branch presence verification, and delivery coordination. Mock locations are rejected, and readings with accuracy worse than 100 meters are discarded.

12Background location and Live Tracking

• When tracking starts: when the courier starts an explicit tracked session (shift or delivery tracking) after granting location permission.
• Who can view it: authorized managers and admins of the courier's own business (branch-scoped), and the assigned business staff viewing the trip.
• History: trip breadcrumb trails and presence events are stored with no automatic deletion period (see Retention) for operations, maps, and dispute review. Temporary live-state data may expire automatically.
• How to stop it: end the shift or tracking session in the app, sign out, or revoke location permission in system settings (revoking permission stops tracking but may limit delivery features).
• Public tracking links: a business may generate a 24-hour expiring link so a recipient can view the courier's name, phone, live location, and estimated arrival. Nothing else about the order is shared.

This web page does not replace the in-app prominent disclosure or the Play Console background-location and foreground-service declarations, which are maintained separately.

13Camera and barcode-scanning permissions

The mobile apps request camera access solely to scan order barcodes and to capture proof-of-delivery photos or attachments you choose to provide. Photos are stored as order or document attachments inside the business workspace. The camera is never used for background recording or facial recognition.

14Notifications and device information

We process push tokens and device identifiers to deliver shift, order, and tracking notifications through Firebase Cloud Messaging. There are two kinds of notifications: persistent notifications stored in your notification inbox, which remain stored indefinitely until you manually delete them, and transient notifications that are delivered without being stored in the inbox. Device tokens are bound to the signed-in session and are released on sign-out.

15Website storage and cookies

The web dashboard stores authentication tokens, the current workspace membership, device identity, language and display preferences, and data-table preferences in the browser's local storage so you stay signed in and the interface remembers your settings. We do not use third-party advertising or analytics trackers on the web dashboard, and no advertising cookies are set.

16Purposes of data processing

• Creating and securing accounts and business workspaces.
• Assigning, tracking, and completing deliveries.
• Showing live courier and trip positions to authorized staff and recipients with tracking links.
• Sending operational notifications (orders, shifts, tracking, exports).
• Recording attendance, performance, and financial settlements.
• Preventing fraud and abuse, keeping audit trails, and meeting legal obligations.
• Improving reliability and supporting users.

17Legal bases

Where data-protection law requires a legal basis, we process personal information as necessary to provide the contracted services to the business, to comply with legal obligations, for legitimate operational interests (such as fraud prevention and service security), and on the basis of consent where it is specifically requested (for example, device permissions and optional features).

18Sharing of personal information

• Within a business: staff see information according to their role; branch scoping limits managers to their own branches.
• Couriers: assigned couriers see the delivery details needed for their orders (address, recipient phone, notes).
• Recipients: recipients with a tracking link see only the courier's name, phone, live location, and estimated arrival.
• Across businesses: no. Each business workspace is isolated; businesses cannot access each other's data.
• Legal: we may disclose information where required by law or to protect safety, security, and rights.

We do not sell personal information and do not share it for third-party advertising.

19Service providers and third-party integrations

• Firebase Cloud Messaging (Google): push notification delivery.
• SMS gateway: delivery of tracking-link SMS where the business enables it.
• Transactional email provider: operational email.
• Maps and routing (web dashboard): OpenStreetMap map tiles and OSRM routing; Google Maps links may be opened by the user for directions.
• Cloudflare R2 Object Storage: production file and attachment storage.

20Data storage and security

Access tokens are kept in secure on-device storage; session, tenant, and branch scoping is enforced on every API request; passwords are hashed; tracking tokens are random SHA-256 values; uploaded files use unguessable names inside tenant-scoped storage; and platform audit logs are append-only. No method of transmission or storage is completely secure, and we cannot guarantee absolute security.

21Data retention

• Trip location trails and presence logs: historical records are currently not automatically deleted; there is no automatic deletion period for them. Temporary live-state and cache data may expire automatically.
• Live presence state: expires automatically within minutes (up to 24 hours after going offline).
• Tracking links: expire 24 hours after creation.
• Generated export files: expire and are deleted 24 hours after creation.
• Backups: created daily at 12:00 AM and include the backend code and the database. The latest 14 days of backups are kept.
• Notifications: persistent inbox notifications remain stored indefinitely until you manually delete them; transient notifications are not stored at all.
• Orders and financial records: retained indefinitely as business records. There is currently no automatic deletion or archival schedule for them, and they cannot be deleted through the application.
• Deleted staff accounts: when an administrator actually deletes an account, its account record is permanently removed after 90 days. Disabling an account alone does not delete it.

22Data deletion and account deletion requests

A company administrator can disable a courier or staff account. While the account remains disabled, the user permanently loses access. Disabling is not the same as deleting the account: a disabled account is not automatically permanently deleted.

Account deletion is managed by the administrator of your company through the existing manual process. Users cannot independently delete their accounts in the application. When an administrator actually deletes an account, its account record is permanently removed after 90 days. No specific deletion-request response timeframe has been established. Individual notifications can be deleted in the app.

To request access, correction, export, or deletion of your personal information, contact your business administrator or us at support@yusr.site. Permanently removing an account does not automatically delete associated order records, financial transactions, or audit history, which are retained as described in Section 21.

23Privacy rights and choices

• Manage device permissions (location, camera, notifications) in system settings at any time.
• Update profile details in the app where the role permits.
• Sign out to release push tokens and end the session on that device.
• Request access, correction, or deletion as described in Section 22.

24Children's privacy

Tayyar is a workforce operations tool intended for businesses and their adult staff. It is not directed to children, and we do not knowingly collect children's personal information.

25International data transfers

Production infrastructure uses Hostinger servers managed with Laravel Forge, and the production database runs on the same server as the backend. The physical server location is not published here.

26Changes to this Privacy Policy

We may update this policy as the services evolve. Material changes will be announced by updating the "Last updated" date above and, where appropriate, through the application. Continued use of the services after an update takes effect constitutes acceptance of the revised policy.

27Contact information

For privacy and support questions about Tayyar, contact us at support@yusr.site.