Trust & safety.
Signed contracts, audit-trailed bookings, and transparent payments. Honest about what v1 does and doesn't do yet.
Account security
Ory Kratos handles authentication. Sessions are cross-subdomain cookie-based on web; mobile uses secure device-storage tokens. PII is access-restricted. Not SOC 2 certified yet — small team, launch posture.
Signed contracts on every booking
Every booking is governed by a written agreement. Legal-name capture, ESIGN/UETA consent, per-signature timestamps + IPs, and a watermark anchor (contract UUID + execution timestamp) on every page of the final PDF. See how signing works →
Direct payments, no escrow
Hosts provide payment instructions and guests pay hosts directly. We never hold rent, deposits, or security deposits, which keeps the flow transparent and contract-led. Payment tracking records what each side marks sent or received, but it is not a platform guarantee.
Guest identity verification
Guests can opt into ID verification. Photo IDs are encrypted, access-restricted, and retained when needed for signed-contract records, disputes, safety, fraud prevention, or legal obligations. Disclosed in our Privacy Policy.
Dispute handling
We don't adjudicate host-guest disputes — the signed contract governs. For platform-level issues (account, bugs, abuse), email support@bookjerseyshore.com — small team, direct founder access during launch. Our Terms and Arbitration Agreement cover formal disputes with the platform.
Every signed contract carries a full audit trail.
Visible on the in-app audit-trail screen for every signed contract in your account. That's what we mean by transparency.