Back to Operalytix Fleet

Privacy policy

For Operalytix Fleet: the iPhone app and the web dashboard at fleet.operalytix.com. Version 2026-10 · Effective 26 October 2026.

In short

  • Your location is recorded only while you are clocked in on a shift. When you clock out, tracking stops, on the phone and on the server. The server refuses location data sent outside a shift.
  • What is recorded during a shift: your position, speed and heading, entering or leaving zones your employer has drawn, and alerts such as speeding or a long stop. Your employer's owners and dispatchers see this live and afterwards.
  • Your employer decides how the service is used and is responsible for your work data. Operalytix runs the service for your employer.
  • Raw location points are deleted automatically after 90 days, unless your employer sets a different period (between 7 and 730 days).
  • No advertising, no analytics or tracking software, and nothing is sold.
  • You can delete your account in the app at any time.

What Operalytix Fleet is

Operalytix Fleet is a fleet management service for delivery companies, made by Evolves EOOD. A company (the employer) creates an account and invites its people:

  • drivers, who use the iPhone app to clock in and out of shifts, take breaks and record vehicle checks;
  • owners and dispatchers, who use the web dashboard and the iPhone app to see drivers on a live map, manage vehicles, documents and zones, and receive alerts.

Drivers and dispatchers cannot sign up on their own: they join only with an invitation from their employer.

Who is responsible for your data

Who is responsible depends on which data it is.

  • Your data as a driver or member of a company — shifts, breaks, location and speed during shifts, zone events, alerts, vehicle checks and photos, your driver profile — is processed for your employer. Your employer decides what is recorded and why, and is the controller of that data in the sense of the General Data Protection Regulation (EU) 2016/679 (GDPR). Evolves EOOD runs the app and the servers on your employer's behalf as its processor: it processes that data only on your employer's instructions, under the data processing agreement.
  • Account, sign-in and security data — what an owner enters when creating a company, sign-in sessions, the technical request logs of the servers, and data used to protect the service from misuse — is controlled by Evolves EOOD itself.

Questions about your work records, corrections and objections go first to your employer (usually its owner or the dispatcher who invited you). You can always also write to us; if the request is one your employer must decide, we pass it on and tell you that we have done so.

Who we are

  • Operator: Evolves EOOD ("Evolves" Ltd.), trading as Operalytix
  • Company number: UIC 206114078, Bulgarian Commercial Register
  • Registered address: 14 Tsar Osvoboditel Blvd, floor 6, Sredets, 1000 Sofia, Bulgaria
  • Data protection contact: privacy@operalytix.com
  • Support: support@operalytix.com

What is recorded, and when

Your account and profile

Your name, email address, role (owner, dispatcher or driver), preferred language (English or Bulgarian), and, if you or your employer add them, your phone number and a profile photo. Your password is stored only as a one-way argon2id hash. If you use Sign in with Apple, we receive from Apple a stable identifier for your Apple Account and the email address you choose to share (which may be an Apple relay address), and, the first time, your name.

For drivers, the employer can also record your driving licence number and its expiry date, so that it is reminded before the licence expires.

Shifts

