Type
(Policy, Regulation, Self-regulation, Technology, multiple)

(?) Unique identifier ID for each case

(?) Name or title of the respective regulation

(?) Country and, if applicable, city where example is implemented

(?) What type of example is this? A policy (government strategy, manifesto pledge, think tank policy proposal), regulation (implemented laws, directives, etc.) or self-regulation (voluntary action, psossibly based on an agreement with (local) government)?

(?) Is the example "in discussion" (e.g. as part of the general political discourse or legislative process), "implemented" (as part of a law or adopted government strategy), and "evaluated" (i.e. has the approach been formally evaluated with regard to its effectiveness?)

(?) What is the broad focus and purpose of the approach, which ODI design pattern does it fit?

What is the context of the approach? E.g. is it motivated by concerns about the affordability of local housing or promoting tourism in a city/region?

(?) What type of properties and property usage does the regulation cover?

(?) What problems have been identified or discussed regarding the approach?

(?) What does the regulation regulate specifically? Is it regulating the asset (e.g. what installations does a property need to be rentable), owner/host behaviour (e.g. how can the owner/host use the property for lettings), or platform (e.g. how can a platform such as AirBnB operate?)

(?) What type of data (or information) is collected/processed/exchanged to implement the approach?
Note: This can happen explicitly or implicitly; e.g. many regulations do not explicitly mention the processing of data, but require this to be implemented.

(?) Who processes data and between which actors is it exchanged?

(?) Is the collection and exploitation of digital, (semi-)structured data an explicit part of the approach?

(?) What amount/volume of data is involved? Large (e.g. when data is automatically extracted from platforms) or small (e.g. when data is selectively extracted from platforms)?

(?) What types of data are collected, e.g. personal data, data on apartment specification, location, rental statistics?

Regulation (2015 Deregulation Act) + voluntary self-regulation of AirBnB (automatic enforcement of 90 days rule)

number of days for which property is rented

data on rental periods, but no data is centrally collected

National regulation + custom self-regulation agreement between Paris and AirBnB

Data on identity of landlord/property owner (including tax record number);
total number of days property is rented

Only proposal 1 would require the continuious collection of data on short-lettings and hosts, still constituting a low-volume data collections. All other proposals depend on even smaller data volumes

- letting statistics
- data on individual letting activities, by host and property
- data on disputes
- data on neighbours (potentially, depending on channel of distribution)

Referring to policy proposals:
1) and 2) Information on intended property usage; property specifications (including number of rooms, technical and safety equipment); property owner; location of property.
3) Data on income generated through short-lets; property owner / host identity; property owner / host contact details
4) requires no specific data to be collected

Referring to policy proposals:
1) and 2) data collected partly by platforms (owner/host identity, location) as well as applicable authorities (e.g. property specification, equipment, intended usage).
3) Data to be collected by platform
4) n/a

Only the collection of income data (potentially also involving collection of transactional data) could amount to relatively large data retrievals; the volume of all other data appears to be very limited.

- personal data: Owner/host identity; income data
- data on property specifications, layout, and equipment
- data on property usage for short lets

Policy proposal / legal analysis

Data affected includes:
1) data on consent of other property owners and/or building managers
2) collection of reputation data on both hosts and guests, including identity of those users
3) and 4) data on relevant safety and accessibility equipment (e.g. fire extinguishers, wheelchair accessible doors and bathrooms); data on property location; data on host / property owner
5) collection of property host / owner; income generated; number of guests; number of beds available for short lets etc.

Data for proposals 1 - 3 is small; data required for proposals 4 and 5 can be more comprehensive and transactional.

- personal data: Owner/host identity; income data
- data on property specifications, layout, and equipment
- data on property usage for short lets
- aggregate data on platform performance (e.g. does a platform have 20% wheelchair accessible bedrooms?)

Policy proposal / guidance for EU member states

