Skip to content
Maatron

Terms of Service

The rules for using Maatron: what we provide, what you agree to do and not to do, who owns what, and what we are answerable for.

Last revised:

Subject and acceptance

[À COMPLÉTER — raison sociale] operates Maatron, an online service that analyzes FANUC controller backup archives and turns them into a structured cell model, engineering findings, documentation and version-to-version comparisons. These terms govern that use.

They bind you as soon as you create an account or first use the service, on trial as well as on a paid subscription. If you are acting for a company, you confirm you have the authority to commit it.

Three further documents form an integral part of them: Privacy policy, Disclaimer and Data Processing Agreement. Where one of them contradicts these terms on the processing of personal data, that document is the one that applies.

What the service does, and what it does not do

You upload backup archives. The service reads them offline, extracts a cell model, and produces deterministic findings: same files, same result.

Maatron connects to no controller. It writes to no robot, deploys no program, changes no parameter and triggers no motion. It has no network access to your shop floor, and will never ask for any.

That boundary is contractual, not merely technical: it cannot move unless these terms move first. The measures that hold it in place are described in Security and trust.

Account and organization

Creating an account creates an organization. Everything you upload belongs to it, and the separation between organizations is the central guarantee of the service.

Inside an organization, every member holds a role — owner, administrator, engineer or viewer — which decides what they can see and do. The organization answers for the access it grants, and for withdrawing it when someone leaves.

Credentials are personal to one user. Tell us at info@maatron.dev as soon as you suspect unauthorized access: we cannot spot it on your behalf. The service sets a session cookie and a language preference cookie, and nothing else; Cookies gives the detail.

Acceptable use

There is no separate acceptable use policy. The rules fit in a few lines, and here they are.

Upload only files you have the right to upload. A backup usually belongs to the plant that runs the installation, not to the integrator who produced it: if you are working for a client, make sure they agree.

Do not try to reach another organization's data, and do not work around authentication, roles or upload limits. Good-faith vulnerability research is welcome, and is reported to info@maatron.dev.

Do not decompile the service, do not probe it to reconstruct how it works inside, and do not harvest its results automatically to build a competing offer.

Do not resell access, and do not share it outside your organization. One account per person: shared credentials make audit logs useless, and you are the first person who needs them.

Your files, our software

The archives you upload stay yours. So do the results derived from them — cell model, findings, documentation, comparisons — and you may export and use them without restriction.

Over that content we take only the limited right to host it, process it and display it in order to deliver the service, including to investigate an incident you report to us. That right ends when the data is deleted.

Your files are not used to train any model, ours or anyone else's. What we keep in order to improve the product is aggregate measurement — volumes, durations, error rates — from which no program, no cell and no customer can be reconstructed.

The service itself, its code, its analysis rules and its documentation belong to [À COMPLÉTER — raison sociale]. What you get is a right to use it, non-exclusive and non-transferable, for as long as your subscription runs.

Availability

We aim to keep the service running and we monitor it, but we promise no uptime figure. These terms are not a service level agreement.

There will be interruptions: maintenance, upgrades, a hosting provider's outage. Planned interruptions are announced in advance where they are likely to be noticed.

A commitment expressed as a number, with the credits that go with it, is negotiated in a contract and offered on that basis only. Printing a percentage here with no on-call duty behind it would serve nobody.

Suspension and termination

You may stop using the service whenever you wish and ask for your data to be deleted. The deletion deadlines are public and set out in Privacy policy.

We may suspend access without notice in case of a security breach, of use that degrades the service for others, or of a legal obligation. We tell you as soon as we can, and say what would restore access.

For any other breach, we write first and allow a reasonable time to put it right. When the relationship ends, you have thirty days to export your data before it is erased.

Changes to these terms

These terms will change: the product moves, and a frozen text ends up describing something other than the service delivered.

Every version carries its revision date, at the top of this page. A substantive change — rights, liability, price — is announced by email to the account address, at least thirty days before it takes effect.

If a change does not suit you, terminate before that date. Carrying on afterwards counts as acceptance. We never rewrite a text you have already accepted: we publish a new version of it.

What we are answerable for

The service is engineering decision support, not a certification. This is not drafting caution: it is what decides the extent of our liability, and Disclaimer explains it in full. Read it.

We answer for the operation of the service and for the protection of your data. We do not answer for the decisions taken from a result, nor for indirect loss: stopped production, lost business, loss of data you hold elsewhere.

Except for gross or intentional fault, and except for bodily injury, our total liability is capped at the amounts you paid us during the twelve months before the event giving rise to the claim. None of these limits sets aside a liability that the law does not allow to be set aside.

Governing law and competent court

These terms are governed by the law in force in the province of Quebec, Canada, together with the Canadian federal law applying there. The courts of the judicial district of the head office of [À COMPLÉTER — raison sociale] have jurisdiction by default; that address is given in Legal notice.

The service is also offered to customers established elsewhere in Canada, in the United States and beyond. The rule above remains the starting point for all of them, wherever the customer is established.

It takes nothing away from the mandatory rules of a customer's own jurisdiction, consumer protection in particular, where that law forbids waiving them. Such a rule then prevails over the matching clause, and the remainder of the terms stays in force.

These terms exist in French and in English, with the same content; neither version is a summary of the other. Should a divergence survive proofreading, the French version governs, the operator being established in Quebec.