SoaringMapby Pro3D3D flight maps

SoaringMap by Pro3D / PRIVACY

Your flight stays yours.

How this application uses your data

Your IGC file is first processed in your browser. To display terrain, the server requests data for the geographical area from Copernicus DEM on AWS, with Mapzen Terrain Tiles on AWS or NOAA ETOPO as fallbacks. Land cover comes from ESA WorldCover 2021 on AWS, or ESA CCI / C3S 2022 hosted by Stanford Natural Capital Alliance. These requests include the map area, not pilot details. The original IGC is not sent to these providers. Your draft and original IGC are temporarily saved in this browser so you can resume later. “New flight” clears this local draft.

If you choose “Save to my account”, we also store your IGC and design privately on our server so you can reopen it on another device. You can remove saved designs in your account; this does not remove submitted orders. Your optional profile name and saved delivery details are used to prefill checkout. Account settings let you update these details and sign out other sessions.

When you place an order or request a custom quotation, we store your original IGC, flight coordinates and elevations, model design, reference link, name, email, delivery and billing addresses, phone number, optional company/tax details and message. No account is needed to order. Requests and files are accessible to the studio administrator and the user with the verified contact email. Setting a password through an email link connects requests submitted with the same address to your private account. Requests are not a public gallery.

Your details are used for order confirmation, production, billing and delivery. Standard orders are paid through Stripe; custom dimensions receive an individual quotation. Necessary delivery details are shared with the carrier. If you submitted while signed in, your inquiry also appears in “My orders”. Your order summary, price and contact details are sent to info@soaringmap.com through Pro3D’s email hosting. The original IGC and production files remain in the private studio.

Card payments are processed by Stripe. We send Stripe the order amount, currency, product description, contact email for direct orders, destination city/country and internal payment references. Stripe collects your payment and billing information. We store payment references, payment status and refund amounts to reconcile your order; we do not store card numbers or security codes. Payment links are private: anyone you share a link with can view the order and its delivery details and pay it. Before payment they may edit delivery details and the discount code. Keep this link private. Your original IGC and production files are not sent to Stripe. Stripe privacy policy.

To limit unwanted submissions, we keep temporary counters keyed by cryptographic hashes of the email and network address when available. These counters do not store raw network addresses.

Passwords are stored only as salted scrypt hashes. Password setup links expire after 30 minutes and can only be used once. Sign-in uses an essential seven-day session cookie; changing the password revokes previous sessions.

To speed up repeat previews, the server temporarily keeps geographic source data and prepared terrain crops in a bounded private cache, without pilot names or original IGC files. Orders are stored separately.

Before submitting, make sure you are authorized to use the flight file and pilot details.