Data Processing Agreement
When you enter personal data into truckplan.app — your customers, their contacts, your drivers and other staff — you are the controller and we are the processor. The GDPR requires both of us to have a written contract setting out exactly what we may do with that data. This is it. It applies automatically together with the Terms; you do not need to sign it separately.
1. The parties and the subject matter
The controller is you, the Customer. You decide what personal data you put into the platform, why you process it and how long you keep it.
The processor is us, the company identified at the end of this document. We process that data solely on your behalf, and only as far as needed for the platform to work.
This agreement forms an integral part of the Terms and Conditions. It is concluded electronically under Art. 28(9) GDPR and is valid without a handwritten signature.
In case of conflict between this document and the Terms, as regards personal data processing, this document prevails.
2. What we process, for whom, and for how long
The elements expressly required by Art. 28(3) GDPR:
Subject matter and duration
The processing has as its subject matter the provision of the truckplan.app platform and lasts for as long as you have an active account, plus the retention periods in section 8.
Nature and purpose
Storage, organisation, structuring, consultation, modification and erasure of the data you enter — that is, the ordinary operations of a business application. There is one purpose: making your application work. No other.
Categories of data subjects
- Your customers and suppliers who are individuals, or the representatives of corporate ones.
- The contact people you add to your address book.
- Your drivers, whether or not they use the platform.
- Your employees and collaborators who use the platform.
- Any other person whose data you enter.
Categories of data
- Identification data: name, company name, tax identification codes.
- Contact data: address, email, phone.
- Driver data: the expiry dates and, where applicable, copies of the driving licence, tachograph card, certificate of professional competence, identity document and medical and psychological certificates; the personal identification number (CNP) and identity document series, only where this option is enabled.
- Activity data: trips performed, days worked, settlement sheets and the amounts in them.
- Commercial data: trips, transport orders, invoices, costs, relationship history.
- Messages and attachments from the connected mailbox, only where email intake is enabled.
- Any content or file you upload.
Data that calls for extra care
In road haulage, some driver data is more delicate than the rest. The platform lets you keep it where your business requires it, and you decide whether and for how long to keep it:
- The CNP is a national identification number, for which Art. 4 of Romanian Law no. 190/2018 lays down special conditions. It is entered only where there is a legal basis for it, for example an obligation under employment or tax law.
- Medical and psychological certificates may contain data concerning health, a special category under Art. 9 GDPR. To track expiry dates, the expiry date is enough; the document itself is uploaded only if you have a basis for keeping it.
- Copies of identity documents and licences are kept for as long as they are needed for the purpose for which you requested them.
The platform is not designed for other special categories of data (political opinions, trade union membership, biometric data), nor for data on criminal convictions. If you need to process such data, write to us first, so that we can agree together on the additional measures required.
3. We process only on your instructions
We process the data only on your documented instructions. Your use of the platform — what you enter, how you configure it, what you ask through support — constitutes your instruction.
The only exception is a legal obligation. If Union or Romanian law requires us to process otherwise, we inform you beforehand, unless the law expressly prohibits such information (Art. 28(3)(a)).
If we consider an instruction of yours to infringe the GDPR, we tell you immediately and may suspend carrying it out until the matter is clarified (Art. 28(3), final paragraph).
What we never do with your data:
- We do not use it for our own purposes.
- We do not sell or rent it.
- We do not use it for advertising, ours or anyone else's.
- We do not use it to train artificial-intelligence models.
- We do not combine it with other customers' data.
4. Confidentiality of people with access
Access to your data is limited to people who need it to do their job, and only for as long as they need it.
All of them are bound to confidentiality, by contract or by law, and the obligation survives the end of their relationship with us (Art. 28(3)(b)).
Administrative access to a customer instance requires mandatory two-factor authentication, and every action is written to a log that cannot be deleted.
5. Security measures (Art. 32)
The measures below are implemented, not planned:
Separation
- A separate database per customer, with its own MySQL user. Not a “customer_id” column in a shared table — separate databases. A programming error cannot mix two customers' data.
- The application user has no rights to modify the database structure. An SQL injection could not drop a table.
- Sessions are bound to the instance; a cookie from one customer is not valid at another.
Encryption
- Fully encrypted traffic (TLS), including on customer subdomains.
- Database access passwords are encrypted at rest (AES-256-GCM).
- User passwords: Argon2id hash, irreversible.
- Backups are encrypted and verified by reading them back after every write.
Access control
- Roles and permissions on every action, closed by default: what is not expressly allowed is refused.
- Double checking — hiding a button is not a security measure; the route refuses anyway.
- Rate-limited sign-in attempts, per account and per network.
Continuity
- Regular backups, tested by actually restoring them — a backup never restored is an assumption, not a measure.
- Logging of security events.
We may improve these measures at any time. We will not reduce them below the level described here for the duration of the contract.
6. Sub-processors
You give us general authorisation to use sub-processors, on the conditions below (Art. 28(2)).
Each sub-processor is contractually bound to the same obligations as us. We remain fully liable to you for what they do (Art. 28(4)).
Who they are, today
| Category | What it does | Where |
|---|---|---|
| Hosting | The servers running the platform and the databases | European Union |
| Email delivery | Sending messages generated by the application | European Union |
| Payment processing | Collecting the subscription. Receives no data from your instance. | European Union |
| Artificial intelligence (OpenAI) — only with the “Documents with AI” option | Automatically reading documents uploaded on a driver's record: the document type, the expiry date and, where that option is enabled, the CNP. Does not use the data to train its models. | United States, with the safeguards in section 10 |
The named list, with exact company names and locations, is available on request at the dedicated data-protection address. We keep it off the public page so it does not become a map of our infrastructure for anyone looking for where to strike. The artificial intelligence provider is named above because data reaches it outside the European Union.
The “Documents with AI” option is included in some plans or enabled at your request. Using it — uploading a document on a driver's record — constitutes your instruction for this processing.
Integrations you choose
The services you connect yourself — the Oblio invoicing software, the ANAF Virtual Private Space, your own mailbox — are not our sub-processors. They are recipients chosen by you, with whom you have your own relationship, and data reaches them on your instruction.
Changes
When we intend to add or replace a sub-processor, we give you at least 30 days' notice. You may object with reasons within that period. If your objection is well founded and we cannot find a reasonable solution, you may terminate without penalty, with a pro-rata refund of the paid, unused amount.
7. How we help you meet your obligations
Data subject requests (Art. 28(3)(e))
If a person asks us directly for access to, rectification of or erasure of their data in your instance, we do not answer them — we have no right to. We pass the request to you without delay and help you answer it.
The platform gives you the tools: search, edit, delete and export, straight from the interface. For most requests you do not need us.
Security breaches (Art. 28(3)(f), Art. 33)
If a security breach affecting your data occurs, we notify you without undue delay and, in any case, within 48 hours of becoming aware of it.
The notification tells you: what happened, which categories of data and roughly how many people are affected, the likely consequences, and what we have already done. We give you everything you need to make your own notification to the supervisory authority within your 72 hours.
Notifying the authority and the data subjects is your responsibility, as controller. We give you everything you need to do it.
Impact assessments (Art. 28(3)(f), Art. 35–36)
If you need a data protection impact assessment or a prior consultation with the authority, we make available the processing information we hold.
8. What happens to the data at the end (Art. 28(3)(g))
On termination, you choose: we return your data, or we delete it.
- Export — you can do it yourself, at any time, from the platform, in a structured, machine-readable format.
- Temporary retention — we keep your data for 30 days after termination so you have time to take it. On request, we extend reasonably.
- Deletion — after that period we delete everything permanently, including from backups, within 90 days of termination.
The only exception is data the law requires us to keep (for example, the financial documents between you and us). Those remain, solely for that purpose, and we tell you which they are.
On request, we confirm deletion in writing.
9. Evidence and audit (Art. 28(3)(h))
We make available all information necessary for you to demonstrate compliance with Art. 28.
You have a right to audit, once per calendar year or whenever a security incident affecting you occurs. The conditions, so it stays workable for both sides:
- Written notice at least 30 days in advance.
- During normal business hours, without disrupting operation of the platform.
- The auditor signs a confidentiality agreement. You may object to an auditor who is a direct competitor of ours.
- The audit may not touch other customers' data. That is not negotiable: it is our obligation to them, identical to the one we owe you.
- You bear your own costs, unless the audit reveals a significant breach on our side — in which case we bear them.
If we hold independent certifications or audit reports, we make them available and they may replace an audit of your own.
10. Transfers outside the European Economic Area
Your data is stored and processed in the European Union.
The exception: reading documents with AI
When the “Documents with AI” option is enabled, a document uploaded on a driver's record is sent to the artificial intelligence provider in section 6, which may process it in the United States. The transfer relies on the European Commission's adequacy decision on the EU–US Data Privacy Framework, for as long as the provider is certified under it, and in any case on the Standard Contractual Clauses. Under the provider's terms, the data sent is not used to train models and is kept only temporarily, for abuse prevention, for at most 30 days. Only the result of the reading and the uploaded document remain in your instance.
Without this option, no document leaves the European Union.
Other transfers
If any other transfer outside the EEA ever becomes necessary, we make it only on the basis of:
- an adequacy decision of the European Commission, or
- the Standard Contractual Clauses adopted by the Commission, with an assessment of the law in the destination country and supplementary measures where that assessment requires them.
We tell you beforehand, under the conditions in section 6.
11. Liability
Each party is liable for its own breaches, under Art. 82 GDPR.
As controller, you are responsible for the lawfulness of the data you enter. In practice, this means:
- having a legal basis for each category of data, in particular for drivers' CNPs, document copies and medical certificates (section 2);
- informing the data subjects under Art. 13–14 GDPR, including about the use of the platform and, where you have enabled it, about the automatic reading of documents;
- keeping only the data that is needed, for as long as it is needed, and then deleting it from the platform;
- giving access in the application only to users who need it, through the available roles and permissions;
- checking automatically completed data (AI reading, email intake) before relying on it.
As processor, we are responsible for complying with this agreement and with the GDPR obligations that fall on us directly.
The liability cap in the Terms applies here too, except for administrative fines imposed by the authority for acts attributable solely to us, and for cases where the law does not permit limiting liability.
Who issues this document
- Company
- SQUEY APPWORKS S.R.L.
- Tax ID
- 49637953
- Trade register
- J24/296/2024
- Registered office
- Str. Transilvaniei nr. 6, bl. TJ1/70, ap. 7, Baia Mare, jud. Maramureș, 430213
- Contact
- contact@truckplan.app
- Data protection
- gdpr@truckplan.app
- Report abuse
- abuse@truckplan.app