Privacy Policy
Version 2026-11-08.1 · Syvex Labs, North Carolina, USA
Effective November 8, 2026. UPS Virtual Operations (UPSVO) is operated by Syvex Labs in North Carolina, United States. Contact support@upsvo.com for privacy questions, corrections, access or deletion requests. UPSVO is an independent flight-simulation community, not UPS or UPS Airlines. Membership is for people aged 18 or older.
Information we process and why
- Waitlist: email address, signup time, permission wording/version and notification status, to manage the launch and recruitment updates you request. Signup does not create pilot membership.
- Applications and assessment: vAMSYS registration/user identifiers, staff-verified contact information, invitation and access history, assessment answers, scores, attempts, cooldowns and commissioning-review records. These administer applications and manual review. Passing an assessment does not hire an applicant.
- Pilot identity and access: provider-confirmed name, email, pilot identifier, airline membership/status, rank, statistics, home hub, virtual location, onboarding acknowledgments and relevant granted permissions. We use these to identify the correct member and enforce access. OAuth access credentials remain server-side; we do not receive your vAMSYS password.
- Simulated operations: bookings, aircraft, routes, flight reports, available telemetry, SimBrief plans and MINA shipment allocations, manifests and custody history. These support dispatch and simulated cargo continuity. A virtual airport location is not your physical location.
- Community: linked Discord identity and membership/role verification where configured, to verify required community access. Clicking an invite alone does not prove membership.
- Technical records: request/IP and browser information, security and access events, error records, authentication cookies and display preferences. Passwords, session secrets and OAuth tokens must not be written to diagnostic logs.
Public information
Public pages display aggregate pilot/fleet/network counts, schedules, airports and approved MINA activity summaries. Live-flight cards may display the UPS pilot identifier, callsign, simulated route, aircraft type/registration, status and available telemetry. Applicant names, email addresses, assessment results, private provider identity numbers and credentials are not public flight data. Crew pages provide access to the authorized member's own records.
Providers and responsibility for copies
vAMSYS controls its own platform accounts, membership and operational records. UPSVO is responsible for the copies it obtains and its own assessments, onboarding and simulated cargo records. OAuth permission authorizes the requested data sharing; it is not blanket permission for marketing. Deleting a UPSVO copy does not delete a vAMSYS account.
Authorized staff have access appropriate to their duties. Rocket hosting and security/CDN services process website traffic and stored information. Microsoft 365 is used for recruitment correspondence. MapTiler receives map requests including request/IP information, and UNPKG supplies the MapLibre library. Discord and SimBrief process information for their associated community and planning services. These providers publish their own policies. We do not sell applicant or pilot information.
UPSVO operates in the United States and uses international service providers. Processing may occur outside your country. We have not verified an EU-only processing location for UPSVO or all providers' backup locations; we do not make that claim.
Purposes, choices and applicable rights
We use information to provide the application/membership services you request, administer simulated operations, secure the service and meet applicable obligations. Optional launch/marketing contact uses your separate permission, which you may withdraw. Essential service communications are separate. Where applicable law requires a particular lawful basis or transfer safeguard, that requirement is separate from accepting this notice; this notice does not waive your rights.
Contact support@upsvo.com to request access, correction, deletion or withdrawal of optional contact permission. We verify requests against the relevant record without asking for passwords or tokens. Depending on applicable law, you may also have rights to restriction, objection, portability or complaint to your data-protection regulator. We explain any necessary retention exception. Use vAMSYS's own process for its account and records.
UPSVO retention schedule
These are UPSVO operating periods, not statements of legally mandated deadlines. They apply to UPSVO-controlled copies.
| Records | Period |
|---|---|
| Waitlist | Until withdrawal or conversion to an application; otherwise 12 months without engagement. |
| Unsuccessful or withdrawn applications and assessments | Six months after closure or final decision. |
| Former-member profiles and identifiable operational copies | 12 months after membership ends, then deletion or irreversible anonymization. Anonymous network totals may remain. |
| Routine technical logs | 30 days. |
| Security and access-audit logs | 90 days, with restricted access. |
| Active dispute or security incident | Only necessary records until resolution, with a documented exception and review. |
The schedule was adopted on November 8, 2026. Initial cleanup is in dry-run review; not all record categories yet have automated deletion. Current member records and ongoing operations are not cleanup targets. We do not describe a session expiry as deletion of an application. Consent and terms-acceptance evidence requires its separately documented justification and schedule; that review remains open rather than assigning an invented period.
Backups and restoration
On November 8, the production hosting dashboard showed 30 daily automated restore points, October 10–November 8, and no cloud backups. Separate restricted release backups also exist. This observation is not a guarantee that every backup copy expires after 30 days. Deleted data may remain in restricted backups until those copies expire or are removed. Before a restored site returns to service, deletion requests must be reapplied; verification of that restore safeguard is a release requirement, not a completed test.
Cookies, security and changes
See Cookies and preferences for the observed storage inventory and display-preference reset. No analytics or advertising tracker was observed in the inspected public Home requests; this does not characterize every third-party service you may visit. Authentication and security storage must remain available for requested private services.
We restrict access and keep integration secrets server-side. No service can promise absolute security. Changes to this policy are versioned. Reading this notice is not blanket consent or acceptance of membership terms.
Provider references: vAMSYS Privacy Policy, Terms, Cookie Policy and Data Sharing Agreement.
Questions or privacy requests: support@upsvo.com.