Terms
Terms of use for the CALIBRIX VAULT portal
Using the service, including entering the portal, registering an account, signing in, buying credits, uploading a file, downloading a file, sending messages or continuing to use the account, means that the user has read and accepted these terms.
This document sets out the rules for accepting orders, settling credits, handling ECU files and defining the responsibilities of both parties. It is a technical and organisational document and must be read together with mandatory legal rules.
A cash refund is not the standard settlement method for the service. Corrections, accepted complaints and repeated work are normally settled by returning credits for further use in the portal, unless mandatory law requires another method.
Returning to the sign-in screen and continuing to use the service confirms acceptance of these rules.
1. Definitions and scope of the portal
- CALIBRIX VAULT is a technical platform for ECU file handling and communication between the client and the operator providing calibration, diagnostics, verification and file preparation services.
- An order means every uploaded file, archive or data set that creates a ticket in the system and requires technical assessment, credit valuation or work by the operator.
- Credits are an internal portal balance used to settle technical work. They are not electronic money, a bank account or an independent payment instrument.
2. Nature of the services
- The services are specialist, technical and individual. Each file is assessed in the context of the specific ECU, read method, software version, vehicle history and data quality.
- The operator may refuse an order if the file is damaged, incomplete, encrypted, unreadable, from an uncertain source, contains unsafe content or cannot be safely analysed.
- The portal does not replace mechanical diagnostics, measurements, electrical repair, fuel system repair, boost system repair, exhaust system repair or engine condition checks.
3. Account, client data and responsibility for information
- The client must provide accurate contact details and information required for the order, especially make, model, year, ECU, read type, tool, VIN or reference number when available.
- Missing, conflicting or approximate data may delay the order, require additional questions or lead to a file that does not match the actual vehicle.
- The client is responsible for securing the account, password, e-mail inbox and devices used to access the portal.
4. File uploads
- The client should upload a single file or a ZIP/RAR archive when the read consists of multiple elements. The archive should contain all data needed for assessment.
- Files may be automatically scanned for malicious content. The operator may remove or block a file if the scan or technical analysis indicates a risk to the portal infrastructure.
- The client should keep their own copy of the original read. The portal is not a permanent archive or the only storage location for client data.
5. Credits and settlement
- Orders are settled with credits according to the price list visible in the portal or according to an individual administrator correction when the scope of work or an incorrect client selection requires a different charge.
- Submitting an order may deduct credits from the balance. If the client selected the wrong scope, the administrator may charge missing credits, return an overpayment in credits or ask for clarification.
- For an accepted complaint, the primary settlement method is repeated work, file correction, another version or returning the appropriate number of credits to the client balance.
6. No guarantee of effect and limitation of liability
- The operator is not responsible for the consequences of using a file where the result follows from the actions of the client, a third party, technical condition, read defects, write defects or an incorrect procedure.
- The client decides whether to use the received file, how to test it and whether the vehicle or machine can operate with the given modification.
- If the client orders work related to emission systems, DTC diagnostics, limiters, sport functions or other systems, they do so on their own responsibility and should ensure that use of the file is lawful where the vehicle or machine is operated.
7. Complaints and file versions
- A complaint should be submitted in the relevant ticket with symptoms, fault codes, write method, tool, logs, photos or other data needed to reproduce the issue.
- Subsequent file versions may be marked V1, V2, V3 and so on. Preparing another version is a normal part of refining a file.
- The operator may refuse further correction if the client changed the base software, wrote a third-party file, replaced the ECU, did not perform recommended tests or did not provide data.
8. Prohibited use of the portal
- It is forbidden to upload malware, executable files disguised as ECU reads, stolen data, files infringing third-party rights or content intended for abuse.
- It is forbidden to overload the server, scan the portal automatically without consent, bypass limits, test vulnerabilities on production accounts or share an account with unauthorised persons.
- The administrator may temporarily or permanently block an account if the client’s behaviour threatens the security, stability or reputation of the portal or breaches these terms.
9. Used files, previous modifications and technical risk
- Working on used files, repeatedly modified files, files from an uncertain source or files read with an unknown tool involves increased risk.
- The operator is not responsible for earlier modifications, patches, checksums, locks, tune-protect, incomplete segments, version mismatches, WinOLS project errors or damage that existed before the file was uploaded.
- In case of doubt, the operator may recommend a new read, full backup, bench/boot read or full archive upload.
10. Communication and notifications
- The ticket in the portal is the primary communication channel. Telegram, e-mail or other channels are auxiliary and do not replace the order history stored in the portal.
- Notifications may be delayed, undelivered or duplicated for technical reasons, external service dependencies, application blocks, phone settings or network issues.
- The operator may contact the client to clarify data, warn about risk, provide information about missing credits or notify that a file is ready.
11. Data, confidentiality and storage
- Files, notes and technical data are stored as needed to handle orders, complaints, version history, settlements and portal security.
- The operator applies organisational and technical safeguards, but no internet infrastructure gives an absolute guarantee against failure, data loss or security incidents.
- The client should not include data in files or comments that is not needed for the order.
12. Final provisions
- Use of the portal means acceptance of these rules to the extent that they comply with mandatory law. If any provision proves invalid, the remaining provisions remain effective.
- The operator may change the terms, price list, service scope, credit charging rules, technical limits and security procedures.
- These terms are an operational portal document and should be reviewed by a competent lawyer before use as an official public legal document.
