Defining the security requirement
A useful security request begins with the people, locations, timings and known concerns involved, without presuming a particular protection model. Close protection, a security-trained driver, an advance assessment or another service may be considered, but only a qualified provider can evaluate the declared exposure and recommend an appropriate scope. Passenger preferences do not replace professional judgment, local law or authority requirements. The Client should identify the purpose and limits of the request accurately, while avoiding unnecessary personal data until a responding provider explains what information is required and how it will be handled.
- People and itinerary: Provide passenger numbers, roles, airports, addresses, dates, local timings, public appearances and known itinerary changes in advance so a provider can assess the request without assuming uninterrupted coverage.
- Known concerns and constraints: Describe relevant concerns factually and precisely, including crowd exposure, media attention, previous incidents, mobility needs or official protocols, while distinguishing verified information from assumptions or unconfirmed intelligence.
- Provider-led assessment: A suitably licensed security provider, consulted by a participating vetted Broker Partner, determines the appropriate risk or threat assessment, personnel profile and operating plan; neither IONA JETS nor the Broker Partner provides professional security advice.
Providers, permits and contractual scope
Close protection and related security services should be assessed for each country, task and movement. A complete proposal identifies the responsible security company, personnel scope, relevant credentials, insurance, permitted equipment, subcontractors, geographic limits, exclusions and cancellation terms. Where armed protection or specialist authority is requested, the provider should explain the applicable licensing, permit and notification requirements and document the service it can lawfully perform. Requirements differ sharply between countries, so confirm each leg separately rather than assuming a departure arrangement applies on arrival.
- Licenses and credentials: Ask the provider to document applicable company licenses, personnel qualifications, insurance and any subcontracting arrangements, recognizing that requirements and permitted activities differ by jurisdiction and specific assignment.
- Weapons and restricted equipment: Declare any request involving firearms or controlled equipment early; the provider and authorities alone determine legality, permits, transport, storage, carriage and operational use under local law.
- Contract and responsibility: Review the named provider, service period, staffing, locations, inclusions, exclusions, liability provisions, insurance evidence, cancellation conditions and escalation contacts in writing before accepting the proposed security arrangement.
Airports, vehicles and official controls
Airport access and ground movements depend on infrastructure, security rules, operator procedures and competent-authority decisions. A protection officer or vehicle cannot enter a restricted area because the request accompanies a charter flight. Airside passes, driver credentials, escorts, screening and vehicle authorization may be required or refused. Armored vehicles and security-trained drivers depend on local licensing, specifications and availability; no vehicle description establishes suitability. Border, customs and police procedures remain official functions. Each handoff, meeting point and fallback arrangement should be confirmed for the movement.
- Restricted-area access: Request airside access only where operationally relevant, understanding that airports and authorities independently decide passes, screening, escorts, permitted routes, meeting points and access withdrawal for the proposed operation.
- Vehicles and drivers: A chauffeur or armored vehicle may be proposed by an identified provider, but vehicle specifications, driver credentials, routing, positioning and availability require separate written confirmation for each movement.
- Terminals and formalities: VIP terminal access may be assessed separately, while security screening, immigration, customs, police measures and processing locations remain controlled by airports, approved providers and competent authorities alone.
Communications, privacy and changing conditions
Security arrangements may require contact details, itineraries and sensitive information, but collection should be proportionate to the task. Clients and providers should agree who receives information, which channels are used, how updates are authenticated and when data is deleted. Code words, encrypted devices or confidentiality clauses do not guarantee secrecy or prevent interception, disclosure or human error. Personnel, routes, meeting points and handovers may change because of legal, operational or safety conditions. The proposal should define reporting lines, update procedures, contingencies and the authority to modify or stop the service.
- Data minimization: Share only information reasonably required for assessment and delivery for the assignment, using the channels specified by the responsible provider and observing applicable privacy, retention and cross-border transfer requirements.
- Communications protocol: Confirm primary and backup contacts, authentication methods, update deadlines, device expectations and responsibility for notifying changes, without treating any channel or confidentiality commitment as completely secure under all conditions.
- Handoffs and changes: Document meeting points, team handovers, fallback arrangements and decision authority, recognizing that providers or authorities may alter, suspend or cancel elements when conditions, permissions or safety judgments change.
.png)
