Terms of Use and License · RAMS Analytics

Version 2026-09-26.1

Draft for legal review. Sandbox acceptance is a test record, not a production contract.

Contract particulars

Supplier identification pending

Technical validity: Pending

Retention and export: Pending

The order receipt identifies the customer, plan, amount, currency and renewal. Existing contracts retain their commercial conditions.

1. Parties and contract documents

The supplier must be identified by legal name, tax registration, address and contact channels in the contract particulars. The customer is the individual or organization identified in the account and order; an organizational representative confirms authority to contract. These terms, the software annex, the order specifying plan, seats, currency, price, term and renewal, and any specific enterprise agreement form the contract. The accepted offer and mandatory rights prevail over conflicting provisions. Features described as future work are outside the current delivery.

2. License and plans

Axion grants a non-exclusive license for the contracted term and scope, without transferring software ownership. Home is an individual license for its named holder, without credential sharing; the offer must disclose any further usage restriction. Named enterprise licenses cover the identified users and organization. Concurrent/floating licensing requires an express order, stated concurrency limit and an available enforcement mechanism; its description does not mean it is available for purchase. Bundles include only the products and rights itemized in the order. Buying one module does not unlock others. Exporting data does not transfer or extend the software license.

3. Price, term and renewal

Before payment, the customer must receive the total price, currency, disclosed charges, term, plan and renewal conditions. An annual license runs for one year according to the confirmed order dates. Renewal under this offer is manual, with no automatic debit. Its price follows the agreed conditions and must be presented before a new acceptance. Existing contracts retain their conditions; revised price lists or terms do not retroactively change price, term or renewal. Test environments involve no real charge and grant no production license. Acceptance and payment are separate events: acceptance does not prove payment, and commercial access requires payment confirmation and eligibility.

4. Technical purpose and professional judgment

The tools support engineering studies, planning and decisions. They do not replace inspections, tests, root-cause investigation, manufacturer documentation, risk assessment, detailed design or legally required professional responsibility. The customer must appoint competent professionals to check inputs, units, system boundaries, assumptions, models and results before applying them. Forecasts are conditional on data and assumptions; they do not guarantee useful life, failure-free operation, savings or operational safety. The programs are not protection, interlock or equipment control systems. Standards references identify methodological sources and do not certify the software or project.

5. Axion obligations

Axion must deliver the contracted scope, disclose material limitations, maintain support channels, use proportionate security measures and address reported defects according to severity and applicable commitments. The technical validity period of the version and associated support must be specified before commercialization. Absolute availability is not promised; maintenance and incidents require diligent handling and communication. Cloud providers used by Axion do not remove its own responsibilities. Support times, SLA, recovery and backup commitments are guaranteed only when expressly specified and supported by operations.

6. Customer obligations

The customer must supply lawful, authorized and sufficiently complete data; review consistency, quality and currency; safeguard credentials; assign appropriate access; document material decisions; and report inconsistencies through support. Applicable safety standards and intervention procedures must be followed. Unnecessary personal data or unauthorized third-party information must not be uploaded. Local exports are recommended for additional continuity and do not replace Axion obligations for storage and security.

7. Responsibility and limitations

Each party is responsible for its acts and omissions under applicable law and demonstrated causation. Axion does not assume responsibility for outcomes exclusively caused by incorrect customer data, unauthorized modifications, use outside documented scope or independent operational decisions, to the extent those factors actually caused the loss. This does not exclude liability for Axion own defects or inadequate information. There is no waiver of statutory warranties, consumer rights, data protection, mandatory remedies or liabilities that cannot legally be limited. Any negotiated enterprise liability cap must be specific, proportionate and legally valid; this draft sets no general cap or automatic exclusion of lost profits. Acceptance does not transfer all safety obligations to the user.

8. Data, confidentiality and privacy

Customer data and studies remain owned by the customer or their lawful owners. Axion may process them only to perform the service, provide authorized support, meet legal obligations and protect operations under applicable legal grounds. No general permission is granted to sell studies or train models on them. Account, licensing and billing data involve Axion own processing purposes; personal data within studies require controller/processor roles to be defined for the actual operation, with an enterprise addendum where needed. The privacy notice must identify contacts, purposes, provider sharing, international transfers, security, retention and data-subject rights. License acceptance is not blanket consent for marketing or optional processing.

9. Saving, history and export

The system must distinguish local edits from confirmed cloud writes. Customers should check confirmations and address conflict or failure messages before closing their work. Studies can be exported in available formats. History and technical records may be retained for integrity and investigation with restricted access and proportionate retention. Contract particulars must state retention, post-termination export and deletion policies, including backups. Auditable history does not imply absolute protection against privileged administrator changes or a qualified digital signature.

10. Intellectual property and permitted use

Axion retains rights in its software and original materials without acquiring ownership of customer data. Unauthorized redistribution, sublicensing outside the order, credential sharing and circumvention of access controls are prohibited, subject to legally protected uses and exceptions. Customers may use their generated reports in their activities while identifying the method and not claiming nonexistent certification.

11. Cancellation, refunds and suspension

Applicable withdrawal, refund and warranty rights remain intact, including the statutory seven-day withdrawal period for eligible distance contracts in Brazil. Providing access or recording acceptance does not automatically waive those rights. Requests go through the support channel in the contract particulars and must be acknowledged and handled within applicable legal periods. Suspension requires legitimate grounds, notice and an opportunity to remedy where appropriate; immediate containment may be needed for a security incident. Termination must respect the offer, acquired rights and export policy. Legitimate complaints or disputes do not automatically forfeit rights.

12. Updates and electronic acceptance

The complete presented version is identified by version, language and hash; acceptance records contain the authenticated user, server timestamp, software, plan and order. Customers can access a copy and receipt. Material changes for new contracts or renewals require presentation and new acceptance and are not imposed retroactively during the contracted term. Security and operational corrections do not permit arbitrary removal of acquired scope. Electronic records provide evidence and are not represented as ICP-Brasil signatures.

13. Applicable law and disputes

Brazilian law applies subject to conflict-of-law rules and mandatory rights of other applicable jurisdictions. This draft does not establish universal suitability for international sales. Parties should seek resolution through support, without preventing access to regulators, consumer authorities or courts. Jurisdiction follows applicable law, preserving consumer venue rights. Mandatory arbitration is not imposed.

14. Acceptance statement

I have read and accept the Terms of Use and License, the software annex and the commercial conditions presented for this order. I understand that results require professional evaluation and that my statutory rights remain intact. If acting for an organization, I confirm authority to contract. This acceptance does not authorize marketing.

Software annex · RAMS Analytics

RAM/RBD, LDA/RGA, Bad Actors, FMECA and maintenance strategies: check boundaries, dependencies, exposure and repair effects. Crow and Weibull serve different purposes; beta does not identify causes. The equivalent Crow rate reproduces reliability at the specified mission; associated availability and MTTF are stationary approximations.

SHA-256 8d3f0715596d6c080ecf55db7e616d6f3b00ea27ecf5ae47f67a57bd55a4997c