Logisteo Carrier Portal Terms of Service

Terms for the Logisteo Carrier Portal: accounts, cooperation, documents, public information, complaints, ending the service and protection of entrusted data.

Version: 8 October 2026

§ 1. Operator and scope of these Terms

The provider of Logisteo Carrier Portal is DevConcept Venture Lab Bartosz Polak, ul. Romualda Mielczarskiego 121/416, 25-611 Kielce, Poland, Polish tax identification number (NIP) 9591437100, statistical identification number (REGON) 260030117, referred to as the “Operator”. For contracts, complaints, data exports and privacy matters, contact biuro@devconcept.eu. Correspondence may also be sent to the postal address above.
These Terms, version 2026-10-08, govern the electronic services provided through Logisteo Carrier Portal at carrier.logisteo.eu and the public availability boards associated with the Portal. They apply to organisation accounts, individuals using the Portal on their behalf and, where relevant, visitors to public boards.
The Operator supplies software and provides the agreed electronic services. Creating an account or using the Portal does not make the Operator a party to a carriage or freight forwarding contract, a carrier, insurer, freight payer or user’s representative. Any such role requires a separate, express legal basis.
The relevant parties agree the terms of carriage, freight forwarding, insurance, freight payment and settlements between business partners. Their contracts and applicable law determine the effects of actions carried out through the Portal. These Terms do not replace a transport order or transport contract.
The Operator makes these Terms available free of charge before a contract is concluded, in a form that can be saved and reproduced. A copy of these Terms and information about a customer’s own contract can also be obtained by contacting the Operator. Data processing is described in the Logisteo Carrier Portal Privacy Policy.

§ 2. Definitions and participants

Organisation or customer means the entity for which an organisation account is maintained and which enters into a contract with the Operator through an authorised representative. An individual contracting in their own name is the customer for that contract. Statutory consumer protection, including protection applicable to certain sole traders, depends on the law and the circumstances of the contract.
User means an individual using an account within the permissions granted and the authority they hold. An organisation administrator is a user authorised to manage its account; that application role does not by itself determine who is the controller of personal data.
Carrier means an organisation with a carrier profile in Logisteo. Authorisation to carry out transport, use vehicles and assign work to drivers follows from applicable law and legal relationships, rather than the creation of a profile.
Driver means an individual whose details are associated with an organisation, vehicle or transport order. Adding a driver record does not create an account, conclude a contract with the Operator or constitute consent to unrestricted processing of that person’s data.
Partner means a separate organisation participating in cooperation through Logisteo, including a freight forwarding company. Pool moderator means an authorised person acting for the organisation that manages a pool and its membership and publications.
Availability entry means information about a vehicle, an area or route and a declared availability period. An entry presents a resource for cooperation; it does not automatically reserve a vehicle.
Pool and public board mean a collection of publications managed by a specific organisation and its public view containing a limited set of data. A public board can be viewed without signing in, including by opening the address provided by a QR code.
Organisation content means data and files entered into the Portal, including company, fleet, driver, availability and order information, documents, messages and offers. The organisation’s rights to that content remain subject to other persons’ rights and applicable law.

§ 3. Services and technical requirements

Within the available functions and assigned permissions, the Portal enables customers to maintain an account and carrier profile, fleet and driver records, cooperate with partners, handle enquiries, offers and orders, exchange documents, publish vehicle availability, use pools and public boards, and view summaries, notifications and data from authorised integrations.
The service available to an organisation is determined by its contract, the description of the available functions and its permissions. A function described as planned, unavailable or requiring separate activation is not included in the service until it is made available on agreed terms.
Use requires an internet-connected device, a current browser supporting JavaScript, the ability to use session data necessary for account operation and a working email address. A camera is required only for selected scanning functions. Location integration requires an authorised GPS data source and configuration of that function; it is not required for ordinary account browsing.
The relevant form specifies permitted file formats and size limits. The organisation must ensure that an uploaded file meets those requirements. If an error prevents use of an agreed function, it can be reported to the Operator under the complaints procedure.
The Operator maintains the agreed functions with due care and provides updates required by the contract and applicable law. The user is responsible for their own device and connection. Use of the Portal and maps may involve communication with external services described in the Privacy Policy.
The Portal helps organise transport cooperation. It does not replace road navigation, safety equipment or actions required when carrying out transport. A user may operate a device while driving only in a lawful and safe manner.

§ 4. Registration and contract formation

