Data Sharing Between Platforms and Authorities in the EU

Data sharing under Regulation (EU) 2024/1028 is a structured pipeline: platforms send monthly activity data to the Single Digital Entry Point of the member state where each unit sits, and authorities use that data for enforcement and policy. It is not casual browsing of host accounts. The structure matters because it limits what flows: activity tied to registration numbers, through one channel per country, on a monthly rhythm. Hosts who imagine authorities reading private guest messages misunderstand the pipeline; hosts who imagine no data flows at all misunderstand it in the opposite direction.

That pipeline also explains why consistency matters more than ever. When registration, listings and reported activity are linked by number, a discrepancy in any one element becomes visible in the others. A host whose records agree across all three elements rarely attracts attention, while a host whose elements disagree invites questions even when the disagreement is innocent.

Entry points route data to authorities concerned with short-term rentals, which may include tourism, housing, planning or tax bodies depending on national organisation. Purposes centre on verifying registration, checking compliance with local rules such as caps and planning conditions, and understanding short-let activity for policy. Data is not collected for unrelated purposes, and hosts do not need to consent separately to platform reporting where the regulation requires it, though national data protection rules still govern handling.

Hosts should not try to map every receiving body in every country from this guide. National implementation names the relevant authorities and the entry point operator. What a host can do universally is keep records that would satisfy any of those bodies: registration confirmation, stay log, payout statements and listing views. Those four documents answer most data-related queries regardless of which authority asks.

Hosts control registration accuracy, listing accuracy and their own stay log. They do not control platform reporting formats or entry point routing, and they should not try to influence a platform's report after the fact except to correct a genuine error through the platform's process. Attempting to suppress a legitimate report, for example by asking a platform not to report a stay, would be both ineffective and damaging if discovered.

Hosts can control channel mix, and channel mix affects what is reported through platforms. Direct stays are not platform-reported, but they still require registration, planning and tax compliance, and may require a separate national declaration. A host who shifts stays off platform to avoid reporting has not avoided compliance; they have changed its channel and its evidence requirements. Keep direct stays in the same log as platform stays.

Reconciliation is the host-side skill that matches the pipeline. Monthly, compare your stay log with payout statements and, where platforms provide activity summaries, with those summaries. Note differences and their explanations: month-boundary stays, extensions, cancellations and refunds. File the reconciliation note with the month's records. Over time, that habit produces a year of monthly notes that can answer almost any query without reconstruction.

Annual reconciliation adds a second layer: total nights per unit against any local cap, total income per unit against tax records, and total platform activity against direct activity. Annual totals catch slow drift, such as a cap approached gradually across a year, that monthly views miss. Do the annual check before the next season, not after an authority query.

Errors usually originate upstream: a wrong number, a duplicate listing, or a stay attributed to the wrong unit. When a host suspects an error in reported data, start with their own log and listing, then ask the platform what it reported for that unit and month, then ask the registration authority whether the number record is correct. Correct the source error, keep evidence of the correction, and note the months affected. Platforms and authorities can then be asked to note the correction where their systems allow it.

Not every discrepancy is an error in shared data. Timing differences, fee treatments and refund handling can make two correct records look different. Before alleging an error, check whether a timing or fee explanation fits. A host who alleges errors that turn out to be timing differences loses credibility for the genuine errors that matter.

Hosts handle guest data too, and the same consistency principle applies. Collect only what is needed for the stay, store it securely, and do not share guest details beyond what the booking, safety or legal duty requires. A host who keeps a tidy, minimal guest record file, separate from financial records, will find both privacy and tax questions easier to answer.

Verify the current data-sharing arrangements on the official portal for each country. This guide is general information only and was last verified on 26 October 2026; national implementation details continue to evolve.