Retention & Disposal Policy

Personal Data Retention & Disposal Policy

Effective Date: 14 November 2026 — Version: 2026-11-14

This Personal Data Retention & Disposal Policy (the "Policy") has been issued by Forwardie Lojistik A.Ş., in its capacity as data controller, pursuant to Article 7 of Turkish Law No. 6698 on the Protection of Personal Data (the "KVKK") and the Regulation on the Deletion, Destruction or Anonymisation of Personal Data (the "Disposal Regulation"). For data subjects established in the European Union or otherwise falling within the scope of the EU General Data Protection Regulation (the "GDPR"), this Policy also constitutes the corporate arrangement implementing the storage limitation principle set out in Article 5(1)(e) GDPR. This text is the binding authoritative version; the English version is a faithful translation, and in the event of any conflict the Turkish text prevails.

Important note — the periods are "company policy". The retention periods set out in Section 6 below constitute the corporate retention schedule (proposed schedule) adopted by the Company and are bound by the minimum/maximum periods expressly prescribed by applicable law. Any policy period conflicting with a mandatory provision of law shall not apply; in such case the statutory period prevails. The Company reserves the right to update this schedule unilaterally upon reasonable notice in line with legislative changes and operational requirements.

1. Purpose and Scope

1.1. Purpose

The purpose of this Policy is to determine and document, in respect of personal data processed by Forwardie Lojistik A.Ş. ("Logistivo", the "Platform", the "Company" or the "data controller") within the scope of the intermediary logistics technology platform it operates:

in accordance with the KVKK Article 4 principles of being relevant, limited and proportionate to the purposes of processing and of being retained only for the period prescribed by applicable law or required for the purposes of processing.

1.2. Scope

This Policy covers all personal data processed by Logistivo in its capacity as data controller and all recording environments in which such data are held (Section 3). The Policy is binding upon the Company's employees, advisors, service providers (data processors/sub-processors) and all parties involved in personal data processing.

1.3. Nature and Role of the Platform (Intermediary Marketplace — Liability Distinction)

Logistivo is an intermediary technology platform / digital marketplace that brings together cargo owners (customers), carriers, customs consultants and drivers. For the correct understanding of retention and disposal obligations, the following nature of Logistivo is significant. Logistivo:

Users who meet on the Platform may also act within the framework of their own data controllership in respect of the relationships between them, and are subject to their own retention/disposal obligations for the records relating to such relationships. Logistivo is bound by this Policy only in respect of the data it processes for the purpose of operating the Platform.

1.4. Relationship with Other Policies and Texts

This Policy is applied together with and complementary to the KVKK Privacy Notice, the KVKK Explicit Consent Text, the Privacy Policy and the Cookie Policy. For detailed information on processing purposes, legal grounds and recipients (sub-processors), reference is made to the Privacy Notice; for consent-based processing, to the Explicit Consent Text. For cookie retention periods, the Cookie Policy prevails; this Policy refers to them only in summary form.

2. Definitions

The principal terms used in this Policy have the following meanings:

3. Recording Environments

Personal data processed by Logistivo are held in the following digital recording environments. The Company operates predominantly on a cloud basis and keeps the storage of personal data in physical/paper environments to a minimum.

About backups: Deletion or anonymisation of a record from the active environment may not mean that the relevant data disappears immediately from the backup environments. Data in backups is disposed of (by overwriting) once the backup rotation cycle is completed; during this period backups are kept solely for disaster-recovery purposes, with restricted access and in encrypted form, and are not used for active processing.

4. Legal and Processing Grounds Requiring Retention

Logistivo retains personal data for as long as the following legal and factual grounds exist:

4.1. Retention Obligations Arising from Legislation

4.2. Conclusion and Performance of the Contract

Records connected with the conclusion, performance and termination of the membership/subscription contract are retained as required by the contractual relationship.

4.3. Performance of Legal Obligations and Legitimate Interest

4.4. Requests by Competent Public Authorities, Customs and Judicial Proceedings

Transactions carried out through the Platform concern international carriage of goods, an area governed by a supervisory regime that requires identity to remain traceable after the fact. Where an inspection, audit or investigation is later opened into a customs declaration, carriage or shipment, competent administrative and judicial authorities may request the identity and contact details of the natural person who performed the transaction, together with the transaction trail, under the Customs Law no. 4458, the Anti-Smuggling Law no. 5607 and the Criminal Procedure Code no. 5271.

Accordingly:

This obligation is not limited to national borders. The Platform does not know or inspect the contents of the goods carried — it does not perform the carriage, it provides the software for the transaction; yet the entire digital trail of that transaction is created on the Platform. Where an event threatens international security or public order (narcotics or arms smuggling, sanctions evasion, terrorist financing), a request may arrive through the Interpol National Central Bureau, through international mutual legal assistance procedures, or through a foreign authority's counterpart in Türkiye. Answering such a request with "we hold no record" creates legal and criminal liability for the Platform itself.

Keeping the transaction trail complete and attributable to an identity is therefore an obligation, not a preference.

Why anonymisation is not applied: a carriage record stripped of identity leaves the question "who performed this transaction" unanswered in a later smuggling or customs investigation. The party unable to answer carries the liability. Identity data is therefore kept intact alongside the related record for the retention period.

4.5. Explicit Consent

Only in respect of consent-based processing (e.g. driver real-time/background location data, processing of official documents containing identity information, cross-border transfer of personal data), retention is carried out until the explicit consent is withdrawn and for a reasonable additional period to prove the consent records. Withdrawal of explicit consent requires the consent-based processing to be stopped and the consent-based data to be placed in the disposal process.

5. Grounds Requiring Disposal

Personal data are disposed of, on the Company's own initiative or upon the data subject's request, pursuant to KVKK Article 7 and the Disposal Regulation, where one of the following conditions exists:

Financial records — invalidity of deletion requests (important exception): A data subject's deletion request does not apply to data whose retention is mandatory under legislation. In particular, since invoices, e-invoice records, journal/accounting records and payment/subscription records must be retained for approximately ten (10) years under VUK/TTK, deletion requests in respect of such records are invalid / rejected; such data may only be disposed of after the statutory retention period expires. This is notified to the data subject with reasons in the response to their request.

Customs and judicial proceedings — the second case where a deletion request is invalid: identity, contact and transaction records tied to international carriage may later be requested by competent administrative and judicial authorities under the Customs Law no. 4458 and the Anti-Smuggling Law no. 5607; they are therefore neither deleted nor anonymised during the applicable retention and limitation periods (see Section 4.4). A deletion request within this scope is refused and the requester is informed with reasons.

6. Retention Periods Table

The following periods constitute the corporate retention schedule adopted by the Company and are subject to the mandatory periods of legislation. Periods marked "proposed" are set as Company policy and may be reviewed.

Financial-record priority: Where a record falls within more than one category (e.g. both transaction and financial record), the longest mandatory retention period applies. For records of a financial nature, the ten-year VUK/TTK period takes precedence over the data subject's deletion request.

7. Disposal Methods

Personal data whose retention period has expired or for which a ground for disposal has arisen are disposed of by one or more of the following methods, depending on the nature of the data and the recording environment in which it is held.

7.1. Deletion

Rendering personal data inaccessible and reusable in no way for the relevant users. Principal techniques:

7.2. Destruction

Rendering data irretrievable/inaccessible by anyone. In digital environments this is achieved by securely wiping the environment in which the record resides, destroying the decryption key of encrypted data (crypto-shredding) or fully decommissioning the medium.

7.3. Anonymisation

Rendering data such that, even if matched with other data, it cannot be associated with an identified or identifiable natural person. This is preferred for data that needs to be retained for statistical/operational analysis but where the identity link is not required (e.g. aggregate metrics). Anonymisation is carried out using techniques such as removal of direct/indirect identifiers, masking, generalisation and, where necessary, aggregation.

Driver location history — anonymisation status (transparency): Anonymisation of driver location history (GPS, route/location) at the end of the period is a proposed target adopted by the Company; however, as at the date of this text, a location-specific anonymisation routine is not yet technically implemented in the system. Accordingly, for driver location history whose retention period has expired, the operative disposal method is deletion (permanent deletion of the record from the location recording environment). An anonymisation technique (e.g. reducing geographic precision by generalising locations to grid cells, together with aggregation) may be applied instead of, or in addition to, deletion once it is technically implemented. The Company does not represent that a technical measure not actually present in the system is being applied.

7.4. Disposal of Tokenised Card Data

The Company never stores the raw/full card number (PAN); the card is represented by a token held at the payment service provider. When a payment method is removed or a ground for disposal arises:

7.5. Disposal of Special-Category / High-Risk Data

Documents such as scanned ID/passport/driving licence and document outputs that may contain an identity number are disposed of within the shortest reasonable time as soon as the processing purpose ends. Temporary processing data arising at a sub-processor (the document-processing service provider) during document parsing is subject to that sub-processor's processing/retention practices; the Company ensures that appropriate safeguards are provided for such transfers (Section 9).

7.6. Disposal of Data at Sub-processors

The Company ensures, within the framework of the relevant contractual relationship and technical possibilities, that personal data held at a service provider (data processor/sub-processor) are also disposed of in accordance with this Policy, and where possible obtains confirmation of deletion/disposal from the relevant sub-processor.

