A small service with as little data as possible.

Last updated 31 August 2026

Who is responsible for the data?

AnotherPillow is operated by World Wide Wood AB in Stockholm. Questions and personal data requests should be sent to filip@claridad.io.

Hotel accounts

For early-access hotel accounts, we store a verified work email address and stable account ID, hotel name, city, room count, website, booking link, currency, page status, requested add-ons, uploaded hotel images and facts approved by the hotel. AnotherPillow email access does not require a social login.

Hotel images and approved information

Uploaded images are stored in protected object storage and served through AnotherPillow. The hotel decides what is public and can remove images or approved answers in its dashboard. The free plan does not use this material to train a general AI model.

Public Hotel Fjällro demo

The fictional Hotel Fjällro flow is a working database demo, not a live hotel. It accepts only restricted example details: a name beginning with “Test Guest”, an example.com, example.org or example.net email address, and the fixed demo phone number. It stores those example details together with dates, guests, room-type ID, arrival window, total, booking reference and booking, payment and prepared-email status. The public hotel view hides the example name, email and phone. Test records are retained for development and may be deleted periodically.

Payments and email

The demo does not collect real card details, move money or send external email. It stores only a simulated payment status and metadata for prepared confirmation jobs. In a production installation, raw card data must go directly to the hotel’s payment provider through hosted fields; AnotherPillow would store only the references and status required to operate the booking.

Live guest data is not active yet

No real hotel may use the public test flow for guest data. Before a live booking engine can activate, World Wide Wood AB and the hotel must agree the controller and processor roles, data-processing terms, subprocessors, retention, deletion, backup and incident procedures, then test the complete booking, payment, cancellation and delivery flow.

Account history

We store a limited audit history of created hotels, settings changes, add-on requests and publication status. It is used to prevent misuse and investigate account or support issues.

Customer communication

AnotherPillow may prepare standard service messages to the hotel account owner. In the current development environment, external delivery is not automatic. The demo booking database stores recipient kind, recipient address, template name, status and time for prepared confirmation jobs.

Why we process data

Hotel settings, images and approved content are used to create and manage the requested booking page, prevent misuse, provide support and follow up requested add-ons. The legal basis is delivery of the requested service and our legitimate interest in protecting and improving it.

Subprocessors and international access

The development service uses infrastructure and sign-in providers required for operation and secure account identity. A future live checkout also uses the hotel’s selected payment provider. Hotel data is not sold. A complete subprocessor list and responsibility split must be provided and agreed before production activation.

Retention and rights

Account data is stored while the hotel uses AnotherPillow and then for a limited period where security, accounting or legal claims require it. You may request access, correction, export or deletion and may complain to your local data protection authority.