Sign inRegister
person
Specification 13.3 & 13.4 Privacy, consent architecture & checkout acceptance

Consent & legal acceptance patterns

Standardised consent components engineered for strict compliance, equal visual weighting between acceptance and refusal, and frictionless legal verification across booking workflows.

13.3 Cookie consent dialogs

Dual presentation demonstrating the floating contextual banner alongside the expanded modal view.

Floating view (Docked bottom-left) Width: 440px
cookie

We use cookies that keep the site working and, if you agree, cookies that show us how it is used.

gavel Regulatory compliance note

Equal visual treatment between 'Accept all' and 'Reject non-essential' prevents asymmetric nudging under GDPR and ePrivacy requirements.

Preferences modal (Open state) Width: 560px

Cookie preferences

close

Choose which cookies you allow us to use. You can update these settings at any time.

Necessary Required

Essential for site security, user authentication, and escrow session persistence.

lock
Analytics

Helps us measure site traffic, popular resort search routes, and feature usability.

Marketing

Enables relevant timeshare listings and resort partnership notifications.

13.4 Acceptance and consent patterns

Component patterns deployed inside booking engines, checkout sessions, and owner onboarding funnels.

Pattern 01 Guest Checkout

Traveler booking acceptance

Used on the final step before payment escrow allocation.

lock Escrow held Explicit opt-in required
Pattern 02 Owner Listing Flow

Host & owner acceptance

Precedes title confirmation, deed submission, and resort week listing.

Last updated March 3, 2027
verified_user Deed verified Binding contract
Pattern 03 Re-consent

Agreement update notice

Displayed on user portal entry whenever contract clauses or payout schedules are revised.

We updated the Host and Owner Agreement.

Read what changed
Required to proceed

State management & persistence

All consent actions invoke cryptographically keyed events with UTC timestamp, contract SHA-256 fingerprint, and anonymised user session IDs forwarded to the ETS audit ledger.