Access by company role
Visibility configured according to operational responsibility.
The Zenit Fleet Management Platform supports role-based access configuration and traceability for operations provided by the system. The public website and customer operating environment remain separate. These technical functions support governance, but do not define purpose, legal basis, retention or GDPR policies on the customer's behalf.
This page describes only declared functions and separations, without attributing unpublished certifications or infrastructure characteristics.
Access by company role
Visibility configured according to operational responsibility.
Traceability of operations
Supported actions linked to their operating context.
Separate environments
The public website is not the customer operating environment.
Project configuration
Roles, visibility and requirements are compared with the organization's context.
A security function reduces or makes a technical risk observable; compliance also requires the organization's decisions, records and procedures.
The platform can configure role-based visibility and make supported operations traceable. The detail depends on the module and active configuration.
The customer decides who can view location, history, events, driver records or video. It also defines purposes, retention periods, review procedures and request handling.
Hosting, data location, continuity, exports, logs, backups and other infrastructure requirements must be checked against the documentation applicable to the project. This page makes no additional guarantees.
The GDPR defines principles, accountability, rights and safeguards for personal-data processing; implementation must be assessed for the specific context.
The official text covers, among other matters, data minimization, storage limitation, accountability and security of processing.
Clarifications on access, traceability and separation between public site and operating platform.
No. The public website presents Zenit and collects commercial enquiries; fleet operations take place in the customer platform with dedicated access.
Yes. Configuration can distinguish visibility and responsibility according to the roles involved in fleet management. The effective perimeter is defined for the project.
No. Technical functions can support access control and traceability, but purpose, legal basis, notices, retention, roles and procedures remain the organization's responsibility.
They are checked for the project against configuration, roles, data flows, company requirements and available technical documentation. This page does not attribute undocumented certifications or architecture to the platform.
A technical contact can answer specific questions about access, traceability and hosting.
We use necessary technical cookies. With your consent, we may use analytics cookies to measure the site and Meta Pixel to attribute campaigns, build audiences and personalise advertising. You can reject or choose each category; the site will still work. Cookie policy · Privacy policy