Legal information
MEHANIK Privacy Policy
Revision dated 02.11.2026
1. Who processes data and why
MEHANIK personal data contact: the support channel. Processing relates to registration, the selected digital service, order performance, calculations, safety, support and legal obligations. Different actions may require different grounds; accepting an agreement is not universal permission for every data item or purpose. Separate permission, where required, is requested through the applicable process. Users may seek processing information and request correction, access or deletion.
2. Data categories
Depending on the function, data includes name, phone, profile and photos; listings, products, services and bookings; driver, business, company, vehicle and invitation details; route points, times, location, GPS history, sensors and phone beacon data; orders, OTP confirmations and collection/handover photo/video; balances, tariff snapshots, reserves, charges and disputes. Technical data includes IP, sessions, access and notification tokens, language, app/browser parameters and diagnostics. These are applicable categories, not a requirement for every user to provide all of them.
3. Visibility to other participants
Visitors may view a listing’s public fields and uploaded materials. Relevant parties receive order details, necessary contacts, points and assigned vehicle; a customer may see the performing driver’s location. Parcel handover evidence is available in relation to that order, not as a public gallery. An invited telematics driver sees only authorised vehicles and settings. Administrative access depends on permissions and serves moderation, support, security and disputes. Do not put unrelated contacts, documents or unnecessary personal details in public descriptions or addresses.
4. Location, background use and permissions
Map-point selection uses the location provided. Driver operation and a phone beacon may require regular coordinates, including while the screen is off, where the user enabled that mode and OS permissions. Beacon controls allow it to be stopped; location permissions can be changed in device settings, affecting dependent features. Smartphone data must not be represented as vehicle ignition readings. A tracker owner must have a basis for monitoring the vehicle and affected persons and inform them; one account owner’s permission does not replace other people’s rights.
5. Technical providers and disclosure
Services may require processing by server, storage, map and push providers, including the Google Maps, FCM and APNs integrations in use. Information needed for a particular function is disclosed, such as a map point or notification token; using a map does not make the entire account history public. Recipients and processing countries may depend on the function and infrastructure, so exclusively local storage or the complete absence of third parties is not asserted. Lawful authority requests are considered under applicable law. Details of applicable providers and disclosure grounds may be requested from the operator contact.
6. Retention, safeguards and deletion
Technical and organisational safeguards restrict access; order and consent materials are retained for performance, verification and disputes. Absolute security or uninterrupted connectivity is not promised. Retention depends on the category, necessity and applicable basis; this document introduces no arbitrary universal period for all GPS, media and financial data. Deletion requests undergo obligation checks; deactivation anonymises main profile fields and revokes access, while related evidence may remain under restricted access. Pending grounds and periods for a category are not represented as complete physical erasure. /deletion explains the procedure and contact.
7. Data rights and requests
Profile tools and support allow correction of available details and requests for processing information, restriction, deletion or review of wrongly published data. Identity and authority may need verification to prevent unauthorised requests, without excessive document collection. Changing device permissions stops dependent future features but does not itself erase materials already lawfully retained. Requests about another person consider their rights and those of other participants. A data request does not waive complaints to competent authorities; mandatory law applies independently of this policy.