V-Air Ops
LEGAL & SYSTEM INFRASTRUCTURE • SECURITY POLICY

Security Policy

Last Updated: September 7, 2026 • Enterprise Infrastructure Defense

01. Security Architecture & Commitment

Security is foundational to the V-Air Ops platform. We operate a multi-tenant Virtual Airline architecture designed to ensure total data isolation between airline communities, secure API access, and encrypted telemetry transmission for ACARS flight tracking.

02. Technical Safeguards & Encryption

TLS 1.3 / SSL Data in Transit

All web traffic, API requests, and ACARS client telemetry streams are strictly encrypted in transit using modern TLS 1.3 encryption protocols.

Password & Token Hashing

User credentials are protected using industry-standard bcrypt hashing. API authentication utilizes scoped Laravel Sanctum Bearer tokens.

Multi-Tenant Data Isolation

Global middleware (`EnsureActiveAirlineSelected`) and tenant-scoped database queries ensure Virtual Airlines cannot access each other's private data or flight logs.

CSRF & Injection Protections

All form submissions enforce CSRF token validation (`XSRF-TOKEN`). Database interactions utilize parameterized Eloquent ORM queries to eliminate SQL injection risks.

03. ACARS Telemetry & V-AirOps Client Security

The V-AirOps ACARS desktop client establishes secure, authenticated web-socket and REST connections to the V-Air Ops telemetry endpoint. Telemetry packets are validated for active user session tokens, rate-limited against DDoS or spoofing attempts, and sanitized before storage in flight log databases.

04. Vulnerability Disclosure & Responsible Reporting

We welcome security researchers and community developers to report any security vulnerabilities responsibly. If you discover a potential security flaw in the V-Air Ops web console, API, or ACARS telemetry pipeline:

SECURITY REPORTING CONTACT: security@artmex-hosting.com
  • Provide detailed steps or proof-of-concept (PoC) to reproduce the vulnerability.
  • Allow reasonable time for our development team to patch the issue prior to public disclosure.
  • Avoid accessing or modifying other users' data during testing.

05. Recommended Operational Security for VA Owners

  • Role-Based Access Control (RBAC): Grant administrative staff permissions (`manage_fleet`, `manage_routes`, `manage_notams`) sparingly.
  • API Key Safety: Do not publicly share VA API keys or Discord webhook URLs in public community channels.
  • Session Protection: Always sign out of staff consoles when using shared computers.

Privacy & Cookie Preferences GDPR Compliant

We use cookies and telemetry storage to ensure core flight dispatching functions, remember your virtual airline settings, analyze ACARS performance, and cache flight plans. You can customize your preferences or accept all cookies.

Cookie Consent Preferences

Manage what cookies and local storage tokens we store

Strictly Necessary Cookies Always Active

Essential for basic platform navigation, user authentication (vops_session, XSRF-TOKEN), secure CSRF protection, and virtual airline tenant routing. These cannot be switched off.

Functional & UI Preferences

Remembers your selected Virtual Airline switcher view, interface theme parameters, live radar map center coordinates/zoom level, and audio alert sound preferences.

ACARS Telemetry & Diagnostics

Allows anonymized telemetry performance metrics, landing rate touchdown diagnostic logs, and ACARS ping latency statistics to help us optimize flight tracking speed and prevent sim stuttering.

External Flight Services Integration

Enables cached integrations for SimBrief OFP flight plans, VATSIM / IVAO pilot status checks, and AirLabs worldwide route data caching.