Privacy Policy

What Havrell collects, why, and how guest information stays protected.

This deployment has not yet been configured with Havrell's registered legal details. The wording below is not the published version for a live sale.

1. Who is responsible

Havrell is the controller of personal data processed for Havrell accounts, billing and the Havrell website.

For guest information that a host collects or uses through Havrell (their guide, bookings, messages, registration details, the arrival check, photos and guest purchases they sell), the host is the controller and Havrell processes that information on the host's behalf and on their instructions. Guests can contact their host, or Havrell, who will pass the request on.

Havrell is the controller for what Havrell sells to guests directly, such as eSIMs, and for keeping the service secure.

2. Customer information we collect

  • Account details: name, email address, organisation name and role.
  • Order details: package chosen, amount, tax status, accepted policy versions and acceptance timestamps.
  • Property information you submit: addresses, arrival instructions, photos, videos and operational details.
  • Support messages you send us.
  • Commercial declarations and guest service terms: the adult declaration, wording and version accepted, time, Stay or account reference and supplier terms snapshot. These declarations do not collect a birth date or identity document and are separate from marketing permission.
  • Service safety and privacy reports you submit, and the staff decisions recorded while handling them. Avoid including access codes, identity documents or unnecessary sensitive information.

3. Payment information

Payments are processed by Stripe. Havrell never receives or stores your full card number. Havrell stores the order reference, amount, status and Stripe identifiers needed for reconciliation and receipts.

4. Guest information

  • A guest guide contains only what the customer supplies.
  • Secure guest Stay links use hashed tokens; physical access details are released only on a deliberate request and expire after the stay.
  • Havrell does not require guests to create an account.
  • Guests only provide identity details where their host asks for them, as described in section 4b.
  • Where usage measurement is enabled, it is first-party, aggregated and never stores access codes, passwords, raw links or full IP addresses.

4a. What stays on a guest's own device

  • Offline access: when a guest keeps a guide available offline, a copy of the public guide content is stored by their own browser on their own device. Door codes, lockbox codes, key locations and Wi-Fi passwords are removed before anything is stored, and the copy is cleared when the guide is opened again online after the stay.
  • Wallet passes: a stay pass added to Apple Wallet or Google Wallet contains only the property name, the stay dates and the link to the guide. It never contains an access code or a password, and a pass is refused if any field looks like one.
  • Read aloud: the optional voice reader uses the speech engine already built into the guest's phone. No audio is recorded, and sensitive lines are replaced before any text is spoken.
  • None of these features send additional personal data to Havrell.

4b. Guest information your host asks for

Hosts can turn on the following. Havrell processes this information for the host, who decides whether to use it.

  • Guest registration: where the law of the property's country requires hosts to register guests with the authorities, guests may be asked for their name, date and place of birth, nationality and identity-document type and number. Havrell prepares the file; the host submits it. The details are kept for the period the host sets, which the law of some countries requires to be several years, and are then deleted.
  • Arrival check: where the host turns it on and the country's rule allows it, the guest takes a live picture of their face and identity document so that a person can compare them once. There is no automatic face matching. The picture is deleted as soon as the host decides, and after 24 hours at the latest. Where the law forbids copies, a code sent by e-mail is used instead.
  • Arrival and condition photos: photos a guest adds through their Stay link within 24 hours of check-in, and photos taken by the host's team, are kept with the time they were stored and a fingerprint of the file, so the host can rely on them in a damage claim. Photos are kept while the host keeps the stay's records.
  • Messages: messages between guests and the host, including those sent through WhatsApp, Telegram, Viber, e-mail or a booking platform, are stored so the host's team can reply. Messages may be translated automatically.
  • Phone line: when a guest calls a Havrell phone line, the call is answered automatically. The caller's number is stored only in a hashed form, with the questions and answers.
  • Team location: the host's own workers can choose to share their location while working; it is kept for 12 hours at most and stops when they stop sharing.

