Privacy · Private pilot

FleetOS Privacy Policy

Status: technical notice for the private pilot. FleetOS does not claim final general-commercial legal review until the final policy is approved.

1. Scope of this notice

This notice describes the current technical handling of personal and business data in the FleetOS private-pilot environment. Final commercial privacy commitments remain subject to legal review before general commercial availability.

FleetOS is intended for organizations operating fleets, transport, logistics and related workflows. The subscribing or pilot organization controls most business data entered by its users.

2. Data categories

Depending on the enabled modules, FleetOS may process account details, organization membership, audit activity, fleet and trip records, driver information, customer and supplier records, financial transactions, uploaded documents, and subscription references.

Payment-card handling depends on the configured billing provider. FleetOS does not represent that every deployed environment stores or processes card details directly.

3. How data is used

Data is used to operate the agreed FleetOS workflows, authenticate users, enforce permissions, support customers, maintain auditability, secure the service, send necessary transactional communications, and meet applicable legal or record-keeping obligations.

The read-only AI assistant is permission-scoped: it may answer supported questions only from data the requesting user is authorized to access and is not presented as an autonomous record-creation or posting system.

4. Organization isolation and access controls

FleetOS is a multi-organization SaaS application. Product access is scoped by organization, role and granted capability so one tenant is not intended to access another tenant’s business records through the application.

Sensitive operational actions use authorization and approval controls according to the configured workflow.

5. Security and service providers

FleetOS uses security controls including encrypted transport, password hashing, role-based authorization, audit logging and controlled document access. Final hosting, residency, backup-retention and sub-processor commitments depend on the deployed production configuration and customer agreement.

Service providers may be used for infrastructure, storage, monitoring, communications or billing according to the configured environment. FleetOS does not sell customer personal data for advertising.

6. Retention, export and deletion

The public pilot does not promise a fixed post-cancellation retention, export or deletion timeline. Final commitments depend on the production workflow, statutory record requirements and the applicable customer agreement.

Requests for access, correction, export or deletion can be submitted to privacy@fleetosuae.com and are handled subject to applicable legal and record-keeping obligations.

7. Cookies and telemetry

FleetOS uses essential session and security cookies where required. Any non-essential analytics or telemetry enabled in a deployed environment must be documented and governed through the applicable privacy and cookie configuration.

8. Contact and policy changes

Privacy enquiries and data-rights requests can be sent to privacy@fleetosuae.com.

Material notification commitments and the final commercial privacy text will be completed through legal review before general commercial availability.