The registering person must provide accurate and current details required by the form, an email address under their control and a password meeting the stated requirements. The organisation form includes the company name and Polish tax identification number (NIP). Anyone acting for an organisation must be authorised to enter into the contract and begin account configuration.
Before submitting the form, the user can read and save these Terms and the Privacy Policy. Accepting the Terms is a declaration concerning the service contract; it does not replace separate consent required for marketing, optional technologies on a device or other processing purposes.
A contract for Portal services is concluded for an indefinite period when a correctly completed form has been submitted, the Terms accepted and the account made available, unless an expressly accepted order specifies the duration of another service. Functions requiring an active account become available after email verification. The Operator makes contract confirmation and its terms available in a form that can be retained.
Registration may be refused because of incorrect information, lack of authority, a conflict with an existing account or a justified security risk. The issue can be clarified by contacting the Operator. Protecting existing users’ data may limit the detail of a message concerning an email address already in use.
Email verification, assessment of company documents and approval of pool membership are separate stages. An account or status in the Portal does not confirm the validity of all licences or insurance, creditworthiness or entitlement to use a particular vehicle.
Creating or activating an account or viewing a function does not create a payment obligation without express acceptance of a paid order and its price under § 12.

§ 5. Accounts, permissions and security

A user must act within their own authority and assigned permissions. The organisation must keep account details and its representatives’ access rights current. When authority ends, it must promptly change access using an available function or ask the Operator to revoke it.
Passwords, verification codes, integration keys and active sessions must not be shared with unauthorised persons. Suspected account compromise or disclosure must be promptly reported to the Operator. The Operator does not require a password or online banking credentials to investigate a report.
The Operator may use proportionate protective measures, including request rate limits, session expiry, temporary restrictions on suspicious sign-in attempts and additional verification of significant operations. A user can clarify the reason for a restriction by contacting a person acting for the Operator.
Online services involve risks including phishing, malware and session compromise. Users should update their device and browser, protect their email account, check the website address and exercise care when opening files and links. Login details should not be sent in response to messages from unverified senders.
The organisation may enter only bank accounts and integrations it is authorised to use and must check their accuracy. Changing a bank account in the profile does not replace notifying business partners in the manner required by their contracts.
Activity records and necessary technical data support service operation, security and incident investigation under the Privacy Policy. The Operator’s access to organisation content is limited to justified service needs, instructions and legal duties.

§ 6. Cooperation, enquiries, offers and orders

An invitation to cooperate concerns establishing a relationship in the application. Acceptance, rejection, suspension or reactivation affects the functions and data visibility assigned to that relationship. Those actions do not by themselves set rates, exclusivity, transport conditions or the partners’ liability.
Before making or accepting a binding declaration, a user must check their role, the other party’s identity, the order terms, vehicle specifications, locations, dates, price, currency, taxes and payment terms. Whether a declaration is binding follows from its substance, the parties’ agreements and the law, rather than solely from an application status label.
An enquiry, an offer, a response to an enquiry and order assignment are separate stages. Confirmation of an individual operation concerns that operation. The parties retain the complete agreed terms and documents required for the relevant transport.
The organisation must keep information, statuses and documents consistent with the actual course of cooperation. Questions about an order, performance, payment or obligations must be clarified with the relevant partner. The Operator handles reports concerning the software’s operation.
Exchanging transport documents or reports through the Portal does not alter statutory or contractual deadlines applicable to that transport. A complaint to the Operator about the Portal is separate from a claim against a carrier or freight forwarding company.

§ 7. Vehicle availability in the cooperation network

The organisation may list vehicles it is entitled to use and must provide current information about their specifications, route or area and availability period. An entry does not authorise loading or transport inconsistent with vehicle specifications or the law.
Visibility in the Logisteo network may include authorised recipients of that function even without an individual connection to the carrier. Visibility to trusted partners requires an active relationship and permission to view availability; selecting particular relationships may further narrow it. Visibility to selected partners restricts access to the specified active relationships holding the relevant permission.
Before selecting a visibility scope, the organisation must check that it is entitled to disclose the company, vehicle and entry information covered by that scope. The selected-partners option gives those partners access and is not restricted to the entry’s author.
Publication in the cooperation network is separate from publication on a board accessible without signing in. Public publication requires the actions and authorisation relating to a specific pool under § 8.
When plans change or the resource is used, the organisation must update or withdraw the entry. The Portal indicates its availability and expiry period. Renewing an entry does not reserve transport or accept a partner’s terms.
If the organisation uses an available automation following order completion, an entry for trusted partners may be created from the order performance information. The organisation must check that the entry remains accurate. The automation does not constitute separate authorisation for publication on a public board.

§ 8. Public availability boards and QR codes

