Terms and Conditions
Professional ECU file-processing platform — contractual terms. ECU-LAB is designed for professional users. Modified calibration files may affect emissions, power, safety, warranty and vehicle approval. The availability of an option does not establish that its use is lawful.
Version 3.4-N · In force since 2026-08-25
1. Operator and scope
ECU-LAB is the online file-processing service published at ecu-lab.online (“ECU-LAB”, “we”, “us”). These Terms are the agreement between ECU-LAB and the Client for the use of that service.
Legal notices: contact@ecu-lab.online. File-specific questions must be submitted through the ticket attached to the relevant order.
The Service is offered primarily to businesses and professionals acting in their trade. By opening an account, the Client represents that it is at least 18 years old, has legal capacity and, where a company is named, authority to bind that company. Mandatory consumer rights remain unaffected where they lawfully apply.
2. Nature of the service
The Service consists solely in the automated or engineer-assisted processing of data and the application of binary modifications, on the express instruction of the Client and strictly to the binary file uploaded by the Client. What the Client receives is its own file, modified.
ECU-LAB does not deliver, distribute, license or transfer ownership of any pre-existing file from its own resources. No file held by ECU-LAB is supplied to the Client at any point.
The Client declares and warrants that it is the lawful holder of the software copy submitted, or that it is authorised by that holder, and instructs ECU-LAB to carry out the requested modification on that copy.
ECU-LAB owes professional care in carrying out the operations confirmed in the order. This is an obligation of means, not of result: ECU-LAB does not promise a particular power output, fuel consumption, durability or mechanical outcome.
For the avoidance of doubt, ECU-LAB does not: sell or distribute pre-stored ECU files; give access to its internal materials; read from or write to an ECU on a vehicle; install the result; inspect, diagnose or repair a vehicle; physically disable any component; or certify the legality, type approval or roadworthiness of a vehicle.
3. Definitions
- Account — the Client’s non-transferable access profile.
- Uploaded File — the ECU binary and related information submitted by the Client.
- Automatic Processing — automated processing available only when the Uploaded File is identified as an exact supported file, in which case ECU-LAB applies to it a modification it already holds for that file; it does not extrapolate or engineer a solution for an unknown file.
- Manual Processing — individual work performed by an ECU-LAB engineer under a separate price and delivery arrangement.
- Output File — the file generated for the selected options.
- Green Coins — daily plan allowance for Automatic Processing; they reset each day and do not roll over.
- Red Coins — purchased units, shown at the applicable EUR value, which do not expire while the Account remains active and may pay for Automatic or Manual Processing.
- Plan — prepaid access for the stated fixed period. Plans do not renew automatically unless checkout expressly states otherwise and the Client separately accepts recurring billing.
4. Acceptance and contract record
The Client accepts these Terms through an unticked checkbox at registration and, where displayed, again before authorising payment or download.
ECU-LAB records the document version, date and time, account, IP address and browser/user-agent as evidence of acceptance.
Material changes require renewed acceptance before continued use.
5. Service scope
The Client uploads its own file. ECU-LAB may identify it, restore supported calibration areas, or apply selected modifications to it. Automatic Processing applies only modifications that ECU-LAB already holds for that exact file; nothing is generated for an unknown file and nothing from the resources of ECU-LAB is delivered. If an exact supported match is not found, ECU-LAB does not automatically process the file and no Automatic Processing coins are charged.
Automatic Processing is a software operation, not an engineer review, custom calibration, dyno test or vehicle diagnosis. Manual Processing is separate and is performed only after its price and scope are accepted.
The platform displays only the options it considers available for the identification made. The absence of an option means it is not offered for that Operation; the Client cannot obtain an unavailable modification by renaming the file, adding a note or sending a message.
Displayed processing times are estimates. Statements such as “under a minute” describe the usual operation of automated Operations and are not a guarantee for every file or moment.
6. Restore to Original
Restore to Original is an automated function available only where the platform identifies the software version with sufficient certainty and holds the compatible References required for reconstruction.
The function aims to remove the calibration differences detected against the compatible original reference and to preserve, as far as technically determinable, the individual data that must remain associated with the unit or vehicle.
Restore to Original is not available for every file and does not guarantee a bit-for-bit reproduction of the content present in the unit at the time of manufacture, in particular where the original individual data has been erased, corrupted, replaced or cannot be identified safely.
Where the platform cannot establish a reference, or a safe separation between common and individual areas, with sufficient certainty, the Operation is refused and the Client is not charged.
7. Automatic Processing and charging workflow
- The Client uploads a file, selects available options and accepts the applicable notices.
- The platform attempts processing before any coins are debited.
- If processing fails or no supported exact match exists, no coins are charged.
- If processing succeeds, the platform displays the completed Output File, applied options and final coin cost.
- Coins are debited only when the Client expressly confirms payment/unlock. Until then, the Client may decline and allow the prepared file to expire without charge.
- After a successful debit, download access is unlocked. The Client must download and retain its own copy.
The applicable cost is the amount displayed at the unlock step. Stale browser pages or previously prepared files may display an earlier price; ECU-LAB must show the final charge before confirmation, and that displayed charge governs the transaction.
8. When Automatic Processing cannot be delivered
Automatic Processing depends on two conditions: that ECU-LAB identifies the uploaded file, and that a supported, verified solution already exists for that exact file. Where the file cannot be identified, where identification succeeds but no supported exact match exists, or where the modification the Client wants is not offered as an automatic option for that file, Automatic Processing does not take place and no coins are charged.
Green Coins do not create a right to free work. Green Coins are a daily usage allowance for Automatic Processing only. Neither an active Plan, nor a remaining Green Coin balance, nor a completed identification entitles the Client to have such a file processed at no further cost, to obtain a modification that is not offered for that file, or to require ECU-LAB to develop, adapt or test a solution that does not already exist.
A file that cannot be completed automatically may be processed only through Manual Processing, under the section of these Terms that governs it. Manual Processing is a separate service: it is requested per file, quoted per file, and paid in Red Coins. Red Coins are purchased separately and are not included in any Plan allowance.
Support tickets exist for questions, technical complaints and follow-up on an existing order. A ticket does not start work on a file and does not replace a Manual Processing order. Where work by an engineer is required, the Client must place a Manual Processing order, which is charged individually in Red Coins.
9. Manual Processing
Manual Processing requires a separate request, scope, price and estimated delivery time. Red Coins may be reserved or debited only after the Client accepts those terms.
If ECU-LAB rejects the request as unsupported or technically infeasible before work begins, the reserved Red Coins are released. Changes beyond the accepted scope are new paid work.
10. Coins and Plans
Green Coins. Green Coins are a daily usage allowance included with an active Plan. They are not sold separately, have no cash value, are non-transferable and cannot be refunded as money. The balance reloads to the Plan’s daily amount at the scheduled daily reset; unused Green Coins expire at that reset and are not accumulated.
Red Coins. Red Coins are purchased separately at the price displayed at checkout. They are non-transferable and have no value outside ECU-LAB. They do not expire while the Account remains active, subject to lawful suspension and the closure rules below. They may supplement Green Coins for Automatic Processing and may pay for Manual Processing. Unless the checkout states otherwise, available Green Coins are used first for Automatic Processing and Red Coins cover the remainder.
Plans. A Plan activates for the purchased fixed period and ends on its stated expiry date. Renewal is a new purchase. Unused daily allowances do not extend the Plan. Device/session and upload limits shown for the selected Plan form part of the contract.
11. Prices, VAT and payment
Prices are displayed in EUR. VAT is calculated according to the Client’s status, evidence and location under applicable law.
Payments may be processed by Stripe or PayPal; ECU-LAB receives transaction status and references but does not store full payment-card details. An invoice is issued using the billing information supplied by the Client.
12. Automatic Output Files: “as generated” and support
An Automatic Output File is supplied as generated for the selected supported options, in the current condition of the Uploaded File and with any defects it carries. ECU-LAB applies the selected modifications to what the Client sent; it does not repair, complete or validate the file it was given. The price does not include diagnosis, customisation, log review, dyno verification, free revisions or adapting the file to mechanical changes.
A request to alter a successfully generated file, create a different variant, investigate vehicle behaviour or provide engineer intervention is Manual Processing and is charged separately.
This clause does not remove any mandatory remedy for a platform error or legally applicable lack of conformity. The Charging and Refund Policy explains the available remedies.
13. Technical conformity criterion
An automated Operation is performed as described when the platform processes the Uploaded File that was submitted, uses the identified compatible Reference, applies the confirmed option, completes the automated checks provided and delivers the Output File associated with that Operation.
Technical conformity of the Service is not a promise of a particular power, torque, consumption, behaviour, dyno result, the disappearance of a mechanical fault or compatibility with undeclared hardware modifications.
The result also depends on factors outside ECU-LAB’s control: the accuracy of the read, data integrity, the tool used, the writing procedure, supply voltage, the configuration and condition of the vehicle or equipment, manufacturer updates and previous interventions.
An Output File must not be written if the identification shown by the platform does not match the physical unit, if there is doubt about the read/write method, or if the vehicle or equipment has faults incompatible with the intervention.
14. Client technical responsibilities
- Use professional, compatible reading/writing equipment and follow the tool manufacturer’s instructions.
- Keep verified backups of the complete original read before writing any Output File.
- Submit the correct full file and accurate ECU, vehicle, hardware, software and modification information.
- Verify that the vehicle is mechanically sound and that requested changes are appropriate for its hardware.
- Perform appropriate bench, diagnostic, logging and safety checks before operation.
- Understand that checksum correction, CVN handling or other technical operations are included only when the interface expressly says so.
15. Lawful use and vehicle responsibility
Modified files are supplied for lawful professional use, including motorsport, off-road, testing or research where permitted. Modifications can affect emissions systems, type approval, insurance, warranty and roadworthiness.
The Client alone determines and documents whether a requested modification and its use are lawful in the relevant jurisdiction, obtains any approval or certification and informs the vehicle owner/operator. Interface availability is not legal approval.
The duty of compliance is not limited to passenger cars or to use on public roads. It also concerns type-approved or regulated propulsion systems fitted to commercial vehicles, tractors, combines, construction machinery, excavators, loaders, forklifts, generators, boats and other mobile or stationary equipment.
Declaring an off-road, competition, research, export or industrial use does not by itself make an Operation lawful. The Client must verify the specific regime that applies and obtain the necessary authorisations.
The platform may restrict certain options depending on country, user type, declared destination or other compliance criteria. ECU-LAB may refuse or stop an Operation it considers technically unacceptable, dangerous or potentially unlawful. The Client remains responsible for approvals, inspections, informing the owner, environmental obligations, insurance and any obligation to return the equipment to its permitted configuration before use in a regulated regime.
16. Rights in uploaded files
The Client warrants that it owns the Uploaded File or is authorised by the owner to read, submit and process it.
The Client retains its rights in its submitted material and grants ECU-LAB a limited licence to store, analyse and process it solely to provide, secure and document the Service. ECU-LAB does not grant rights in manufacturer software or third-party intellectual property.
17. Licence to use the Output Files — no redistribution
An Output File is supplied to the Client for the single vehicle described in the order. ECU-LAB grants the Client a non-exclusive, non-transferable and non-sublicensable licence to install and use that file on that vehicle. No other right is granted; the Output File and the know-how embodied in it remain ECU-LAB's.
The Client shall not, whether for payment or free of charge: resell, rent, lend, share, publish or otherwise distribute an Output File; upload it to a forum, a file-sharing or cloud service, a chat group, a marketplace or any other medium accessible to third parties; pass it to another tuner, workshop or software provider; or include it in a database, catalogue, product or service offered to others. The Client shall not decompile an Output File, reverse engineer it, or derive further files from it in order to circumvent this restriction.
Processing files for the Client's own customers, on their vehicles, through the Client's own Account is permitted and is the intended use of the Service. What is prohibited is any transfer that allows a third party to obtain, keep or reuse the file itself outside a vehicle the Client has serviced.
Breach of this section withdraws every right granted under these Terms with immediate effect. The Client's right to use any Output File already received ends, the Account may be suspended or closed under the section on suspension and termination, and no refund is due for unused Coins, for a Plan still running, or for files already delivered. ECU-LAB further reserves the remedies available to it in law, including damages. Every delivered file is issued under a unique export reference recorded against the Account it was issued to.
18. Accounts, devices and account sharing
An Account is assigned to one Client and must not be sold, rented, lent, sublicensed or shared between unrelated people or businesses. Only the number of users/devices expressly included in the Plan may use it.
ECU-LAB may enforce one active session, device registration, re-authentication and reasonable anti-abuse controls. The Client is responsible for credentials and must report suspected compromise immediately.
The Client must not create multiple Accounts to bypass limits or pricing, automate access without written permission, scrape or probe the Service, defeat security, reverse engineer platform components, resell access, or use outputs/data to build or train a competing service.
19. Delivery, storage and deletion
Prepared files are temporary, not an archive. A prepared but unpaid file expires automatically. A paid file is deleted after successful download, subject to a short operational grace period. Ticket attachments are normally deleted after 30 days.
The Client must keep its own files and records. Minimal transaction, hash, audit and accounting metadata may be retained as described in the Privacy Policy.
20. Availability and changes
ECU-LAB may perform maintenance, deploy security updates, change supported ECU coverage and suspend functions where necessary. No uninterrupted availability is promised.
A material reduction of a prepaid Plan benefit will not apply retrospectively without an appropriate remedy required by law or the Charging and Refund Policy.
21. Warranties and limitation of liability
The Service is an obligation of means, not of result: to the extent permitted by law it is provided with reasonable professional care, but without promises of a particular power, economy, durability or mechanical outcome. Results depend on the Uploaded File, vehicle condition, hardware, fuel, tools and use outside ECU-LAB’s control.
For business Clients, ECU-LAB is not liable for indirect or consequential loss, loss of profit, business interruption, lost data, inspection failure, regulatory penalties or damage caused by incorrect information, unsuitable hardware, improper flashing, unlawful use or a vehicle defect.
ECU-LAB’s aggregate contractual liability is limited to the amount paid for the affected transaction or, for a Plan-wide claim, fees paid in the preceding 12 months.
Nothing excludes liability that cannot lawfully be excluded, including fraud, wilful misconduct, gross negligence where applicable, or mandatory consumer rights.
22. Suspension and termination
ECU-LAB may restrict or suspend an Account where reasonably necessary for security, fraud prevention, non-payment, chargeback investigation, unlawful use, account sharing or a material breach. Where circumstances allow, ECU-LAB will explain the reason and permit correction. If the suspicion proves unfounded, access and affected balances are restored.
The Client may close the Account at any time. Closing does not convert Green or Red Coins into cash. Before voluntary closure, the Client should use any Red Coins or contact ECU-LAB about any mandatory statutory right.
Accounting, consent and dispute records remain for their lawful retention periods.
23. Consumer right of withdrawal
A consumer benefits from the withdrawal rights provided by the law applicable to distance contracts, to the extent they apply to the specific type of supply.
Where the consumer requests immediate activation of benefits, immediate crediting of Red Coins or the start of an Operation before the withdrawal period expires, the platform will ask for the consumer’s express consent and confirmation of the legal consequences of immediate performance.
Loss of the right of withdrawal is not presumed and does not follow from the general acceptance of these Terms alone. It applies only where the applicable legal conditions are met and the platform has recorded the necessary confirmations.
In the event of a valid withdrawal, the consequences for unused Red Coins, benefits already activated and fully performed Operations are determined by mandatory rules. Nothing in these Terms limits the legal remedies for lack of conformity.
24. Refunds and payment disputes
Charges, corrections, coin returns and refunds are governed by the ECU-LAB Charging and Refund Policy, incorporated into these Terms.
The Client should contact ECU-LAB before initiating a payment dispute so a billing or delivery error can be investigated. Fraudulent or abusive disputes may justify suspension; legitimate statutory rights are unaffected.
The following do not by themselves constitute a lack of conformity: an incorrect selection by the Client, uploading a file other than the one written, an incomplete read, using an incompatible method, vehicle defects, third-party interventions, a later software update, expectations not stated in the description, or the unavailability of an option that was not displayed.
Before initiating a chargeback for a technical issue, the Client is encouraged to use the complaint procedure so ECU-LAB can verify and remedy the situation. ECU-LAB may provide the payment processor with the transaction evidence: acceptance of the Terms, the account identifier, the invoice, logs, hashes, options, delivery and support history. A chargeback initiated in bad faith after using the Service may lead to account suspension and recovery of the loss by lawful means; the legitimate exercise of consumer rights or a good-faith dispute is not an abuse.
25. Technical complaint procedure
A complaint is submitted through the ticket attached to the relevant order (or the indicated support channel), stating the Operation identifier, the vehicle or equipment, the ECU/TCU, the tool, the read and write method and an exact description of the observed behaviour.
On request, the Client will provide the Uploaded File, the Output File actually written, the backup, the ECU identification, fault codes, logs, tool reports, photographs or other technical data reasonably required. A generic statement such as “it does not work” may be insufficient for diagnosis.
The Client must stop using the result if it suspects a risk and allow ECU-LAB a reasonable period for analysis. Successive interventions that destroy the ability to determine the cause should be avoided where this can be done safely.
Platform logs, hashes, the Terms version, the selections, the cost, the moment of delivery and the download history may be used as evidence, without excluding the Client’s right to present evidence to the contrary.
The recommended internal period for notifying technical incidents is 30 days from delivery. This period does not reduce the mandatory time limits and rights of a consumer.
26. Personal data
ECU-LAB processes personal data under Regulation (EU) 2016/679 as described in the ECU-LAB Privacy Policy, which identifies the controller, purposes, legal bases, recipients, retention and data-subject rights.
27. Final provisions
These Terms, the Privacy Policy, the Charging and Refund Policy, the selected Plan and the order confirmation form the entire agreement.
Invalid provisions are severed only to the required extent. Failure to enforce a right is not a waiver. Neither party is liable for delay caused by events beyond reasonable control.
The Client may not assign the agreement without written consent; ECU-LAB may assign it as part of a lawful business transfer with appropriate notice.