Back to Anderson Dynamics

Privacy policy

What this system holds about a person who uses it, what it records while they use it, and which other parties receive anything. Written against the source rather than from a template, because most of the answers here are “nothing” and a template would not have said so.

Last reviewed
17 September 2026
Status
Prototype — single-tenant demo
Not legal advice.

This page describes how the software behaves, verified against the source. It has not been drafted or reviewed by a lawyer, and it does not attempt to establish what any jurisdiction requires. Before this product is offered to a customer, counsel must review these pages and complete the items marked TODO.

1What this page covers

Wingates is an operational data system for an airline. It reconciles a published timetable, an operations log and ADS-B telemetry into one record per flight leg, and shows where each number came from. It is deployed as a single-tenant instance: this deployment holds Nepal Airlines data and is not pooled with any other operator.

Two surfaces are covered: this marketing site, and the application itself. They behave differently and are described separately wherever that matters.

2What the system stores about you

One table holds people. It has five columns and this is all of them:

ColumnWhat it holds
idA generated UUID.
emailThe address used to sign in.
password_hashA bcrypt hash at 12 rounds. The password itself is never stored.
tenant_idWhich operator’s data the account may read.
created_atWhen the row was made.

There is no name field, no telephone number, no job title, no address, and no IP address in this table. There is no second table about people. Accounts are created by the operator of the instance from environment variables; there is no public sign-up, and the application has no way for a user to create an account or add information to a profile.

3What is recorded while you use it

The application server runs under uvicorn with its default access log enabled. That log writes one line per HTTP request containing the client IP address, the request line and the response status. So:

Your IP address is written to the server’s log output for every request you make.

This is ordinary web server logging rather than anything built into this product, and the application code itself neither reads those lines nor stores them in the database. When the instance is deployed to Render, that log output is captured and retained by the hosting platform under its own retention rules.

TODO The retention period for those logs has not been configured or verified for this deployment, and this page must state a real figure before it goes in front of a customer. It would be wrong to print a number here that nobody has checked.

4Signing in, and what holds your session

Signing in exchanges an email and password for a JSON Web Token, signed HS256, valid for eight hours. The token is held in the page’s memory for the life of the browser tab and is gone when the tab closes.

It is deliberately not placed in localStorage, where it would outlive the session and be readable by any script on the page, and it is not placed in a cookie. Closing the tab ends the session; there is nothing to sign out of on another device because nothing was left behind on this one.

A failed sign-in returns the same message whether the address or the password was wrong, so the form cannot be used to discover which addresses have accounts.

5Operational data, which is not personal data

The substance of this system is flights, not people: scheduled and actual departure times, block minutes, aircraft registrations, routes and delays. Aircraft registrations identify airframes rather than individuals. Crew names are not loaded, and no passenger data of any kind enters this system.

6What your browser contacts

A request from your browser to a third party discloses your IP address to that party whether or not any data is sent deliberately. These are all of them.

HostSurfaceWhy
tiles.openfreemap.org Application Basemap tiles for the live flight map. No key, no account, no identifier is sent.

That is the complete list, and the basemap host is now the only entry on it. The home page previously fetched the JetBrains Mono webfont from Google, which disclosed your IP address to Google on every visit; this page recorded removing it as a known improvement rather than a completed one. It is now completed. The type across the product and this site is Helvetica, which is already installed on the device rendering it, so nothing is fetched to display any of it.

No page here loads a webfont. The application makes no request to Google, and these legal pages make no third-party request of any kind.

7What the server contacts

The server calls these services to build the live map and the reconciled record. None of them receives anything about you.

HostPurposeState
opendata.adsb.fiLive aircraft positions.In use
api.adsb.lolPublished route for a callsign.In use
opensky-network.orgHistorical position data.In use
api.deepseek.com An optional panel that would put a finding into prose. Not wired. No key is configured; the endpoint refuses the request rather than calling out. Nothing reaches this host unless an operator sets a key and a user explicitly asks for an interpretation.

8What this system does not do

These are absences verified in the source, not intentions.

  • It sets no cookies. Not one, on any surface.
  • It writes nothing to localStorage or sessionStorage.
  • It contains no analytics, no tag manager, no session recorder, no heat-mapping and no advertising technology of any kind.
  • It builds no profile of a user and scores nobody.
  • It sells nothing and shares nothing for marketing.
  • It sends no email, so there is nothing to unsubscribe from.
  • It has no tracking pixels and no third-party iframes.

9Security, stated plainly

Passwords are hashed with bcrypt at 12 rounds. Tokens are signed with a secret supplied through the environment; the server refuses to issue tokens at all when that secret is absent, rather than falling back to a default. Database credentials and API keys come from the environment and are not committed to the repository.

Data in this system is not encrypted at rest.

That sentence is here because its opposite appears on most pages like this one and is usually untrue. Transport is protected by HTTPS when the instance is deployed behind a platform that terminates TLS. Beyond that, what protects this data is the access control described above and the security of the host.

10Asking about your data

There is one account record per user and it contains the five columns in section 2. To see it, change it, or have it deleted, write to hello@anderson-dynamics.com. Deleting the account row removes everything this system holds about a person; the flight data is about aircraft and is unaffected.

TODO The statutory basis for processing, the identity of the data controller, the governing jurisdiction, and a response deadline all need to be settled with counsel and stated here.

How this page was verified — 11 checks

Every statement on this page was read out of the repository before it was written. These are the places that establish each one.

ClaimEstablished by
No cookie is ever setno set_cookie in backend/*.py
Nothing is written to browser storageno localStorage write in frontend/src/*.jsx
Account table has exactly five columnsbackend/auth.py SCHEMA
bcrypt at 12 roundsbackend/auth.py CryptContext bcrypt__rounds=12
Token is HS256, valid eight hoursbackend/auth.py ALGORITHM, TOKEN_HOURS = 8
Token held in memory, never localStoragefrontend/src/App.jsx useState(auth)
Server refuses to issue tokens without a secretbackend/auth.py _secret()
Access log records client IP by defaultuvicorn Config.access_log default True; no override in render.yaml
Browser contacts only OpenFreeMap and Google FontsURL sweep of frontend/src/*.jsx and landing/index.html
DeepSeek is unwiredbackend/llm.py raises 400 without DEEPSEEK_API_KEY; render.yaml sync: false
No analytics presenttracker-name sweep of landing/index.html and frontend/src