5. Why we process information

  • To create, publish and host the guide you ordered, and to provide the features you turn on (legal basis: performing our contract with you).
  • To take payment and meet accounting and tax obligations (legal basis: legal obligation).
  • To provide support and communicate about your order (legal basis: contract).
  • To keep the service secure and to prevent abuse and fraud (legal basis: our legitimate interest in a safe service).
  • To process guest information for hosts (legal basis: the host's own basis, such as their contract with the guest or a legal obligation to register guests).
  • To measure page visits and feature use with first-party product analytics on our website and account pages (legal basis: our legitimate interest in improving the service). This measurement starts by default, but browser Do Not Track or Global Privacy Control signals and previously saved refusals are respected. We do not collect form text, access codes, full URLs or screen recordings for this purpose.
  • To record how you use Havrell's own pages, only if you agree, so we can find what is confusing or broken (legal basis: your consent). See section 5a.
  • To find and fix errors in Havrell's pages and servers, from cleaned error reports (legal basis: our legitimate interest in a service that works). See section 5b.
  • To send marketing, only where you have agreed (legal basis: consent, which you can withdraw at any time).

5a. Session recordings (only if you agree)

On Havrell's own pages (the website, the guide builder, sign-in and the host workspace) and on the host screens of the Havrell app we may ask once whether we can record how you use them. Nothing is recorded unless you say yes, and saying no changes nothing else.

A recording shows the page layout, where you click and how you scroll. Everything you type and all text on screen is replaced before it leaves your browser, uploaded photos and videos are replaced by empty boxes, and page addresses are shortened to the page itself, without codes from links or search terms.

  • Never recorded: guest guides, Stay links, booking pages, guest messages, stays, guest requests, registration and arrival-check pages, damage claims, Havrell's admin pages, and pages opened from a private link.
  • Recordings are sent through Havrell's own server to PostHog, on its servers in the EU. Your IP address, cookies and browser details are not passed on, and a recording is not linked to your name, email address or account.
  • In the Havrell app, the same question can appear on the host screens (Today, Tasks, Team and Account). Guest, Stay and cleaner screens, stays, conversations and task details are never recorded. The app sends recordings directly to PostHog's EU servers, which are set to discard IP addresses; the recording uses a new anonymous id each time the app starts and is not linked to your account. You can turn it off in the app's Account screen.
  • Your browser's Do Not Track or Global Privacy Control signal, or a refusal of analytics, turns recordings off.
  • Recordings are used only to improve Havrell, are kept for 30 days and are then deleted.
  • You can withdraw your consent at any time below, or in the account menu of your workspace. Recording stops at once; anything captured in the last few seconds may still arrive.

5b. Error reports

When something breaks on a Havrell page or on our servers, a short error report is sent so we can fix it. It says what kind of error it was, where in Havrell's code it happened, on which page (with codes and ids removed from the address), the browser's name and main version, the system, whether it was a phone, tablet or computer, and when.

  • On guest guides, Stay links, booking pages and other private links, on pages about individual guests, and on Havrell's admin and legal pages, the error's own message is never sent: only its kind and where it happened in our code.
  • On other pages the message is cleaned first: e-mail addresses, phone numbers, numbers, codes, page addresses and anything in quotes are removed.
  • Reports are sent through Havrell's own server to PostHog, on its servers in the EU. Your IP address, cookies and the full description of your browser are not passed on, and a report is not linked to your name, e-mail address or account. If you agreed to session recordings (section 5a), the report is linked to that recording.
  • If your browser sends Do Not Track or Global Privacy Control, or you refused analytics, Havrell only counts that an error happened on that kind of page, and nothing is sent to PostHog.
  • Error reports are used only to fix Havrell and are deleted after the period in section 7.

6. Who we share information with

Each provider receives only what it needs for its task. Havrell does not sell personal data and does not run advertising networks.

  • Stripe, for payments, payouts and receipts.
  • PostHog (EU servers), for session recordings, only if you agree to them (section 5a), and for cleaned error reports (section 5b).
  • Our hosting, database and file-storage providers (Vercel and Supabase), for running the service.
  • Our e-mail provider (Resend), for transactional messages.
  • Our AI model provider, reached through an AI gateway, to draft suggestions, translations and replies and to sort uploaded photos. Content is sent only for the request being made.
  • Twilio, for the phone line and text messages, when a host turns them on.
  • WhatsApp (Meta), Telegram and Viber, for guest messages, when a host connects them.
  • Hostaway and the booking platforms behind it, when a host connects their account.
  • Seam, for smart locks and thermostats, when a host connects them.
  • Our eSIM partner, to deliver mobile data a guest buys.
  • Apple and Google, when a guest adds a Wallet pass.
  • Local partners, such as luggage storage or tour providers, when a guest books their service.
  • Authorities, where legally required. Registration files are submitted by the host, not by Havrell.

7. How long we keep information

  • Account and guide content: while the account is active.
  • Order and payment records: as long as required for accounting and tax law.
  • Guest stay links: expire after the stay; records are removed on a rolling basis.
  • Arrival-check pictures: until the host decides, and 24 hours at most.
  • Guest registration details: for the period the host sets, at least as long as the property's country requires.
  • Worker location: 12 hours at most.
  • Product analytics: for the retention period set on the account's plan.
  • Session recordings: 30 days.
  • Error reports: 1 month.

8. Your rights

Depending on where you live, you may have rights to access, correct, delete, restrict or port your personal data, and to object to certain processing. Where we rely on consent, you can withdraw it at any time. Contact us and we will respond within the period required by applicable law.

You also have the right to complain to a data protection supervisory authority, in particular in the country where you live or work.

9. Security

  • Data is separated per organisation and enforced in the database, not only in the interface.
  • Physical access details are stored apart from public guide content.
  • Access to production data is limited to the people who need it.
  • Physical access details are never written to a guest's device, a wallet pass or a spoken summary.
  • Connections to booking calendars and other systems use credentials held server-side; they are never exposed to a browser.

9a. What stays in your own browser

  • A guide you build at /start before creating an account is stored only in your own browser on that device. Nothing is sent to Havrell until you create an account and import it. Clearing your browser data deletes it.
  • Your language choice and a refusal of analytics are remembered in your browser.
  • Your answer about session recordings is remembered in your browser for up to 180 days. While a recording runs, an anonymous recording identifier is kept in that browser tab only.

10. International transfers

Our providers may process data outside your country. Where that happens, we rely on the safeguards offered by those providers under applicable data protection law.

11. Changes to this policy

We may update this policy. The version and effective date are shown at the top of this page, and each order records the privacy version accepted at the time of purchase.