Mehanik

Legal information

MEHANIK Account Deletion

Revision dated 02.11.2026

1. Submitting a request

An authenticated user requests deletion through the website or app account-deletion function; help is available through support. The procedure is shared across MEHANIK platforms, not merely leaving one area. The request is linked to the account owner; external requests require identity and authority verification. Do not disclose passwords or OTP to strangers. Request status is distinct from signing out, uninstalling an app or revoking location permission.

2. Why a request may be held

Checks cover unfinished purchases, sales and bookings, current and scheduled transport obligations, open disputes, accepted parcels with unresolved handover/return, relevant balances, reserves and debts, and unclosed companies or fleets. An unavailable required check does not count as no obligations. The user is informed of held status and available reasons; once resolved, the request may be retried, or an authorised administrator may recheck the existing request with a recorded reason. Holding a request does not authorise taking a balance or remove statutory data rights.

3. Effects of deactivation

After successful checks, account and local-session access are revoked, main contact fields are anonymised, active publications are discontinued within the implemented mechanism, and schedule execution and professional access are disabled. Driver assignments and invitation access end through the applicable procedure. MEHANIK’s phone and hardware ingestion mechanisms must not accept new GPS events for a deleted owner. This is not a command to physically switch off another person’s tracker, erase device memory, close a third-party account or erase all of its external storage.

4. Information that may remain

Financial operations and evidence, tariff snapshots, necessary order and participant identifiers, disputes, handover proof, consent records and security logs may remain where a basis applies. Third-party materials are not erased solely because one participant closes an account. GPS history, photos, video, chats, complaints and copies require category-specific purpose, basis and period assessment. Automatic irreversible purging is not enabled for categories without established rules; this is represented neither as perpetual retention nor completed full erasure. Explanations or review may be requested for particular data.

5. Statuses and repeated requests

A held request means checks or obligations still prevent the relevant stage. “Access disabled, retention pending” means deactivation with the listed categories retained, not full physical erasure. Repeated requests refer to the existing request and must not create another financial settlement. Administrative rechecking records actor, reason and outcome; it does not bypass an open order, dispute, third-party rights or balance. If a reason is disputed, contact support with the request reference and evidence of resolution.

6. Individual requests and law

This procedure describes the available technical mechanism and does not remove statutory rights to correction, cessation of processing or deletion. If full account closure is held, a separate request may address particular excessive or inaccurate data. Periods and grounds are considered per category under applicable law, without an invented universal deadline. The operator does not represent deactivation as erasing every backup and third-party system. Access to competent authorities and courts remains; related terms are at /privacy and /agreement.