Datenschutzerklärung

1. Data Controller

The controller within the meaning of the General Data Protection Regulation (GDPR) and other national data protection laws of the member states, as well as other data protection provisions, is:

2. Data Protection Contact & EU Representative

For all data protection enquiries, please contact us at:

Please direct all requests regarding the processing of personal data, the exercise of your rights, and data protection incidents to this address. We respond within one month in accordance with Art. 12(3) GDPR.

A representative pursuant to Art. 27 GDPR has not yet been appointed. We will publish the contact details here as soon as the appointment has been made.

3. Collection of General Data and Information

The DOMIVENDOMO website collects a range of general data and information with every access by a data subject or an automated system. This data is stored in the server's log files.

The following may be collected:

• browser types and versions used,
• the operating system used by the accessing system,
• the website from which an accessing system reaches our website (referrer),
• the sub-pages accessed on our website via an accessing system,
• the date and time of access to the website,
• an internet protocol (IP) address,
• the internet service provider of the accessing system.

The legal basis is Art. 6(1)(f) GDPR (legitimate interest in operational security, error analysis, and abuse prevention). Our application server logs and API logs are deleted automatically, after 365 days at the latest. Access logs generated by our hosting provider are subject to that provider's retention periods.

4. Cookies & Tracking

On this website, we use only one technically necessary cookie (language preference). Third-party trackers, advertising cookies, or cross-site tracking do not take place on domivendomo.com. The map, which only loads when you click, is an exception (see below).

Your cookie-banner choice itself is not stored in a cookie: it is kept in your browser's local storage under the key domivendomo_cookies. You can withdraw it at any time by clearing your browser's local storage for this site.

Map view: Some pages contain a map from the service Mapbox, Inc. (USA). It only loads when you click “Show map”; before that, your browser does not connect to Mapbox. After the click, your browser loads the map library and the map data directly from Mapbox. In the process, Mapbox receives your IP address, the information your browser sends with every connection (such as browser type and operating system), the time and the map section displayed. In addition, the map reports each load to Mapbox; Mapbox uses these reports to count map loads, which is how the service is billed. The map library also stores a randomly generated identifier in your browser's local storage (entries whose names begin with mapbox.eventData) and sends it to Mapbox with these reports. The map library also keeps loaded map tiles in a cache named mapbox-tiles. The map does not set any cookies.

The legal basis is the consent you give by clicking “Show map” (Art. 6(1)(a) GDPR; for storing data in your browser, Section 25(1) of the German Telecommunications Digital Services Data Protection Act (TDDDG)). Your consent only applies to that page view; the next time, the map loads only after you click again. The identifier has no expiry date; you can remove it by clearing your browser's local storage for this site. For the transfer to Mapbox in the USA, see section 8.

5. Registration & Account

To create a user account on app.domivendomo.com, we collect the following data:

• Email address (required)
• First and last name (required)
• Phone number (optional)
• Profile picture (optional)
• Language preference & time zone

Legal basis: Art. 6(1)(b) GDPR (performance of a contract) for the required data, and Art. 6(1)(f) GDPR (legitimate interest in a usable profile) for the optional phone number and profile picture.

Support requests. If you write to us via the support page of our web app, we process your message with its subject and category, your user ID and any details you include yourself, in order to answer your request. When your account is finally deleted, we delete your requests together with our replies. Legal basis: Art. 6(1)(b) GDPR.

6. Listings & Bookings

When creating a listing, we process all data entered by the host — description, photos, address, price, availability, documents. The description, photos, address and price, as well as the provider's contact name and phone number, are displayed publicly on the platform while the listing is active; uploaded documents are not.

Public provider profile: Providers with a business account can switch on a public profile in their settings. It shows the name, type of business, logo, location, website, a self-written description, the date of registration (“member since”), the published listings and, where available, the reviews. It is then visible to all visitors; without this setting, no profile is shown. You can switch it off again at any time. Legal basis: Art. 6(1)(b) GDPR; you switch the feature on yourself.

