Version: 5.7.2 Effective date: August 20, 2026 Market: Syria
How this document works
FleetOS operates market-by-market through separate Local FleetOS Entities. Only the Part for your country applies to you, and only the entity named in that Part and recorded in your acceptance evidence is your contracting party. A FleetOS agreement, licence, Wallet, Driver status, Office status or regulatory permission in one country does not automatically apply in another country.
Each Part varies FOS-01 to FOS-04 for that market. Where a Part conflicts with those documents, the Part prevails for that market (FOS-01 §1.6).
Country ring-fencing is substantive. Each active country is intended to have separate contracting records, payment and merchant accounts, financial ledgers, regulatory approvals, insurance, tax records, market tenant and dispute forum. No country entity guarantees another, and no country entity is liable merely because another country uses the same FleetOS brand or technology.
If the same owner, director, employee, brand licensor, software vendor or cloud provider is involved in more than one market, that common feature does not merge the entities or their contracts. Any intercompany service must be documented separately and does not make the service-provider entity a party to the user’s local agreement.
Part C — Syria
C1. Contracting entity
Syria public contacts: Legal/support: info@fleetapp.net · Privacy: privacy@fleetapp.net · Telephone: +963 992 222 338 · Legal Center: https://fleetapp.net/#legal. Registration/licence particulars and the registered street address are maintained privately and disclosed only where legally required or to an authorised authority.
Your contracting entity is Ramo Single-Member Limited Liability Company (شركة رمو المحدودة المسؤولية ذات الشخص الواحد). This public edition does not publish the company registration/licence number or registered street address. This Part applies where the Platform Services are offered in Syria or a Ride begins in Syria.
Syria separation. The Syrian contracting entity is solely responsible for Syrian FleetOS obligations. The United States and Qatar FleetOS entities are not parties, guarantors or co-obligors under Syrian user or Office contracts merely because of brand, ownership, technology or support arrangements. Syrian accounts, SYP settlement records, contracts, regulatory records and data-controller records are maintained as a separate market tenant.
C2. Language
Documents are published in Arabic and English. The Arabic text controls in Syria.
C3. Governing law and jurisdiction
These Terms are governed by the laws of the Syrian Arab Republic, and the competent Syrian courts have jurisdiction. Mandatory Syrian consumer and labour law is unaffected. Arbitration under Part A does not apply and no class-action waiver is asserted.
C4. The sanctions and export-control position
C4.1 What changed
The United States sanctions position on Syria changed substantially between 2025 and the date of this document. Executive Order 14312, issued on June 30, 2025, removed United States sanctions on Syria, revoking the six executive orders that formed the foundation of the Syria sanctions programme and terminating the underlying national emergency. On December 18, 2025, the FY2026 National Defense Authorization Act repealed the Caesar Syria Civilian Protection Act of 2019.
On export controls, exports and reexports of EAR99 items to Syria have been authorised since September 2, 2025 by License Exception Syria Peace and Prosperity, provided the transaction does not otherwise require a licence based on end-use or end-user, including OFAC Specially Designated Nationals under part 744 of the EAR. United States-origin software and technology with purely civilian uses — classified EAR99 — can generally go to Syria without an export licence.
C4.2 What remains restricted
Targeted U.S. sanctions, restricted-party rules, end-use and end-user controls, and export controls continue to apply to particular persons, entities, items and activities. Third-party banks, app stores, cloud providers and other service providers may also impose their own lawful restrictions. FleetOS therefore screens relevant parties and evaluates the legal basis for any U.S.-nexus software, technology, payment channel or service before enabling the affected functionality.
C4.3 Why this matters to a Syrian user
The Syrian Local FleetOS Entity is a separate contracting entity, and the existence of a separate United States FleetOS market entity does not by itself make the U.S. entity a party to Syrian contracts or liable for Syrian operations. United States sanctions and export-control rules may nevertheless apply to a particular service or transaction where there is a U.S. nexus, including participation by a U.S. person, U.S.-origin or EAR-subject software or technology, a U.S. financial channel, or a restricted end user or end use. Those questions are assessed transaction-by-transaction under the compliance programme in C5.
C5. Conditions of operation
FleetOS operates in Syria subject to a compliance programme with four mandatory components. Each is a condition of your access.
C5.1 Export classification
Before software or technology is supplied or enabled for Syria, FleetOS records the applicable export-control classification and lawful basis in the FleetOS compliance record and re-assesses that position when relevant functionality changes. Where an item is subject to the EAR and classified EAR99, current BIS rules may permit export or reexport under License Exception Syria Peace and Prosperity (SPP), subject to its conditions and all end-user, end-use and other restrictions. A feature remains unavailable whenever the required export-control basis has not been verified.
C5.2 Restricted-party screening
| Every Office, every beneficial owner, every Driver and every payment counterparty is screened against the OFAC Specially Designated Nationals list and other applicable restricted-party lists at onboarding and on a recurring basis. Screening is enforced as a mandatory compliance restriction in the product, not as a manual policy step. A positive or unresolved match blocks activation and suspends existing access pending resolution. |
|---|
By using the Platform Services you give the warranty in FOS-01 §24.1 on each occasion of use, and you consent to this screening as described in FOS-02 Annex C §C4.
C5.3 Prohibited end uses
The Platform Services must not be used for or in support of any military, intelligence, security-service or government surveillance end use; any activity involving a designated person or entity; the proliferation of weapons; or any end use prohibited under applicable export-control law. This is an ongoing covenant, and breach permits immediate termination without notice or liability.
C5.4 Continuing review
The Syria position is under active legal development, including an open review of the State Sponsor of Terrorism designation. FleetOS re-reviews the position at least quarterly and on any material development, and may suspend or restrict any feature or the whole service where a change in law, sanctions designation, banking availability or security conditions makes continued operation unlawful or unsafe. This may happen at short notice and without liability to you.
C6. Payments
Payment and user-funded stored-value features remain disabled until an actually available, lawful and contractually approved processor/merchant/settlement structure for the Syria Local FleetOS Entity is documented and verified. Cash or other lawful off-platform settlement may be supported only if separately configured and disclosed.
Payment features in Syria are enabled only where the FleetOS compliance record records a lawful banking or payment arrangement that has been screened and confirmed. User-funded Wallet (FOS-03 §6.1 State 3) and currency conversion remain disabled in Syria. Where payment features are not enabled, Rides are settled directly between the Passenger, Driver and Office outside the Platform Services, and FleetOS is not involved in that settlement.
C7. Licensing and the Office's role
Operator Network. Operator Network Rides remain the Office's transportation operation. The Office is responsible for every Syrian transport authorisation applicable to it, vehicle and Driver licensing, insurance, employment/contractor obligations, fares and taxes, passenger service and regulator cooperation. For those Rides, the Syrian Local FleetOS Entity supplies platform technology and does not become the transportation provider merely because the Office uses FleetOS.
FleetOS Direct. FleetOS Direct is a separate operating model and must not launch in Syria unless Syrian counsel has confirmed in writing the Local FleetOS Entity's lawful role, required transport/app/platform authority, Direct-driver legal framework, insurance, consumer disclosures, pricing/payment position and any other prerequisite. If Direct is lawfully activated, the Syrian Local FleetOS Entity will assume the obligations Syrian law places on it as the identified Direct transportation provider.
C7.1 Syrian domestic-law launch opinion
Before passenger booking, dispatch, FleetOS Direct, Driver onboarding, in-app payments or other regulated mobility functionality is commercially launched in Syria, FleetOS must obtain a written opinion or launch certificate from qualified Syrian counsel addressed to the Syrian Local FleetOS Entity. The opinion must identify, as applicable: (a) passenger-transport and electronic-platform/app licensing; (b) Office, vehicle and Driver authorisations; (c) worker classification, employment and contractor requirements; (d) compulsory motor/passenger/employer insurance; (e) fare, tax, receipt and consumer-protection rules; (f) electronic-contract and electronic-signature requirements; (g) privacy, location-data, government-access and data-hosting/transfer rules; (h) payment, stored-value, settlement and currency controls; (i) advertising and communications rules; (j) accessibility and passenger-safety obligations; and (k) the appropriate Syrian dispute forum and enforceability of limitation, indemnity and arbitration provisions.
This Country Supplement does not represent that a U.S. sanctions/export review is a substitute for Syrian domestic-law authorisation. Where Syrian law or regulator practice is uncertain, FleetOS will use the more conservative operating position until Syrian counsel provides an updated written basis.
C8. Data protection and elevated-risk handling
FOS-02 Annex C applies. Where local conditions create elevated risk to individuals — including risk from disclosure of location or travel patterns — enhanced minimisation applies: shortened location retention, restricted internal access, and optional analytics disabled.
C9. Availability
Operational availability of an application does not itself establish sanctions, export-control, app-store or local-regulatory compliance. iOS distribution may be enabled, restricted or suspended only in accordance with documented legal and platform eligibility.
C9.1 Compliance conditions
FleetOS may restrict or withhold Ride-marketplace, Driver, payment, iOS-distribution or other functionality in Syria where applicable sanctions, export controls, restricted-party screening, local licensing, banking, insurance, data-hosting, privacy, security or third-party platform requirements are not satisfied.
No user or Office acquires a right to a feature merely because that feature exists in another FleetOS country. Syrian relationships remain solely with the Syrian Local FleetOS Entity, and any cross-border technology, hosting or support arrangement is treated as a separate service relationship rather than a guarantee or assumption of Syrian liabilities by another FleetOS entity.