Types of data affected vary:
1) Market access: identity of owner/operator/host; total duration of stays; number of guests; (depending on specific regulations: proof of compliance with health and safety regulations; commercial registration documents; proof of compliance with minimum room/habitability requirements; insurance documents).
2) proof of compliance with insurance requirements (e.g. indemnity insurance)
3) collection of data on the equipment and condition of properties offered on a platform (relevant in order to assign quality labels)
4) collection of host income data (generated through platform); data on identity of host/owner; data on number of nights property is let

All data to be collected by the relevant platform

Data exploitation is recognised as a separate activity as long as it supports related regulatory activities, e.g. data collected by platforms has to be processed and exploited by regulators in order to assess applicable taxes and whether a host should register as a commercial provider.

Data is mostly small, covering e.g. one-off data on registrations; property equipment and specificatons; host identity.
Data on letting activities (nights rented) and income generated relate to transactional activities and could therefore be more substantial.

- personal data: Owner/host identity; income data; insurance policies
- data on property specifications, layout, and equipment
- data on property usage for short lets (how many nights?)
- (if required) data on registration with regulators (e.g. local tourism office)

Proposals affect multiple types of data, including:
1) precise data on property location; data on safety equipment; building status; ownership information.
2) data on health and sefty equipment of property
3) owner/host identity; data on generated income through short-lets; collection of detailed information on guests; collection of data on neighbours and (if applicable) building managers; total length of lettings per day

data is to be collected by platforms; additional data, e.g. on health and safety, can be collected by local authorities through inspections

Data is mostly small, covering e.g. one-off data on registrations; property equipment and specificatons; host identity.
Data on letting activities (nights rented) and income generated relate to transactional activities and could therefore be more substantial.

- personal data: Owner/host identity; income data; insurance policies; guest ID data; identity of neighbours and building managers
- data on property specifications, layout, and equipment
- data on property usage for short lets (how many nights?)

Data on owner / host identity (including date of birth, marital status, previous addresses);
Data on apartment equipment and specifications (number of rooms, size, number of occupants, location, social housing?);
Data on property utilisation (including current and previous tenancy agreements, duration of rent, rent level/amounts, receipts);
(if applicable) company data: company name; proprietors; form/legal status or organisation

Data is collected both by property owners/hosts and platforms

no - data exploitation only takes place in support of investigations or legal proceedings

- Personal data owner / host identity (including date of birth, marital status, previous addresses);
- Data on apartment equipment and specifications (number of rooms, size, number of occupants, location, social housing?);
- Data on property utilisation (including current and previous tenancy agreements, duration of rent, rent level/amounts, receipts);
- (if applicable) company data: company name; proprietors; form/legal status or organisation

Depending on proposal, different types of data are affected:
1) owner / host identity; property location; information on future use of property (for planning permission for commercial property)
2) owner / host identity; property location; information on health & safety installations (e.g. smoke detector); tenancy agreements (if applicable); data on size of property

According to current early-stage proposals, it appears all data would have to be collected entirely by the council. No cooperation with businesses such as AirBnB is foreseen.

Data exploitation is only foreseen for the immediate monitoring and enforcement of applicable regulations.

Amounts of collected data would likely be small and are non-transactional.

Personal data: data on owner/host identity
All other data is non-personal and concerns information such as the location of a property and certain property equipment (e.g. smoke detectors, size and layout of flat, etc.)

No specific proposal has been made, however (if implemented) the regulation would likely affect:
1) data on owner/host identity
2) location of property
3) count of days property has been short-let
4) potentially information on property specification (e.g. number of rooms, size, etc.) and health and safety equipment (e.g. smoke detectors)

Data could either be collected by the city council or AirBnB/peer-to-peer businesses

Data exploitation is only foreseen for the immediate monitoring and enforcement of applicable regulations.

Amounts of collected data would likely be small and are non-transactional.

Personal data: data on owner/host identity
All other data is non-personal and concerns information such as the location of a property and certain property equipment (e.g. smoke detectors, size and layout of flat, etc.)

Self-regulation (voluntary agreement between the City of Genoa and AirBnB)

Implemented (effective from 1st August 2017)