Location in the map search: In the map view of the search in our web app (app.domivendomo.com), you can have your location determined. Only if you click or tap the location button there does the app ask your browser for your position. Your browser only releases it with your permission; you can revoke that permission in your browser settings at any time. Providing it is voluntary — without it, you search by place or keyword as usual. Your position serves as the centre of the search and of the map:

• Together with the radius you have chosen, it is sent to our servers in Stockholm, which use it to find the offers within that radius.
• The map centres on your position. Your browser loads the map section directly from the map service Mapbox, Inc. (USA); Mapbox receives your IP address and the coordinates of the displayed section.
• If you select a category under “Nearby places”, such as schools or pharmacies, our server looks up such places around your position with Mapbox. This request is made by our server, not by your browser; Mapbox does not receive your IP address in the process. We keep the places found, together with their distance from your position, in a cache for a short time, without your IP address and without any link to your account.

We do not store your position itself — neither in our database, nor in our search index, nor in our logs. The legal basis is Art. 6(1)(b) GDPR; you trigger the radius search yourself. Retrieving the position from your device is strictly necessary for this function, which you have expressly requested (Section 25(2) no. 2 of the German Telecommunications Digital Services Data Protection Act (TDDDG)). For the transfer to Mapbox in the USA, see section 8.

A booking or inquiry opens a direct communication channel between the buyer/tenant/guest and the host. We process the messages, attachments, and booking and payment data exchanged.

Payments to us — the purchase of credit for platform services — are processed exclusively via Stripe Payments Europe Ltd. (Dublin, Ireland). We do not store credit card data ourselves — only a transaction reference, the amount, and the payment status. No payment between seeker and provider is processed via the platform; bookings are transmitted as a non-binding request. We do not make payouts to providers.

Legal basis: Art. 6(1)(b) GDPR. Invoices and transaction records are retained for 10 years pursuant to § 147 AO and § 257 HGB (German tax and commercial codes).

Reports and blocks

Reports. Signed-in users can report listings, reviews, messages, conversations, user accounts and answers from the AI assistant. Without signing in, only answers from the AI assistant in your own conversation can be reported, up to ten within 24 hours. For this we store your user identifier (without signing in, a technical identifier of your access), which content you reported (its type and identifier; for listings also the identifier of the provider at the time of the report; for an answer from the AI assistant the identifier of the conversation and the wording of the answer, but not your question), the reason you chose, your optional description (up to 2,000 characters), the time and the processing status. To apply the limit without signing in, we count your reports for 24 hours under your guest identifier (section 7). When we decide on a report, we also store the decision, who made it, an internal note on it and the time. Every report is looked at by a person; a report alone does not hide any content. For every new report we receive an email with the type and identifier of the reported content or account, the reason and the time, sent via Resend (section 8); it does not say who reported it and does not contain your description. Reports can only be viewed by the platform's administrators; we pass them on to authorities only where the law requires it (for example Art. 18 of the Digital Services Act). We do not tell the person whose content was reported who reported it, unless the law obliges us to.

If you are reported. If you or content of yours is reported, we store the identifier of the content or of your account, for listings your identifier as the provider, the reason and the description from the report — both come from the reporting person — as well as our decision and an internal note on it. To review the report, a person looks at the reported content, and for reported messages and conversations also at their text.

Blocks. Signed-in users can block other users. For this we store who blocked whom and since when. After that, neither side can write to the other; earlier conversations remain readable for both. Anyone who wants to write to you only learns that the conversation is not possible, not who set the block. Only you can see the list of people you have blocked; you can lift a block at any time.

The purpose is to review and remove content that is unlawful or violates our terms of use, and to protect users from unwanted contact. The legal basis for reports is Art. 6(1)(f) GDPR (our legitimate interest and that of our users in a safe platform); for reports of illegal content under Art. 16 of the Digital Services Act (Regulation (EU) 2022/2065) it is Art. 6(1)(c) GDPR. For blocks it is Art. 6(1)(b) GDPR, and towards the blocked person Art. 6(1)(f) GDPR (protecting the blocking user from further contact). How long we keep reports and blocks is set out in section 12.

