Testing release. This policy describes the actual data-processing activities of the currently distributed ViaNexis Driver app version. If features or data-processing activities change, this policy will be updated before the next release.

This document is officially available in Hungarian and English. The application interface may be available in additional languages, but this legal document does not currently have official translations in those languages.

ViaNexis Driver – Data Safety Summary

Version: 1.0 · Effective date: 2026-07-31 · Last updated: 2026-07-31

This page summarises in plain language which data categories ViaNexis Driver may process, which permissions they relate to, and where the detailed legal documents are. The table is an overview; the chapters also describe limits found in the code audit.

This summary is informational. It is not the Google Play Data safety form, does not mean Google approval, and does not replace the Privacy notice. The Play form must be completed from the distributed app version’s actual permissions, SDKs and data flows.

Data category	What we may process	Required / optional	Source	Purpose	Recipients / providers
Account data	Name, email, phone, company affiliation; local PIN salted hash; auth tokens	Required for account use	User / system	Authentication, account management	Carrier company; hosting. Not sold.
Location data	GPS when permitted (when-in-use; no background location permission in the manifest)	Optional, permission-based	Device sensors	Map, trip location capture, some evidence/alert features	Depending on feature: backend / company; map stream may stay local
Camera, photos, videos	Trip / document / damage media	Feature-dependent, typically optional	User	Documentation, evidence	Carrier company; storage provider on upload
Documents and signatures	Transport documents, signature strokes, timestamp, optional location	Feature / trip dependent	User / company	Evidence, operational documentation	Carrier company; authority where legally required
Messages	Operational messages and attachments	Optional	User	Communication, documentation	Carrier company; translation path if translation is enabled
OCR / speech (if used)	OCR text; speech / audio input	Optional	Device / OS / upload	Input assistance	OCR typically on-device; speech/translation depends on path
Push token	FCM token, device-registration meta	Optional, when push is active	Automatic	Operational notifications	FCM / backend (to be assessed as a processor)
Device and security meta	Platform, language, timezone; security events	As needed	Automatic	Operation, security	Hosting; no separate analytics/Crashlytics SDK per current audit

1. Purpose of this document

This document is a plain-language summary of data-handling and security characteristics of the ViaNexis Driver application. It complements, but does not replace, the Privacy notice. It is not an official copy of the Google Play Data safety form and is not the store’s own declaration.

2. Covered application and version

Covered application: ViaNexis Driver. This summary aligns with the document version shown in the public legal package and with a code audit of the currently distributed app features. Features may differ by environment. Provider: Turul Atilla, sole proprietor and operator of the ViaNexis brand. ViaNexis is not presented as a separate legal entity.

3. What data the application may process

The application may process account, profile, trip, document, message and device data needed to operate the service. Some data arise only if the user grants permission or uses a feature (location, camera, microphone, notifications). Automated output (OCR, translation, speech recognition) may be assistive only.

4. Account and profile data

May include name, email, phone number, company affiliation, driver profile and session data. Authentication tokens may be kept in protected on-device storage. A local PIN may be stored as a salted hash, not as plaintext. Server-side password handling is described in the Privacy notice.

5. Trip and company data

May include trip identifiers, statuses, stops, pick-up/delivery data, vehicle and trailer data, licence plates, company settings and related operational metadata. These support the carrier company’s workflows. ViaNexis is a technology provider, not a carrier.

6. Location

The current Android manifest declares ACCESS_FINE_LOCATION and ACCESS_COARSE_LOCATION; ACCESS_BACKGROUND_LOCATION is not declared. Map own-position display is designed as when-in-use, local presentation.

Some features — for example trip-related location capture, checklists, signature metadata or a company alert — may record location during a user action, and that data may be sent to the backend or another channel the user initiates. Location may be inaccurate. Revoking permission may limit location-dependent features.

7. Camera, photos and videos

Camera and media-library access may be used for trips, documents, damage records or attachments. Content may be uploaded to the backend. Do not capture media in a dangerous way while driving. The feature is typically optional, but a company process may make it required for a task.

8. Documents and signatures

