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.
In which recording environments such personal data are stored;
The legal, contractual and processing-based grounds requiring retention;
The grounds requiring disposal (deletion, destruction or anonymisation);
The retention periods per data category and the basis for such periods;
The methods and techniques of disposal;
The periodic disposal process and the responsible unit and persons;
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.
Is not a party to any carriage, freight or logistics contract;
Is not a carrier, freight commission agent, freight forwarder, insurer or customs consultant;
Does not take possession of the cargo;
Does not guarantee the performance, the lawfulness of declarations, the solvency or the conduct of users.
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:
Term — Definition
Personal data — Any information relating to an identified or identifiable natural person.
Special categories of personal data — High-risk data listed in KVKK Article 6, such as data on race, health, biometric data, etc., as well as official documents containing an identity number.
Data subject — The natural person whose personal data is processed (user, driver, contact person, etc.).
Data controller — Forwardie Lojistik A.Ş., which determines the purposes and means of processing personal data and is responsible for the establishment and management of the data recording system.
Data processor / Sub-processor — Third-party service providers that process personal data on behalf of the data controller (e.g. cloud-infrastructure, payment and document-processing service providers).
Recording environment — Any environment in which personal data are held (databases, object storage, log systems, backups, etc.).
Retention — Keeping personal data for the period determined by the purpose of processing and/or applicable law.
Disposal — The deletion, destruction or anonymisation of personal data.
Deletion — Rendering personal data inaccessible and reusable in no way for the relevant users.
Destruction — Rendering personal data inaccessible, irretrievable and reusable in no way by anyone (e.g. complete destruction of the physical/digital medium).
Anonymisation — Rendering personal data such that it can in no way be associated with an identified or identifiable natural person, even if matched with other data.
Soft-delete — Deactivating a record at application level with a deactivation/soft-delete timestamp; physical deletion (purge) occurs at the end of the determined period.
Tokenisation — Representing card data by a token held at the payment service provider instead of its raw form; the raw/full card number (PAN) is never stored by the Company.
Periodic disposal — The process of disposing, on the Company's own initiative at recurring intervals determined under the Disposal Regulation, of data whose processing grounds have ceased to exist.
VUK / TTK — Respectively, Tax Procedure Law No. 213 and Turkish Commercial Code No. 6102.
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.
# — Recording Environment — Nature — Typical Data Types
3.1 — Relational database — Primary application database (EU-based cloud infrastructure) — Identity/account, company/organisation, business contact, transactions (demand/load/bid), invoicing/accounting, financial (IBAN / tokenised card reference), device/push, log/audit, business e-mails and instruction and rule records processed on behalf of customers
3.5 — E-mail / notification systems — Outbound and inbound e-mail and notification infrastructure — Sent e-mail logs, notification records, transmission of business e-mails reaching the Platform (including transfer to the e-mail infrastructure provider)
3.6 — Log / audit and error-tracking systems — Application logs and error tracking — User activity logs, sales action logs, payment/e-invoice/AI service-provider call logs, error-monitoring records (personal data minimised)
3.7 — Backup environments — Database and object-store backups — Periodic backups of the above environments (rotated)
3.8 — Sub-processor environments — Third-party service-provider infrastructures — Data held at the relevant sub-processor (e.g. tokenised card at the payment institution, temporary processing at the document-processing provider)
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
Tax Procedure Law No. 213 (VUK) and Turkish Commercial Code No. 6102 (TTK): retention of books, invoices, e-invoices and financial records for the period prescribed by law.
KVKK No. 6698 and secondary legislation: keeping processing and disposal records, the burden of proof of consent and the privacy notice.
Law No. 6563 on the Regulation of Electronic Commerce and related legislation, together with the Distance Contracts Regulation: retention of records relating to commercial/electronic communications and the subscription relationship.
Evidence and right-of-withdrawal processes under Consumer Protection Law No. 6502.
Periods prescribed by other applicable legislation (e.g. payment services, anti-money-laundering legislation to the extent it applies directly to the Company).
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
The necessity of evidence (proof) for the protection of rights and interests and against potential disputes and claims (throughout limitation periods);
Platform security, prevention of fraud/abuse, audit and accountability (log/audit records);
Operational integrity of demand/load/bid transactions and related participant relationships.
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.
The identity and contact details of the acting user cannot be severed from the related transaction record (request, load, bid, document, declaration); such data is not anonymised or pseudonymised. An anonymised record can no longer answer the authority's question, and that failure creates legal liability for the Platform itself.
This retention relies on KVKK art. 5/2(a) (expressly provided for by law) and art. 5/2(ç) (performance of a legal obligation); it does not depend on explicit consent and does not end when consent is withdrawn.
The retention period is determined by the period prescribed in the relevant legislation together with investigation, prosecution and limitation periods; where that period is longer than the periods set out elsewhere in this policy, the longer period applies.
A data subject's deletion request is invalid for data within this scope (see Section 5); the requester is informed with reasons.
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.
The purpose requiring processing ceases to exist;
All legal grounds underlying the processing cease to exist (where legislation, contract, legitimate interest and consent have all ended);
Where processing is based solely on explicit consent and the data subject withdraws that consent;
Where the data subject requests deletion or destruction pursuant to KVKK Article 11 / Article 13 and the request is accepted by the Company;
Where it is established that the processing is contrary to law or the rule of good faith;
Where the maximum retention period has expired and there is no other condition requiring longer retention.
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.
# — Data Category — Retention Period — Rationale / Basis
6.1 — Financial / invoice records (invoices, e-invoice XML, journal/accounting records) — 10 years — Mandatory retention under VUK and TTK; renders deletion requests invalid (Section 5).
6.2 — Contract & membership / subscription records — Duration of relationship + 10-year limitation — Performance of the contract and proof against potential claims (general limitation).
6.3 — Explicit consent records — Until consent is withdrawn + reasonable additional period for proof — KVKK Article 5/1 and the accountability/burden-of-proof obligation.
6.4 — Driver location history (real-time GPS, route/location history, background location) — Active load + operational-dispute period (proposed: 1 year), followed by deletion (proposed: anonymisation — pending technical implementation) — Performance of the service + limited legitimate interest. High-risk / consent-based data. Deletion of location history at the end of the period is the operative method; anonymisation is a proposed option to be applied once technically implemented (see Section 7.3).
6.5 — Chat messages (original + translated + content-moderated/masked version) — While account active + 10 years after soft-delete — Continuity of communication + evidence. Aligned with TCC art. 82 commercial-book retention and the general statute of limitations: in transport disputes the chat record is often the only written evidence.
6.6 — Scanned documents (ID/passport/driving licence, information extracted from documents, document verification result) — Processing purpose + statutory retention period; deletion once the purpose ends — Bound by the processing purpose; special-category/high-risk data are disposed of within the shortest reasonable time.
6.7 — Push / device tokens (push token, platform, device model/OS/version, permission status, anonymous web identifier) — While device registered + cleanup after 90 days of inactivity — Functioning of the notification service; regular cleanup of inactive tokens.
6.8 — Log / audit records (activity, sales action, e-mail log, payment/e-invoice/AI service-provider logs) — 10 years — Security, accountability and evidence in disputes (legitimate interest); aligned with TCC art. 82 and the general statute of limitations.
6.8a — Session replay — technical re-play of page interaction; password, one-time-code and card fields are NOT recorded; /backoffice and admin paths are never recorded — Indefinite (sessions shorter than 5 seconds / unplayable ones are destroyed after 3 days) — Understanding product usage, fault diagnosis and evidence in disputes (legitimate interest). Short sessions carry no observable information and are pruned regularly.
6.9 — Cookies and trackers — Per category: session / 6–12 months — The Cookie Policy prevails; category-based periods are specified there.
6.10 — Identity & account data (name, e-mail, phone, password hash, user code, 2FA flag, language, avatar) — Duration of relationship + relevant limitation; soft-delete + purge on account closure — Performance of the contract + proof; bound to the account lifecycle.
6.11 — Company / organisation & business-contact data — Duration of relationship + limitation — Operational relationship and proof; placed in disposal process once the relationship ends.
6.12 — Financial data (IBAN, BIC/SWIFT, account holder, bank, currency; tokenised card: token, last 4 digits, cardholder, expiry) — While relationship/payment method active; disposal when the payment method is removed or the relationship ends (financial-record exception reserved) — Performance of payment/subscription. Raw PAN is never stored; when a tokenised card is deleted, the token reference held at the payment institution is invalidated.
6.13 — Transaction data (demand/load/bid, participants, price/credit) — Duration of relationship + limitation; additional period under Section 6.1 for financial implications — Operational record + financial/proof requirement.
6.14 — Onboarding / verification (information processed during the membership/verification process, verification code) — Verification code: very short (minutes); other onboarding records: duration of relationship + limitation — Verification is momentary; onboarding records are kept for proof.
6.15 — Derived data (country detection from IP, document-type information) — Bound to the retention period of the source data; anonymous/aggregate where possible — Derivative data bound to the original processing purpose.
6.16 — Referral / affiliate (referrer attribution, commission earnings) — Commission period + financial-record period — Calculation of commission and financial/tax proof (financial-record exception reserved).
6.17 — Business e-mails — associated with a demand, load, quotation or invoice record (content, attachments, translations and summaries; in the capacity of processor on behalf of customers) — For the retention period of the record to which they are linked — Nature as commercial correspondence; instruction of the customer as data controller (Data Processing Agreement). The customer's return and deletion instructions are reserved.
6.18 — Business e-mails — not associated with any record — Content: 30 days from receipt (content that entered AI processing: 6.21); header information (sender, recipients, subject, date): period in 6.8; attachments: for the duration of the customer relationship, with earlier record-by-record destruction on the customer's instruction or the data subject's request — Data minimisation; header information is kept for security and evidentiary purposes.
6.19 — Rejected e-mails (unrecognised recipient, unsolicited e-mail, volume limit exceeded) — Content is not stored; security record (sender, recipient, date): period in 6.8 — Prevention of abuse and unsolicited e-mail (legitimate interest).
6.20 — Instruction and automation rule records (instruction text and versions, checklist marks, rule definition and approval record) — Duration of the customer relationship + statute of limitations; rule execution records: period in 6.8 — Performance of the service, traceability of changes and proof; for the part processed on behalf of customers, the Data Processing Agreement is reserved.
6.21 — AI interaction records (inputs given to AI functions — questions, instructions, text, document and e-mail content sent to AI — and the outputs produced; time of the operation, user and company, feature, feedback) — 10 years — Security, prevention of abuse, audit and proof; measuring and improving service quality (KVKK Art. 5/2-c, f). Period aligned with 6.8. Logistivo is a controller in its own right for these records (Data Processing Agreement 9.6); the customer's end-of-contract deletion request does not cover them.
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:
Row/column deletion from the database: permanently deleting the relevant record or overwriting personal fields with empty values.
Physical purge after soft-delete: records deactivated at application level via a soft-delete flag are permanently deleted at the end of the purge period set for the relevant category (e.g. proposed 1 year for chat).
File deletion from object storage (cloud object storage): permanent deletion of document/file objects from the object store.
Cache/queue cleanup: automatic expiry or cleanup of short-lived records at the end of their period.
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:
The token reference and metadata held by the Company (last 4 digits, cardholder name, expiry) are deleted;
The process required to invalidate/cancel the token at the payment service provider is initiated.
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).
Period: The Company carries out periodic disposal at intervals not exceeding six (6) months (in the relevant periods of each calendar year).
Scope: The periodic disposal scan covers all recording environments (Section 3) and all data categories (Section 6).
Documentation: Each periodic disposal operation is recorded with the date, scope, method applied (deletion/destruction/anonymisation) and the responsible person. Disposal records are retained for the minimum period prescribed by legislation (at least three years unless otherwise prescribed).
Automation: For data categories where possible, disposal is carried out through time-based automatic cleanup jobs (e.g. cleanup of inactive push tokens after 90 days, purge after soft-delete, cache expiry cleanup).
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:
Detection and internal logging: Suspicion/detection of a breach is immediately recorded by the responsible unit (Legal/Compliance + Technical/System Administration); the scope of the incident, the affected data categories and the number of data subjects are determined. All findings relating to the breach are documented in an incident log.
Assessment timeline: Whether the incident constitutes a personal data breach and its risk level are assessed without delay and within a reasonable maximum of three (3) days from detection.
Notification to the Board / competent authority: Notification is made to the Personal Data Protection Board (and, to the extent applicable, the relevant EU supervisory authority) within seventy-two (72) hours at the latest of the Company becoming aware of the breach. If notification cannot be made within this period, the reasons for the delay are recorded.
Notification to data subjects: Where the breach is likely to result in a high risk to the rights and freedoms of the data subject, the affected data subjects are notified within the shortest reasonable time in clear and plain language, with information on the nature of the breach, its likely consequences, the measures taken/to be taken and a contact point.
Documentation and record-keeping: Each breach is documented together with its causes, effects, corrective/preventive measures taken and notification steps, and these records are retained for auditability for the period set by Company policy (proposed: at least two (2) years).
Responsible unit and escalation: Coordination of incident response is the responsibility of the Legal/Compliance unit; technical response is carried out by Technical/System Administration. High-risk breaches are immediately escalated to the Data Controller Contact Person and senior management. Where the breach occurs at a sub-processor, the Company ensures information is obtained from the relevant sub-processor without delay and coordinates the notification obligations.
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).
Encryption in transit: Platform and API traffic is encrypted at the transport layer (TLS/HTTPS).
Protection of sensitive data: Passwords are stored only in hashed form; the raw/full card number (PAN) is never stored, and card data is tokenised at the payment service provider.
Access control and authorisation: Access to data is restricted on a role basis; data isolation between tenants is ensured in the multi-tenant architecture; internal team access is limited to what operations require.
Authentication: Token-based authentication; login for drivers via a short-lived/temporary code; a two-factor authentication flag where appropriate.
Error tracking and data minimisation: Transmission of personal data in error tracking (error/exception monitoring tool) is minimised; minimal personal data is kept in logs.
Backup and recovery: Backups are kept with restricted access, encrypted and solely for disaster-recovery purposes (Sections 3 and 7.7).
Organisational measures: Confidentiality obligations of employees/advisors, appropriate safeguard arrangements with sub-processors (Section 9) and the periodic disposal discipline set by this Policy.
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.
EU-based cloud infrastructure & storage provider — Application hosting (servers and database) and file / document / invoice storage — EU (Germany) — abroad for KVKK purposes — Every use of the Platform (hosting); when the user uploads a file/document or an invoice/PDF is generated (storage)
Contracted payment institution — Card tokenisation, 3D Secure, collection — Türkiye — domestic — When the user adds a card / a payment or subscription charge is made
Contracted payment institution — Payment — Türkiye — domestic — When the relevant payment flow is processed via this provider
E-invoicing & accounting integrator — E-invoice / accounting synchronisation — Türkiye — domestic — When e-invoice/accounting synchronisation is triggered
Document processing service provider — Document processing / parsing (full document including ID) — USA — cross-border — Only when the user uploads a document (e.g. ID/verification document) and document processing is triggered
Speech-to-text (transcription) service — Audio transcription — USA — cross-border — Only when the user sends a voice message and transcription is triggered
AI / language-model service providers — AI assistant, content moderation (compliance/masking); classification of, information extraction from, summarisation and translation of, and reply drafts for business e-mails; interpretation of instructions and automation rules — USA; other countries depending on the model used — cross-border — When interacting with the AI assistant, when chat/document content is run through the content-moderation process, when a business e-mail reaches the company or the user requests a draft/suggestion, or when instruction or rule text is entered
Push notification infrastructure provider — Push notifications — USA — cross-border — When the user grants push-notification permission and a device token is registered
E-mail infrastructure provider — Sending and receiving e-mail — USA — cross-border — When a system-driven e-mail (verification, notification, invoice) is sent; when a business e-mail is sent with the user's approval; when a reply arrives at the company's operations address or to a business e-mail sent through the Platform
Third-party map & location service provider — Routing / geocoding — USA — cross-border — When routing/geocoding or map display is triggered
Third-party map & location service providers — Map tiles — EU / USA (mixed) — When a map tile is displayed
Third-party IP geolocation services — Country detection — USA / EU — When country detection from IP is required
Error/exception monitoring tool — Error tracking (transmission of personal data is minimised) — USA (default) — When an error/exception occurs in the application
Public-holiday calendar data provider — Public-holiday calendar (no personal data) — USA — On public-holiday calendar synchronisation (no personal data is transferred)
Integration / data-bridge partner — Sharing of load / carrier data with an external system (data bridge) — Türkiye — When the relevant load/carrier data is shared via the webhook bridge
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:
Does not use the outputs of these models as a solely automated decision mechanism that produces legal effects concerning the data subject or similarly significantly affects them; AI outputs serve operational facilitation, classification and content moderation (compliance/masking), and the final decision/approval processes are subject to human oversight. In the e-mail, instruction and automation features, AI only produces suggestions: no e-mail is sent without the user's approval, suggestions do not change records until approved, and automation rules do not run without the approval of an authorised user.
Records and retains the inputs and outputs of AI functions (6.21); uses these records for security, audit and measuring and improving service quality, does not use them for marketing or profiling and does not provide them for training third parties' general-purpose AI models. AI requests are handled only by service providers that declare they do not use the data to train their own models.
Does not guarantee document-processing/AI accuracy (see Section 7.5 and the Privacy Notice / Explicit Consent Texts); confirming the official/legal/tax accuracy of document, declaration or location outputs is the user's responsibility.
The data subject may exercise their rights regarding automated processing affecting them (objection, requesting human intervention, expressing their view) under KVKK Article 11 and (to the extent applicable) GDPR Article 22, by the procedure set out in Section 12.
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.
Role — Duty
Technical / System Administration — Technical execution of deletion/destruction/anonymisation operations in the recording environments (relational and NoSQL databases, cache, cloud object storage, log/e-mail systems); operation of automatic cleanup jobs.
Accounting / Finance — Oversight of the retention of financial and invoice records for the VUK/TTK periods; placing expired financial records into disposal.
Legal / Compliance — Oversight of the compliance of retention periods with legislation, evaluation of data subject applications, justification of cases where deletion requests are invalid.
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.
Learn whether their personal data is processed and, if so, request information about it (access);
Learn the purpose of processing and whether the data is used in accordance with that purpose;
Know the third parties to whom the data has been transferred domestically/abroad;
Request rectification where the data has been processed incompletely/incorrectly;
Request deletion/destruction within the framework of the conditions of KVKK Article 7;
Request that rectification/deletion operations be notified to the third parties to whom the data has been transferred;
Object to an adverse outcome arising as a result of analysis by automated systems (see Section 9.1);
Claim compensation where they suffer damage due to unlawful processing.
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
The Company concludes the application as soon as possible depending on the nature of the request and in any event within thirty (30) days at the latest.
The application is, as a rule, free of charge. Where the operation additionally entails a cost, a reasonable fee in the tariff determined by the Personal Data Protection Board may be charged; for manifestly unfounded/excessively repetitive requests, a reasonable fee may be charged or the request may be refused.
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
Sub-processor — Transfer Nature — Basis (current) — DPA/SCC Status
EU-based cloud infrastructure & storage provider — EU (Germany) — abroad for KVKK purposes — KVKK Art. 9 appropriate safeguard (standard contract) — In process of execution
Contracted payment institution — Domestic — Contract performance — In process of execution
Contracted payment institution — Domestic — Contract performance — In process of execution
E-invoicing & accounting integrator — Domestic — Contract performance — In process of execution
Document processing service provider — Cross-border (USA) — Explicit consent / KVKK Art. 9 appropriate safeguard — In process of execution
Speech-to-text (transcription) service — Cross-border (USA) — Explicit consent / KVKK Art. 9 appropriate safeguard — In process of execution
AI / language-model service providers — Cross-border (USA; other countries depending on the model used) — KVKK Art. 9 appropriate safeguard (standard contract); Art. 9/6 in incidental cases — In process of execution
Push notification infrastructure provider — Cross-border (USA) — Explicit consent / KVKK Art. 9 appropriate safeguard — In process of execution
E-mail infrastructure provider — Cross-border (USA) — KVKK Art. 9 appropriate safeguard (standard contract); Art. 9/6 in incidental cases — In process of execution
Third-party map & location service provider — Cross-border (USA) — Explicit consent / KVKK Art. 9 appropriate safeguard — In process of execution
Third-party map & location service providers — EU / USA (mixed) — Appropriate safeguard (per provider) — In process of execution
Third-party IP geolocation services — USA / EU — Appropriate safeguard — In process of execution
Error/exception monitoring tool — Cross-border (USA) — Data minimisation + appropriate safeguard — In process of execution
Public-holiday calendar data provider — USA (no personal data) — Not applicable (no personal data transferred) — N/A
Integration / data-bridge partner — Domestic — Contract / data-bridge arrangement — In process of execution
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.