VALIDUS AERO
Privacy noticeBook a briefing ↗
TRUST CENTRE / 01

Security and privacy.
Clear boundaries.

What Validus Aero controls today, what must be agreed before a live pilot, and where the operator remains responsible.

Last updated 1 September 2026
AUTH

Authenticated access

Users must sign in before accessing operational functions.

RBAC

Role permissions

Actions are limited according to operational responsibility.

TXN

Transactional records

Live status and supporting audit history are committed together.

CLOUD

Cloud-backed pilot

A managed pilot environment is available, with customer-specific live-data gates.

DEMO-DATA DISCLAIMER

Illustrative product views—not operational records.

All names, identifiers, qualification statuses, ratings, simulator assignments, reports, and audit records shown in public Validus Aero demonstrations or marketing material are synthetic unless a customer has given explicit written permission for a specific use. Demo content must not be used for operational, regulatory, employment, or training decisions.

SECURITY & PRIVACY FAQ

Questions an operator should ask before a pilot.

01

How is access to Validus Aero controlled?

The application requires authenticated access. Role-based permissions limit administrative, planning, records, reporting, and other actions according to the responsibilities agreed with the operator. Access roles and privileged accounts are reviewed as part of pilot setup.

02

Can ordinary users rewrite qualification history?

Qualification updates and their audit entries are written together as one transaction. Ordinary corrections preserve the previous value, the new value, the reason, the time, and the responsible user. This makes history resistant to ordinary application editing; it is not a claim that raw infrastructure access can never alter data, so privileged database access must remain tightly restricted.

03

What data should be used during a demonstration?

Only synthetic or properly anonymised demonstration data. No live crew record, real qualification document, personal rating, or operator dataset should be loaded into a public demonstration environment.

04

Where will customer data be hosted?

A cloud-backed pilot environment is now available. For each operator, the deployment record must identify the hosting provider and region, subprocessors, isolation model, backups, recovery objectives, privileged-access boundaries, and retention before live customer data is approved.

05

What does “cloud live” mean today?

It means Validus Aero can be configured in a managed cloud-backed environment for a bounded design-partner pilot. It does not by itself promise a particular data region, service level, recovery objective, certification, or production support model; those commitments are confirmed for the selected customer deployment.

06

Is data encrypted?

A hosted pilot must use encrypted transport and database or storage encryption where supported by the selected environment. These controls, together with backup protection and privileged-access boundaries, are verified for the agreed deployment before onboarding live customer data.

07

Who owns operator data?

The operator retains ownership of its operational and personnel data. Pilot terms should define authorised users, permitted purposes, exports, return or deletion at the end of the engagement, and any records that must be retained for legal or contractual reasons.

08

Is customer data used to train public AI models?

No. Validus Aero does not require customer operational data for public AI-model training. Any future use outside delivery of the contracted service would require a separate, explicit agreement.

09

What happens if a security or privacy incident is suspected?

The affected environment should be contained, access reviewed, evidence preserved, impact assessed, and the customer contact notified without undue delay in accordance with the pilot agreement and applicable law. The escalation contacts and communication route are agreed before live onboarding.

10

Does Validus Aero make an operator compliant?

No software can replace the operator’s regulatory responsibility, approved procedures, nominated persons, or professional judgement. Validus Aero supports qualification control, planning, traceability, and evidence; the operator remains responsible for the validity of its rules, records, decisions, and approvals.

11

What can a prospective operator review before a pilot?

A prospective operator can request the relevant architecture and data-flow description, access-role matrix, data-import plan, backup and recovery approach, retention schedule, subprocessors, security contacts, and a proposed data-processing agreement for the selected deployment.

BEFORE LIVE DATA

The pilot order, security schedule, data-processing terms, deployment details, backup plan, and named incident contacts must be agreed before production operator data is loaded.

© 2026 Validus Aero
Privacy notice[email protected]