Skip to content
Foreword.host

Privacy

What we collect, what we don't, and what to do if you want it gone.

Last updated: October 2026

The short version

  • We keep what you type to build your Books, the email you sign in with, and a billing record from Stripe. We never see your card number.
  • Your door code and Wi-Fi password appear only inside your Book, to anyone with its link. Treat the link like a key.
  • We don't sell data, run ads or use tracking cookies.
  • A short list of vendors processes data so the service runs; they're named below.
  • Ask, and we delete everything within 7 days.

What you give us

When you build a Book or subscribe, you give us four kinds of data:

  • Account info — the email you sign in and pay with, so we can reach you about your plan and your Books.
  • Property details — the address, Wi-Fi, door code, and check-in times you type into the form, so we can build your book. Printable signs you made with our earlier sign maker are handled the same way.
  • Host details — your name, phone, email, and anything you write about hosting. These appear in the book you share with guests.
  • Payment — your card is entered on Stripe's secure checkout page — we never see or store card numbers. What we keep is the billing record Stripe gives us: your email, the amounts, and references for your plan and its payments.

What we keep, and for how long

Your property details and each Book stay in our database while the Book is online; that's what keeps your guest link working. If you cancel before a Book is yours, it goes offline and we keep its content for at least 12 months, so it comes back at the same link if you return. Ask us and we'll delete any of it sooner.

The free builder keeps your draft in your browser. If you open it on your phone or go to checkout, we save a copy so you can pick it up there. Copies you don't publish are deleted within 30 days. Photos you add in the free builder are uploaded right away so your preview can show them. Ones that never make it into a published Book are deleted automatically after 90 days, or sooner if you ask.

We record basic, non-identifying usage events (for example, that a book page was opened, or how far someone got in the free builder) so we can tell whether the product is working. These carry no name, email, or address.

Vendors who process data for us

We use a small number of vendors to run the service. Each sees only what it needs to:

  • Supabase — our database. Stores your form data and generated book.
  • Vercel — hosting. Serves the site and your guest book link.
  • Google Places — receives your property address so we can find nearby restaurants and sights. We don't send your name or any host details to Google.
  • Anthropic (Claude) — sees your form contents to draft the prose. On plans with the assistant, it also receives a guest's question and your Book's text (never the door code) to answer it. We don't send payment information, and the data isn't used to train their models.
  • Stripe — payment processing for your plan. Stripe sees your card details on its own checkout page; we receive only the billing record (email, amounts, references).
  • Resend — sends transactional email, such as your book-is-ready message. It sees your email address.
  • Sentry — error monitoring. May incidentally capture technical details of a request when something breaks, so we can fix it.
  • Viator — only if you opt into the tours section. Receives the property location to return nearby tours.

These vendors operate in the EU and the United States. We don't sell data to anyone, we don't run third-party advertising pixels, and we don't share lists with marketing partners.

Cookies

We only set our own cookies, and only for three things: keeping you signed in; opening a one-time Book's private edit page from the link in your email (Books bought before October 2026); and, if you arrive through another host's referral link, remembering that link for 60 days so they get the credit if you subscribe. The referral cookie holds their code, nothing about you. The edit-page and referral cookies are HttpOnly, so scripts in your browser can't read them.

We don't use tracking cookies, advertising cookies, or fingerprinting, and there are no third-party trackers on this site.

Your keys and codes — the honest version

Your Wi-Fi password and door code are the most sensitive things you give us, so here is exactly what happens to them:

  • Where they live: in our database, readable only by our own server — no app user, script, or browser can query them directly. They're stored in usable form because your book has to display them to guests; that's the product.
  • Where they appear: only inside your book page. The link is an unguessable ID and we tell search engines not to index book pages — but by default anyone who has the link can see them. That's what lets a guest open the door at midnight without an app or a login.
  • If your code changes each stay:don't put a code in the book. Write how guests get theirs (for example, “sent by Airbnb message the day before”) and the book shows that instead.
  • During generation: your form contents (including the Wi-Fi details) are processed by Anthropic's AI to write your book, under terms that exclude training on your data. Our prompts explicitly forbid repeating credentials in the book's prose — they appear only in their dedicated cards.
  • When a guest asks the assistant: their question and the Book's text (not the door code) go to Anthropic to write the answer, under the same no-training terms. We keep the question itself, with no name or other detail about the guest, and whether the Book could answer it, so the host can see what guests ask; the answer is not stored. Questions are deleted after 12 months.
  • Your controls: treat the link like a key, and place the QR card inside the property, not on the door. Change your door code between stays (you can mark it as changing each stay, and the Book then shows how guests get theirs instead of a number), edit the Wi-Fi password anytime, take a Book offline instantly from its edit page, or ask us to delete everything — done within 7 days, confirmed in writing.

What your guests see

Your welcome book is shared by a private link. It isn't listed publicly or indexed by search engines. Anyone holding the link can open it — that's what makes it easy for guests — so treat it the way you'd treat any share link, and remember you can take a book offline at any time.

We don't ask your guests to sign in, and nothing on the book page asks them for personal details.

If you connect a booking calendar (an iCal link or Hostaway), we store each reservation's dates and, when the calendar includes it, the guest's first name. We use them to show the right stay and to greet the guest on their personal link. Disconnecting an iCal calendar deletes its reservations; otherwise they're deleted with the book, or sooner if you ask us.

How to delete your data

Write to us at hello@foreword.host from the email on your account. We'll delete your account, property details and Books within 7 days and confirm in writing. Deleting a Book takes its guest link down with it.

You can request a copy of everything we hold on you the same way, with the same 7-day turnaround.

Children

The product isn't designed for under-18 users and we don't knowingly collect data from minors. If you believe a minor has used the service, write to us the same way and we'll delete the data.

Changes to this policy

If we change anything material, we'll email everyone with an active book at least 14 days before the change takes effect. We won't apply changes retroactively.

Who we are, legally

Foreword.host is the data controller for the purposes of GDPR. For any data-protection inquiry, reach us at hello@foreword.host. You also have the right to lodge a complaint with your local data protection authority.

Questions?

Email hello@foreword.host. We usually reply within a day.