From check-in to a guest you can still reach.

Booking.com blocks outside links in guest messages by default, so you need to whitelist your domain once:

Extranet → Property → Messaging Preferences → Messaging Security → Add a link.

Whitelist the whole domain — dropsphere.dropby.biz — not a shortened or redirected link. Booking.com blocks link shorteners outright, so a service like bit.ly will get flagged even after you whitelist it.

Your DropSphere link isn't a booking or payment link — it's a check-in and guest-guide page, which both platforms allow once whitelisted. It replaces a PDF or a wall of texts, not the booking itself.

No. It's a link that opens straight in their phone's browser — no app, no account, nothing to install.

Yes — that's the core of what DropSphere solves. When a guest checks in through your page, their name, address, and email come to you directly, not just through a platform inbox that gets masked after checkout.

Guest submissions are stored per-property and are only accessible to you, not shared across hosts or with any third party. If you have specific compliance requirements for your business, we're happy to talk through the details directly.

Either works. You choose open or password-protected when setting up your listing, and the QR code and instructions your guest receives adjust automatically.

Not yet — that's coming. Right now the guide is text and structured info (WiFi, house rules, local tips), and photo support is on our list to build next.

Not yet, and this is one of the first things we're improving. Right now, each guide is set up once when you onboard — if something changes (a new house rule, a WiFi password update), let us know and we'll rebuild the guide for you.

This is an interim step, not the long-term design — self-service editing is on our roadmap.

No — nothing in the guide or check-in flow is hardcoded to one country. It works the same whether your property is in Germany, elsewhere in DACH, or the Netherlands.