Product terms
PROBATIS · Terms of use
The proposed framework for access, use, responsibilities and personal data.
PROBATIS
IT teams, managed service providers (MSPs) and organisations planning their recovery.
Product-specific provisions
Authorised systems and connector scope
The customer must have authority over each connected system. Access mode, permissions and any test action are approved in advance. No intrusive scan, restoration in production or modification of a third-party system is authorised merely by subscribing or requesting a demonstration.
Evidence and limits of recovery claims
Recovery objectives, laboratory observations and production performance are distinct. PROBATIS is a functional MVP and does not by itself establish a recovery guarantee. The customer retains its backup, continuity and recovery responsibilities, and must validate connector behaviour and any restoration procedure before operational use.
Common service provisions
1. Document status and contracting party
These product terms are proposed prepublication documents. They become applicable only after the publisher has been identified, the service scope has been confirmed and the applicable agreement has been made available and accepted where required. The institutional preview does not create a subscription or a commitment to deliver a particular feature.
2. Service scope and product stage
The product page describes the current project stage. A demonstration, a pilot and a production service have distinct scopes. The order form or pilot agreement must identify the enabled functions, environment, users, duration, support and any prerequisites. Planned integrations and roadmap items are not included solely because they are mentioned in product material.
3. Accounts, roles and authorised access
Each organisation designates authorised administrators and users. Accounts are personal where the service requires it; access must follow the role and scope granted. Users protect their credentials and promptly report suspected unauthorised access. The parties must agree on onboarding, access review, departure and incident contact procedures before live use.
4. Permitted use and user content
Users may use the service for its documented purpose and only with information they are entitled to provide. Fraudulent, unlawful, discriminatory or unauthorised activity is prohibited. Users remain responsible for the accuracy and relevance of information they submit and must not introduce sensitive or third-party information outside the agreed scope. Security testing requires a separate express authorisation.
5. Professional judgement and human decisions
The service supports work and information processing within its stated scope. Indicators, recommendations and generated documents must be reviewed by appropriately authorised people. They do not replace professional responsibilities, required qualifications or the organisation’s own checks. No result, matching indicator or technical status is a guarantee of an individual, commercial or operational outcome.
6. Intellectual property and content rights
The applicable agreement defines the limited right to use the service. It does not transfer ownership of the software, trademarks or underlying materials. Users retain their rights in content they lawfully provide and grant only the permissions necessary to operate the agreed service. Third-party and open-source components remain subject to their own licences. The parties must resolve the relevant rights before distributing or reusing content.
7. Personal data and confidentiality
Before live processing, the parties identify their respective roles, purposes, legal bases, data categories, recipients, hosting locations, transfers and retention rules. Where required, a data processing agreement must be completed before personal data is introduced. Information shared for a pilot must remain within its agreed use and authorised recipients. The institutional contact form must not be used to submit patient, pupil or candidate records for a product demonstration.
8. Security, availability and support
The technical and organisational measures, backup arrangements, support channels and service commitments must be documented for the actual deployment. Independent audits, certifications, guaranteed recovery times or continuous availability are not asserted unless specifically evidenced and agreed. Maintenance, incidents and planned changes must be handled under the applicable agreement and communicated through the defined contacts.
9. Fees and third-party services
Any fees, taxes, trial period, payment schedule and renewal rules must appear in the accepted commercial documents. An indicative presentation is not a payment order. External messaging, payments, hosting or integration services may have separate costs and terms, which must be identified before activation. No paid subscription is created by viewing this institutional site.
10. Suspension, termination and data return
The agreement defines the duration, termination process and any notice period. Access restrictions should be proportionate to security, contractual or legal needs. Before termination, the parties must define the available export, the return period, authorised recipients and subsequent deletion or justified archiving. Product-specific retention must be confirmed rather than inferred from the institutional website’s policy.
11. Responsibilities and mandatory rights
Each party remains responsible for its own obligations and decisions within the applicable law and contract. Any allocation or limitation of liability must be assessed for the actual service and cannot remove rights or liabilities that the law does not permit the parties to exclude. A pilot should state its limits clearly and provide a suitable fallback for the intended activity.
12. Changes, applicable rules and contact
The publisher identifies the document version and informs affected users of relevant changes under the applicable agreement. Governing law, dispute resolution and any mandatory consumer, employment, education or healthcare rules must be specified for the contracting entity and territory concerned. Questions should be directed to the contact shown in the completed legal notice.