Uploaded documents and captured signatures support trip evidence. A timestamp and optional location may be attached. A digital copy is not necessarily an original instrument, and a captured signature is not automatically a qualified electronic signature. See the Terms of Use and Responsible Use documents.

9. Messages and notifications

In-app messages and attachments support operational communication and may be stored in the backend. Notifications may be operational. Under the current product intent there is no marketing push. Notifications may be delayed or may fail; they are not an emergency hotline.

10. Push token

When push is active in the relevant build and environment, the app may process a device/install-bound push token via Firebase Cloud Messaging (FCM) and register it with the backend. The token is needed for delivery. Notification permission can be revoked in system settings. Lock-screen previews may use a privacy-cautious local display path.

11. OCR and on-device processing

Some document aids may use Google ML Kit text recognition on the device. OCR may misread data. OCR output is not by itself a certified copy. Human review is required. This audit does not treat a cloud OCR vendor as active merely because a dependency exists.

12. Audio and speech recognition

If the user grants microphone permission, speech recognition or audio recording may assist input. Recognition may use the operating system or related services, and some paths may upload audio to the backend for transcription. The feature is optional. Completeness of iOS usage descriptions must be verified before an iOS store release.

13. Device and diagnostic data

May include platform markers, language, timezone, identifiers related to push-device registration, and security-relevant events. Based on the current code audit, we did not identify a separate Crashlytics, Sentry or analytics SDK in the distributed app package. Local debug logging may occur in development builds.

14. Third-party providers

Processors may be used to provide the service, such as hosting, database and file storage, and push delivery (FCM and, where applicable, APNs). Map-tile, translation or other external providers are treated as active only when enabled in the relevant environment. Google Play’s “sharing” concept differs from everyday language; classifying service providers requires operational and legal decisions.

16. Encryption and security

Data transmission uses a TLS connection when the service is available and properly configured for HTTPS. We do not claim that every build and every secondary path uses an encrypted channel under all circumstances.

On the device, authentication tokens and the local PIN hash may be protected with flutter_secure_storage, including the Android encryptedSharedPreferences option. We do not claim that every locally stored document or upload queue is encrypted at rest. We do not claim an independent security review or that the system is unbreachable.

17. Offline storage

Some data and upload queues may remain temporarily on the device (for example SharedPreferences and application files). Synchronisation may be delayed or may fail. Uninstalling the app may cause local data loss without deleting the server-side account.

18. Retention

Retention periods are determined by the purpose of the service, the carrier company’s obligations and applicable law. This page does not invent concrete retention deadlines in days. Details: Privacy notice.

19. Deletion and user control

Deletion requests are handled through a controlled process. Uninstalling the app, signing out and unlinking from a company are not the same as permanent account deletion. A request does not trigger immediate automatic full data deletion.

Request deletion of your account and associated data: https://vianexis.eu/en/driver-app/account-deletion

Privacy request form: https://vianexis.eu/en/privacy-request

Operating-system permissions (location, camera, microphone, notifications) can be managed in device settings.

20. Children

ViaNexis Driver is a professional driver application. It is not a service directed at children and is not aimed at users under 13. We do not knowingly collect children’s data.

21. Relationship to Google Play Data safety

The Google Play Data safety form must always be interpreted against the actual permissions, SDKs and data flows of the distributed ViaNexis Driver app version. This page is not the Play form, does not mean Google approval, and does not replace the store declaration.

22. Contact

Privacy: privacy@vianexis.eu Support: support@vianexis.eu Security: security@vianexis.eu Legal: legal@vianexis.eu Web: https://vianexis.eu

23. Final provisions

Related documents: Privacy notice: https://vianexis.eu/en/privacy Terms of Use: https://vianexis.eu/en/terms Responsible Use: https://vianexis.eu/en/disclaimers Account deletion: https://vianexis.eu/en/driver-app/account-deletion

In case of conflict, the Privacy notice and applicable law prevail. This document is officially available in Hungarian and English.

Questions about how we handle data?

Privacy / GDPR: privacy@vianexis.eu
Privacy contact: gdpr@vianexis.eu
Legal matters: legal@vianexis.eu
Customer support: support@vianexis.eu
Security reports: security@vianexis.eu