A specific pool’s public board can be viewed without signing in. A QR code leads to the board’s address and does not prevent that address from being shared further.
Before publication, the carrier must select a specific pool and separately authorise participation in it. Moderator approval of membership and an active relationship with availability permission are also required. Acceptance of these Terms does not replace that authorisation.
Publication authorisation is a functional setting. The organisation must ensure an appropriate legal basis for processing personal data and provide the required information to individuals whose data may be involved in publication. Where processing relies on an individual’s consent, that consent must separately satisfy legal requirements.
A public entry contains a code, vehicle category and body type, loading method, declared load capacity and dimensions, selected equipment, availability area and availability, update and expiry dates. The area means a 20 km radius around the selected reference point; it is not the vehicle’s current GPS position.
An entry does not disclose the vehicle registration number, carrier name or direct contact details, its Polish tax identification number, private identifiers, detailed route, prices, orders or documents. Limiting the information does not mean an individual or carrier cannot be identified when it is combined with other information.
The board displays contact details for the organisation managing the pool. An interested recipient gives that organisation the entry code. An authorised moderator may link the code to the carrier and its contact details within the current membership, relationship and authorisation.
The organisation managing a pool may publish individuals’ contact details only on an appropriate legal basis and after providing the required information. Availability description fields must not contain unnecessary personal or confidential data.
Publication dates are interpreted in the Europe/Warsaw time zone. Publication lasts no longer than 14 days from creation or renewal, and expires no later than 24 hours after availability ends, subject to that 14-day limit. The displayed expiry date governs the specific entry.
A carrier can withdraw an entry or revoke pool authorisation without closing its account. Withdrawal, expiry, suspension of membership or loss of the required relationship ends public visibility. An authorised moderator can also stop publication in their own pool.
The Operator removes or restricts publications under its control as required by law. Copies previously saved by recipients outside the service may require separate action. Vehicle availability and transport conditions must be confirmed with the relevant party before a contract is concluded; membership approval is not a certificate of licensing or insurance.

§ 9. Documents and AI-assisted analysis

The organisation must upload legible documents in the correct category and only to the extent needed for the relevant process. It must retain originals where required by law or contract. Saving a copy in the Portal does not replace requirements concerning originals and proper archiving.
Uploading a document, reading its content, checking completeness and assessing entitlement or authenticity are separate actions. Upload confirmation concerns saving the file and does not by itself constitute a favourable assessment of the document.
AI-assisted document analysis is carried out by the Operator on its servers. It may assist in reading data, dates and risk indicators. Results may be incorrect or incomplete, particularly with illegible files or unusual content, and must be checked before being used for legal, tax, financial or authorisation decisions.
A technical error or absence of an analysis result is not an adverse assessment of a document’s authenticity. A risk label is not a finding of forgery, and completed processing is not confirmation of all company authorisations. Users can challenge a result and obtain an explanation by contacting the Operator.
Where an analysis result affects access to a function, the user can request reassessment by an authorised person and provide additional information. The Operator handles that request under the complaints procedure. Rights concerning decisions based solely on automated processing remain applicable where the statutory conditions for those rights are met.
Receipt or reading of a tachograph file does not by itself confirm the validity of a digital signature, the completeness of data or compliance with working and driving time obligations.
Document content is used for the agreed service under the Privacy Policy and data processing arrangements. Excessive personal data, unnecessary copies of identity documents and specially protected data must not be uploaded without an appropriate basis and need. Acceptance of these Terms does not authorise the Operator to use organisation documents for training general AI models or advertising.

§ 10. GPS, integrations and driver data

The organisation may connect only integrations it is authorised to access and grant them only the permissions needed. It must use driver, employee and contractor data lawfully; the Operator remains responsible for its own data processing obligations.
Location data may identify an individual and reveal their activity. Before monitoring begins, the relevant controller must determine the purpose, legal basis, scope, period, recipients and retention, assess necessity and proportionality, and carry out a data protection impact assessment where required by law. It must provide the required information to the individuals concerned. Employee consent or an employer’s acceptance of these Terms is not automatically an appropriate basis for every form of monitoring.
Sharing performance information with a partner must concern an authorised order and the justified scope of cooperation. Access to location history does not authorise its further disclosure beyond the agreed purpose.
Positions and statuses depend on the source, its latest update and connectivity. Users must consider timestamps and missing or delayed data. A map does not by itself confirm performance of transport. The history visible in the Portal does not determine the data retention period.
A public board displays an availability area and does not disclose a driver’s current location. GPS processing in other modules takes place within the relevant permissions, data processing terms and Privacy Policy.

§ 11. Financial information, early payment discounts and self-billing

