6Ride Enterprise

Corporate SLA & Enterprise Terms

These Corporate SLA & Enterprise Terms apply to organizations, institutions, hotels, campuses, event operators, and government entities using 6Ride for structured transportation and logistics services. They supplement the 6Ride Terms of Service and other policies and may be further refined by separate written agreements.

Effective: August 1, 2025Last updated: November 1, 2025HQ: Cross River State, Nigeria (HQ)Duty-of-care ready

Terms Privacy Acceptable Use Contact

Structured transport

Scheduled trips, policy controls, guest rides, campus/hotel pickup zones, and compliance-aligned workflows.

Enterprise governance

Admin roles, cost centers, reporting, incident workflows, and integrity controls for large organizations.

SLA clarity

Targets and triage rules are transparent; credits/remedies require defined scope and valid measurement.

Enterprise scope

1. Service Scope

What enterprise services include and how enterprise differs from consumer rides.

Enterprise services are designed for organizations requiring structured transport workflows, governance, and consolidated billing. Offerings vary by region and agreement and may include rides and (where available) delivery/logistics coordination.

Structured transportation

Scheduled trips, shift transport, campus/hotel pickup zones, guest rides, event shuttles, and approved route patterns where offered.

Governance & controls

Role-based access for admins, traveler groups, cost centers, policy flags, and booking permissions where offered.

Commercial operations

Invoicing, billing cycles, spend summaries, and dispute workflows under written agreement.

Compliance-first usage

Enterprise accounts must comply with platform rules, local law, and (where applicable) institution-specific safeguarding standards.

Separate written agreements

If an enterprise agreement conflicts with this page, the signed agreement controls for that enterprise relationship, subject to applicable law.

Governance

2. Enterprise Roles & Responsibilities

Clear roles reduce misuse, improve safety outcomes, and strengthen auditability.

Enterprise Admin

Controls onboarding, policy configuration, traveler permissions, and cost allocation. Must secure admin credentials and approve only authorized users.

Traveler / Employee

Uses 6Ride within enterprise policy. Must comply with Acceptable Use and safety rules and provide accurate booking information.

Guest / Visitor

May be booked through guest workflows where offered. Guests are still bound by safety and conduct rules during trips.

Institution / Campus Coordinator

Defines pickup zones, access points, time windows, and safeguarding expectations; coordinates with security where applicable.

Duty-of-care principle

Enterprises remain responsible for internal policies and traveler authorization. 6Ride provides tooling and enforcement, but cannot replace internal governance.

Targets

3. Availability & Performance Targets

We target high availability; operational realities and exclusions are clearly defined.

While 6Ride targets high availability, enterprise services are influenced by traffic, weather, supply, regulatory constraints, and third-party dependencies. Targets below are operational objectives, not unconditional guarantees, unless expressly stated in a signed agreement.

Platform Availability (App Services)

Target: Target high availability (region-dependent)

We aim to keep core booking and account services available. Availability is measured by the ability to request rides, view trips, and access enterprise tooling where offered.

Common exclusions

Scheduled maintenance windows (announced where feasible)
Third-party outages (maps, telecom, payment processors) beyond our control
Regional internet disruptions, power outages, or force majeure
Account-level restrictions due to fraud/safety/compliance reviews

Dispatch Performance (Pickup Experience)

Target: Operational target, not guaranteed

Pickup times depend on supply, traffic, weather, demand peaks, and local regulations. For scheduled programs, we apply structured dispatch workflows where offered.

Common exclusions

Traffic congestion, road closures, security checkpoints
High-demand events (concerts, stadium events, weather disruptions)
Rider/guest no-shows or incorrect pickup information
Safety holds and verification requirements

Enterprise Support (Response Routing)

Target: Severity-based prioritization

Enterprise support is prioritized by severity. Safety and security matters route ahead of billing and general inquiries.

Common exclusions

