Passwordless email codes
Short-lived one-time codes, verification checks, throttling, replay prevention, and bot-defense controls.
Security and privacy
Designed around least access.
Travel documents are sensitive. Travel Pro separates ownership, trip membership, resource visibility, and delivery recipients so convenience does not silently widen access.
Hashed and expiring
Traveler claim tokens are stored as hashes, expire in seven days, are single use, and require the exact invited email.
Role and membership checks
Agent and traveler contexts are distinct. Shared trips do not imply access to every file inside them.
No authenticated page caching
The service worker avoids portals, documents, app screens, and API requests. Sensitive HTML is never used as an offline fallback.
Safer staging delivery
Staging can redirect every outgoing message to a controlled inbox while preserving intended-recipient records for testing.
Auditable actions
Claim, document, trip, reminder, subscription, and delivery actions remain traceable for support and incident review.
Responsible disclosure
If you believe you found a security issue, email security@travel.sandl.pro. Do not include live traveler documents or credentials in the initial report.