Privacy policy

At Huurmarkt we take your privacy and the protection of personal data seriously. This privacy policy explains how we collect, use, store, share and protect personal data when you use our website, mobile application and related services (together: the "Platform").

This is a translation of the Dutch original. In the event of any discrepancy, the Dutch version prevails.

1. Who we are

Huurmarkt operates an online marketplace where users can offer, search for, rent and rent out products, vehicles, spaces and other goods. Huurmarkt merely facilitates transactions between users and is not itself the owner or the renter of the items offered.

For the processing of personal data described in this policy, Huurmarkt is the controller within the meaning of the General Data Protection Regulation (GDPR).

Huurmarkt BV
Ukkelstraat 2K
5628 TE Eindhoven
The Netherlands

Email: info@huurmarkt.nl
Chamber of Commerce (KvK) number: 99794322
VAT identification number: NL869135818B01

2. What personal data we collect

We collect personal data you provide to us, data generated by your use of the Platform, and data we receive from third parties. This may include:

• Identification and contact details such as name, email address, phone number, profile photo and account details.
• Account and profile information such as listings, descriptions, photos, prices, availability, preferences and settings.
• Transaction data such as bookings, rental periods, payments, refunds, deposits, protection contributions and related communication.
• Communication data such as messages sent through the Platform, contact with customer service, feedback and reviews.
• Verification data such as the status of identity verification, age checks or verification results provided by our verification partner. Upon an approved identity verification we ourselves store first name, last name, date of birth, nationality, document type (for example passport or driving licence), country of issue, the expiry date of the document and, for a driving licence, the licence categories. Our verification partner Didit also processes, on our behalf, the photos of your identity document, your selfie, the recording of the liveness check and your facial data, and keeps them for 1 month; see Payments, protection and external services. Our own database holds no photos, selfies or facial data. How long we keep data is set out in Retention periods.
• Technical and usage data such as IP address, device type, browser, operating system, timestamps, pages visited, log files and cookies.
• Location data such as an approximate location, city or region and map-related search interactions.

3. Purposes of processing

We process personal data only where there is a valid legal basis, for the following purposes:

• Providing, maintaining and improving the Platform and its features.
• Creating and managing user accounts.
• Facilitating bookings, rentals, payments, deposits and Huurmarkt Protection.
• Enabling communication between users.
• Providing customer service and handling disputes.
• Carrying out identity verification and preventing fraud, misuse and unauthorised use.
• Creating a payout account for hosts with our payment service provider, so you can receive your earnings. We only use the name and date of birth verified with us for this purpose with your separate permission.
• Analysing and improving the use and performance of the Platform.
• Complying with legal obligations and lawful requests from competent authorities.
• Sending service messages and, where permitted, marketing communications.

4. Legal basis

We process personal data on one or more of the following legal bases:

• Performance of a contract.
• Compliance with a legal obligation.
• Legitimate interest, such as securing the Platform, preventing fraud and improving our services.
• Consent, where required (for example for marketing purposes, for statistics through Google Analytics, performance monitoring in the app, and for showing the renter's phone number to the host of a confirmed booking, see Your phone number after a confirmed booking).

5. Payments, protection and external services

Payments on the Platform are processed by external payment service providers, including Stripe. Huurmarkt does not store full payment card details.

Payouts to hosts. If you want to receive money as a host, we create a payout account for you with Stripe. For this we pass on to Stripe: your first and last name, your date of birth, your home address, your phone number, your email address, a link to your public Huurmarkt profile and — for a business account — your company name. Your account number (IBAN) goes straight from your browser to Stripe and never reaches our servers. We also record with Stripe that and when you accepted its terms, together with the IP address at that moment.

Stripe uses these details to verify who receives the money. That is a check Stripe must carry out itself under financial regulations. For that part Stripe is therefore not a processor acting on our instructions, but an independent controller with its own privacy statement and its own retention period. If the check cannot be completed on the basis of these details, Stripe may ask you directly for an identity document; that document goes to Stripe and not to us.

Reuse of your verification data. If you have already completed an identity check with us, we can use the first name, last name and date of birth confirmed at that time instead of the name and date of birth you enter yourself. They then match your ID document exactly, which reduces the chance of an extra document check. This only happens if you give separate permission for it when linking your account — and we only ask for that permission if you have actually completed such a check. We record your permission, and you can refuse without consequences: we then use what you entered yourself. Your nationality and document details are never included.

Huurmarkt Protection is managed by Huurmarkt itself through a risk pool and is not insurance; see the terms of service.

Identity verification is carried out by our processor Didit, through a secure flow hosted by Didit. The check includes automatic reading of the document, a liveness check and a 1:1 face comparison; this involves the processing of biometric data, solely for the purpose of uniquely identifying you as part of the verification. Didit acts on our behalf. Didit keeps the photos of your identity document, your selfie, the recording of the liveness check and your facial data for 1 month after the check and then deletes them. That month is needed so that a doubtful case can be looked at by hand and so that you can object to a rejection. Didit also compares your face with earlier identity checks on Huurmarkt, to see whether the same person has several accounts; because Didit deletes the data after a month, that comparison only works against checks from the past month. Our own database holds no photos, selfies or facial data. Which data we keep ourselves and for how long is set out in What personal data we collect and Retention periods.

For the optional "Fill in with AI" feature in the listing wizard, the photos you select and any title are sent server-side to our processor Anthropic (United States), solely to generate suggestions for your listing (such as category, title, description, features, amenities and house rules). This data is not used for advertising or marketing purposes. Processing only takes place if you start the feature yourself; see also International transfers.

Statistics through Google Analytics, on the website and in the app.

• What. We use Google Analytics from Google, through Firebase. It measures which pages and screens you view and what you do, such as searching, saving a listing, requesting a booking or creating a listing.
• Why. To see how the Platform is used and to improve it.
• Legal basis. Only with your consent. On the website we ask for it in a small notice, in the app in the privacy notice. Without consent, Google Analytics does not load.
• Linking. If you are signed in, we link the measurement to your account ID: a random number, not your name or email address. That way your use of the website and the app is counted together.
• What is sent. From the address of a page we first remove anything that says something about you, such as a booking number or an invitation code. Some events do include an internal number of a booking, conversation or listing, for example when you request a booking, send a message or view a listing. A search is sent with the search term as you typed it, unless it looks like an email address, phone number or postcode. Chat messages are never sent.
• Retention. Google keeps user-level data for 2 months.
• Transfer. Google may process the data in the United States. That transfer relies on the EU-US Data Privacy Framework, under which Google is certified.
• Withdrawing. You withdraw your consent through "Cookie settings" (in your profile, on the sign-in page or at the top of the cookie policy), with the "Analytics" switch under Profile → Privacy & Sharing, or in the app under Profile → Privacy & Sharing.

Our own measurement of creating a listing, on the website and in the app.

• What. When you create a listing, we record which step you reached, whether you used the AI scan, which required fields were still missing (only the names of those fields, never what you entered), how long you took and whether you published the listing or saved it as a draft. A random number for that one attempt goes with it: on the website in your tab's storage (hm-wizard-sessie, see the cookie policy), in the app only in memory. We also record whether the entry comes from the website or the app.
• Why. To see where creating a listing gets stuck, and to improve that.
• Legal basis. Our legitimate interest in a listing flow that works. We do not ask for consent for this, so this measurement also runs if you decline Google Analytics.
• What is not included. The recorded entry contains no name, email address, account number or listing number.
• What is. The request reaches our hosting provider, which records the IP address and the time of the request in its log.
• Retention. As long as our hosting provider keeps that log; after that the entry is gone.

Crash reports in the app (Firebase Crashlytics). In the app we use Firebase Crashlytics from Google to see and fix crashes and errors. A report contains technical data about your device, the app version and what went wrong, and is linked to your account if you are signed in. We do this on the basis of our legitimate interest in a stable app. It is on by default, and you switch it off with the "Crash reporting" switch under Profile → Privacy & Sharing in the app.

Performance monitoring in the app (Firebase Performance).

• What. In the app we use Firebase Performance Monitoring from Google. It measures how quickly the app starts and how quickly search results load, with technical data about your device, operating system and network and the Firebase installation ID. It also automatically measures how long the app is in the foreground and background, how much processor and memory it uses and, per screen, how many frames are slow or frozen. Our own measurements also record which screen opened first, whether you searched by place or category (only yes or no), how many results came back and whether loading succeeded. Crash reports carry the same installation ID and, if you are signed in, your account; that way the measurement can be linked to your account.
• Why. To see where the app is slow, and to improve it.
• What is not sent. No search terms, no location of your device (Google only derives the country from your IP address) and no numbers of your account, a booking or a listing. Automatic measurement of network requests is switched off.
• Legal basis. Only with your consent: the same consent as for Google Analytics, which we ask for in the app in the privacy notice. Without consent, performance monitoring stays off.
• Retention. Google keeps measurement data linked to an IP address for 30 days and other measurement data for 60 days; after that Google starts deleting it.
• Withdrawing. With the "Analytics" switch under Profile → Privacy & Sharing in the app. It switches off Google Analytics and performance monitoring together.

Crash reports from the website (Google Cloud Error Reporting).

• What. If something goes wrong on the website — an error in our code in your browser or on our server — we send an error report to Error Reporting from Google Cloud. There we see which errors occur, how often and in which version of the website, and we are notified of a new error.
• Why. To find and fix errors, even when nobody reports them to us.
• Legal basis. Our legitimate interest in a website that works. We do not ask for consent for this: it is on by default, and you can switch it off (see below).
• What is sent. The error message and the place in our own code where it went wrong; the address of the page, without the part after the question mark and with a booking number, user number or invitation code replaced by a placeholder; which browser and operating system you use; and the version of the website. We first remove email addresses, phone numbers, bank account numbers, codes, keys and addresses of other websites from the error message; for an error from our own backend only the type of error and the status code are sent, not the text. A report that does not come from our own code (for example from a browser extension) is not passed on.
• What is not sent. We do not send your account or your IP address. An error message is free text: whatever happens to be in it and does not look like an email address, phone number or code (a name, for example), we cannot always recognise. The report first reaches our hosting provider, which, as with any other request, records the IP address and the time in its log.
• Retention. Google keeps the reports for 30 days.
• Transfer. Google may process the data in the United States; see International transfers.
• Switching it off. With the "Crash reports" switch: in the cookie notice under "Customise", through "Cookie settings", and if you are signed in under Profile → Privacy & Sharing. Switching it off takes effect immediately, also in your other tabs and also for errors on our server. We remember that choice for 12 months in the cookie __Host-hm-crashrapporten (see the cookie policy); switching it back on removes that cookie. Your choice about Google Analytics does not change.

If you choose to sign in with Google or Apple, we receive your name and email address from that party and that party processes the sign-in under its own privacy policy; and if you schedule an introduction through the Cal.com calendar on the page for businesses, Cal.com processes what you enter there (Cal.com sends error reports from the calendar to Sentry in the United States).

For fraud prevention, email delivery, hosting, cloud storage, mapping services and customer service we also use carefully selected external service providers. These parties process personal data solely on our instructions and under appropriate contractual safeguards. This does not apply to the check Stripe must carry out itself for a payout account, described above: there Stripe does not act on our instructions but under its own legal obligation.

6. Sharing personal data

We may share personal data:

• With other users, to the extent necessary to carry out a rental or booking transaction.
• With external service providers who support us in operating the Platform.
• With payment providers for the purpose of processing payments.
• With Stripe, when you link a payout account as a host, so that Stripe can carry out the legally required check on the recipient of the money. See Payments, protection and external services for which details these are.
• With government authorities or other parties where legally required or necessary to protect our rights.

We do not sell personal data to third parties.

Your phone number after a confirmed booking

A phone number is useful at the moment you need each other: you are standing at the door and the key is not there. That is why the renter's phone number can become visible to the host. This happens only with the renter's consent:

• Which number. The number the renter has with Huurmarkt: the verified login number or, if there is none, the contact number the renter entered themselves (we have not checked that one; the host sees a note saying so). If there is no number, there is nothing to show.
• To whom. Only to the host of that booking. Not to other users, and not on listings, profiles or in lists.
• From when. Only once the booking is settled: completed, or accepted and paid. A request that is still pending shows no number.
• For how long. Until 72 hours after the end of the rental (counted from the return, or otherwise from the end of the day of return). After that the host no longer sees the number on Huurmarkt. What the host has already written down, we cannot take back.
• Legal basis and your choice. The renter's consent. As a renter you give it when you book, for that one booking, next to the sentence "The owner will see your phone number once your booking is confirmed". You can refuse without any consequence for your booking.
• Use by the other person. The number is meant for reaching the renter for this rental, and only for that.

Your message on a contact listing

Some of the listings on Huurmarkt are contact listings: a listing by a company that you do not book, but on which you get in touch through Huurmarkt. You can recognise it by the "Get in touch" button and by the notice underneath it saying that this owner arranges the rental themselves. If you send such a message, it reaches that company:

• What we pass on. The name or username you go by on Huurmarkt and the content of your message, plus anything else you share in the conversation yourself — including a phone number, an address or a photo, if you send one.
• To whom. Only to the owner of that listing. Not to other users, and not on listings, profiles or in lists.
• Legal basis. The same as for any conversation on Huurmarkt: enabling communication between users (see Purposes of processing and Legal basis).
• Who is responsible for what. For this conversation, we and that company are each an independent controller. The company therefore does not process your data on our behalf, nor do we on theirs. It informs you about its own processing itself, at the latest with its first reply.
• What the company may do with it. Our terms for this type of listing state that the company uses the data from your message solely to respond to that message and to enter into and perform any rental agreement. Not for direct marketing, newsletters, profiling or enriching its own records, and not for disclosure to third parties — unless you give the company separate, demonstrable permission yourself, or the law requires it. The company keeps the data no longer than is necessary for that purpose.
• Your rights. For the conversation as it is held by us, you can come to us (see Your rights). For what the company does with your data afterwards, you submit your request — access, correction, erasure, objection — to that company; it handles that itself within the statutory period.
• What we do not give the company. We show the company how many contact requests its listing received per period. That figure contains no names, no contact details, no message content and nothing by which a visitor can be identified.

7. Retention periods

We do not retain personal data longer than necessary for the purposes for which it was collected, taking statutory retention periods into account. Data that is no longer needed is securely deleted or anonymised.

For identity verification these periods apply:

• Photos of your identity document, your selfie, the recording of the liveness check and your facial data (at Didit): 1 month after the check. Didit then deletes them.
• The data we keep ourselves (first name, last name, date of birth, nationality, document type, country of issue, expiry date and licence categories): for as long as your account exists.

For statistics through Google Analytics and for crash reports, the retention periods are in Payments, protection and external services.

8. Security

We take appropriate technical and organisational measures to protect personal data against loss, misuse, unauthorised access, disclosure and alteration. Despite these measures, complete security can never be guaranteed.

9. Your rights

Under the GDPR you have the right to:

• Access your personal data.
• Have inaccurate or incomplete data corrected.
• Request erasure of your personal data.
• Restrict or object to processing.
• Request data portability.
• Withdraw your consent, where processing is based on it.

You can submit requests through the help centre. You also have the right to lodge a complaint with the Dutch Data Protection Authority (Autoriteit Persoonsgegevens).

10. Automated decision-making

The outcome of identity verification is reached automatically (document verification, a liveness check and a face comparison by the verification partner). A rejection may affect your ability to book certain products.

You have the right to human intervention: in the event of a rejection or doubt, you can request a manual review by a member of staff through the help centre. You can explain your point of view and have the outcome reconsidered.

The suggestions produced by the AI photo scan are not automated decision-making within the meaning of Article 22 GDPR: they are non-binding proposals that you review, adjust and publish yourself.

11. Cookies and similar techniques

We use cookies and similar techniques to make the Platform work, and — only with your consent — for statistics through Google Analytics. Exactly which ones, what they do and how you withdraw your consent is set out in our cookie policy.

12. Minors

The Platform is not intended for persons under 18. We do not knowingly collect personal data from minors.

13. International transfers

Personal data may be processed or stored outside the country where you live. For transfers outside the European Economic Area we apply appropriate safeguards in accordance with the GDPR: an adequacy decision where available, and otherwise the EU Standard Contractual Clauses (SCCs) with supplementary measures where necessary.

For the AI photo scan, photos and any title are transferred to Anthropic in the United States. This transfer relies on the EU-US Data Privacy Framework to the extent the certification covers it, and additionally or otherwise on the SCCs.

For statistics through Google Analytics, performance monitoring and crash reports in the app (Firebase Performance and Firebase Crashlytics) and crash reports from the website (Google Cloud Error Reporting), Google may process data in the United States. This transfer relies on the EU-US Data Privacy Framework, under which Google is certified.

14. Changes to this privacy policy

We may amend this privacy policy. The most recent version is published on the Platform.

15. Contact

For questions about this privacy policy or the processing of personal data, please contact us through the help centre or by email at info@huurmarkt.nl. Our full company details are under Who we are.