Trust & security
The certificate is the artifact.
Prearrive's value is the evidentiary chain we put around your signed packet. Here's exactly what we capture, what we don't, and how a third party can verify it.
SHA-256 content hash
Every packet's text — rules, fees, welcome, exact wording — is hashed at send time. The hash is printed on the certificate. Any later edit to the packet produces a different hash, so the version the guest signed is provable.
Two-step audit trail
We capture timestamp + IP at the email click and again at the signed action. Both endpoints are in the certificate. This is the two-step record Airbnb's Resolution Center and most small-claims clerks look for.
Drawn signature, in image
The guest draws a signature with their finger or mouse. We keep the raw PNG and embed it in the certificate. Not a typed-name proxy and not an "I agree" checkbox.
No ID scans, no biometrics
We do not collect government ID, selfies, or biometric data. We collect only what's needed to make the acknowledgment legible as evidence: who clicked, who signed, what they saw, when, from what IP.
7-year retention
Certificates are kept for 7 years from sign date — long enough for the longest US statute-of-limitations window for small-claims property disputes. Hosts can export at any time; Pro gets CSV of the full audit trail.
Hosted on Cloudflare
The whole product runs on Cloudflare Workers + R2 storage. US-only data residency by default. Operator access is behind Cloudflare Access — no shared admin passwords, no SSH bastion.
The artifact, opened up
What's printed on every certificate.
- Property + guest identity — listing name, guest name, email, stay dates, source
- Each rule — quoted text exactly as the guest saw it
- Each fee — label, amount, unit, full description
- Per-item acknowledgments — never one blanket checkbox
- Drawn signature image — PNG, embedded inline
- Two timestamps + two IPs — click + signed action
- ESIGN/UETA consent line — recorded verbatim
- SHA-256 of packet text — for tamper-evidence
c5f1 d8b4 6e3a 2049 cbd0 fa6e 22e6 9c14
Re-hash the packet text yourself — same SHA-256 means the version on the certificate matches what the guest saw, byte for byte.
ESIGN + UETA compliant electronic record. Not a contract; the certificate is evidence of an acknowledgment. Not a substitute for legal counsel.
Send your next reservation through a packet.
Build one packet, send to one guest. If the next dispute pays for years of Solo, you keep the rest.