Financial summaries present information recorded in the relevant process. The scope, period, currency and source must be checked before they are used for settlements. Amounts in different currencies must not be treated as a single total without an appropriate and disclosed conversion.
A Portal record, PDF file or export does not independently confirm correct invoice issuance, acceptance by the relevant official system, delivery to the business partner or recording of a payment. The significance of a document or confirmation follows from the relevant process and applicable law.
An early payment discount requires agreement between the relevant parties on its basis, amount, deadline and effect. Accepting a proposal or recording a Portal status does not prove receipt of funds. Payment confirmation requires information about the actual transfer of funds; discrepancies must be clarified with the relevant party.
Self-billing requires a prior agreement between the relevant parties, a procedure for approving individual invoices and any necessary authorisation. Accepting these Terms does not conclude such an agreement with the buyer of services. The function may be used only once its legal conditions are met and the appropriate process is made available.
The organisation must check the issuer’s and buyer’s roles, tax information, tax rate, currency, numbering and payment deadline before putting a document into commercial use. The Operator is responsible for the agreed software functions, while tax obligations and sales settlements remain with the relevant parties.
The Portal contract does not include holding customer funds, payment services, freight financing or factoring. Any separate service of that kind requires express terms, identification of its provider and compliance with applicable legal requirements.

§ 12. Fees and paid service orders

A payment obligation to the Operator arises only after the customer expressly accepts a paid order and its price. Creating or activating an account, using a function available without such an order or viewing a paid module does not create an amount payable.
Before a paid order is placed, the Operator presents the service scope, total price, currency, taxes, additional costs, billing method and period, contract duration and termination terms. Where the nature of the service prevents the price from being calculated in advance, the Operator states the calculation method and possible costs. It does not charge costs to which the customer has not lawfully agreed.
An electronic order must clearly indicate that it entails an obligation to pay. Additional paid options require a separate, express choice. Silence or a preselected option does not constitute consent to an additional fee.
A subscription, automatic renewal, minimum service period or special cancellation conditions apply only if disclosed before ordering and expressly accepted. These Terms do not themselves create those obligations.
Fees for other panels, implementations or separate services require an appropriate order and agreement on their terms. Transport remuneration agreed with a partner is separate from software fees.
Price changes do not apply retroactively to services already performed or ordered. A new charge requires disclosure and express acceptance of its terms. Statutory rights to reimbursement, price reduction and settlement for unused services remain unaffected.

§ 13. Content, rights and prohibited conduct

The organisation retains its rights to content. It authorises the Operator to store, technically process, reproduce, display and transmit that content only to the extent necessary for the agreed service, selected visibility scope and legal duties. This authorisation does not transfer ownership of data or copyright in documents.
Organisation content is not used for the Operator’s advertising or training general artificial intelligence models merely on the basis of these Terms. Separate use requires an appropriate basis and express agreement, respecting the rights of the individuals concerned.
Users must not supply unlawful content, impersonate individuals or organisations, falsify documents or statuses, infringe intellectual property, trade secrets or individuals’ rights, disclose data without a lawful basis, or list vehicles they are not entitled to use.
Attempting unauthorised access to another party’s data, circumventing security measures, distributing malware, deliberately overloading the service and sending spam are prohibited. Integrations and automated access require appropriate permissions and must respect security and other users’ rights.
To the extent protected by law, the software, marks and the Operator’s own content remain subject to the rights of their rightful holders. Users obtain the right to use the Portal within their contract. Actions that cannot be contractually prohibited under mandatory law remain permitted.
A suspected vulnerability can be reported to the Operator in good faith, describing the issue without unnecessarily disclosing another person’s data. Reporting does not require further exploitation of the vulnerability or obtaining unauthorised access.

§ 14. Moderation, notices and restrictions

Unlawful content, abuse and violations can be reported to biuro@devconcept.eu. This channel is available without an account and enables contact with a person. Polish or English may be used.
A notice should identify the precise content location, such as the page address or entry code, and explain the alleged violation. Contact details should be provided to receive acknowledgement and the outcome; statutory exceptions and additional requirements are not excluded by these Terms. The reporting person must act in good faith and according to their knowledge.
The Operator assesses notices diligently and without undue delay, acknowledges receipt where the supplied details permit and informs the reporting person of the outcome and available ways to challenge the decision. An account or legal representation is not required.
The Operator may proportionately restrict content, publication or access where required by law, a reliably established breach of these Terms or an urgent security threat. It considers the severity, scope, repetition, effects and possibility of remedying the breach, as well as the rights of those concerned. Where restricting a single entry is sufficient, an entire account is not blocked unnecessarily.
A person affected by a restriction receives its reasons, scope, basis and information about how to appeal, unless disclosure is legally prohibited. They can request reassessment by an authorised person acting for the Operator. Statutory remedies, including complaints or proceedings before a competent body, remain available.
A moderator manages content and membership in their own pool. Their actions do not remove the Operator’s service obligations. Notices to a moderator can be sent to the board’s contact address, and notices to the Operator to the address in these Terms.
Entry expiry, withdrawal of authorisation and absence of required membership or an active relationship may automatically end public visibility. This implements publication conditions rather than determining that a carrier has acted unlawfully. The Operator assesses content-violation decisions with human involvement; supporting AI analysis is subject to § 9.