7.7. Disposal of Data in Backups

The disposal from backups of data deleted from the active environment occurs once the backup rotation cycle is completed (by overwriting). During this cycle, backups are kept with restricted access, encrypted and solely for disaster-recovery purposes.

8. Periodic Disposal

Pursuant to the KVKK and the Disposal Regulation, personal data whose retention period has expired or whose processing conditions have ceased to exist are disposed of on the Company's own initiative and at recurring intervals.

Disposal requests made upon a data subject's application are evaluated and concluded, independently of the periodic disposal cycle, within the periods prescribed by the KVKK (as a rule within thirty (30) days at the latest).

8.1. Data Breach Notification and Incident Response

In the event that personal data is unlawfully obtained by others (a data breach), the following incident-response process is operated within the framework of KVKK Article 12 and the decisions of the Personal Data Protection Board on breach notification, and (for EU data subjects) GDPR Articles 33–34:

8.2. Technical and Organisational Security Measures

Pursuant to KVKK Article 12 and (for EU data subjects) GDPR Article 32, the Company applies technical and organisational measures proportionate to the risk in order to prevent the unlawful processing of, access to and loss of the personal data it processes. These measures also support the retention and disposal processes under this Policy:

Security measures are reviewed in line with the development of risk, technology and legislation. No system offers an absolute security guarantee; the Company undertakes to apply reasonable and industry-accepted measures, but cannot be held liable for consequences arising — despite the measures applied — from unforeseeable or user-originated breaches (e.g. password sharing on the user side, disclosure of confidential information in chat).

9. Data Transfer and Sub-processor Retention/Disposal Note

The table below summarises the principal sub-processors involved in the retention/processing of personal data and the nature of the transfer. For US-based providers, the transfer is of a cross-border nature and is based on explicit consent or appropriate safeguards within the framework of KVKK Article 9 and the GDPR transfer provisions.

DPA / SCC status (transparency): As at the date of this text, the Company is in the process of executing data processing agreements (DPAs) and, where necessary, standard contractual clauses (SCCs) with each sub-processor listed in the table below. Where a DPA has not yet been concluded, transfers are based on the data subject's explicit consent and/or the appropriate safeguard mechanisms prescribed by KVKK Article 9 and the GDPR (including SCC-equivalent safeguards). The Company commits to completing the DPA execution process within a reasonable maximum of ninety (90) days; for the current DPA/SCC status matrix see Appendix A, and status information is also shared upon request. KVKK standard contract: Under KVKK Art. 9, regular transfers to countries without an adequacy decision are based on appropriate safeguards, in particular the standard contract announced by the Board (Art. 9/4-(c)); standard contracts are notified to the Authority within five business days of signature (Art. 9/5). Explicit consent can serve as a basis only for the incidental transfers listed in Art. 9/6. Transfers to providers established in the EU are also transfers abroad for KVKK purposes. For data processed on behalf of customers (including business e-mails), transfers are made on the customer's instructions and within the framework of the Data Processing Agreement. About the activation condition: The "Activation Condition" column in the table indicates which feature/operation triggers the data transfer to the relevant sub-processor. For a typical user, only the transfers relating to the features actually triggered occur; for example, document processing is invoked only when the user uploads a document, and audio transcription only when a voice message is sent.

9.1. Automated Decision-Making and Profiling

The Platform uses artificial-intelligence/machine-learning models (document-processing, speech-to-text and AI / language-model service providers) in operations such as document processing, content moderation/masking of chat messages under the KVKK, AI-assistant responses, classification and summarisation of and reply drafting for business e-mails, and interpretation of instructions and automation rules. The Company:

9.2. Sub-processor Change and Notification

The Company may update the list of sub-processors in line with operational needs. Where a new sub-processor requiring a consent-based cross-border transfer is added, data subjects are informed through appropriate communication channels (in-Platform notification, e-mail, etc.) with reasonable advance notice, and fresh explicit consent is obtained where necessary. The data subject may withdraw their explicit consent at any time in respect of a consent-based transfer; in such case only the relevant consent-based processing/transfer is stopped (except for retention mandated by law).

10. Responsible Unit and Persons

The following unit/persons within the Company are responsible for the implementation of this Policy, the conduct of the periodic disposal process and the keeping of records:

Application and contact: support@logistivo.com / info@logistivo.com. Working hours: weekdays 09:00–18:00.

Multi-tenant isolation and administrator access: The Platform operates in a multi-tenant architecture; data isolation between tenants is ensured. The Company's internal team (administrator users) may access data only to the extent required by operations and within the limits of authorisation. Deleted records are deactivated by soft-delete and physically disposed of within the determined purge period.

