HRS Vault is the enterprise trust layer built into the HRS platform. It protects travelers' identity, passport data, and personal information across the full booking ecosystem by intercepting PII at the platform boundary, tokenizing it, and passing only tokens and relay identities downstream. It is part of the platform, not an add-on product.

No. Vault Standard is part of the HRS platform for every customer. Vault Pro, where you host the vault in your own infrastructure with your own encryption keys, is available for organizations with sovereignty requirements. Your HRS account team can walk you through which Vault provisions apply to your environment.

Tokenized booking references and HRS relay identities: a relay email address and an HRS hotline number that work for every operational purpose. Your employees' real names, contact details, and passport data stay encrypted in the Vault.

Only if they receive real data — and with Vault they never do. Personal data that was tokenized and masked before it reached a downstream system cannot enter any training dataset. There is nothing to train on.

No. Vault complements your security model. It makes the travel data layer transparent, governable, and auditable, so your security, legal, and Works Council stakeholders can sign off on the platform.