§ 15. Service availability and complaints

The Operator maintains the service with due care, investigates reported defects and takes steps to remedy them. The service must meet the agreed scope and characteristics required by law. A specific availability level or response time applies where the parties expressly agree it for the relevant service.
The Operator gives reasonable advance notice through an available channel of a foreseeable interruption materially affecting use. In urgent circumstances, it contains the threat and gives information when possible. A technical interruption does not by itself exclude liability for failure to fulfil obligations.
Complaints can be sent to biuro@devconcept.eu or the Operator’s postal address. A description of the problem and contact details are sufficient; the incident time, case identifier and requested solution are helpful if known. Passwords and unnecessary personal data must not be sent.
Absence of a screenshot, error number or complete documentation does not automatically result in rejection. Where clarification requires additional information, the Operator requests only what is necessary, without creating excessive obstacles to exercising rights.
The Operator responds within 14 days of receiving a complaint, on paper or another durable medium, including email. The response contains findings and a proposed solution. The response deadline does not mean every technical repair must be completed within the same period; statutory rights and agreed repair obligations remain binding.
Where applicable law treats a complaint as accepted because no response was given by the deadline, that consequence remains in force. The contractual deadline for other customers does not restrict their statutory claims.
The complaints procedure is not a prerequisite for going to court, contacting a competent authority or using another remedy, unless applicable law requires it. A complaint about Portal services does not replace a transport complaint directed to the relevant transport party.

§ 16. Personal data and confidentiality

The Operator is a controller for its own registration, account administration, security, billing and contact activities. Purposes, legal bases, recipients, retention periods and individual rights are described in the Logisteo Carrier Portal Privacy Policy. A contract with an organisation is not automatically a contractual basis for all data concerning its employees or drivers.
Where the Operator processes operational data for an organisation according to its documented instructions, it acts as a processor. Processing is governed by § 21, which forms part of the contract, or an applicable individual agreement. The actual role follows from processing purposes and means; an application role does not determine legal status.
The organisation must ensure a lawful basis for collecting, transferring and sharing data and fulfil its own information duties. The Operator remains responsible for its obligations. Partners and pool-managing organisations are separate controllers for their own cooperation and publication purposes; jointly determining purposes and means requires the arrangements prescribed by law.
Accepting these Terms does not replace consent to marketing, optional technologies storing or accessing information on a device, publication of personal data or GPS monitoring. The service uses session data necessary for its operation. Other technologies and marketing communication require an appropriate basis and consent where legally required; refusal does not remove access to service functions independent of that consent.
Hosting is provided through OVH infrastructure and the Operator’s own servers. Document analysis, email handling and error monitoring are carried out by the Operator on its servers. External maps and other authorised integrations are described in the Privacy Policy.
The Operator and the organisation protect confidential information obtained through the service. Access is limited to authorised persons and justified needs. Confidentiality does not cover content properly made public within the selected scope, information lawfully public or disclosure required by law or a binding request from a competent authority. Authorisation for one publication does not extend access to other data.
The Operator implements technical and organisational measures appropriate to the risk. Requests concerning data rights can be sent to biuro@devconcept.eu. Individuals can also complain to the competent supervisory authority. Processing arrangements do not restrict data subjects’ rights.
Data is retained according to its purpose, instructions, legal duties and the Privacy Policy, including export and retrieval after the service ends. The Operator does not make an individual’s exercise of data rights conditional on purchasing a paid service.

§ 17. Termination, export and switching providers