Incomplete requests lacking trip IDs, dates, city, or evidence
Issues requiring third-party verification or multi-party disputes
Requests outside the defined enterprise scope or missing agreement coverage
Abusive or spam requests that require integrity review

Measurement note

“Availability” generally refers to platform service accessibility, not guaranteed driver supply in every neighborhood at every moment.

Priority help

4. Enterprise Support & Escalations

Severity-based routing ensures safety and time-critical incidents get the fastest path.

Severity 1 — Safety critical

Credible threats, harassment, child/student safeguarding concerns, severe accidents, or active fraud signals. Routed to safety-first response.

Severity 2 — Operational disruption

Enterprise scheduling failures, major event transport disruption, widespread billing impact, or repeated dispatch failures.

Severity 3 — Standard requests

Routine billing questions, receipts, traveler onboarding, policy updates, and general support.

What speeds up resolution

Trip IDs, timestamps, city/region, traveler identifiers (enterprise), and clear desired outcome.

Abuse of escalation

False “safety critical” claims to bypass queues may result in restricted support access or account enforcement.

Structured trips

5. Booking Rules & Structured Transport

Enterprise booking tools are designed for predictability, auditability, and compliance.

Scheduled programs

Shift transport, school/campus runs, hotel transfers, and event logistics may use scheduling windows and approved pickup zones where offered.

Guest rides

Enterprises may book guests for conferences/hotels where offered. Guest behavior remains subject to platform conduct rules.

Policy-based restrictions

Enterprises may restrict ride times, locations, service types, or spend thresholds where offered.

Integrity requirements

No deceptive pickup/destination entries, no off-platform payment coercion, and no attempts to bypass enterprise controls.

Campus and school zones

If the enterprise is a school/campus, the Child & Student Safety Addendum applies and may require authorized handoffs and pickup controls.

Duty of care

6. Safety, Security & Duty of Care

Enterprise programs must be safe by design, not safe by luck.

Safety standards

All travelers, guests, drivers, and couriers must follow safety rules, Acceptable Use, and local law at all times.

Incident handling

Safety incidents may trigger immediate account actions, investigations, and—in lawful cases—cooperation with authorities.

Risk-based controls

We may apply extra verification, restrict features, or enforce compliance holds where risk signals appear.

Emergency service (where offered)

Some emergency workflows may require verified 6Clement Joshua membership and an active emergency subscription for specific tools; safety reporting remains available.

Enterprise responsibility

Enterprises must educate travelers/guests on behavior expectations and ensure only authorized users access enterprise booking tools.

Commercial

7. Billing, Invoicing & Taxes

Consolidated invoicing and flexible cycles may be configured under written agreement.

Corporate accounts may receive consolidated invoices and customized billing cycles. Specific pricing, discounts, taxes, and fees are defined by region and agreement.

Billing cycles

Monthly, bi-weekly, or custom cycles may be supported under agreement. Late payment may trigger restrictions.

Disputes

Disputes should be submitted promptly with trip IDs, receipts, traveler identifiers, and dispute reason.

Taxes and compliance

Enterprises are responsible for tax treatment of services where applicable. 6Ride provides receipts/invoices as available.

Non-payment

Non-payment or repeated payment failures may result in suspension or termination of enterprise services.

Invoicing precision

Enterprise invoices reflect recorded trip data. If your internal traveler roster is not maintained, reconciliation becomes slower and more costly.

Analytics

8. Reporting & Analytics

Reports support governance, budgeting, and compliance—but have limitations.

Common reporting outputs

Spend summaries, trip counts, utilization by cost center, top routes, cancellation patterns, and operational notes where offered.

Compliance reporting

For regulated programs, reporting may include audit-friendly exports where offered and permitted by law.

Limitations

Reporting availability varies by region, product maturity, and agreement scope; some data may be aggregated or delayed.

Confidentiality

Reports are for enterprise use and must be protected. Sharing or misusing personal data violates policy.

Rules

9. Compliance & Conduct

