What we collect, and what we don't.

02What we collect

Two kinds of data pass through the product.

Host account data. When you sign up we store your email address and name, the properties and packets you build (house rules, itemized fees, welcome content), the reservations you enter, and your billing status. Sign-in is passwordless — we do not store passwords.

Guest data. When a host sends a packet, the guest reviews and signs it. To do that we collect the guest's name and email address, the IP addresses recorded when they open and when they sign, the drawn-signature image, and a two-event audit trail of the open and sign events. We also store a SHA-256 hash of the exact packet text the guest signed. Guests are not PreArrive account holders — their data is collected on behalf of the host who sent the packet.

Optional photo at signing. Paid hosts can require a plain camera photo before signing. This is not an ID scan and not biometric matching. We store the photo encrypted, strip EXIF location, and delete it one year after checkout by default unless the host configured a shorter window or a dispute/legal hold applies. The guest deletion path is linked from the signing-confirmation email. See the photo policy.

We also keep ordinary server logs and first-party analytics about how the marketing site and app are used. Google Analytics 4 runs only after a marketing-site visitor chooses Accept all in the cookie banner. We do not run third-party ad or tracking pixels.

Bot-challenge signals. The help-widget escalation form runs Cloudflare Turnstile to block automated abuse. Turnstile collects the visitor's IP address and a set of browser and device signals (challenge solve patterns, hardware characteristics, header values) to score whether the request looks human. We do not see those signals; Cloudflare returns only a pass/fail token. Cloudflare's processing of this data is governed by the Cloudflare Turnstile Privacy Addendum, which is incorporated into this policy by reference.

04Who else touches the data

A short list of sub-processors.

We keep the vendor list explicit and describe each processor by purpose, region note, and data category. Each of these processes data only to provide its service to us. We do not sell your data, and we do not share it with marketers, data brokers, or insurance carriers.

Core application records are stored in the Cloudflare production project with US-region durable storage where supported. Edge execution, KV, email, payment, support, OAuth, and analytics providers may process data under their own regional infrastructure and policies. PreArrive does not claim SOC 2, ISO 27001, HIPAA, or PCI certification for the product today.

06Your choices

Access, export, and deletion.

Hosts can export their data — including certificates and audit trails — from the product. If you want a copy of the data tied to your account, or you want it redacted or deleted, email [email protected] and a person will handle it. Guests whose data was collected through a host's packet can ask us, or the host who sent the packet, for access or deletion. We honor those requests subject to the retention rules above — some audit-trail metadata is kept so a deletion stays provable.

If a dispute, insurance filing, platform claim, security investigation, or legal hold is active, destructive deletion may be paused. We will explain that path and remove recoverable data once the hold lifts.

08Changes and contact

If this policy changes.

If we change this policy we will update the date at the top of this page; material changes will be communicated to active hosts by email. Questions, requests, or corrections go to [email protected].