A customer may terminate an indefinite account contract by emailing biuro@devconcept.eu, with immediate effect or on a specified later date. A person terminating an organisation’s contract must hold appropriate authority. The Operator verifies identity and authority only as necessary, confirms the end date and agrees a secure means of delivering data. Termination does not require an automated function in the Portal.
The Operator may terminate an indefinite contract on 30 days’ notice for an important reason: a material or repeated breach of these Terms; failure to remedy missing authority or information necessary for the service; failure to meet an expressly agreed payment obligation; a legal duty preventing further provision; or discontinuation of the contracted service. Where the cause can be remedied, the Operator first requests a remedy and allows an appropriate period of at least 7 days.
In the event of a serious and immediate threat to security or other persons’ rights, or an order from a competent authority, the Operator may immediately restrict access to the necessary extent. Termination without notice is permitted where continuing the service is unlawful or the threat cannot be resolved by a less restrictive measure. The Operator gives reasons unless disclosure is legally prohibited and enables the decision to be challenged and data to be retrieved securely, unless delivering it is legally prohibited.
Export of the customer’s own data or assistance with switching providers can be requested at the same email address, including before termination. The customer states whether they want a copy, transfer to another provider or their own infrastructure, or service termination and deletion. The Operator confirms the scope, recipient, format and transfer method; persons authorised by the customer can participate. Ordinary delivery of data and the switching process are free of charge.
Export covers data entered by the customer or generated through use of their service: organisation profile and account information; assigned fleet and driver records; relationships and availability settings; entries and publications; enquiries, offers, orders, statuses and history available to the organisation; messages, documents and processing results; financial and settlement information; supplied GPS data; and links, timestamps and metadata needed to reconstruct that information. It includes digital assets to which the customer is entitled and data within the agreed retention period.
Tabular data is provided in CSV or JSON format using UTF-8 encoding, with descriptions of the fields and relationships needed to use it. Files are supplied in their retained source formats. Export does not transfer software, source code, internal security keys or other organisations’ data to which the customer is not entitled. Protection of intellectual property and internal trade secrets must not be used to conceal the customer’s exportable data or hinder or delay its transfer.
When switching providers, the period between notifying the Operator and the start of the transition does not exceed 30 calendar days; the parties may start sooner. The transition lasts no longer than 30 calendar days. During it, the Operator continues the agreed service, exercises due care to maintain continuity, provides reasonable assistance, communicates known risks and protects data during transfer. The customer cooperates in good faith and provides the necessary information about the destination provider or infrastructure.
If completing the transition within that period is technically impossible, the Operator provides specific reasons and an alternative period, not exceeding 7 months, within 14 working days of receiving the request. The service continues throughout that period. The customer may extend the transition once by a period they consider appropriate for their purposes. The Operator confirms the agreed dates on a durable medium.
The contract concerned by switching ends after successful completion of the process, which the Operator confirms to the customer. If the customer chooses termination and deletion without migration, the contract ends on the date resulting from their notice, no later than 30 days after that choice is communicated. A request for a data copy alone, without termination, does not end the contract.
After the transition ends, the Operator allows at least 30 calendar days to retrieve data. For termination without migration, the same retrieval period runs from the end of the service. Earlier deletion requires an express, confirmed instruction from the authorised customer, within the limits of the law. After that period, or a later agreed date, data covered by the ended service is returned or deleted according to the instruction, § 21 and the Privacy Policy; separate statutory retention duties remain applicable.
Closing an account or deleting Portal data does not terminate transport contracts with partners or remove due obligations previously lawfully agreed. Separate services are settled under their expressly accepted terms and applicable law. No penalty applies for ending the indefinite account itself, and no fee may be used to circumvent the right to switch providers.
These rules do not restrict data portability, content retrieval, withdrawal or switching rights under the GDPR, consumer law and the Data Act where applicable. Switching does not guarantee identical operation of another provider’s software; the Operator nevertheless fulfils its obligations to enable transfer and cooperate.

§ 18. Liability

The Operator is liable for failure to perform or improper performance of its own obligations under the contract and applicable law. It is also responsible for persons and entities used to provide the service to the extent required by law. Using hosting, integrations or analytical tools does not automatically transfer that responsibility to the customer.
The organisation and user are responsible for their own unlawful acts, declarations and supplied content within the limits of applicable law. An individual’s or partner’s error does not relieve the Operator of responsibility for its own contribution to harm.
Carriage and freight forwarding obligations, resource availability information and settlements between partners remain with the relevant parties. The Operator does not guarantee the truth of every partner statement or successful cooperation, but retains its duties concerning its software, security and responses required by law.
Circumstances beyond the parties’ control are assessed under the law and according to their actual effect on performance. A party must communicate material impediments and take reasonable steps to reduce their effects. A failure or describing an event as force majeure does not by itself establish exemption from liability.
These Terms do not exclude liability for intentionally caused harm or liability and rights that cannot lawfully be excluded or limited by contract. They do not impose a general compensation cap, waiver of claims or an obligation for the customer to cover all of the Operator’s costs.

§ 19. Statutory protection for consumers and other entitled individuals

