1. Service provider
The service provider's details are waiting to be completed by the administrator. Contact: form /kontakt/ with the selection of the appropriate topic.
2. Scope of service
The platform organizes sites, meters, measurements, tariffs, documents, budgets, alerts and reports. The information page, dashboards and Android app are related service channels.
3. Agreement and permissions
Organisation access follows the agreement and LifeNexa CORE permissions. Submitting the contact form or downloading the APK does not constitute a paid agreement. Scope, price, limits and subscription period must be presented before an order is placed.
4. Technical requirements
Web requires a current browser that supports JavaScript, HTTPS and the necessary session memory. Android requires at least version 7.0 and appropriate storage. Synchronization, reporting and logging require a network; the offline queue does not replace the server.
5. Account and security
Use your own account, protect your password, MFA and device. Permissions are granted by the organisation. You must not attempt to access third party tenants, bypass limits, violate the system or introduce malicious files. Events are subject to audit.
6. Data and documents
Users are responsible for their authority to enter data and for checking its quality. A missing reading does not mean zero consumption. OCR, imports and analysis do not replace human checks. Corrections and approvals must retain their history; financial documents have separate processes.
7. Payments and invoices
CORE bills LifeNexa SaaS subscriptions. Amounts owed by an organisation’s customers belong to a separate relationship with the specified seller. Stripe and Przelewy24 are available after configuration; payment is confirmed by a verified server event, not a browser return. Fakturownia requires a document preview and confirmation.
8. Performance and infrastructure
Forecasts, ROI and emissions are estimates with assumptions. They do not constitute a guarantee of savings, investment advice or a certified ESG report. The system does not send commands to critical infrastructure. Operational decisions are made by an authorised person.
9. Availability and maintenance
The scope of support, SLA and planned breaks are specified in the contract. Errors are reported via the form or support module. The service does not replace alarm systems or the obligation to have your own documentation.
10. Completion and export
Renewal, termination and export access terms are specified in the CORE Agreement. The user can export data within the granted scope. Deleting data requires checking the legal obligations and rights of the organisation.
11. Complaints and statutory rights
The complaints procedure is described at /reklamacje/. These terms do not restrict the rights of consumers or businesses entitled to consumer protections under applicable law. Where a distance contract carries a right of withdrawal, statutory time limits and exceptions apply. Downloading the application alone does not remove that right.
12. Changes and priority
Changes require publication of a version and communication appropriate to the contract. They do not apply retroactively to acquired rights. In matters not regulated, the law applicable to the contract shall apply; provisions inconsistent with mandatory provisions do not limit the user's rights.
Reference materials: UODO — your data protection rights, UOKiK - consumer rights, Electronic Communication Law. Checked 15/10/2026.