Reserve RequestVault Security
Reserve RequestVault is built for booking deposits and reservation holds: authenticated sender access, signed client links, private payment details, reminder controls, and reservation-history tracking that fits booking workflows instead of claims review.
1. Reservation-link access
Public reservation pages are accessed through unique links tied to a specific reservation request. Clients do not need to create an account, and sender-side reservation management requires an authenticated RequestVault session.
Reserve dashboards stay inside the reservation workflow, so public booking pages and internal team tools are not exposed as a shared general-access portal.
2. Private payment and submission handling
Reservation details, client contact fields, and deposit-related activity are kept inside managed application storage and protected routes instead of being spread across invoice threads, attachments, and manual notes.
The goal is to let teams confirm bookings and review reservation history without turning sensitive customer and payment-adjacent details into inbox clutter.
3. Authenticated sender access
Reservation builders, queues, follow-up actions, and internal links require an authenticated RequestVault account. That keeps sender-side booking controls separate from the public page the client opens to reserve the date or slot.
4. Reminder controls and SMS consent
Reserve teams can send email or SMS follow-up, but reminder activity is tied to sender-side controls and consent checkpoints. Suppressed or blocked numbers should not continue receiving booking reminders until consent is documented and messaging is allowed again.
5. Reservation history and audit trail
RequestVault records key reservation events such as request creation, page views, payment completion, reminder actions, cancellations, and follow-up status so teams can see what happened without reconstructing the timeline from scattered conversations.
6. Hold expiration and lifecycle controls
Reservation requests can expire, be canceled, or move into confirmed states based on the workflow. That lets teams manage date holds deliberately instead of leaving stale booking links open indefinitely.
7. Current limits
RequestVault is designed to reduce risk and make booking workflows more controlled, but no online system can guarantee perfect security or replace your own legal, accounting, retention, or payment-handling obligations.
If your reservation workflow needs additional controls or a documented fit review, contact RequestVault before using the product for that use case.
Last updated May 30, 2026