Security & Reservation Information
What to Share Before Check-in, on Arrival, and During the Stay
Direct answer
Guest information is easier to use when it is divided into four stages: before check-in, arrival day, during the stay, and before checkout. Lead with only the next action at each stage. Exact addresses, Wi-Fi credentials, and entry codes require real access controls and should appear only after booking verification and the host's configured release time.
Create a Free Guest Guide with stayV HostKey takeaways
- Divide information into four stages from booking to checkout.
- Show the immediate action first at each stage.
- Protect addresses, Wi-Fi credentials, and entry codes with access checks, not search directives.
What should a host share before check-in?
After booking, confirm the property, stay dates, approximate area, check-in and checkout times, public guide link, and contact expectations. Give enough context for travel planning without including a live entry credential.
- Property and stay-date confirmation
- Approximate area and transport preparation
- Check-in time and luggage policy
- Public property-guide link
What should appear first on arrival day?
Prioritize a copyable address, the correct building entrance, the check-in sequence, and a help route. After booking verification and the host's release condition, an exact location can appear. Entry codes may require a shorter, check-in-specific window.
What information matters during the stay?
Separate Wi-Fi, heating and cooling, hot water, laundry, waste, parking, and quiet hours into facility-specific answers. Use the actual appliance model and control photo, and publish only safety guidance that the manufacturer or host has verified.
What should be repeated before checkout?
Send a short checklist for checkout time, keys or cards, waste, used dishes, heating or cooling, and door locking. Do not automatically add cleaning demands, penalties, or threats that the property does not actually require.
How to apply this in stayV Host
stayV separates public L0, detailed L1, and check-in-only L2 information. The actual scope depends on the active plan and the property's booking-verification settings.
A Free guide password does not verify a booking and must not be used to reveal entry codes. Follow the current protected-field and validity policy for booked-guest values.
Frequently asked questions
Should every check-in detail be sent immediately after booking?
The overview and contact rules can be sent early, but a live entry code has a different risk. Release sensitive details only after the required booking check and close to the time they are needed.
When should an exact property address be shown?
The right time depends on the property and local requirements. A practical approach is to keep the public location approximate and reveal the exact location after booking verification at the host's configured pre-arrival time.
Is a noindex page safe for private guest details?
No. Noindex is a search directive, not an access check. Sensitive values must be returned only after server-side booking, password, validity, and release-time verification.