Sponsored placements: when we show a sponsored placement, we count for the advertiser how often it was displayed and clicked; the advertiser receives only these totals. Which placement appears depends on the page and the location of the listing shown, not on information about you. So that the same placement is not shown to you too often, we count per day how often we have shown it to you, under your user ID or, if you are not signed in, under the technical identifier of your access. This daily counter currently has no fixed deletion period: if we show you the same placement again on the following day, we remove the previous day's counter; otherwise it is kept for as long as the campaign is stored, including after it has ended. Legal basis: Art. 6(1)(f) GDPR (legitimate interest in limiting how often ads are shown and in accountable billing to the advertiser).

Listing views. When you open a listing, we record that and when it was opened, but not who opened it; only views by signed-in users up to 26 October 2026 are still linked to their account. We do not count views that we recognise as coming from automated programs. We do not count views by a provider of their own listings. Providers can only see how often their listing was opened, not by whom. The legal basis is Art. 6(1)(f) GDPR — our legitimate interest, and that of the providers, in being able to assess the reach of a listing. We delete these records 90 days after the view; when an account is finally deleted, all records linked to it and the statistics for its listings are deleted earlier.

Image check during the review of new listings. When we review a new listing, we compare individual images that do not show any people with the TinEye image search (Toronto, Canada) to detect copied photos. For this purpose, we upload the image to TinEye; according to TinEye, it does not add the image to its search index and deletes it within 24 hours. Canada is covered by an adequacy decision of the European Commission to the extent that the recipient is subject to the Canadian data protection act PIPEDA. Legal basis: Art. 6(1)(f) GDPR (legitimate interest in preventing listings with third-party or copied photos).

7. AI Property Twin

The AI Property Twin answers questions on the basis of the information the provider entered in the listing — title, description, amenities, price, location and size — plus the conversation so far. The answer is generated by a language model and may therefore include wording and general knowledge that does not come from the listing. The following applies:

• In the assistant, you are informed that you are talking to an AI system.
• Answers are marked as AI-generated and may contain errors.
• We use Amazon Bedrock to generate the answers.

When a provider uploads documents for a listing, those documents are read by machine: Amazon Textract extracts the text they contain. The extracted text is stored as a text file in our storage. The following applies:

• Uploading new documents for a listing has been switched off since 31 July 2026. Documents already uploaded remain viewable and can be deleted; when one is deleted, we remove the extracted text immediately, while the uploaded file itself currently remains stored.
• The extracted text is currently not used for the answers given by the AI assistant. The document search it was intended for has been switched off since 10 July 2026.
• Sensitive details are not redacted automatically during this process. Please do not upload documents containing personal data of third parties, or particularly sensitive information, unless it is necessary for the listing.
• There is currently no automatic deletion period for the extracted text. If you would like it removed, a message to us is enough — we will then delete it together with the corresponding document.

When a provider uploads financial documents for a listing, such as invoices, those documents are read by machine: Amazon Textract extracts the text, and a language model accessed via Amazon Bedrock derives the individual line items from it. For each line item we store the amount, the date, the category, whether it is income or an expense, the name of the issuer where it appears on the document, and a short excerpt of the text as evidence. The full extracted text is not stored. We delete the uploaded document once it has been read: it is immediately no longer retrievable. Backup copies remain for another 30 days and are permanently removed after that.

We store your user or guest identifier together with the full text of your question and the answer. If you ask without signing in, in the browser or in the mobile app, the guest identifier is a randomly generated identifier that your browser or your installation of the app stores on your device. For conversations held without signing in, we delete this data automatically 90 days after the respective question. For conversations of signed-in users there is currently no automatic deletion period — the data remains stored until you request its deletion or delete your account; in that case we delete it 30 days after the account is deleted. A message to us is enough. Legal basis: Art. 6(1)(b) GDPR. Should we put the document search back into operation, we will amend this policy beforehand and inform registered users.

8. Hosting & Service Providers

