vDAL.to — Virtual Delta Air Lines← Return to vDAL.to
Privacy & pilot data

Privacy Policy

Virtual Delta Air Lines · Updated November 14, 2026 · Hosted beta

In brief: vDAL.to connects to vAMSYS with your permission to display your virtual airline career and assist with flight dispatch and booking management. We do not ask for your vAMSYS password. This website is currently in hosted testing.

1. Who operates this service

The vDAL Pilot Portal (vDAL.to) is an independent, noncommercial virtual airline community website operated by the vDAL team for flight simulation purposes. Questions or privacy requests can be emailed to vdalstaff@gmail.com. vDAL is not affiliated with Delta Air Lines.

2. Information we access

When you choose to sign in through vAMSYS, you are redirected to vAMSYS to authorize access. The portal requests these permissions:

We also display general airline operation information from the vAMSYS Operations API and publicly available VATSIM information. Other permissions may be requested in the future, with updates to this policy as needed.

3. How we use this information

We use authorized account data to verify that you belong to vDAL, provide your personal Flight Deck and flight statistics, show bookings and activity information, open dispatch sessions, and process booking cancellations when you request them. We do not use this information for advertising or sell your personal data.

4. Authentication, cookies, and storage

vAMSYS handles your sign-in and consent. The portal receives short-lived OAuth access tokens and refresh tokens after approval; these tokens remain on the portal server and are not provided directly to website JavaScript. The portal uses essential, HTTP-only, secure cookies to recognize your session and protect the authorization flow.

Pilot OAuth tokens and associated pilot session information are kept in server memory, not a persistent pilot-account database. Pilot sessions generally expire after about one hour and are lost if the application restarts. The Management Studio separately stores authorized staff accounts and management sessions on the server’s persistent storage. General operational airline data may be cached to improve performance; the operations cache is not intended to retain personal Pilot API responses.

5. Sharing and third-party services

Personal pilot information is obtained from vAMSYS under the permissions you grant. The hosted website runs on Render over HTTPS. Render processes hosting-related connection data. The website also loads mapping libraries and map tiles from third-party services and may request publicly available VATSIM data. Those providers may process network metadata such as IP addresses under their own policies.

6. Retention, protection, and limitations

We use HTTPS access, restricted OAuth permissions, server-side token handling, and secure session cookies. No online service can guarantee complete security. The website is currently undergoing hosted testing. Staff account data, content, settings, and uploaded branding may be stored on persistent server storage and included in administrative backups. Security, retention, and recovery practices will be reviewed as the service develops.

7. Your choices and privacy requests

You can decline vAMSYS authorization and still browse public airline pages. You can sign out of the portal and revoke its access through your vAMSYS account's connected-app settings, where supported. To request information about data associated with your portal session or ask that information be removed, email vdalstaff@gmail.com. vAMSYS account data itself is managed by vAMSYS and may require a separate request to that provider.

8. Changes to this policy

We may revise this policy as the portal develops, particularly when we add new features, persistent pilot accounts, or additional permissions. Material changes will be reflected here before those features are made available to pilots.