Privacy
What this site stores about you, why, who can see it, and how to get it changed or deleted.
What this page is
This is the demonstration rebuild of the Mooney Safety Foundation’s website. This page describes what the software you are using actually does with information about you. It is written to be checked against the code rather than to be reassuring.
What is collected, and when
If you only read the site, nothing about you is stored. There is no analytics script, no advertising pixel, no third-party tracker and no cookie set until you do something that needs one. The colour-scheme preference, if you change it, is kept in your own browser and is never sent anywhere.
If you send a message through the contact form, your name, email address and the message are stored so that somebody can reply to it.
If you create an account, your email address is stored. Signing in works by sending a single-use link to that address - there is no password, so there is no password to lose.
If you enrol on a programme, the details the Foundation needs to run it are stored: your name and contact details, your certificate and ratings, your aircraft, its model and equipment, and any instructor you have asked to fly with. Your payment is taken by Stripe; card numbers never reach this site and are never stored here.
If you sign up for email, your address and your consent are stored, along with the date and the page you gave it on, so that an unsubscribe can be honoured and evidenced.
Who can see it
Your own account pages show you your own records and nobody else’s - the query that fetches them takes your session as its only argument and there is no way to ask it for somebody else’s.
Foundation staff can see registrations, messages and rosters, because running the programme requires it. Instructors can see the pilots they are assigned to fly with, and the aircraft those pilots will bring. An instructor cannot see another instructor’s assignments, and nobody outside the Foundation sees any of it.
Cookies
One, and only when you sign in: an opaque session identifier. It carries no personal information - it is a random string that points at a record on the server - and it is set with the HttpOnly, Secure and SameSite flags, so it cannot be read by a script and is not sent to other sites. Signing out destroys the server-side record, not just the cookie.
How long things are kept
Registrations and payment records are kept while the Foundation needs them for its accounts. Contact messages are kept until they are dealt with and archived. Scholarship applications are deleted after the board has chosen a recipient - that is the Foundation’s own stated policy, and this build implements it as a scheduled deletion rather than as a flag.
What you can ask for
Ask, through the contact form, and the Foundation will tell you what it holds about you, correct anything that is wrong, or delete it. Unsubscribing from email is one click from the bottom of any message the site sends and does not require an account.
About the data in this demonstration
Every person, address, telephone number, aircraft registration and certificate number visible in this build is invented. No registrant record, no roster and no mailing list from the Foundation’s own files has been loaded into it, and an automated check runs over the repository on every test run to keep it that way. Payments run against Stripe’s test mode only; no real money can move through this site.