Privacy principles

Travel data deserves thoughtful handling.

Fliwise is designed to use the context needed to support corporate travel operations while reducing unnecessary exposure.

Incoming contextRequestTravellerQuoted historyPayment detail

Minimise & protectNeeded travel contextUnrelated and sensitive content reduced where appropriate

Controlled accessTenant-aware accessHuman checkpointsVisible events

01Incoming contextRequest, traveller and quoted history arrive.

02MinimiseUnrelated content is reduced where appropriate.

03ProtectSensitive travel and payment identifiers are handled carefully.

04Controlled accessTenant and permission boundaries govern access.

05Accountable actionsEvents and human checkpoints remain visible.

Careful by design. Accurate in language.

Retention, data residency, subprocessors and customer-specific privacy requirements are agreed during onboarding. This page describes design principles and does not claim an external certification.

Questions: hello@fliwise.com