Privacy

Discretion protects what is personal.

The information that makes private travel feel personal should be handled with the same care as the flight itself.

Discretion by Design

Only what serves the trip.

Atavis asks for personal context when it helps arrange the flight, meet a requirement, reduce repetition, or protect the guest’s privacy. Information is collected with purpose, used with restraint, and handled as part of the standard behind each trip.

Why Details Matter

Personal should not become overfamiliar.

Private travel can reveal movement, timing, relationships, preferences, and household patterns. Atavis uses that context carefully, so future travel can feel better prepared without making the guest feel studied.

01

Purposeful Guest Context

Atavis asks for context when it helps arrange the flight, reduce repetition, or protect privacy. The information should have a clear use, not simply make a profile feel more complete.

02

Anticipation Without Intrusion

Remembered details should make a trip easier to prepare, not make the relationship feel overly familiar. The guest should feel understood, not observed.

03

Representative Awareness

Assistants, advisors, family offices, and household teams often hold the details that make a trip function properly. Atavis treats those relationships with the same discretion as the guest relationship.

04

Need-to-Know Coordination

Guest information is shared according to role, purpose, and trip requirement. The right parties should receive what they need, without widening access unnecessarily.

Information Handling

Restraint guides the process.

Guest information is handled according to its purpose: what is needed to arrange the flight, what improves continuity, what a partner requires, and what should remain closely held.

01

Collect with Purpose

Atavis asks for information when it supports the trip, satisfies a requirement, or improves service.

02

Use with Restraint

Personal context is used to reduce repetition and prepare more precisely, not to make the relationship feel watched.

03

Share with Precision

Operators, FBOs, ground providers, and trusted partners receive only the details relevant to their role.

04

Remember with Care

Useful preferences and service notes may carry forward when they make future travel easier. Sensitive context is kept closely held.

Secure Collection

Some information deserves a safer path.

Some details should not move casually. When identification, payment, manifest, or sensitive family information is needed, Atavis uses a more controlled path where appropriate and limits access according to role and need.

01

Secure Guest Forms

Sensitive details may be collected through secure Atavis forms rather than informal channels. This is especially important for identity documents, travel information, and other details that should not move casually.

02

Limited Access

Guest information is not treated as general background. Access is guided by role, need, and trip requirement, so sensitive details are visible only where they have a clear service or operational purpose.

03

Clear Purpose

When Atavis asks for sensitive details, the reason should be clear. The information should support flight preparation, satisfy a requirement, or help coordinate service with appropriate discretion.

Begin with Atavis

Travel with discretion.

Share where you need to go, who is traveling, who is arranging the trip, and what the trip needs to support. Atavis will review the request and respond with the most appropriate next step.

Have a specific itinerary in mind? Request a trip. For recurring travel, advisor introductions, or a broader conversation, start a conversation with our team.

Atavis reviews each request personally and uses appropriate secure channels when sensitive details are required.