Enterprise users must align internal policies with platform standards and local law.

Local laws apply

Traffic rules, licensing, campus procedures, and safety standards vary by city/region; enterprises must comply locally.

Platform policies apply

Terms, Acceptable Use, Safety policies, and relevant addenda (e.g., Child & Student Safety) remain enforceable.

Training expectation

Enterprises should provide traveler guidance to prevent policy violations, misuse of support channels, and safety escalations.

No misuse

No harassment, discrimination, fraud, or attempts to bypass enterprise controls and fees.

Governance

10. Data, Privacy & Security

Access control, minimization, and privacy alignment are mandatory in enterprise programs.

Role-based access

Only authorized enterprise admins should access reporting dashboards and traveler data.

Data minimization

Enterprises should request and store only what is needed for governance and compliance.

Security obligations

Enterprises must protect admin credentials and prevent unauthorized use of enterprise booking tools.

Data processing and disclosure rules are governed by the 6Ride Privacy Policy and applicable law.

Sensitive programs

For campus and youth programs, additional safeguarding and privacy constraints may apply.

Remedies

11. Credits, Remedies & Limitations

SLA remedies require defined scope, measurement, and timely reporting; they are not open-ended.

Remedies for SLA misses, if offered, depend on what is explicitly covered by a signed enterprise agreement (service scope, measurement method, credits schedule). Absent a written agreement, this page describes operational targets and governance principles rather than contractual credits.

Eligibility for credits (if agreed)

Enterprise must report within the defined window, provide evidence, and the miss must be attributable to covered services.

Exclusions

Force majeure, third-party outages, traffic/weather, inaccurate bookings, no-shows, fraud/safety holds, and regulatory actions.

Limitations

Credits (if any) are typically the exclusive remedy for SLA misses under the enterprise agreement.

No double recovery

You cannot claim both a refund and a credit for the same issue unless explicitly permitted in writing.

Investor-grade clarity

SLAs must be measurable to be enforceable. We avoid ambiguous guarantees and instead define targets, exclusions, and governance.

Account actions

12. Suspension & Termination

We may suspend/terminate enterprise services for risk, non-payment, policy violations, or legal requirements.

Non-payment

Repeated late payments or failures may trigger restrictions, downscoping, or suspension until resolved.

Serious policy violations

Fraud, harassment, safety abuse, or repeated misuse may trigger immediate suspension/termination.

Legal and regulatory requirements

We may suspend or modify services to comply with law, regulator directives, or safety mandates.

Program shutdown

We may retire or modify enterprise features with notice where feasible; signed agreements may define transition obligations.

Continuing obligations

Confidentiality, payment obligations, and compliance duties may survive termination to the extent permitted by law and agreement.

Worldwide

13. Global Coverage & Local Terms

Enterprise programs scale across regions, but regional realities and laws still apply.

Region-specific addenda

Some countries/cities require additional addenda for licensing, campus operations, or government transport programs.

HQ reference

Administrative headquarters: Cross River State, Nigeria (HQ). Operational support may be distributed globally as 6Ride expands.

Regulated sectors

Government and regulated sector programs may require stricter controls, documentation, and approval workflows.

Stricter standard prevails

Where rules differ, the stricter standard applies unless a signed agreement explicitly states otherwise within lawful bounds.

Updates

14. Changes to These Terms

We may update enterprise terms as products evolve; signed agreements control where applicable.

We may update this page to reflect product improvements, operational changes, or regulatory requirements. When we update it, we update the “Last updated” date at the top.

Material changes

For significant changes, we may provide additional notice to enterprise admins where feasible.

Automation note

Set NEXT_PUBLIC_POLICY_BUILD_DATE=YYYY-MM-DD in your deployment environment when you update this page to reflect the current date.

Enterprise services may also be governed by separate written agreements. Nothing on this page limits mandatory consumer protection rights where applicable law applies. For formal enterprise onboarding, use the Contact & Support page.