The agreement regulates the collection of data relevant to the calculation and collection of city taxes:
1) Owner / host identity; address; (potentially tax ID)
2) Property location
3) Revenues generated from short-lets; total period/duration of renting activities

Data is collected primarily by AirBnB. The platform then calculates and collects the applicable tax amount, and remits this to the city.

Data exploitation by AirBnB's is an objective and motivation of the agreement, in order to facilitate automated tax calculation and collection. Limited data is shared with city officials where necessary (see previous cells).

Data is both static (e.g. owner/host identity; property location) and transactional (e.g. rental periods; revenues generated). Both data will be limited in size, but transactional data could be more comprehensive.

1) Personal data: Owner / host identity; address; (potentially tax ID)
2) Non-personal data: Property location; revenues generated from short-lets; total period/duration of renting activities

Self-regulation (voluntary agreement between the City of Genoa and AirBnB)

NB: The self-regulation is complemented by the Portuguese law on short-term apartment rental (Lei do Alojamento Local em Portugal), which provides stream-lined regulation for short-term lets.

The agreement regulates the collection of data relevant to the calculation and collection of city taxes:
1) Owner / host identity; address; (potentially tax ID)
2) Property location
3) Revenues generated from short-lets; total period/duration of renting activities

Data is collected primarily by AirBnB. The platform then calculates and collects the applicable tax amount, and remits this to the city.

Data exploitation by AirBnB's is an objective and motivation of the agreement, in order to facilitate automated tax calculation and collection.

Data is both static (e.g. owner/host identity; property location) and transactional (e.g. rental periods; revenues generated). Both data will be limited in size, but transactional data could be more comprehensive.

1) Personal data: Owner / host identity; address; (potentially tax ID)
2) Non-personal data: Property location; revenues generated from short-lets; total period/duration of renting activities

Regulation + self-regulation

Data affected includes:
- owner identity; identity of guests
- location of property; property specification (number of rooms)

Data is collected by landlords and subsequently submitted to authorities.

NB: For AirBnB, a separate agreement specifies that AirBnB will automatically transfer guest data to authorities. However, this is not part of the law.

The exploitation of data for regulatory purposes is a distinct feature of the approach. Particularly, the issuance of a property ID creates a new type of data, which is also made available through a designated databank for police and tourists. Notably, the purpose of the database is beyond the monitoring of regulatory compliance and also covers tourist information.

Data is static (e.g. owner/host identity; property location) and will therefore likley be limited in size and dynamics.

Personal data: owner identity; identity of guests
Other data: location of property; property specification (number of rooms)

Regulation + Self-regulation

The agreement regulates the collection of data relevant to the calculation and collection of tourist accommodation taxes:
1) Owner / host identity
2) Property location
3) Number of nights rented and number / type of guests (adults vs. children)

Data is collected by AirBnB. The platform calculates and collects the applicable tax amount, and remits this to local authorities.

Data exploitation by AirBnB's is an objective and motivation of the agreement, in order to facilitate automated tax calculation and collection.

Data is both static (e.g. owner/host identity; property location) and transactional (e.g. rental periods; number/type of guests). Both data will be limited in size, but transactional data could be more comprehensive.

Personal data: Owner / host identity
Other data: Property location; number of nights rented; number / type of guests (adults vs. children)

Canton Geneva - LDTR (Loi genevoise sur les démolitions, transformations et rénovations de maisons d’habitations)

Regulation
NB: The LDTR was initially introduced in 1996.

Data is only collected ad hoc, i.e. where authorities have indications that a property is used illegally. In such cases, the following data would like be affected:
1) Owner / host identity
2) Property location
3) information on renting activities (number of nights rented; number of guests; total income generated)

Since data is only collected ad-hoc, amounts will likely be small and not comprehensive.

If data is collected:
- Personal data: Owner / host identity
- other data: Property location; information on renting activities (number of nights rented; number of guests; total income generated)

Regulation
NB: Electronic registration of hotel guests has been in place since 2008 and thus predates the emergence of the modern peer-to-peer accommodation market. Registration of foreign accommodation guests has been required by Swiss federal law since 1929.