These Terms do not restrict consumers’ mandatory rights or those of an individual sole trader whose contract is not professional in character and who receives statutory protection to the relevant extent. Providing a tax identification number, using a business account label or describing cooperation as commercial does not by itself remove that protection. A voluntary declaration of the contract’s professional character is not a condition of entering into the contract.
Where a statutory withdrawal right applies to a distance contract, the entitled individual may withdraw without giving a reason within 14 days of conclusion. It is sufficient to send an unequivocal statement before the deadline to biuro@devconcept.eu or the Operator’s postal address in § 1. The Operator acknowledges receipt of a statement submitted electronically.
The following wording may be used, but a particular form is not compulsory: “To DevConcept Venture Lab Bartosz Polak, ul. Romualda Mielczarskiego 121/416, 25-611 Kielce, biuro@devconcept.eu. I give notice that I withdraw from the contract for Logisteo Carrier Portal services. I provide my name, address, the contract date and the date of this statement.” A paper statement should be signed; a handwritten signature is not required in an email.
Following valid withdrawal, the Operator reimburses payments received without undue delay and no later than 14 days after receiving the statement, using the same payment method unless the entitled individual expressly agrees to another method without costs. If that individual requested the paid service to begin before the withdrawal period ended and the legal requirements were met, settlement for the part performed may take place only under statutory rules.
Creating an account, signing in or accepting these Terms does not waive the withdrawal right. Any statutory exception requires all relevant conditions, prior information and separate declarations where required. The Operator does not infer loss of the right merely from starting to use the Portal.
Where digital service legislation applies, the Operator is responsible for supplying the service and its conformity with the contract, including required functionality, compatibility, security and updates. Entitled individuals have the remedies provided by law, including bringing the service into conformity, price reduction or withdrawal where the relevant conditions are met.
A material change negatively affecting access to or use of a digital service is subject to requirements for information on a durable medium and statutory termination without notice. Where the law allows 30 days to exercise that right from the change or later notification, these Terms do not shorten the period. Changes not necessary to maintain conformity do not create additional costs for a consumer.
The Operator enables retrieval of content to which an entitled individual has a statutory right within a reasonable period, free of charge, in a commonly used machine-readable format, subject to statutory exceptions and other persons’ rights. That right is separate from personal data rights.
Information about assistance and out-of-court consumer dispute resolution is available on the Polish Office of Competition and Consumer Protection (UOKiK) website. Consumers may contact the relevant consumer ombudsman or authorised body. If a complaint is not upheld, the Operator provides the legally required information about the competent body and its position on participating in those proceedings. Access to courts remains available.

§ 20. Changes to the Terms, governing law and disputes

These Terms, version 2026-10-08, apply to contracts concluded on their basis. Incorporating new terms into an existing contract must comply with the law, follow delivery to the customer and include the actions required for the relevant change. Historical acceptance of different wording is not treated as acceptance of new data processing terms.
The Operator may change these Terms or a continuously supplied service for a justified reason: changes in applicable law or binding decisions; the need to address a specific security threat; adaptation to a material change in supported technologies or integrations; improvement of an existing function; addition of a new function; or changes to the Operator’s details. Changes must be proportionate to their cause. They must not remove acquired rights or impose a fee without the required acceptance.
The Operator communicates a material contractual change on a durable medium, including email, at least 30 days before it takes effect, stating the reason, scope, new wording, date and right to terminate. A shorter period may apply only to a change required by binding law or necessary to address an urgent threat; the Operator explains the reason and preserves legally required protection.
The customer may end the contract before a material change takes effect and use export and retrieval under § 17. Where a change requires separate consent, continued use or silence does not replace it. Statutory rights concerning changes to a digital service remain unaffected.
The contract is governed by Polish law, taking directly applicable European Union law into account. This choice does not deprive an entitled individual of protection under mandatory provisions of the law that would apply without the choice.
Disputes are heard by the court competent under applicable law. These Terms do not impose exclusive jurisdiction at the Operator’s place of business or mandatory arbitration. The parties may seek an amicable solution without restricting statutory remedies.
The Polish and English versions present the same terms. Any discrepancy must be interpreted with regard to the actual contract, the language in which it was concluded and the protected individual’s applicable rights. Neither language version restricts mandatory rights.

§ 21. Personal data processing agreement

