Skip to content

SteerSim Privacy Notice (Beta)

Last updated: 19 November 2026 (UTC).

This notice describes how SteerSim (“we”, “us”) handles personal data when you use the SteerSim website and planner at steersim.com and the associated API. All times are UTC.

Contact for privacy questions, a copy of the data we hold for your account, or a deletion request: support@steersim.com, from the address on the account.

1. Who this applies to

SteerSim is a browser-based airside planning aid. Planning aid only. It is not directed at children, and we do not knowingly collect data from children.

2. Data we collect

2.1 Account, sign-in, and the beta email gate

Before a signed-out visitor can use the planner, we ask for an email address. Submitting that form does not create an account, does not set a password, and does not require a confirmation email. You can use the planner as soon as the address is accepted.

We store that address as a beta lead: the normalised email, the UTC time it was first received, an anonymous visitor identifier if one is already present in the browser, and the same coarse advertising source label described in section 2.4 when we have one. If you later sign in with the same email (sign-in link or Google), we link the lead to your account.

We use beta leads to contact people who tried the planner, to understand demand during the beta, and to attribute first-touch ads. We do not sell this data.

To avoid asking again on the same browser, we store a first-party pass in browser storage and in a cookie named steersim_email_gate. The cookie holds a lead identifier, not the email address. It lasts up to 400 days.

Beta leads are kept until you ask us to delete them, until we reset beta data (see the Terms), or until they are linked to an account, in which case they follow the account retention in section 5.

If you request a sign-in link, we store:

  • your email address;
  • a one-time sign-in token, stored only as a hash, with an expiry of 20 minutes;
  • when you complete sign-in: a user record with plan (paid features are free during the beta), role, sign-up method (email link, or Google if enabled), an optional coarse advertising source label from the first visit (for example facebook/paid), country, city, creation time, the UTC time of your last sign-in, and the UTC time you were last active while signed in (updated at most every few minutes);
  • the UTC time you accepted our Terms and Privacy Policy, and the terms version;
  • a session, stored as a hashed token, tied to your user id, with a 14-day expiry.

If Google sign-in is enabled, we receive your email address and Google account identifier (subject) from Google and store a link to your SteerSim account.

We send the sign-in email through Namecheap Private Email, from support@steersim.com. The link expires in 20 minutes.

2.2 Session cookie

When you are signed in, we set a first-party session cookie named steersim.session (the older name airsidekit.session is still accepted). The cookie is HttpOnly, SameSite=Lax, and Secure when the server is configured for HTTPS cookies. It holds a session token, not your email. This is an authentication cookie, not an advertising cookie.

The visit counter itself does not set a cookie. Authentication uses the session cookie above.

We also store your cookie choice (below) in your browser’s local storage and in a first-party cookie named steersim_consent. It records only whether you allowed analytics and advertising, and when. It expires after 180 days, when we ask again.

2.3 Saved projects and sharing

If you sign in and save to the cloud, we store project names, the project document (layout and planning data you create), version history, update times, and the user id they belong to. If you create a share link, we store an unguessable token that can open that project. If someone posts a comment on a share or a project, we store the author name they enter, the comment body, and the time.

You should not put secrets or unnecessary personal data in project files, share links, or comments. Anyone with a share link can open the shared project.

Projects may also be saved in the browser’s local storage on your device. That copy stays on your device unless you save it to your account.

2.4 Usage analytics (first-party)

The site sends usage events to our own servers. This first-party counting does not use cookies or third-party analytics products.

For a page visit we record: the URL path (query and fragment stripped, admin paths excluded), the external referrer hostname if the referrer is not our own site, a coarse first-touch source label built from standard campaign parameters (source, medium, campaign) or from the presence of a Facebook click identifier (recorded only as facebook/paid — the identifier value is never stored), a coarse device class and browser family derived from the user-agent string, country, and city when available. We also store a daily visitor identifier that is a hash of a per-day random salt, the client IP address, and the user-agent. The IP address itself is not written into the analytics tables. Salts rotate each UTC day, so the identifier is not a stable long-term ID across days. The source label is first-party counting, not an advertising cookie, and is stored in browser storage so a later sign-up can be attributed to the same first visit.

Visit events and visitor hashes are deleted after 90 days. Daily aggregate counts derived from them may be kept longer.

For planner usage we record counts of imports and exports (DXF, PDF, GeoJSON, PNG, video), and simulation events that include the aircraft type string, a clearance result of pass/warn/fail, and whether the session appeared signed in. Sign-in and sign-up counts are stored by method and, for sign-ups, by country.