We use the following processors. Data processing agreements under Art. 28 GDPR are in place with all providers. For transfers to the listed service providers in third countries, the EU Standard Contractual Clauses (Commission Implementing Decision (EU) 2021/914) apply. Stripe, Resend, Mapbox, GitHub and Google are additionally certified under the EU-U.S. Data Privacy Framework.

You can obtain a copy of the standard contractual clauses on request at marketing@domivendomo.com.

9. Sign in with Google

DOMIVENDOMO offers "Continue with Google" as an optional way to create and access your account, via Google's OAuth 2.0 / OpenID Connect sign-in. When you choose this option, we request the permissions openid, email and profile from Google. From the details Google provides, we store the following in your account with us:

• your email address
• whether it has been verified
• your first and last name
• a persistent identifier for your Google account

We do not take a profile picture from Google. We do not request or access your Gmail, Google Drive, Google Calendar, Google Contacts, or any other Google Workspace data, and we never use this data to train AI models.

The data is used solely to create your DOMIVENDOMO account, pre-fill your name, and recognise you when you sign in. It is processed and stored by our authentication provider, Amazon Cognito (AWS EMEA SARL, eu-north-1, Stockholm), and is not shared with any third party beyond what is required for authentication.

You can revoke DOMIVENDOMO's access to your Google account at any time via your Google Account permissions page. Revoking access does not delete your DOMIVENDOMO account; to delete your account, use the account deletion option in the app or contact marketing@domivendomo.com.

Our use of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements.

Recipient: Google Ireland Limited, Gordon House, Barrow Street, Dublin 4, Ireland. Legal basis: Art. 6(1)(b) GDPR (performance of a contract).

10. Your Rights

You have the following rights regarding your personal data:

• Right of access (Art. 15 GDPR) — what data we hold about you.
• Right to rectification (Art. 16 GDPR) — correction of inaccurate data.
• Right to erasure (Art. 17 GDPR, "right to be forgotten") — unless statutory retention obligations apply.
• Right to restriction of processing (Art. 18 GDPR).
• Right to data portability (Art. 20 GDPR) — on request we provide your data in a common, machine-readable format.
• Right to object (Art. 21 GDPR) to processing based on legitimate interests.
• Right to withdraw consent (Art. 7(3) GDPR) — at any time and without detriment.

Please direct requests to marketing@domivendomo.com. We respond within one month in accordance with Art. 12(3) GDPR.

11. Right to Lodge a Complaint with a Supervisory Authority

Without prejudice to any other remedy, you may lodge a complaint with a data protection supervisory authority (Art. 77 GDPR), in particular in the EU Member State of your habitual residence, your place of work or the place of the alleged infringement. For users in Austria, this is the Austrian Data Protection Authority (Datenschutzbehörde); for users in Switzerland, it is the Federal Data Protection and Information Commissioner (FDPIC) (Art. 49 of the Swiss Federal Act on Data Protection).

12. Data Retention Period

Personal data is stored only as long as necessary for the respective purpose or as required by statutory retention obligations. Specifically:

Last updated: 26 October 2026. In the event of material changes, we notify all registered users by email at least 30 days before they take effect.

13. Mobile app: camera, location, notifications and crash reports

This policy applies to our mobile app as well. In addition to the processing described above, the app asks for the following permissions. You trigger each one yourself; without your approval the app does not access them.