When you clock in and clock out: the times, the vehicle you chose, and, if you enter them, the odometer reading, the fuel level, a photo of damage and a note. The shift also stores an identifier of the iPhone it runs on (created by the app when it is installed, not your phone's serial number), so that only one phone records a shift at a time. Breaks are recorded with their start and end. Staff can correct a shift or end one you forgot to close; the correction is recorded with who made it. This is your employer's record of working time.

If a shift is still open after the maximum shift length your employer has set (16 hours unless it chose otherwise, or never if it turned this off), the server ends it automatically, at the time of the last position it received, and records that the system ended it. Tracking stops, the app tells you, and your employer receives an alert.

Location, only during a shift

Between clock-in and clock-out, the app records your iPhone's position every few seconds: latitude and longitude, accuracy, speed, heading (direction of travel), altitude when available, the time of the reading, and the phone's battery level (so a dispatcher can tell a flat battery from a lost signal). The positions are sent to the server in batches: by default every 15 seconds (less often while the vehicle stands still), and every 5 seconds while a zone applies to you, so that leaving a zone is noticed within seconds. If there is no connection, they are kept on the phone and sent when the connection returns, then deleted from the phone.

To keep recording while the phone is locked or the app is in the background, the app uses iOS background location for the duration of the shift. iOS shows the location indicator while this happens, and a Live Activity on the Lock Screen shows the shift timer, your speed and that tracking is on.

If Precise Location is off for Operalytix Fleet, iOS gives the app only an approximate position, which is not enough to check zones and the speed limit. The app then asks you to allow precise location for the shift and shows that the location is approximate; your employer sees "Approximate location" too. Whether to allow it is your choice in the iOS settings.

When you are not on a shift, the app does not record or send your location. Clocking out stops it. The server rejects location data that does not belong to an active shift.

What the server works out from your location

From the positions recorded during a shift the server calculates: distance driven, time driving and time stopped, top speed, and your current status (driving, stopped, on break, offline). It also detects, and records as events and alerts for your employer:

  • Leaving or entering a zone your employer has drawn on the map, and returning to it (with the time spent outside). Small GPS jumps at the boundary are ignored: a crossing counts only after two consecutive positions on the other side, or one position more than 25 m beyond the edge.
  • Lost signal near a zone boundary: the phone stopped sending positions within 100 m of a zone edge.
  • Speeding: driving above the speed limit your employer has set for longer than the time it has set.
  • A long stop during a shift (not on a break), and no location for longer than the time your employer has set while you are clocked in.
  • A shift ended automatically after the maximum shift length (see "Shifts" above).

Your employer can switch off the speeding, long-stop and no-location alerts for the whole company; switched-off alerts are not created at all. Your status and position are still shown.

An alert shows your name, the vehicle and its registration number, the time, where it happened, your current position, speed and heading. Owners and dispatchers can acknowledge an alert with a note; the note and who acknowledged it are recorded.

On your phone, the app also warns you when you drive above the company speed limit and when you are close to the edge of a zone that applies to you. These warnings are worked out on the phone itself.

Vehicles and fleet records

For each vehicle: registration number, make, model, year, VIN, photo, assigned driver, odometer, status, and its documents (insurance, registration, technical inspection, service, vignette) with expiry dates and scanned copies. Maintenance and fuel records: date, type, cost, odometer, place, and photos of receipts, with who entered them. A fuel record you enter during a shift is linked to you and to that shift.

Photos and documents

Photos (profile, vehicle, damage, receipts) and documents (PDF or image) are uploaded only when someone chooses to attach one. Before an image is stored, the server re-encodes it and removes all metadata embedded in it, such as the GPS position where it was taken, the date and the camera model. They are stored privately and can be opened only through a link that expires after 15 minutes. Uploads that are never attached to a record are deleted after 24 hours.

Notifications and devices

If you allow notifications, the app registers a push token with the server. On the web, if you allow browser notifications, the browser registers a push subscription. Alerts are sent only to owners and dispatchers; drivers do not receive alert notifications. During a shift, the iPhone app itself can warn a driver who exceeds the company's speed limit or leaves or approaches a zone; these warnings are created on the phone and do not pass through our server or a push service. For each sign-in session we store the device type and name and the app version, so you can recognise your sessions: Signed-in devices in your account settings (iPhone app: Settings › Account, or Profile › Account for drivers; web: Account) lists them, and you can sign out any one of them or all others, for example after losing a phone.

Face ID

If you turn on Unlock with Face ID in the iPhone app, iOS checks your face (or Touch ID, or the device passcode) on the phone itself. The app only learns whether the check succeeded. No biometric data is available to the app, Operalytix or your employer, and nothing about it is sent to the server. Locking the app does not stop tracking during a shift.

Audit log

The service keeps an audit log of significant actions: sign-ins and failed sign-ins, password resets, signed-out devices, changes to company settings, members, vehicles, zones and shifts, acknowledged alerts, exports (including every export of a driver's data), and every time an owner or dispatcher opens a driver's location history. Each entry records who acted, when, and the network (IP) address.

Server request logs

Like any web service, the servers keep a technical log of requests: time, network (IP) address (shortened in the web server's log), the address requested, the result and the app version. It is used only to run the service and investigate faults and misuse. Access tokens, signed file links, password reset links and invitation codes are removed from these logs, and so is the address of the page a request came from (the Referer).

What is not recorded

  • No location outside shifts. There is no trail of where you were before you clocked in or after you clocked out.
  • No advertising and no tracking. The app and the dashboard contain no advertising, analytics, crash-reporting or tracking software of any third party. Nothing is sold or shared with data brokers.
  • No contacts, no photo library browsing. The app sees only the photo you take or pick to attach.
  • No automated decisions about you. Alerts are information for people at your employer. The service does not take decisions that have legal or similarly significant effects on you; any decision is made by your employer.

Why, and on what legal basis

Data your employer controls

Your employer uses the service to organise deliveries, to know where its vehicles and drivers are during working time, to protect drivers, vehicles and goods, to respond to incidents and breakdowns, to keep working-time records, to manage vehicle documents and costs, and to encourage safe driving. The legal bases are normally:

  • Article 6(1)(b) GDPR (performance of the employment or service contract), for recording shifts, breaks and the vehicle used;
  • Article 6(1)(c) GDPR (legal obligation), where your employer must keep working-time records under the Bulgarian Labour Code or similar law in another country;
  • Article 6(1)(f) GDPR (the employer's legitimate interests in safety, protection of property and the organisation of work), for location, speed, zones and alerts during working time only.

The service is designed so that the legitimate-interest balance stays reasonable: tracking is limited to clocked-in time, raw positions are deleted after a set period, and every view of a driver's history is logged.

Location tracking during work is not based on your consent, because consent at work is rarely free. The screen the app shows at first launch informs you how tracking works and records that you have read it; it is not a request for consent.

In Bulgaria, an employer that introduces a system for monitoring working time and work discipline must adopt internal rules on it and inform its employees (Personal Data Protection Act, Art. 25h, together with Article 88 GDPR and the Labour Code). Your employer is responsible for that, for informing you before tracking starts, and for consulting employee representatives where the law requires it. Ask your employer for its rules.

Data Evolves controls

  • Creating and running a company's account: Article 6(1)(b) GDPR (the contract with the company).
  • The audit log, the server request logs and protection against misuse: Article 6(1)(f) GDPR (Evolves's legitimate interest in keeping the service and its customers' data secure).
  • Service emails about the account and changes to these documents are part of the contract. We send no marketing.

Who can see your data

  • Within your company: owners and dispatchers see drivers' live positions, statuses, shift and trip history, alerts, vehicles and reports. Drivers see their own shifts and the zones that apply to them, not other drivers' locations.
  • Evolves: only the few people who operate the service, when needed to run, secure or support it, on your employer's instructions, and bound by confidentiality.
  • Sub-processors and service providers:
    • CloudClusters, on the network of Psychz Networks (Dallas, Texas, USA): hosting of the servers, database and file storage.
    • Apple: Sign in with Apple (if you use it), delivery of push notifications to owners' and dispatchers' iPhones (the notification text and the device's push token), and maps. On iPhone, maps are Apple Maps; in the web dashboard, Apple MapKit JS is used when enabled.
    • OpenFreeMap: when the web dashboard does not use Apple maps, map images are loaded from OpenFreeMap. The viewer's browser sends its IP address and the map area being viewed; no names or driver data are sent.
    • Browser push services (for example Apple, Google or Mozilla, depending on the browser): deliver web notifications to owners' and dispatchers' browsers. The content is encrypted end to end; the push service sees only the subscription address.
    • Email: invitation, password reset and expiry reminder emails are sent from Operalytix's own mail server, which runs on the same hosting provider.
  • Authorities: only when the law requires it.

The full list of sub-processors is in Annex III of the data processing agreement. Companies are told 30 days before a sub-processor is added or replaced.

Where your data is stored

The servers, database and file storage are on a virtual server rented from CloudClusters, on the network of Psychz Networks, in a data centre in Dallas, Texas, USA. Storing data there is a transfer outside the European Economic Area. It is protected by the European Commission's Standard Contractual Clauses (Implementing Decision (EU) 2021/914) with the hosting provider, and by the security measures described below. You can ask for a copy of the relevant safeguards at privacy@operalytix.com.

How long it is kept

Retention is enforced by jobs on the server that run automatically, not by anyone remembering.

  • Raw location points (every position recorded during shifts): 90 days by default. Your employer can set a period between 7 and 730 days. After that the positions are deleted; the shift totals (distance, top speed, times) and the alerts and zone events stay.
  • Shifts, breaks, alerts, zone events, vehicle and fleet records, photos attached to them: for as long as your employer's company uses the service, unless your employer deletes them earlier. They are your employer's working-time and fleet records; how long it must keep them depends on the law that applies to it.
  • Unattached uploads: 24 hours.
  • Sign-in sessions: up to 60 days after the last use; expired sessions are deleted.
  • Audit log: for as long as the company uses the service.
  • Server request logs: 30 days.
  • Encrypted backups: 14 days, including any copy kept on separate storage. Data deleted from the service disappears from the backups within 14 days.
  • A deleted company: everything is erased immediately, then from the backups within 14 days.

Deleting your account

You can delete your account yourself. In the iPhone app: Settings › Account › Delete account (owners and dispatchers) or Profile › Account › Delete account (drivers). In the web dashboard: your name at the bottom of the sidebar (Account) › Delete account. You confirm with your password, or with Apple if you use Sign in with Apple (accounts without a password are deleted in the iPhone app). If you use Sign in with Apple, deleting your account also revokes Operalytix Fleet's access to your Apple Account, so it disappears from the apps using Sign in with Apple in your Apple Account settings; you can also remove it there yourself at any time.

  • Deleted at once: your sign-in and password, all your sessions, your push tokens, your profile, and all raw location points recorded on your shifts.
  • Kept by your employer: the shift records (times, breaks, vehicle, distance) and alerts, with your name as it was at the time, because they are your employer's working-time and fleet records. They are no longer linked to any account and cannot be reached by any sign-in. Ask your employer how long it keeps them.
  • If you are the only owner of a company, deleting your account deletes the whole company with all its data, after you confirm this separately. To keep the company running, make another member an owner first.

An owner can also delete the whole company directly: in the web dashboard under Settings › Company › Delete company, or in the iPhone app under Settings › Company › Delete company, confirming with the company's name and the password (or Apple). All members' accounts and all of the company's data are then erased at once, and from the backups within 14 days.

If you cannot sign in, write to privacy@operalytix.com from the email address of your account, and we will carry out the same deletion after confirming it is you.

Your rights

Under the GDPR you have the right to access your data, to have it corrected, to have it erased, to restrict its processing, to data portability, and to object to processing based on legitimate interests (including location tracking during work). For data your employer controls, send the request to your employer; you can also send it to us and we will pass it on and help your employer answer it. For an access or portability request, an owner of your employer can export everything the service holds about you as a driver in one ZIP file: your profile, shifts, breaks, all location points still kept (as a table and as GeoJSON), alerts, zone events, fuel records you entered and the audit log entries about you. The export itself is written to the audit log. For data Evolves controls, write to privacy@operalytix.com. We answer within one month.

You may also lodge a complaint with a data protection authority, in particular in the EU country where you live or work. In Bulgaria, this is the Commission for Personal Data Protection (КЗЛД), 2 Prof. Tsvetan Lazarov Blvd, 1592 Sofia, www.cpdp.bg. It is also Evolves's lead supervisory authority.

How it is protected

All connections are encrypted (HTTPS and secure WebSockets). Passwords are stored only as argon2id hashes. Sign-in tokens expire after 15 minutes and are renewed with single-use refresh tokens; on iPhone they are kept in the Keychain. Every company's data is kept apart from every other company's. The database is reachable only from the server itself. Photos and documents are stored privately and opened only through short-lived signed links. Backups are encrypted archives (AES-256); the key is kept on the server in a separate folder that only its administrators can open, and a copy of the key is kept by Evolves outside the server. Where backups are also copied to separate storage, only the encrypted archives are copied, never the key. Access by Evolves staff is limited to those who need it.

Children

The service is for businesses and the people who work for them. It is not directed at children, and it is not intended for anyone under 18.

Changes

If what the service records changes, this policy changes first and the version and date at the top move. Material changes are announced to companies by email or in the app before they take effect. The current version is always the one published here.

Privacy policy version 2026-10 · Operalytix Fleet · Terms of use · Data processing agreement · Support · privacy@operalytix.com