For data processed by the Operator on the organisation’s behalf, these provisions constitute a data processing agreement under Article 28 GDPR and form part of the service contract. The controller is the organisation determining processing purposes and means and entering into the contract through an authorised person; the processor is DevConcept Venture Lab Bartosz Polak, identified in § 1. Where the organisation is itself a processor for another controller, it must ensure the required authorisation for sub-processing, and the Operator fulfils sub-processor obligations within the agreed scope.
The subject matter is operation of the organisation’s selected, authorised Carrier Portal functions. Purposes include storage and disclosure of its operational data, handling cooperation, fleet, drivers, documents, availability entries, orders and settlements, agreed document analyses and GPS integrations where activated. Processing includes receiving, recording, organising, reading, analysing, updating, transmitting to authorised recipients, exporting and deleting according to instructions.
Data subjects include the organisation’s representatives and users, drivers, employees and contractors, business partners’ contact persons and persons appearing in supplied documents to the extent necessary for the service. Data categories include identification and business contact details, roles and permissions, vehicle associations, orders and performance information, document and settlement data, messages, location and time information and operational metadata. Processing does not include planned collection of special-category data or criminal conviction and offence data without a separate lawful arrangement.
Processing continues during the agreed service, the switching transition and a retrieval period of at least 30 days, unless the controller validly instructs earlier deletion. Where a later date is agreed, it continues until that date. Afterwards the Operator carries out the controller’s choice of return or deletion under the provisions below.
The controller determines a lawful purpose and scope, ensures legal bases and fulfils its own information duties. Documented instructions include the contract, settings and Portal operations selected by authorised persons, and additional instructions supplied in a form that can be retained. The controller may change instructions, receive assistance and information, and verify compliance. A change beyond the agreed service requires agreement on its scope without restricting statutory rights.
The Operator processes data only on the controller’s documented instructions, including transfers outside the European Economic Area, unless processing is required by Union or Member State law to which the Operator is subject. In that case it informs the controller before processing, unless the law prohibits disclosure on important public interest grounds. A transfer to a third country must comply with Chapter V GDPR; an instruction or general sub-processing authorisation alone does not replace those requirements.
The Operator ensures that persons allowed to process data are authorised only as needed and bound by confidentiality or an appropriate statutory duty. Data remains protected after their authorisation ends. Entrusted data is not used for the Operator’s advertising, training general AI models or other unagreed purposes.
The Operator implements and maintains measures required by Article 32 GDPR, appropriate to the risk, nature and scope of the data. They include access and permission controls, transmission protection, separation of organisations’ data, infrastructure and backup security, incident handling, restoration of availability and assessment of safeguards’ effectiveness. Details needed to assess guarantees are made available to the controller while protecting other customers’ security; this does not require disclosure of keys or other organisations’ data.
The controller grants general written authorisation for sub-processing necessary for the service. Before sub-processing begins, the Operator provides a current list identifying the entities, their processing activities and locations, including the relevant hosting providers using OVH infrastructure. The Operator gives at least 30 days’ notice on a durable medium of an intended addition or replacement. During that period, the controller can raise a reasoned data protection objection. An urgent change may occur sooner only with separate prior authorisation from the controller.
Following an objection, the parties seek a solution ensuring lawful protection. If no solution can be agreed, the controller may end the affected service before processing is entrusted to that entity, without a termination penalty and with export and settlement rights for unused services. The Operator imposes the same relevant protection duties on the sub-processor and remains responsible to the controller for their performance. An entity receiving data for its own separate purposes is not a sub-processor merely for that reason.
Taking the nature of processing into account, the Operator assists the controller through appropriate technical and organisational measures with data subjects’ Chapter III GDPR rights, including access, rectification, erasure, restriction and portability. Requests received concerning entrusted data are promptly forwarded to the controller unless documented instructions authorise the Operator to handle them. This does not restrict the Operator’s own duties as a controller in other processes.
Taking the nature of processing and available information into account, the Operator assists with Articles 32–36 GDPR obligations, including risk assessment, security, impact assessments and prior consultation. It notifies the controller of a personal data breach without undue delay after becoming aware of it, provides available information on its nature, scope, effects and remedies, and supplements it as findings develop. It cooperates to enable the controller to make timely reports and communications.
After the services related to processing end, the Operator, at the controller’s choice, returns or deletes all entrusted data and deletes existing copies, unless Union or Member State law requires retention. Return uses an agreed secure method. After the retrieval period expires, in the absence of another lawful instruction, the Operator deletes the data. Backups are protected, excluded from ordinary use and deleted under the retention criteria set out in the Privacy Policy; following restoration, deletion instructions are reapplied. Data retained under a legal duty is limited to the required purpose and period.
The Operator provides all information necessary to demonstrate compliance with processing obligations, allows controller or authorised auditor audits and inspections, and contributes to them. Timing and arrangements must be reasonable and respect security, confidentiality and other persons’ rights, without preventing effective audits, urgent incident review or an authority’s powers. No automatic frequency limit or prohibitive fee may exclude this right.
If the Operator considers an instruction to infringe the GDPR or other Union or Member State data protection law, it promptly informs the controller and explains its concern. It may suspend only the disputed action for the time needed to clarify a lawful course, protecting the remaining data and continuing lawful services. The parties cooperate with the competent supervisory authority within their respective obligations.
An individual processing agreement may specify or modify the scope for an organisation where validly agreed and compliant with the law. It does not restrict mandatory duties, individuals’ rights or liability required by the GDPR. These provisions bind the parties through the contract into which they have properly been incorporated; they do not retroactively authorise unagreed processing.