Hospitality Radar
Counted 21 Nov 20265,199 projects with a published source152 countries874 new signals in 30 daysProject intelligence for hotel suppliers

Privacy policy

1. Controller

ligea GmbH, Hardtstraße 37a, 76185 Karlsruhe, Germany. Contact: [email protected]. We have not appointed a data protection officer, as there is no legal obligation to do so.

2. Browsing the site

Browsing the overview requires no account and sets no tracking cookies. To see how the site is used we use Cloudflare Web Analytics. It works without cookies, does not store IP addresses and creates no user profiles; it counts page views, referring sites, countries and device types (Art. 6 (1) (f) GDPR). Cloudflare delivers and protects the site and processes connection data (IP address, time, requested page) for this purpose, legal basis Art. 6 (1) (f) GDPR. Fonts and scripts are served from our own domain. Map tiles are loaded from OpenFreeMap (tiles.openfreemap.org), which receives your IP address when the map is shown.

Usage counts. We also count how the site is used, for example which pages are viewed and which buttons are clicked on the way to an account or a plan. For this we store only daily totals in our database: event, the button or plan involved, page, language, country, device class (narrow or wide screen) and the kind of source (direct, search engine, the domain of another website, or a campaign link with its utm values). We set no cookie for this, store nothing on your device, give you no ID and store neither your IP address nor details of your browser. To limit abuse, the IP address is held only in the working memory of the server instance that answers the request, for a rate limit of one minute. Each further counting request to that instance removes all entries older than a minute; if no further request arrives, the entry stays in that memory until the instance is shut down. The IP address is never written to a database or log. The counts cannot be traced to a person. Legal basis Art. 6 (1) (f) GDPR, our interest in improving the site. If your browser sends Do Not Track or Global Privacy Control, nothing is counted.

Settings stored in your browser. So that the site remembers your choices, it keeps a few values in your browser's local storage and session storage: the trade you picked (hr_trade, hr_trade_own); your role (hr_role), but only if you choose it yourself: by picking a role under “Not a supplier?” on the home page, with the button “Make this my view” on a role page, in the role or trade field of a contact form or company profile, or through a link that says it saves your view (visiting a role page alone stores nothing); which hints you have already seen or closed (hr_role_hint_closed, hr_supplier_hinweis); the page to return to after signing in (hr_after); the plan you chose with a plan button before signing in, with the time (hr_plan_go), so that the payment page opens only in the browser where you chose the plan; this value counts for at most two hours and is deleted once used or, if it is older, the next time you open a page of this site that shows plans; the territory you set while signed in, stored together with your email address (hr_territory); for the current visit only, whether a demo can be requested from your country (hr_demo_ok) and whether you chose “Not now” at the territory choice after signing in (hr_terr_skip), so that the territory choice is not shown again during this visit; and, if you started to claim a supplier or company profile, the access token of that profile (hr_supplier_t, hr_company_t), so that you can reopen it from this browser. These values stay on your device and are not used for tracking; only the profile token is sent to us, when you reopen your profile with it. You can delete the values at any time in your browser settings; the button “Forget this view” or ?role=none in the address deletes the stored role. Legal basis § 25 (2) no. 2 TDDDG (storage you asked for) and Art. 6 (1) (f) GDPR.

3. Early access and enquiries

When you request access or send an enquiry, we store your email, company, trade, note, the page you came from, a hashed form of your IP address and your browser type, in order to reply and prepare your access (Art. 6 (1) (b) and (f) GDPR). Storage: Supabase, EU region (Frankfurt).

For a demo request we also store your name, the markets you name, the days or times that suit you if you enter them, the country of your connection and the language of the page, in order to arrange the demo (Art. 6 (1) (b) GDPR). Storage as above.

4. Accounts

For each seat holder we store the email address, role, organisation, plan, credit balance, opened files, watch list and the dates of these actions, to provide the contract (Art. 6 (1) (b) GDPR). When you create an account we also store your name, your company if you give it, and the time you accepted the terms. Sign-in works with a one-time link that we send to your email address and that expires after 15 minutes; we store only a hashed form of it. After sign-in we set a session cookie (hr_session, 30 days) that is technically necessary (§ 25 (2) TDDDG). To protect the data against bulk extraction we count file and name views per account and day.

