The full draft is ready. The operator must enter company details and review the document before publication and before handling real data. Bracketed markers indicate missing details.
1. Service provider and purpose
The NexaCare service provider is {operator.legalName}, {operator.address}, Polish tax ID (NIP) {operator.taxId}; email: {operator.contactEmail}. These terms govern the information website and web and mobile applications that support the organisation of care facilities. This document is provided free of charge before a contract is concluded, in a form that can be saved and printed.
NexaCare supports work organisation, documents, communication and billing. It does not replace care services, staff decisions, emergency systems or the facility’s required records and procedures. In an emergency, follow facility procedures and use the appropriate emergency channels. Illustrative material and demonstration data are labelled; they are not references from actual deployments.
2. Definitions and scope of services
An organisation is an entity operating a facility; a user is a person assigned an account and role; a family member is a person authorised in relation to a specified resident. CORE is LifeNexa’s central identity and subscription layer. A product workspace provides only the modules, facilities and data allowed by the user’s role, contract and authorisation.
The website provides product information, documents, a contact form, presentation requests and pricing. Workspaces may cover beds and stays, residents, shifts, tasks, services, meals, incidents, communication, documents, amounts due and reports. Feature availability depends on the selected plan, configuration and permissions. An integration marked as not configured is not an active external service.
3. Technical requirements and availability
The website and workspaces require a current browser with JavaScript and HTTPS support, cookies necessary for sign-in, and internet access. The Android app requires the compatible system version stated for the current installer and sufficient free device storage. An iOS version can be made available only after separate preparation and distribution; an Android installer is not an iOS app.
Selected staff actions can be queued offline; this does not confirm that they have been saved on the server. Users must check synchronisation results and resolve conflicts. Critical data, payments and authorisations require a server connection and confirmation. Maintenance interruptions and incidents are handled as agreed; uninterrupted availability is not promised without a separate SLA. Accessibility feedback can be submitted through the form under Digital accessibility.
4. Contract formation and launch
Browsing the website does not create a paid contract. Submitting the form requests contact, a presentation or an offer; it does not itself place a paid order. The binding scope, price, duration, limits, implementation arrangements, SLA and termination terms are set out in the accepted offer or contract and CORE documents. Before a paid order is placed, the customer receives information about the seller, total price and billing terms; express acceptance of the obligation to pay is required.
The organisation is responsible for valid representation, the legal grounds for processing data, role assignments and the required data processing agreement. Real data may be introduced only after security, authorisations, retention, backups and exit arrangements have been agreed.
5. Account and permissions
Accounts are personal. Do not share passwords, tokens or MFA codes. Administrators use the required strong authentication. Access may be restricted or revoked when employment or authorisation changes. Family members see only the scope assigned for a specific resident. Authorisation to receive information does not automatically grant access to health information, finances or all documents.
Users select the correct facility and check recipients, dates and details before confirming an action. Bypassing permissions, testing other people’s accounts, or distributing unlawful content, malware or data without a lawful basis for access is prohibited. Suspected account compromise must be reported promptly and affected sessions terminated. Security restrictions must be proportionate; further handling of data and claims remains subject to law and contract.
6. Facility operations and responsibility for records
Staff verify documents, allergens, authorisations and source information. Completed actions and billing entries are corrected through the appropriate process with a retained history, rather than by concealing earlier records. Previewing a plan or an AI suggestion does not execute an action. Task planning does not replace the responsible staff member’s assessment of residents’ needs and staffing.
The service provider is responsible for its own obligations under law and contract. These terms do not exclude liability that cannot lawfully be excluded or the user’s statutory rights. Within the limits of the law, the organisation is responsible for the content and lawfulness of entered data, the organisation of services and its staff’s decisions. If an error occurs, users suspend any action requiring clarification and provide information through a secure support channel.
7. Subscriptions, payments and invoices
The LifeNexa subscription is separate from fees for stays and services at the facility. Subscription prices and entitlements are governed by CORE and the contract with the relevant seller; demonstration data is not a binding offer. The seller of facility services is identified in its contract and accounting documents. These amounts must not be combined into an unidentified payment.
Once enabled by an authorised administrator, a payment may be directed to Stripe or Przelewy24. Check the seller, amount, currency and payment reference before confirming. Returning from a payment gateway is not itself proof of payment; status is confirmed using verified provider information and transaction reconciliation. The relevant seller handles service complaints and refunds; gateway technical errors are handled under the provider’s rules. The appropriate seller issues invoices and corrections, optionally through a configured Fakturownia integration. Invoice numbering, taxes and fiscal obligations require that seller’s configuration to be correct.
8. Contact, complaints and support
Enquiries and complaints may be sent to {operator.contactEmail} or through the form by selecting a product and topic. Include a reply method, a description of the issue, the event time and the expected outcome. Do not send health records, passwords or card details through the public form. Each enquiry receives a reference. A CRM record does not confirm that an email has been sent if external delivery has not been enabled.
The service provider acknowledges and handles complaints without undue delay and within the deadline applicable to the legal relationship. Consumer complaints receive a response within 14 days unless a specific provision states otherwise. Contractual arrangements also apply to organisational matters. Reporting an error does not require users to waive statutory rights. Questions about care, stays and facility billing should be directed to the facility; the service provider may help identify the appropriate channel without disclosing another person’s data.
9. Consumer rights
The product is primarily intended for organisations. If a contract is concluded by a consumer or another person entitled to statutory protection, provisions intended for professional relationships do not limit that person’s rights. Before a distance contract is concluded, the person receives the required information, including complaints, conformity of services, withdrawal and costs.
As a rule, consumers have 14 days to withdraw from a distance contract, subject to the exceptions and rules applicable to the service. Starting the service earlier requires the appropriate separate request or consent and information about the consequences; signing in or accepting these terms does not waive the right of withdrawal. A withdrawal statement may be sent to {operator.contactEmail}, identifying the contract, its date, the sender and an unambiguous decision to withdraw. Refunds and any payment due for services already provided are handled in accordance with the law. Information about assistance and out-of-court dispute resolution is available from the Polish Competition and Consumer Protection Office (UOKiK), consumer ombudsmen and the Trade Inspection. The service provider’s participation depends on applicable law or a separate declaration.
10. Termination, data and rights to materials
Rules for subscription termination, renewal, export, account closure and transition period are specified in the contract and CORE. The user may end the session at any time; logging out does not terminate the organisation's contract. The organisation administrator manages accounts and authorisations, maintaining required documents and history.
Before the relationship ends, the parties agree authorised data export, return or deletion and any exceptions arising from retention duties. Data must not be deleted by removing billing or audit records without documentation. Rights to the organisation’s data remain with the entitled parties. The service provider’s software, brand and materials are protected; the organisation receives the right to use them to the extent agreed in the contract. Exports must respect other people’s rights and privacy.
11. Privacy and changes to these terms
The Privacy Policy describes data processing in detail. A data processing agreement and the organisation’s instructions govern processing for the facility. External features and AI require authorised configuration; health information must not be sent to them automatically. The provider gives advance notice of material changes to these terms and the reasons, on a durable medium where required by law or contract. Changes do not remove acquired rights or impose new fees retrospectively.
Polish law applies, subject to mandatory consumer rights and jurisdiction rules. In unregulated matters, appropriate provisions shall apply. Current version: 2026-10-25.1.