Country is taken first from standard hosting headers (for example a Cloudflare country header) if present, otherwise from a local DB-IP Lite IPv4 country database (CC BY 4.0; attribution: IP Geolocation by DB-IP). City is recorded only when the hosting network already supplies a city header. We do not use device GPS, and the product does not store a user’s time zone; the planner uses UTC.

Admin users are excluded from visit collection. Bot-like user-agents are skipped.

2.5 Cookies and ad pixels (only with your consent)

A cookie banner asks for your choice. Analytics and advertising are off until you accept them, and Reject all is as easy as Accept all. You can change your choice at any time with Cookie settings in the site footer.

If you allow advertising, and only when we have set up the relevant ad account, your browser may load these tags to measure our ads: the Google tag (Google Ads) and the X Pixel. They can set cookies and see your IP address, browser details and the page you are on. We send them page views, a sign-up event when a new account is created, and a one-time event for your first simulation. We do not send your email address, project data, sign-in links or share links to these tags. We use Google Consent Mode, so Google tags stay in a denied state unless you accept.

If you withdraw consent, we stop loading the tags, tell them consent is withdrawn where they support it, and clear the ad cookies we can reach on our own domain. Data already sent is handled under the provider’s own policy.

2.6 Rate limiting and logs

To limit abuse, the API keeps short-lived in-memory counts keyed by IP address and, for sign-in requests and the beta email gate, by email address. These counts are not stored.

Application and hosting logs may include IP addresses, request paths, email addresses (for sign-in delivery), and error messages. Magic-link messages and delivery failures use redacted log markers, not sign-in tokens or full links.

Hosting logs are retained according to the host’s settings (see processors below).

2.7 Data we do not collect

We do not use advertising cookies or third-party ad tags unless you accept them (section 2.5), and we do not use third-party analytics trackers. We do not take payment card data (billing is not live). We do not use Google map tiles. Google account data is not collected unless Google sign-in is enabled.

3. Processors and third parties

These organisations may process data because the product uses their systems. These providers have their own privacy policies.

Swipe to see all columns

Party Role
Render Hosts the website, API, and PostgreSQL database, and holds application logs.
Namecheap Private Email Sends sign-in and support email for support@steersim.com.
Esri (and imagery attribution sources, including Maxar and Earthstar Geographics) The browser requests Esri World Imagery and optional Esri gray-canvas or place-name tiles. Those requests come from the user’s network, so Esri may see the user’s IP address and tile coordinates. The API also fetches Esri tiles when building some PDF exports. Tiles are for display only and must not be traced into drawings.
OpenFreeMap Optional streets basemap. The browser requests style and tiles; OpenFreeMap may see the user’s IP address. Data is OSM-derived (ODbL).
MapLibre glyph host (demotiles.maplibre.org) The current map style may request font glyphs from this host, which may see the user’s IP address.
OpenStreetMap Overpass mirrors If a live airport layout refresh runs, our API (not your browser) queries public Overpass endpoints with a map bounding box. Mirrors include overpass-api.de, overpass.kumi.systems, overpass.private.coffee, overpass.osm.jp, and maps.mail.ru. Those operators may see our server’s IP address and the query. Bundled or cached OSM snapshots are stored in our database.
OurAirports CC0 airport-directory data shipped with the site; no user data is sent.
DB-IP A local Lite country database used on our server; lookups do not send your IP to DB-IP.
Google Identity provider, only when Google sign-in is enabled. Google Ads measurement, only if you accept advertising cookies.
X Corp. X Pixel for ad measurement, only if you accept advertising cookies.

See also Data sources and licences.

4. How we use the data

We use this data to operate sign-in, save and share projects, provide support, secure the service (including rate limits), store beta leads from the planner gate, understand how the planner is used, and improve it. We do not sell personal data. With your consent only, we use ad tags to measure whether our own ads lead to sign-ups.

During the free beta we may reset or delete beta data, as described in the Terms. You should keep your own copies of anything you need.

5. Retention

  • Sign-in link hashes expire after 20 minutes and are consumed on use; expired rows may remain until cleaned up.
  • Sessions last 14 days, or until you sign out.
  • Account records (including terms acceptance), project, version, share-link, comment, and unlinked beta-lead records are kept until you delete them, you ask us to delete them, or we reset beta data.
  • Visit event rows, visitor hashes, and daily hash salts are deleted after 90 days. Daily aggregate counts may be kept longer.
  • Emails you send to support@steersim.com are kept in that mailbox according to how we administer it.
  • Hosting logs follow the host’s retention settings.

6. Your requests

Email support@steersim.com from the address on the account to ask for a copy of the account data we hold, or to ask us to delete the account.

7. Changes

This notice may be updated. The “Last updated” date above will change when it is.

8. Contact

support@steersim.com. All times are UTC.