• Camera and photos. When you take a photo for a listing, your profile picture or a 360° tour image, or pick one from your gallery, we store that photo on our own servers at AWS.
• Location (app). The app only uses your location while it is open and you have allowed it access in your operating system: the map then shows your position and centres on you when you tap the button. The app never requests your location in the background; it cannot locate you while it is closed. The app does not use your location to search for offers, and we do not transmit your device location to our servers. By default, the app only determines your approximate location. On iPhone you can change this: if you enable Precise Location under Settings → Privacy & Security → Location Services → DOMIVENDOMO, the app also uses your precise position; you can revoke this there at any time. On Android devices, the app only requests permission for your approximate location. The map itself is provided by Mapbox, Inc. (USA); as a technical consequence Mapbox receives the coordinates of the displayed map area, a device-local identifier and usage data relating to map interaction and, while the map service's location telemetry is switched on, also your location at the accuracy you have granted. Mapbox's own privacy policy applies to that. How the map search on our website uses your location is described in section 6.
• Notifications. If you allow alerts about new messages and booking requests, our server receives a device-local identifier and a push token. Delivery runs through Google Firebase Cloud Messaging (Google Ireland Limited); Google receives the push token and a device installation identifier in the process.
• Crash reports. Only if you switch this on in the app (Profile → Device Preferences → Diagnostics → "Send crash reports"; it is off by default) do we use Firebase Crashlytics, a service of Google Ireland Limited, Gordon House, Barrow Street, Dublin 4, Ireland, to detect and fix software errors. If the app then crashes or an unhandled error occurs, the following is sent to Google: the error report (stack trace and error data), device model, operating system and app version, information about the state of the device such as free memory and storage, two randomly generated installation identifiers (Crashlytics installation UUID and Firebase installation ID) and, for technical reasons, your device's IP address. The app does not send a user identifier or any additional data of its own. The installation identifiers are pseudonymous; we are technically able to associate them with your account. We use this data solely to keep the app stable, not for advertising and not for tracking across other services. Google keeps this data for 90 days and then starts deleting it. A transfer to the USA is possible; Google is certified under the EU-U.S. Data Privacy Framework. You can withdraw your consent at any time with effect for the future by switching the setting off again in the same place.
• Documents. If you upload a PDF, we store it on our own servers at AWS. What happens to the text it contains is described in section 7.
• No advertising or analytics identifier. The app does not request your device's advertising identifier (neither the Android advertising ID nor the iOS tracking identifier) and does not integrate any advertising or tracking components. We do not create a cross-device profile and do not pass anything on for advertising purposes.
• Cached images. An image cache on the device so that images are not reloaded every time they are shown. It holds images from listings, your profile picture (including earlier ones), photos from your draft listings, and the profile pictures of the people you have been in contact with. It is emptied when you delete your account in the app; if you have it deleted another way, it stays on the device until you remove the app at the latest.
• Currency note. Where a listing shows its price in AED and your device shows euros — or the other way round — we display an approximate amount below it, for example “≈ 117 €” under “500 AED”. The app then loads the daily reference rate as a public file directly from the European Central Bank (Frankfurt am Main), at most once per app session. The ECB receives your IP address and the information your device sends with every connection; we transmit no information about you and none about the listing. If the listing's currency and your display currency are the same, no rate is loaded. No transfer outside the EU takes place. Legal basis: Art. 6(1)(f) GDPR (legitimate interest in giving you a price you can understand).

Legal basis: Art. 6(1)(b) GDPR (performance of a contract); for notifications Art. 6(1)(a) GDPR (consent, which you can withdraw at any time in your operating system); for crash reports Art. 6(1)(a) GDPR in conjunction with Section 25(1) of the German Telecommunications Digital Services Data Protection Act (TDDDG) (consent, which you can withdraw at any time in the app).

14. app.domivendomo.com (web app)

This privacy policy applies in full to our web app at app.domivendomo.com. There, too, we use no advertising or analytics cookies and no cross-site tracking. In addition, the web app stores the following entries in your browser:

You can delete all of the entries listed here at any time in your browser settings. If you delete the sign-in cookies, you will be signed out.

Display currency: so that prices appear in a currency you understand, our server reads, when the web app loads, the country that our content delivery network (Amazon CloudFront) derives from your IP address, and chooses the display currency accordingly. If you have chosen a currency yourself, your choice applies (entry dv-anzeigewaehrung). We do not store the country. Our server downloads the exchange rates as a public file from the European Central Bank; we do not transmit any information about you in doing so. Legal basis: Art. 6(1)(f) GDPR (legitimate interest in a price indication you can understand).

Map in the web app: listing pages with a location and the map view of the search contain the same Mapbox map. It only loads when you click “Show on map” or “See results on map”; by clicking, you give your consent. Otherwise, Section 4 applies accordingly, including to the identifier in local storage and the mapbox-tiles cache. We do not link this identifier to your name, your email address or your account.