Owner/host behaviour is regulated: Hosts of any paid accommodation must register their guests in an online database

Local authorities (guest registration database operated by the police)

Data volume is limited and contains only static data on hosts, property location, and guests.

If data is collected:
- Personal data: Owner / host identity; identities of guests
- other data: Property location

Regulation
NB: The tourist tax law in Bern pre-dates AirBnB and similar peer-to-peer accommodation platforms. However, the existing law was revised in 2014 to explicitly mention AirBnB.

Data affected includes:
1) Identity of hosts
2) Location of properties
3) Number of nights and guests for which property has been rented

n/a - data is only used for tax calculation and collection purposes

Data volume is limited and contains only summary static data on hosts, property location, and number nights/guests rented.

- Personal data: Identity of hosts
- Non-personal data: Location of properties; number of nights and guests for which property has been rented

Data affected includes:
1) Identity of hosts
2) Location of properties
3) Number of nights and guests for which property has been rented (in order to calculate applicable tourist tax amounts)

n/a - data is only used for tax calculation and collection purposes

Data volume is limited and contains only summary static data on hosts, property location, and number nights/guests rented.

- Personal data: Identity of hosts
- Non-personal data: Location of properties; number of nights and guests for which property has been rented

Ireland, Dublin (particular focus)

Regulation + regulation proposal

Implemented (regulation) + in discussion (regulation proposal)

n/a - Data is only collected as part of the official planning approval process.

Data affected includes:
1) Owner/host identity
2) Property location
3) Property specification and equipment (fire/life safety installations)
4) Information on insurance policies
5) Platform: Individual information on property listings; quarterly data on new registrations

Data is primarily collected by local authorities (1-4);
platform data is collected by platforms

Data exploitation is only foreseen for the immediate monitoring and enforcement of applicable regulations.

Data collected is relatively comprehensive but static. This implies data volumes will most likely remain small.

- Personal data: Owner/host identity; (potentially) individual information on property listings
- Other data: Property location; property specification and equipment (fire/life safety installations); information on insurance policies; quarterly data on new registrations

Data affected as part of NITB registration process:
- Owner/host identity
- Property location
- Information on property specification (i.e. health and safety installation such as fire alarms)

Data is collected by the Northern Ireland Tourism Board (NITB).

Data is collected to ensure regulatory compliance of landlords. No further data exploitation.

Data contains only limited, static data. Volume is small.

- Personal data: Owner/host identity
- Other data: Property location; information on property specification (i.e. health and safety installation such as fire alarms)

n/a - Data is currently not collected as rules for planning permission approval are unspecified.

n/a - Data would later be collected by the Urban Redevelopment Authority.

in discussion (formal legislative process)

Types of data affected:
- Identity of property owner/host;
- Location of property;
- Property specification and fire protection equipment (NB: depending on scope of city registration scheme);
- Aggregate data/statistics on short-letting activity in the city (precise city reporting requirements not yet defined);
- Data on registered short-letting companies.

Data on registration system is collected by city authorities. Further data collection (e.g. on individual renting activities) occurs through the platform's regular operations.

Data exploitation is only foreseen for the immediate monitoring and enforcement of applicable regulations. Further data exploitation, e.g. by publishing data on the development of the short-letting market or on the registration database is not part of the regulation proposal.

Data is mostly static and therefore limited.

Personal data: Identity of property owner/host;
Other data: Location of property; Property specification and fire protection equipment (NB: depending on scope of city registration scheme); Aggregate data/statistics on short-letting activity in the city (precise city reporting requirements not yet defined); Data on registered short-letting companies.

in discussion (formal legislative process)

Types of data affected:
- Identity of property owner/host;
- Location of property;
- Property details, including building and fire safety equipment;
- Data on registered short-letting companies.

Data exploitation is only foreseen for the immediate monitoring and enforcement of applicable regulations.

Data is mostly static and therefore limited.

Personal data: Identity of property owner/host.
Other data: Location of property; Property details, including building and fire safety equipment; Data on registered short-letting companies.