Privacy Policy

1. Introduction

Yassuh Inc (“Yassuh”, “we”, “our”, or “us”) operates FleetHub, a fleet management and last-mile logistics platform. This Privacy Policy explains how we collect, use, share, retain, and protect information when individuals and organizations use FleetHub and its related applications and services (collectively, the “Service”).

By accessing or using the Service, you agree to the practices described in this policy. If you do not agree, please discontinue use of the Service.

2. Information We Collect

2.1 Account and Organization Information

We collect information used to create, administer, and secure FleetHub accounts, including:

• Name, email address, phone number, and username
• Organization, role, permissions, and account status
• Age and gender, where provided
• Authentication details, security settings, and account-recovery records
• Device identifiers, device name, model, operating system, and app version

2.2 Delivery and Operational Information

We process information needed to plan, perform, verify, and report on logistics operations, including:

• Recipient and customer names, phone numbers, email addresses, delivery addresses, and geographic coordinates
• Package details, tracking numbers, weights, delivery instructions, and Yassuh Codes
• Trip assignments, routes, stops, timestamps, status updates, delivery attempts, outcomes, and failure reasons
• Notes, barcode scans, delivery photographs, and signature images used as proof of delivery
• Information supplied through authorized customer, courier, and webhook integrations

2.3 Location and Device Telemetry

When Driver Mode is enabled, FleetHub collects precise location and related telemetry in the foreground and background, including when the app is not actively in use. This information may include:

• Latitude, longitude, altitude, heading, speed, accuracy, and timestamps
• Device motion, acceleration, and detected activity such as walking, cycling, or travelling in a vehicle
• Battery level, network type, device status, and satellite-fix information
• Trip route geometry and stop arrival information

If a device is offline, FleetHub may temporarily store telemetry and delivery activity on the device and send it when connectivity returns. Authorized users within the relevant organization may use FleetHub records to monitor and review delivery operations, including trip progress, routes, stops, and delivery outcomes.

2.4 Usage, Technical, and Security Information

• IP address, browser type, operating system, pages viewed, and features used
• Session, login, account-recovery, access-control, and audit records
• Error reports, diagnostic logs, crash data, and performance information
• Push-notification tokens, notification content, and delivery status
• Language, map, and other Service preferences

3. How We Collect Information

We collect information:

• Directly from users, such as when they sign in, update account details, scan packages, record delivery results, take photographs, provide signatures, or contact support.
• Automatically from devices and browsers, such as location, telemetry, device, usage, cookie, and diagnostic information.
• From authorized organizations and integrations, such as account details, trip assignments, customer and package information, and delivery updates.

4. How We Use Information

We use information to:

• Authenticate users, secure accounts, and manage access
• Plan, assign, optimize, navigate, and track delivery trips
• Verify package handling and delivery using location, timestamps, photographs, signatures, notes, and status records
• Provide live operational visibility, reports, notifications, and customer support
• Synchronize information with authorized customer, courier, and integration partners
• Diagnose errors, maintain performance, improve reliability, and develop Service features
• Detect, investigate, and prevent fraud, misuse, security incidents, and unauthorized activity
• Enforce agreements and comply with applicable legal obligations

5. How We Share Information

We may share information with:

• Authorized organization users. FleetHub users with appropriate permissions may access account, package, delivery, trip, location, and reporting information associated with their organization.
• Service providers. Providers support functions such as hosting, storage, maps, routing, notifications, diagnostics, security, search, and communications.
• Courier and integration partners. We exchange package, recipient, status, and proof-of-delivery information when needed to provide an integration configured by an authorized organization.
• Legal and safety recipients. We may disclose information when reasonably necessary to comply with law, respond to valid legal process, protect rights or safety, or investigate misuse.

5.1 Major Service Providers

Providers may change as the Service evolves. We take reasonable steps to select providers that protect information appropriately and limit their access to the purposes for which they provide services.

We do not sell or rent personal information, and we do not use FleetHub information for targeted advertising.

6. Cookies and Local Device Storage

FleetHub uses cookies and browser or device storage to maintain authenticated sessions, remember language and map preferences, support offline operation, preserve pending delivery records, and secure account information. The mobile application may store authentication and profile information in secure device storage and operational records in an encrypted local database until they can be synchronized.

We do not use advertising cookies or third-party behavioural advertising cookies in FleetHub.

7. Data Retention

We retain information only for as long as reasonably necessary to provide FleetHub, follow authorized customer instructions, maintain security and business records, resolve disputes, enforce agreements, and meet legal obligations. Retention varies based on the type of information, the purpose for which it is processed, contractual requirements, and applicable law.

Offline records may remain on a device until they are synchronized or removed. Information may remain for a limited period in backups, audit records, or security logs after it is removed from active systems.

8. Data Security

We use reasonable administrative, technical, and organizational measures designed to protect information. Depending on the system, these measures include encryption in transit, password hashing, secure device storage, encrypted local databases, access controls, authentication safeguards, and audit logging.

No method of transmission or storage is completely secure, and we cannot guarantee absolute security. Users should protect their credentials and promptly report suspected unauthorized access.

9. Choices and Privacy Requests

Depending on applicable law and the circumstances, individuals may request access to, correction of, or deletion of their personal information, or may object to or request restriction of certain processing.

Device permissions for location, camera, photographs, and notifications can be reviewed or changed in device settings. Disabling a permission may prevent related FleetHub features from working correctly.

To submit a privacy request, contact us at the email address below or contact your organization administrator. We may need to verify your identity, coordinate with the relevant organization, or retain limited information where required for security, legal, or recordkeeping purposes.

10. Children’s Privacy

FleetHub is a business service and is not directed to children. Children should not use the Service independently. A parent or guardian who believes FleetHub has processed information concerning a child may contact us so that we can review the request and take appropriate action.

11. Changes to This Policy

We may update this Privacy Policy periodically. When we do, we will revise the “Last updated” date at the top of the page. For material changes, we may provide additional notice through the Service, by email, or through an organization administrator. Continued use of the Service after the effective date constitutes acceptance of the revised policy.

12. Contact Us

If you have questions, concerns, or requests regarding this Privacy Policy or our data practices, please contact us: