Privacy

What happens to your log

A blackbox log is a recording of your aircraft and your flying. This page states exactly what leaves the device, what stays, and how long anything is kept. It is written to be checked rather than believed: the claims below are the ones you can verify from your own network tab.

The short version

• A log is analysed to produce your report and is not used to train anything.
• Small logs are processed in memory in the analysis function and are not written to storage.
• Large logs sent in parts are held in private blob storage only until the analysis reads them, and orphaned sessions are deleted by an hourly sweep after ten minutes.
• No account, no password, no advertising tracker, no sale of data.
• The licence key is stored on your device, encrypted at rest, not in a profile on a server.

What leaves your device

Data	When	Kept
Log contents and filename	Only when the web analysis needs the server engine	In memory for the request; chunked uploads in private blob storage for at most ten minutes
Craft profile values you type (frame size, AUW, KV)	With the analysis request	Not stored after the response
Licence key	Activation and periodic verification	A hash and entitlement record on the licence server; the key itself stays on your device
Email address	Only if you buy or ask for the key to be resent	With the payment record, for delivery and support
Payment details	At checkout	Handled by Stripe; card data never reaches this site
Funnel events	During use	Aggregate buckets only: file-size band, extension, firmware family, confidence, outcome

What never leaves your device

• The licence key in clear text, and the local vault that holds it.
• Your saved quads and tune history, which live in local storage.
• The raw log, once the analysis is complete and the response has been returned.
• Anything from a desktop build that uses the local engine.

Analytics

Funnel events are sent to Vercel Web Analytics. They contain no filename, no file hash, no email, no key and no PID values. A filename can contain a name or a location, so it is never included. Events are used to answer questions like “did the upload button work on a phone”, not to profile a pilot.

Cookies and local storage

There are no advertising cookies. Local storage keeps the licence state, saved craft profiles, tune history and the last free log so a second analysis does not need another upload. Clearing site data removes them.

Your choices

• Use the desktop build to keep analysis entirely local.
• Clear site data to remove the local key, saved quads and history.
• Ask for deletion of a payment or support record by writing to easyquadtune@outlook.com. A payment record required for tax or dispute handling may be retained for the period the law requires, and the reply will say so.
• Decline analytics by blocking the script; the analysis still works.

Contact

Privacy questions and deletion requests: easyquadtune@outlook.com. This page is a description of current practice, not a legal certification, and it will be updated when the practice changes.

Easyquadtune is not affiliated with Betaflight. Published 2026-10-21. Measurements come from the maintainer's own flight logs; an example is illustrative of the method, not a tune for your aircraft.