DOCUMENT •
NexaStay PRO platform privacy policy
Content date: 15 October 2026 • template version 2026.10.25-r01
Download the Polish document (.txt)1. Data controller and contact details
not entered PL Contact: not entered Complaints: not entered. Personal data enquiries: not entered. This document covers the platform provider’s own activities, including contact, organisation accounts and subscription billing. For guest and staff data processed on behalf of a hotel, the relevant operator is the data controller; the platform provider may act as a processor under a separate agreement. The app’s logo does not determine these roles.
2. Data scope and sources
Data comes from user forms and activities, from an authorised organisation, or from a properly configured integration. They include contact and account details, role assignment, stay and buyer details, bill items, payment statuses, tickets and voluntarily added task photos. Session data, event dates and technical request information are maintained for access protection. Do not enter full card details or unnecessary special category data into the application. Vendor authentication data is for authorised configuration purposes only and is not public company content.
3. Purposes and legal bases
Handling pre-contractual enquiries and performing a contract rely on Article 6(1)(b) GDPR where its conditions are met. Accounting and legal obligations rely on Article 6(1)(c). Security, accountability and the establishment, exercise or defence of legal claims rely on Article 6(1)(f), following an assessment of necessity and individual rights. Optional marketing requires separate consent for the relevant scope; Article 6(1)(a) may apply alongside the applicable electronic communications requirements. Acknowledging the privacy policy is not, in itself, consent or the legal basis for replying to an enquiry.
4. Required and voluntary data
Fields marked as required are necessary for the indicated activity; failure may prevent its execution. Other information and optional marketing are voluntary. Refusing marketing does not block contact or handling of your stay. Consent to the camera, photos or opening the map applies to the selected function. The application does not require constant location tracking, and opening an external map is the user's decision.
5. Recipients and integrations
No active integration recipients have been identified in company settings yet. Access is granted to authorised persons in the organisation and entities operating the system to the extent actually agreed. The mere provision of Stripe, Przelewy24, Fakturownia, SMTP or push fields does not mean transfer of data to these providers. Before launching them, the administrator completes the actual recipients, roles and cooperation rules. Data may be made available to the competent authority if there is a legal basis.
6. Transfer outside the EEA
We do not assume that every integration stores data in Poland or that naming a country establishes compliance with international transfer rules. If a configured service requires a transfer outside the EEA, the controller should identify the actual scope, recipient and safeguards, such as a relevant adequacy decision or agreed standard contractual clauses with the required assessment. Details of the transfer mechanism and how to obtain a copy are available from the privacy contact. An empty entry does not represent an active or compliant integration.
7. How long we store your data
Account: for as long as an authorised account is maintained and its closure needs to be settled; data needed to defend claims is retained only until the relevant limitation period expires. Stay: while handling the stay and for the required accounting period and the establishment, exercise or defence of related claims. Finance: for the period required by tax or accounting law for the particular document; this obligation may continue after account closure. Support: until a case is closed and for the necessary period to demonstrate how it was handled or defend related claims. Enquiries: while responding and carrying out further agreed correspondence; longer only on a separately documented basis. Marketing: until consent is withdrawn or the purpose ends; necessary evidence of consent or withdrawal may be retained for accountability and the defence of claims. Security: for the documented period necessary to detect and investigate an incident, with further access restricted. Offline data: on the device until the local operation is sent or deliberately discarded, in accordance with app settings; the original gallery photo follows device settings. The controller periodically reviews the need for further retention. Restricting or deleting data must respect legal obligations, legitimate preservation of evidence and other people's data. Backups support recovery and require their own limited retention cycle; they are not an additional marketing database.
8. Your data protection rights
Where provided by law, you have rights of access and a copy, rectification, erasure, restriction, portability and objection. No reason is required to object to direct marketing. Consent may be withdrawn without affecting the lawfulness of earlier processing. Requests can be submitted through the panel or the privacy contact. A response is generally provided within one month; any statutory extension must be notified with reasons within the applicable time limit. Necessary and proportionate identity verification may be required. You may complain to the President of the Polish Personal Data Protection Office (UODO); contacting us first is not a condition for exercising that right.
9. Session, preferences and device memory
Necessary session and security mechanisms allow you to log in and protect your requests. Selected appearance preferences and requested offline features may use device memory. By default, we do not run ads or external analytics. Optional storage or device access requiring consent must only be triggered after the correct selection and must be changeable. Clearing your browser storage may log you out and delete unsent data, so check your queue first.
10. Photos and working without the Internet
Camera and gallery are used after user action. The photo is used to document the selected task and is available according to the role and scope of the property. The offline queue can store the decision and file for later review. If the server has a newer state, the user should compare the conflict; a local decision does not constitute a commit to the server. Logging out does not delete the saved queue. Before changing a user or server on a shared device, verify data assignment and how to terminate it securely.
11. Decisions and operator safety
This installation does not claim to make automated decisions with legal effects on users or to have an active external AI service. Permissions derive from the account and organisation. Availability and price calculations follow the displayed rules and require acceptance; they do not replace human assessment of complaints. If the outcome of an operation is uncertain, check its history first. A technical setting must not conceal a missing connection to a provider.
12. Information updates
The document includes its date, content version and the data controller's details applicable to that publication. An archived version can be retained where provided. New purposes, recipients or communication methods require an accurate update; an earlier marketing choice must not silently be extended to additional purposes.