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. Data controller and scope of this information
The controller of data collected through the information website, commercial correspondence and administration of the NexaCare contract is {operator.legalName}, {operator.address}, Polish tax ID (NIP) {operator.taxId}. Contact: {operator.contactEmail}. For data protection matters: {operator.privacyEmail}. If a data protection officer has been appointed, the operator provides their contact details in the contact section before processing begins.
This policy covers the NexaCare website, account administration and product communications. The entity operating a facility is generally the controller of resident, family and staff data entered by that facility. The software provider processes that data under a data processing agreement and documented instructions. The facility provides its own information about the purposes, legal grounds and retention periods. Having a family account does not itself grant access to health records.
2. What data is needed
The contact form collects a full name, email address, organisation name, selected product and topic, and the enquiry text. A telephone number is optional unless you request a telephone response. Do not enter residents’ details, health information, passwords or identity documents into the public form.
Workspaces process account identifiers, roles, authorisations, organisational data and actions needed to provide the service. The facility determines the scope of resident data and documents. Health information is held in a separate area with additional access controls. The server also records necessary technical data, such as request time, IP address and error identifier, to protect and maintain the service.
3. Purposes and grounds for processing
Responding to an enquiry from someone considering a contract involves taking steps at their request before entering into a contract (Article 6(1)(b) GDPR). For contact by an organisation’s representative and other enquiries, the basis is the controller’s legitimate interest in correspondence and managing professional relationships (Article 6(1)(f) GDPR), unless the person’s rights override that interest.
Contract and account administration, billing and support rely, as appropriate, on performance of a contract, legal obligations and legitimate interests in security and establishing, exercising or defending claims. Accounting records are processed to meet legal obligations. Special-category data in a facility requires a separate applicable condition under Article 9 GDPR; the provider does not determine that condition on the facility’s behalf. The contact form neither records marketing consent nor subscribes anyone to a newsletter. Acknowledging this policy is not consent to marketing.
4. Recipients and integrations
Authorised people and providers of hosting, maintenance and tools necessary to deliver the service may have access under appropriate agreements. When an integration is enabled, data necessary for its purpose may be sent to a payment provider, invoicing system, CORE identity provider or authorised communications provider. Before integrations process real data, the controller publishes the providers actually used, their locations and processing scopes.
LifeNexa subscription billing and billing for facility stays or services have separate sellers and records. NexaCare does not store full payment card details; the selected payment provider supplies the payment form. Data is not sold. Disclosure to competent authorities may take place where required by law.
5. Transfer outside the European Economic Area
Selecting a provider may involve transferring data outside the EEA. Before enabling this configuration, the controller verifies the transfer basis, recipient, necessity and safeguards, including an adequacy decision or appropriate standard contractual clauses and any required supplementary measures. Information about the mechanism actually used is available from the controller. An unidentified provider must not be enabled for sensitive data.
6. Retention periods
Contact enquiries are retained until handled and afterwards only as long as needed to document arrangements or protect legal claims. The operator establishes and applies a specific deletion schedule, taking account of the matter and applicable limitation periods. Contractual and accounting data is retained for the period required by applicable law. The facility determines retention periods for its data, including health records, under the laws that apply to it and the data processing agreement.
Account expiry does not automatically delete records subject to a retention duty. Backups follow a separate, limited restoration and retention cycle; restoration must take completed requests and restrictions into account. Submitting an erasure request does not override legal obligations.
7. Your rights and contact
Subject to applicable law, you have rights of access and a copy, rectification, erasure, restriction of processing and data portability. You may object to processing based on legitimate interests; the right to object to direct marketing is unconditional. Where processing relies on consent, you may withdraw it without affecting the lawfulness of earlier processing.
Write to {operator.privacyEmail}, stating your request and details that allow your case to be located securely. The controller may verify identity proportionately and does not request unnecessary identity document copies. Responses are provided without undue delay, normally within one month; an extension is possible where the law permits, with reasons given. For facility records, use the privacy request workspace or contact that facility’s controller. You may complain to the President of the Polish Personal Data Protection Office (UODO); current contact details are available at uodo.gov.pl.
8. Voluntary nature and consequences of failure to provide data
Providing contact details is voluntary, but an enquiry cannot be handled without a reply address or the question itself. Workspaces require the data needed to grant access and perform authorised actions. Optional fields are marked in forms. A facility must not collect additional data without an appropriate purpose and legal basis.
9. Cookies, device storage and the mobile app
The essential nc_session cookie maintains the sign-in session, is HttpOnly and expires after no more than 8 hours; signing out invalidates the session on the server. Short-lived SSO sign-in data is used to verify authentication. Browser storage remembers the theme, text size and device-storage notice choices. The current configuration does not use advertising or analytics tools requiring additional consent. Any change requires updated information and prior consent where required, with an equally easy way to withdraw it.
The mobile app uses secure system storage for sessions and a local queue of permitted offline staff changes. Synchronisation requires valid access and may require conflict resolution. Camera and notification permissions are separate and depend on the feature and the user’s decision. Facility data must not be stored on a shared or unsecured device.
10. Security, automation and change
Measures include role and facility-scope checks, family authorisations, encrypted connections, auditing and backups. No system removes all risk; report suspected breaches to the controller without sending excessive data. NexaCare does not make autonomous medical decisions or decisions that produce legal effects for residents. Enabling AI requires separate configuration, data-sharing rules and human review.
Policy updates are published with a version number and date. Changes to purposes, recipients or legal grounds require appropriate information and, where necessary, a new decision from the individual. Document version: 2026-10-25.1.