Privacy
Debrief is a personal, non-commercial project. It collects as little as possible — in fact, nothing — so this page is short.
What we collect
Nothing. There is no account, no sign-up, no email, and no analytics. Your flight file is read and analyzed entirely in your browser and is never uploaded — there is no server to upload it to. Debrief is a static site.
What lives on your device
A few things are saved locally so the tool is pleasant to use, and they never leave your browser:
- Recent flights — kept in your browser's local database (IndexedDB) so you can reopen a file without choosing it again. This is the one the logbook's own Clear takes, and it says how many and what goes with them.
- An offline copy of the app — a service worker caches Debrief's own pages and code (so it works without a signal at the field). It caches the app itself, never your flight files.
- 23 small settings — everything below, in local storage. Some of it is more than a preference, so it is all named rather than summarised.
Things you typed
Text you wrote, and the shape of files you mapped by hand.
- the label and notes you typed onto a comparison, and the order you put its columns in
debrief.compare.captions - the column layouts you mapped by hand, filed under your file’s own column headings — or, for an export with no header row, under how many columns it had
debrief.mappings.v1 - plot views you saved, under the names you gave them
debrief.plotPresets
Your rocket’s numbers
What you entered so the analysis could use it, remembered so you don’t retype it every flight.
- your rocket’s descending mass
debrief.mass.kg - the mass you gave for the drag estimate
debrief.dragmass.kg - its body diameter
debrief.diameter.m - its main canopy diameter
debrief.chute.m - its drogue diameter
debrief.drogue.m - the rail you fly off
debrief.rail - the altitude you deploy the main at
debrief.maindeploy.m - your motor’s ejection delay
debrief.delay.s
How you like to read a flight
What you chose to look at, so the tool doesn’t forget what it was just told.
- which channels the chart was plotting, and against what
debrief.plotView - which channel a comparison opens on
debrief.compareChannel - the colours you gave your flights on a comparison
debrief.compare.colors - the colours you gave the report figures
debrief.report.figureColors - which recording you said flew as the first stage, per set of recordings you assembled
debrief.firstStage - event markers you turned off
debrief.hiddenEvents - readings you chose not to show
debrief.report.hidden - figures you chose not to show
debrief.report.hiddenFigures - the order you put the readings in
debrief.report.order - the order you put the figures in
debrief.report.figureOrder
How the app looks
Nothing about you or your flights.
- light or dark
debrief.theme - feet or metres — and, if you set them one at a time, your speed, acceleration, temperature and pressure units
debrief.units
None of it is sent anywhere, and none of it identifies you — but a shared or borrowed laptop is exactly the case a privacy page is for, so here is the control that takes all of it at once. The flights are separate: they live in the local database above, and the logbook's own Clear is what removes those.
Clearing your browser data for this site removes everything on this page, the flights and the offline copy together.
Share links
When you create a share link, the flight is compressed and packed into the part of the URL after the # (the fragment). Browsers never send the fragment to a server, so the flight still isn't uploaded — the link works because whoever opens it decodes it in their own browser. Treat a share link like the file itself: only send it to people you'd give the flight to.
One consequence worth knowing, since the rest of this page is exhaustive about what is kept: opening a share link leaves the whole flight in that browser's address bar and session history. That is the browser's own record of where you have been rather than Debrief's storage — nothing above reaches it, and clearing history is what does.
Hosting
The site is served as static files by Cloudflare Pages. Like any web host, Cloudflare may keep standard, short-lived request logs (such as IP addresses) for delivering and protecting the site. That's infrastructure-level and applies to fetching the page — it never includes your flight data, which stays in your browser.
What we don't do
- No tracking pixels, advertising, or third-party analytics.
- No cookies at all. The settings above are local storage, which is a different thing: it stays in your browser and is never attached to a request.
- No selling, renting, or sharing of anything — there is nothing to share.
Contact
Questions? Open a GitHub issue.