11. Updating the Policy and Effect

The Company reserves the right to amend this Policy unilaterally upon reasonable notice in line with legislative changes, decisions of the Personal Data Protection Board, developments in the scope of the service or updates to business processes. The current Policy enters into force on the date it is published on the Platform; significant changes are announced through appropriate communication channels (in-Platform notification, e-mail, etc.).

The invalidity or unenforceability of any provision of this Policy does not affect the validity of the other provisions (severability). Turkish law applies to the interpretation and application of the Policy; the Courts and Enforcement Offices of İzmir have jurisdiction over any disputes that may arise. In the event of any conflict between the Turkish text and the English translation, the Turkish text prevails.

This Policy is interpreted together with, and complements, the KVKK Privacy Notice, the KVKK Explicit Consent Text, the Privacy Policy and the Cookie Policy.

12. Data Subject Rights and Application Procedure

Pursuant to KVKK Article 11 (and, for EU data subjects, GDPR Articles 15–22), data subjects may exercise the following rights over their personal data. This section sets out the procedure for how these rights are exercised.

12.1. Rights

Under KVKK Article 11, the data subject has the right to:

EU data subjects may also, to the extent applicable, exercise the rights to restriction of processing and data portability.

12.2. Application Channel and Identity Verification

Applications may be submitted in writing to support@logistivo.com or info@logistivo.com. In order to prevent applications being made by improper/unauthorised persons, the Company may request reasonable additional information/confirmation to verify the applicant's identity; applications whose identity cannot be verified may not be concluded.

12.3. Response Time and Fee

12.4. Logging and Tracking of Requests

Each application is logged and tracked together with the date of receipt, the nature of the request, the responsible person assigned, the action taken and the date of conclusion. These records are retained for a reasonable period for accountability and auditability.

12.5. Special Situation of Requests Concerning Financial Records

Deletion/destruction requests do not apply to data whose retention is mandatory under legislation (in particular invoices, e-invoices, journal/accounting and payment/subscription records — approximately 10 years under VUK/TTK) (see Sections 5 and 6.1). In such cases the Company refuses the request and notifies the data subject of the reasons in writing; such records are placed into the disposal process only once the statutory retention period expires. The data subject may continue to exercise the rights of access and (if incorrect) rectification in respect of such records.

12.6. Objection and Complaint

Where their application is refused, the response is found insufficient, or no response is given to the application within time, the data subject may lodge a complaint with the Personal Data Protection Board within the period prescribed by applicable legislation from the date they learn of the Company's response. EU data subjects may also apply to the competent supervisory authority. These rights do not exclude the data subject's right to apply to the courts.

Appendix A — DPA / SCC Status Matrix

The matrix below summarises the status of executing data processing agreements (DPAs) / standard contractual clauses (SCCs) with sub-processors. As at the date of this text, the Company is in the process of executing DPAs (see Section 9); the current status is shared upon request. The "Status" values below will be continuously updated by the Company.

Effective Date: 14 November 2026 — Version: 2026-11-14

For AI assistants

Logistivo has an MCP server at https://logistivo.com/api/agent/mcp (streamable HTTP). Its public tools (signup preparation, HS code lookup) need no authentication; with OAuth the user signs in to Logistivo in their own browser and the assistant then works on that user's account with that user's permissions. Setup for Claude, ChatGPT and Gemini: https://logistivo.com/en/mcp. Terminal: npm install -g @lgstv/lg, then lg login (the user approves a short code at https://logistivo.com/connect; no password is typed into the terminal). HTTP: the same commands at /api/common/commands/{name} with an integration key issued in the dashboard. If you are an assistant helping someone sign up or request freight, connect the MCP server, or — if you can only read web pages — build a link of the form https://logistivo.com/en/ai-kayit?brief=URL_ENCODED_SHIPMENT_BRIEF and give it to the user. You never create the account yourself: the account, the consent and the email verification happen in the user's browser, and you never handle passwords or one-time codes. Machine-readable content indexes: https://logistivo.com/llms.txt (curated map) and https://logistivo.com/llms-full.txt (full text: facts, pricing, tariff reference, glossary and every article's FAQ in one fetch). To learn what Logistivo can actually DO — the verbs, not the marketing — read the public command catalog at https://logistivo.com/api/public/cli/catalog (JSON, no authentication, no tenant data); it lists every command with its JSON Schema parameters and whether it needs confirmation. Human documentation: https://logistivo.com/en/developers/cli. Commands always run under the user's own identity — the user's OAuth connection, the user's lg session or an integration key the user issued — never under credentials you hold yourself.