Security & GDPR

Security and GDPR, explained for fleet operators

Your fleet data includes vehicle locations, courier records, repairs and commercial performance. RideControl keeps the operating model clear: EU hosting, role-scoped access, export on demand, and a DPA for courier data.

RideControl fleet OS

One operating record for vehicles, people and hubs.

EU hosted
Unlimited users
CSV + API
2-week start

EU hosting and data ownership

All data is hosted in the EU. You own your data: every list, delivery trip, service request and invoice can be exported to CSV or pulled through the API at any time. There is no lock-in and no export fee.

  • EU-hosted fleet and courier data.
  • CSV export for lists and reports.
  • REST API access for connected systems.
  • No export fee.

Roles and permissions

Access follows the operating structure. Couriers, mechanics, hub leads and partner staff receive roles scoped to their group. A Warsaw hub lead sees Warsaw; a country manager sees the country. Client accounts can be separated in the same group tree.

  1. Step 1

    Model the groups

    Countries, hubs, fleets and client accounts become nodes in one tree.

  2. Step 2

    Assign a role

    Give each person the role they need for their work.

  3. Step 3

    Limit the scope

    The person sees their node and the parts of the tree it permits.

  4. Step 4

    Review the record

    User lists, handovers, offboarding and audit activity remain available for review.

Courier data and DPA

RideControl acts as processor for courier data. A DPA is available for operations that need one. Retention and deletion requests can be supported from the panel; agree the retention period for your operation during onboarding rather than assuming one universal period.

Backups and operational continuity

Operational data is kept in the hosted service so teams can work from the same current record. Backup and continuity details are available on request as part of an operation's security review. We do not claim certifications or guarantees that are not part of the published product information.

Security review before go-live

  1. Step 1

    Map the data

    List vehicles, couriers, trackers, service requests and the systems that need API access.

  2. Step 2

    Map the people

    Define hub, country, client and workshop roles in the group tree.

  3. Step 3

    Agree the paperwork

    Request the DPA, retention approach and any backup or continuity details your review needs.

  4. Step 4

    Import and reconcile

    Start with fleet CSV and service history, then keep the spreadsheet read-only while the team adopts the panel.

Frequently asked questions

Related

See it on your own fleet

Book a 30-minute walkthrough. We open the panel with your vehicle types, hubs and countries in mind — no slides.

Book a demo