Sidequest
For the person this gets forwarded to

Trust & Security

Hospitality was discreet about its guests long before anybody wrote a regulation about it. This page is that instinct, written down for your security reviewer. It is deliberately unadorned.


We do not hold SOC 2, and we do not claim it.

There is no badge row on this page and no certification logo anywhere on this site, because we have earned none. What follows is a description of how the systems are actually built and operated. If we pursue a certification later, it will appear here, dated, and not before.

The specifics

What happens to a guest’s information.

  • Guest data we hold

    A name, a contact detail, and the details of a booking — what was reserved, where, when, and what it cost. That is what running a reservation requires and it is where we stop. We do not build guest profiles, we do not sell or share data with advertisers, and we do not enrich it from third-party sources. Your guest list does not become an asset of ours.
  • Card data

    Card details never reach our servers and are never written to our logs. Payment is taken through Stripe’s own payment form, hosted by Stripe inside the page. The card number is entered directly into Stripe’s iframe and we receive only a token and a result. Card numbers are also never spoken to the voice agent — a payment goes out as a link your guest opens themselves.
  • Access

    Every person with access is scoped to the properties and markets they are responsible for. Somebody working one of your markets cannot see another market’s bookings or guests. Scope is enforced at the data layer rather than by hiding buttons in an interface, so it holds wherever the data is reached from.
  • Retention

    Booking records are kept for as long as your property needs them for its own operational and accounting purposes, and then removed. You can ask us to remove a specific guest’s records, and we will.
  • AI disclosure

    Our published position: the voice agent discloses that it is an AI by default, in the first few seconds of a call, without being asked. We treat this as a guest-experience decision rather than a legal one. Because the service is managed, your property can be given different behaviour — but the default is disclosure, and it is stated here rather than buried in a privacy policy.
  • Availability and what happens when it isn’t

    If our systems are unavailable, calls fall through to the human path your property already has. That is the position you are in today, so a failure returns you to the status quo rather than to something worse. Nothing about our design puts your guest in a dead end when we are down.
  • Recovery

    Backups are taken continuously, and a restore is rehearsed rather than assumed. We would rather be asked to demonstrate that than be believed about it.

If your security team has a questionnaire, send it. We would rather answer it in writing in week one than have you discover a blocker in week four.

How we build

Practice, not marketing.

  • 01

    Tests before codeBehaviour is specified as a failing test first, and the test is written by someone other than the person who makes it pass. It is a slower way to build and a much faster way to be correct.

  • 02

    Nothing merges unreviewedEvery change is reviewed, and continuous integration has to be green before it can land. There is no path to production that skips this.

  • 03

    The double-booking guarantee is enforced, not intendedTwo of your guests cannot be sold the same bed. That property is held by the system under concurrent load, and it is tested as a guarantee rather than trusted as a convention.

  • 04

    Change controlDeployments are versioned and reversible. We know what changed, when, and who approved it, and we can go back.

  • 05

    Least privilegeSystems and people get the narrowest access that lets them do the job. That includes us.

What we won’t say

The absences on this page are deliberate.

There are no client logos here, no testimonials, no case studies, and no count of properties served. We are early, and every one of those would either be untrue or would name somebody who has not agreed to be named.

If you become a client, the same rule protects you. We would rather be the kind of company that is careful about this now, when it costs us something, than the kind that becomes careful later, after it has cost a client something.


The fastest way to understand this is to hear it.

(305) 555-0148

Call it. You'll be talking to the product.

Request a conversation