4a. Newsletter and weekly emails

If you subscribe to The Radar Weekly, we store your email address, the time of subscription and confirmation, the consent text, the page you came from and a hashed form of your IP address. We send the newsletter only after you confirm the link in our confirmation email (double opt-in), legal basis your consent (Art. 6 (1) (a) GDPR). Account holders receive a weekly email about the projects, companies and cities they watch, as part of the service (Art. 6 (1) (b) GDPR). Every email contains a link to unsubscribe with one click; you can also write to [email protected]. We keep the address with a note of the unsubscription for as long as we need to prove consent, at most three years. Emails are sent through Resend.

4b. AI access (MCP connector)

If you connect Hospitality Radar to an AI assistant such as Claude, ChatGPT or Grok, the assistant sends tool calls to our server, for example a city, a project type or a project reference, and receives our answer. We do not receive your conversation with the assistant, only these calls, and we do not keep a record of what was searched. We count searches per account for the daily limit and delete these counts after one day, and we store when an access key was last used. Files you open and watch list entries you set through the assistant are stored in your account as described in section 4. Access keys are created in your account, or when you connect with OAuth, in which case the key is labelled with the name of the assistant. We store only a hashed form of each key, and you can revoke a key at any time under "AI access" in your account. How the assistant provider handles your conversation is governed by that provider's terms and privacy policy. Legal basis Art. 6 (1) (b) GDPR.

5. Payments

Payments are processed by Stripe Payments Europe Ltd., Dublin. Stripe receives name, billing address, email, VAT ID and payment details and acts as an independent controller for payment processing. We receive the payment status, invoice data and a customer reference. Invoices are kept for the statutory retention periods (Art. 6 (1) (c) GDPR).

6. Referral links

If you arrive through a partner link, we store the partner code in a first-party cookie (hr_ref, 90 days) and, if you buy a plan, assign your account to that partner to calculate commission. The partner sees your company name and plan, not your usage. Legal basis Art. 6 (1) (f) GDPR. If you arrive through one of our ads or another campaign link, the campaign name travels in the address of the pages you open during that visit; we set no cookie for this and store nothing on your device. If you create an account during that visit, we store the campaign name with your account to see which campaign led to a registration or a purchase, and we do not share it or use it for profiling. Legal basis Art. 6 (1) (f) GDPR.

7. Data in files

Files contain information about companies and hotel projects from public sources. For companies they include business contact details (registered address, switchboard, general email such as info@, website), the names and functions of managing directors or board members as published in the company's legal notice or in the commercial register, and the names and roles of other people only where the company itself publishes them on its own website or in its own press releases. Each entry carries its source and the date we saw it. Files do not contain private addresses, private email addresses, direct dials or mobile numbers, and we do not use social networks or contact databases as a source for people in files.

Purpose and legal basis: Radar users are companies supplying hotel projects. They need to know who is responsible for a project at the developer, operator, architect or contractor. This is our legitimate interest and theirs (Art. 6(1)(f) GDPR). We show only what the company has made public about its own staff in their business role.

Information under Art. 14 GDPR: we did not collect these details from you. This section is our information to you: the source is the page named in the file, the categories are name, role and employer, recipients are Radar users, and we keep an entry as long as the source shows it and at most 24 months after we last saw it there. You can object at any time (Art. 21 GDPR), without giving reasons, through https://hospitalityradar.io/profile/#melden or by writing to [email protected]. We then remove your name and keep it from coming back. You also have the rights set out in section 9.

7a. Supplier profiles

