- Guests do not need to register; the app uses a technical account with an anonymous identifier. We send the details of an inquiry only to the host you are writing to; a request is seen by all registered hosts.
- We do not sell personal data and do not use third-party advertising or analytics tools. Hosts only see aggregate statistics for their listings, which you can turn off; requests from a signed-in session carry its session token.
- Location is optional. The nearest destination is selected on your device and sent to our API; loading a map reveals your IP address and the viewed area to the map provider.
- You can delete your account and related data in the app or request deletion by e-mail without reinstalling: RoomsCroatia data deletion.
1. Controller
The controller of personal data in the RoomsCroatia app and on the website roomscroatia.eu (together: the Platform) is CS DATA, obrt za usluge, Kralja D. Zvonimira 5, 10410 Velika Gorica, Croatia, OIB 07928109478 (we). For any privacy questions, write to info@roomscroatia.eu.
We have not appointed a data protection officer, as we are not legally required to do so.
This policy applies to guests, hosts and visitors to roomscroatia.eu, in accordance with the General Data Protection Regulation (Regulation (EU) 2016/679, “GDPR”) and the Croatian Act on the Implementation of the General Data Protection Regulation.
2. What data we process and why
2.1. Guests
| Data | Purpose | Legal basis |
|---|---|---|
| Inquiry: full name, e-mail address, phone number (optional), property and unit, dates, number of adults and children, language, message | Delivering the inquiry to the host of that property and exchanging messages with them | Steps taken at your request prior to entering into a contract, and performance of the contract for use of the Platform (Art. 6(1)(b) GDPR) |
| Request: name, e-mail address, phone number (optional), region or town, dates, number of guests, budget, type of accommodation, message | Showing the request to all registered hosts until the arrival date so that they can send you offers | Art. 6(1)(b) GDPR |
| Messages and offers: content of messages, offers from hosts, inquiry status (e.g. confirmed stay) | Communication between guest and host in the app | Art. 6(1)(b) GDPR |
| Anonymous identifier: a random user identifier without e-mail address or password, linked to your device; associated with inquiries and contact details you provide | Showing hosts' replies under Messages without registration | Art. 6(1)(b) GDPR |
| Review: first name and initial of the surname, rating, comment | Public display with the listing so that other guests get reliable information | Legitimate interest (Art. 6(1)(f) GDPR) |
| Abuse prevention: number of inquiries and requests per e-mail address, IP-derived keys, counters and request times | Preventing spam and misuse | Legitimate interest (Art. 6(1)(f) GDPR) |
2.2. Hosts
| Data | Purpose | Legal basis |
|---|---|---|
| Account: account type (individual or company), full name or contact person, e-mail address, password, mobile phone number, OIB; for companies also name, address, postcode and town | Opening and managing the account, identifying who advertises accommodation, contacting you about your account and listings | Performance of a contract (Art. 6(1)(b) GDPR) |
| OIB and company details | Verifying hosts and preventing fake listings and fraud | Legitimate interest (Art. 6(1)(f) GDPR) |
| Listing: name, address and location on the map, description, photos, video link, units, prices, calendar, last-minute offers, contact name, phone, e-mail, WhatsApp/Viber, website, languages | Public display of the listing to guests | Art. 6(1)(b) GDPR |
| Moderation: listing status, reason for rejection or hiding | Reviewing listings before publication and enforcing the terms of use | Art. 6(1)(b) and (f) GDPR |
| Listing statistics: daily totals of how often the listing card was shown in lists, how often the listing was opened and how often its buttons were tapped (call, WhatsApp, Viber, email, website, map, share, favourites, video), plus the number of inquiries and confirmed stays | Statistics for the host and the administrator (only aggregate counters per listing and day are stored, without visitor identity, device or IP alongside the counters; signed-in requests nevertheless carry a session token; visits by the host and the administrator are not counted; you can turn the statistics off in Profile → Cookie settings) | Art. 6(1)(f) GDPR |
The sign-in system stores passwords as cryptographic hashes, not as readable passwords. On the new hosting, sign-in is managed by our API and database. Photos are resized and re-encoded before upload, so camera metadata (e.g. the GPS location where the photo was taken) is not transferred.
We send e-mails only when they are needed for your account (registration confirmation, password change) or for notices about listings and terms. We do not send newsletters or marketing messages.
If we introduce paid advertising packages, we will process the data needed for invoicing in order to comply with legal obligations (Art. 6(1)(c) GDPR).
2.3. Technical data
The hosting provider (see section 4) keeps technical logs of the web server and proxy (access and errors), security protection (WAF), e-mail and FTP and cPanel logins. The logs contain the IP address, time, full request URL (including parameters, for example search criteria or the requested listing) and the browser or app identifier (user agent). They are kept for security and to keep the service running properly. We do not use these logs to track users. The legal basis is legitimate interest (Art. 6(1)(f) GDPR). The API also processes IP-derived keys, request counts and times to limit abuse. Those records are separate from aggregate listing statistics.
2.4. Terms acceptance, reports and blocking
For guests and hosts we record the user identifier, the version of the content rules accepted and the time of explicit acceptance. This records acceptance of contractual rules (Art. 6(1)(b) GDPR), not blanket consent to all personal-data processing. Merely browsing or signing in does not constitute acceptance.
For content or user reports we process the reporter's identifier, the type and identifier of the reported content, associated authors and the report's target, selected reason, optional details, a report-time snapshot of the reported content (up to 2,000 characters), time, status and administrator's decision. Report data, including details and associated people, is available only to the administrator for handling the report, not to the reported user or the public. This also applies to the content snapshot, which follows the report's retention and deletion, including deletion of an associated account. For blocking we store a pair of user identifiers (who blocked whom) and the time of blocking. Manage your own blocks in Profile → Blocked users → Unblock. The purpose is preventing abuse and enforcing content rules, based on legitimate interest (Art. 6(1)(f) GDPR). Do not include unnecessary personal or sensitive data in reports.
3. Data on your device and third-party services
- Device location – optional, accessed only with permission and when you use the location button. Approximate or precise coordinates are used on your device to select the nearest destination and centre the map. The selected nearest destination is sent to our API as a search criterion. Loading the map tiles described below can reveal the area around your location. We do not send device location to hosts as a device-data field. You can revoke permission in device settings and continue to select a destination manually.
- Favourites, app language and your contact details for the next inquiry – stored only on your device.
- Sign-in – access tokens and the anonymous identifier are stored on your device so that you stay signed in.
- Fingerprint unlock and saved passwords – if you turn on unlocking, your fingerprint, face or PIN is checked by the phone's operating system, and the app only learns whether the check succeeded; it never sees any biometric data. If you save your password, it is kept by your phone's password manager (for example Google, Samsung Pass or iCloud Keychain), not by the app.
- Aggregate listing statistics – the app sends the listing identifier and event type: a card impression, opening a listing or tapping call, WhatsApp, Viber, e-mail, website, map, share, favourites or video. If a signed-in session exists, including an anonymous guest session, the request also carries a session token that lets the API identify the account; the server sees the IP address of the network request. The request is therefore not fully anonymous. Only aggregate counters per listing and day are stored in the statistics, not session tokens, user identity, device or IP. Hosts' own views and administrator views are excluded. Repetition of the same listing and event is limited in working memory during app use. The listing's host and the administrator see the totals. You can turn off sending these statistical events in Profile → Cookie settings → Analytics; doing so does not erase events already included in aggregate totals.
- Maps – when map tiles load, the OpenStreetMap Foundation receives your IP address and requests for the displayed area. Depending on the centre and zoom level, these can reveal the approximate or precise area you are viewing, including the area around your device if you centre the map on its location. This is not necessarily your actual location. Loaded map tiles are temporarily cached on your device.
- Weather forecast – the coordinates of the selected forecast destination are sent to the Norwegian Meteorological Institute (MET Norway). This can include a destination selected with the help of device location; no continuous GPS track is sent. As the network service provider, MET Norway also receives the request's IP address.
- External apps – if you tap call, e-mail, WhatsApp, Viber, website, video or navigation, another app opens, and its provider's rules apply.
4. Who receives data
- Hosts – an inquiry is received only by the host of the property you are writing to, and a request by all registered hosts. From receipt, the host is responsible for this data as an independent controller and may use it only to reply and to arrange the stay.
- Blocking – access to content and contact between blocked users is restricted in both directions as described in the Terms of Use. This is an exception to the general display of requests to registered hosts; it does not recall data already received outside the Platform.
- The public – listing content including the contact details the host entered in the listing, and guest reviews (first name and initial of the surname).
- Infrastructure providers – CREATIVE SOLUTIONS d.o.o., Kralja D. Zvonimira 5, 10410 Velika Gorica, Croatia, OIB 69523788448, is the contracting customer of the hosting package for roomscroatia.eu and e-mail, where the database, sign-in and photo-storage system is also installed. It processes data on our behalf as a processor under a data processing agreement. The hosting itself is provided, as its sub-processor, by Plus Hosting Grupa d.o.o., Pula, OIB 25444746329. According to the provider, the server and data are located in Croatia, and none of the provider's subcontractors have access to the data. The successful transition of the app and portal to this system was confirmed on 6 November 2026. The Supabase Inc. project was paused that day; historical data still remains there and has not been deleted. Pausing is not deletion.
- Independent service providers – OpenStreetMap Foundation (maps), MET Norway (weather forecast) and Google (distribution of the app via Google Play), under their own privacy policies.
- Public authorities – only where required by law or by a decision of a competent authority.
We do not sell personal data and do not share it for advertising.
5. Transfers outside the EEA
The primary server of the new system at Plus Hosting and its hosting backups are located in Croatia, within the EU. This covers the database, files and e-mail on that hosting package, not every third-party service that can be opened from the app.
Historical data remains in the paused Supabase project in the Ireland (EU) region until separately removed. Supabase Inc. is based in the USA; any access by its staff from outside the EEA is a separate matter of international data transfers. This policy does not confirm that the contractual documentation for processing and such transfers has been reviewed. The OpenStreetMap Foundation is based in the United Kingdom, and MET Norway in Norway, which is a member of the EEA.
6. How long we keep data
- Accounts and user content are kept while the account exists or until individual content is deleted earlier. This includes the guest's technical account, inquiries, contact details, messages, reviews, requests and offers, and the host's profile, listings and photos. Account deletion removes associated data from the active system as described in the deletion section; a guest's inquiries and reviews are not merely detached from their identity and left behind.
- Content and user reports are kept while being handled. After resolution, the intended retention is up to 180 days, after which the daily cleanup task removes them. Actual removal depends on the task running; it is not instantaneous at expiry, and task failure or missed runs can delay removal. Reports associated with an account being deleted, including personal data and free text, are deleted with that account.
- Terms acceptance records (version and time) are kept while the account exists. Blocks remain until removed by the user who set them or until either associated account is deleted.
- IP-derived rate-limit records have an intended retention of 24 hours; the cleanup task removes older records in bounded batches. Actual removal depends on task execution and backlog, so we do not promise instantaneous deletion at exactly 24 hours.
- Technical hosting logs are separate from those records and listing statistics. The hosting provider keeps them for security and operation of the service: proxy logs (HAProxy) for 7 days and the others (web server, WAF, e-mail, FTP and cPanel logins) for 30 days. The logs are also included in the daily backups, which are kept for up to 30 days, so an individual log entry can exist for up to about 60 days. On shared hosting we cannot shorten these periods ourselves. You can request information about processing at info@roomscroatia.eu.
- Listing statistics (aggregate totals without visitor identities) are kept while the listing exists and deleted with it. Deleting a guest cannot separate their past events from aggregate totals.
- Automatic hosting backups of the MySQL database, files and e-mail are made daily. They are stored in Croatia and retained for no more than 30 days from creation of each copy. Data deleted from the active system may remain in earlier copies until that period expires; account deletion does not immediately erase all backups.
- Local migration copies are separate from hosting backups. We retain them with restricted access to verify the transfer and allow recovery. The successful transition was confirmed on 6 November 2026; review and removal of these copies must finish by 6 December 2026 (30 days after transition). They include encrypted archives and unencrypted local restores and exports in folders protected by operating-system permissions. Removal follows a previously checked inventory of migration files and databases, not automatic hosting-backup rotation. Historical data in the paused Supabase project has also not yet been deleted and is subject to separate review and removal.
- Hosts' independent copies, such as e-mails or data exported from the Platform, cannot be deleted by us from the host's systems. Request their deletion from the host as an independent controller.
- Accounting records, if we introduce paid packages, are kept for as long as the law requires.
7. Security
Data is transmitted encrypted (HTTPS). On the new system, the app and portal access data through our API, which checks sign-in, role and permission to access each record. Approved listings and their public data are publicly available; guests can access private data for their own inquiries and messages, and hosts for their own listings and received inquiries. Database credentials, private configuration and stored application files are kept outside the public web directory. The administrator accesses data only when necessary to review listings, handle reports and support users.
8. Deleting your RoomsCroatia account and your rights
- Host: Profile → Edit profile → Delete my account, then confirm deletion.
- Guest: Profile → Delete my data, then confirm deletion. This also deletes the technical account with its anonymous identifier, not just the display of data on your device.
- Without the app or reinstalling: e-mail info@roomscroatia.eu with the subject “Delete RoomsCroatia account and data”. State your account or inquiry/request e-mail address and enough information for us to locate your records. Do not send your password. We verify identity where needed; you can submit the request even if you have lost access to the app. We reply without undue delay, at the latest within one month.
Scope: the active system removes your account, profile and sign-in sessions/identities, your inquiries with contact details and associated messages and reviews, other messages and reviews you authored, requests and their offers, your own offers, listings, units and files. Associated reports, blocks, terms acceptances and authorship links are also removed, rather than merely detaching personal content from the account. Other users' unrelated content is not deleted.
Photos and remaining copies: photos immediately become inaccessible through the Platform. Physical file removal follows the committed deletion transaction; failed attempts are retried by the cleanup task. Hosting backups may retain earlier data for no more than 30 days from each copy's creation. Migration copies, historical Supabase data, technical logs and hosts' independent copies have the limitations described in section 6. Uninstalling the app alone does not delete server-side data.
With regard to your personal data, you have the right:
- of access to your data and to a copy of it,
- to rectification of inaccurate data (hosts can do this themselves under Profile → Edit profile),
- to erasure following the instructions above,
- to restriction of processing,
- to portability of the data you have provided to us,
- to object to processing based on legitimate interest,
- to withdraw consent where processing is based on it, without affecting the lawfulness of earlier processing; location permission is managed separately in your device settings.
Send your request to info@roomscroatia.eu. We reply without undue delay and at the latest within one month. Since guests have no registered account with an e-mail address, we may ask you to send the request from the e-mail address you used in the inquiry or request so that we can verify that the data is yours.
If you believe that we process your data unlawfully, you can lodge a complaint with the Croatian Personal Data Protection Agency (AZOP), Selska cesta 136, 10000 Zagreb, azop.hr, or with the supervisory authority of the EU member state where you live.
9. Children
The Platform is not intended for persons under 16, and host accounts can only be opened by adults. If we learn that we have received data of a child under 16 without parental consent, we will delete it.
10. Cookies and storage on your device
The app does not use cookies, advertising identifiers or third-party analytics tools. It only uses its own aggregate listing statistics described in section 3. They do not store a persistent analytics identifier on your device, but signed-in requests carry a session token. You can turn off sending statistical events in Profile → Cookie settings → Analytics. The data it stores on your device is described in section 3. A list of this data, including the cache of listing photos and map tiles already loaded, and the option to delete it are in the app under Profile → Cookie settings.
The website roomscroatia.eu does not use cookies for tracking, analytics or advertising. Its only cookie is set by the host for technical reasons and is described in the cookie settings.
11. Automated decision-making
We do not take decisions based solely on automated processing that have legal or similarly significant effects on you, and we do not create user profiles. An administrator reviews new listings and reports of violations. Reviews may appear before moderation; not every review is checked in advance. Request limits and user blocks are enforced automatically according to the service rules.
12. Changes to this policy
We may change this policy when the Platform or the law changes. We publish the amended policy on roomscroatia.eu and in the app with a new date, and inform hosts of significant changes by e-mail.