We list companies that supplied hotel projects, each entry with a public source (press, trade media, the company's own reference pages). This concerns companies, not people. To invite a company to check its entries, we email one business address per company: the business address of a person in a management, sales or projects role, and only exceptionally a shared address published by the company. We take the person's name and role from the company's legal notice or website, a company register or press releases. We found the address on the company's website or through a business contact database (Hunter, Hunter Web Services Inc.), or derived it from the address format the company itself uses, and checked that it is deliverable (MillionVerifier). If you ask, we tell you the specific source of your name and address. Legal basis: our legitimate interest in accurate supplier data and in offering our service to businesses (Art. 6(1)(f) GDPR / UK GDPR). We keep the address until you unsubscribe or for at most 12 months after our last email. Every email has a link to stop further emails, and a short reply works too. We do not track whether you open an email.

On the profile page, the company can name contact persons. A person is stored only when the company ticks the consent box, and shown only after that person confirms by email themselves (Art. 6(1)(a)). Without confirmation we delete the entry after 30 days. Consent can be withdrawn at any time through the same link, without any effect on the company profile. Radar users who can see a confirmed contact are companies supplying hotel projects, which can include competitors.

When a company has completed its profile, a member of our team looks at the company's entries, its profile details and whether it already has a Radar account or plan. A person, not an automated system, then decides whether we offer the company a time-limited Radar access, and we keep that decision with its reason. We may then email the same business address once to thank the company, and, if we offered access, once more shortly before it ends. Access ends by itself, needs no payment details, and the account returns to the free Explorer plan. Legal basis: our legitimate interest in offering our service to businesses (Art. 6(1)(f)). We record which links were clicked, whether the profile was opened and completed, which project files were opened during the access and whether a plan was chosen, to see which offers are useful.

Reference lists uploaded by a company are used under the permission given on upload. Please do not include names of people. In the UK you can also complain to the Information Commissioner's Office (ICO).

7b. Company profiles

Companies named in project files (developers, owners, operators, hotel groups, architects, interior designers, contractors, consultants, purchasing agents) can confirm a profile. To invite a company, we email one business address per company, normally the business address of a person in a management or business development role, with the same sources, checks and rights as described in 7a. A company can confirm or correct its projects, describe itself and set how suppliers should contact it. Corrections and objections never require a profile: anyone can report wrong details or object to being named at https://hospitalityradar.io/profile/#melden.

Contact persons in a profile: a company can name contact persons. A person who adds themselves while signed in with a company address agrees directly by ticking the box. Anyone else is shown only after confirming by email themselves. The legal basis is consent (Art. 6(1)(a) GDPR), which can be withdrawn at any time through the same link or by writing to us, without any effect on the company profile. We store the wording the person agreed to and the time. Radar users who see a confirmed contact are companies supplying hotel projects, which can include competitors.

A company can also start its profile from its own company file, without an invitation: we bind the profile to the account when the signed-in email address belongs to the company's own domain as we know it from our research. Otherwise nothing is bound and we check the request by hand.

Changes to a profile appear in the files after our check. We record when a profile link was opened, saved and confirmed. For links in our emails we also store whether a request came from the network of a known email security service, so that automatic link checks are not counted as visits; we store the network number only, not the IP address. If the company chooses, we email the signed-in address when the company is named in a new project. This can be switched off on the profile page.

Enquiries through the Radar: a Radar user can send an enquiry to a verified company about the topics the company has chosen. We forward it to the company's enquiry address. The company sees the sender's name, company and email address; the sender does not see the company's address. We keep a record of each forwarded enquiry and of reports of misuse.

Studio access: for studio accounts we record which projects were viewed in which month, to apply the monthly limit, and we show an account code derived from the account in every view and file.

8. Processors

ProviderPurposeLocation
Cloudflare, Inc.Hosting, protectionEU/US, EU Standard Contractual Clauses and Data Privacy Framework
Supabase, Inc.DatabaseEU (Frankfurt)
Stripe Payments Europe Ltd.Payments, invoicesEU/US
IONOS SE, MontabaurEmail ([email protected])EU (Germany)
Plus Five Five, Inc. (Resend)Sending emails (sign-in links, newsletter)US, EU Standard Contractual Clauses
MillionVerifierChecking that business email addresses are deliverableEU/US

9. Your rights

You have the right to access, rectification, erasure, restriction, data portability and to object to processing based on legitimate interests, and the right to lodge a complaint with a supervisory authority, for example the State Commissioner for Data Protection and Freedom of Information Baden-Württemberg (LfDI BW).

10. Retention

Account data is deleted three months after the end of the contract, unless statutory retention applies. Enquiries without a contract are deleted after twelve months.