SimNavLog (the "service") is operated by Virtual Void Stockholm AB, Sweden — the data controller for the personal data described here.

We keep only what is needed to run your account:

• Email address and a hashed password — to create your account, sign you in, and send account emails (confirmation, password reset, email change).
• Sign-in provider identifiers (e.g. Microsoft) — only if you choose to sign in with a third-party account.
• Flight plans you create (routes, waypoints and nav logs) — stored so you can save and reload your work. The shape of a route may additionally feed an anonymous shared collection, stripped of anything you typed; the terms explain what that means.
• Tours you create (the name, the goal in your own words, the briefing, the outline you draw, notes on its points, and a record of where you actually landed and when) — a tour is a binder around many flights, and everything in it is written by you. Stored so a long journey survives between sessions.
• Screenshots you attach to a flight — stored as JPEG copies for telling the story of the flight, and shown only to you. They are lossy copies, not your originals: keep your own.
• Problems you report — what you were doing, what you expected, and the context the page attaches: which plan you had open, its route, the build, and your browser's user-agent string. Sent to us by email as well as kept, so that the same fault reported three times reads as one bug rather than three mails a week apart.
• Your nav log settings (whether calculated values start visible, and which aircraft you picked as yours) — stored so the nav log opens the way you left it. They are included in the copy you can download.

Our lawful basis for processing your account data is performance of a contract — providing the service you asked for (GDPR Article 6(1)(b)). We do not use your data for advertising and we do not sell it.

Our server records ordinary operational logs for every request — the time, the page requested, and the IP address it came from. These are needed to keep the service running and to stop abuse such as password-guessing and sign-up floods. They are kept on the server only, capped in size and rotated away automatically; they are never stored in the database, never combined with your account, and never shared.

We set only strictly-necessary, first-party cookies: a signed session cookie, an optional "remember me" cookie (only if you tick that box at login), and a CSRF-protection token. The session cookie carries a random identifier for your browser session, so that two windows of the same plan can find each other; it names no person and is kept nowhere else. We use no analytics, advertising or third-party tracking cookies. Because these cookies are strictly necessary to provide the service, no cookie-consent banner is required.

We share your data with nobody by choice. What follows is what using the service entails — above all the map, which cannot draw itself without your browser asking somebody for tiles.

• Map tiles. The interactive map loads chart tiles directly in your browser from OpenFreeMap (the default base map), OpenStreetMap, OpenTopoMap, Open Flightmaps and (for US charts) Esri/ArcGIS. Those providers therefore receive your IP address and the map area you view — not because we send it to them, but because that is how a tiled map is drawn. The Esri/ArcGIS request involves a transfer to the United States.
• Weather and navigation data. METAR, winds-aloft, terrain, magnetic-variation and airport lookups are made by our server (not your browser) and send only coordinates or station codes — no personal data.
• Email delivery. Account emails are sent through an email provider, which processes your email address to deliver them.
• Signing in with Microsoft. Only if you choose it. Your browser goes to Microsoft, which tells us your account identifier and email address once you approve. Microsoft learns that you signed in to SimNavLog; we never see your Microsoft password. This involves a transfer to the United States.

You can, at any time:

• Access / export your data — download a copy from your account settings .
• Rectify your data — change your email or password from account settings.
• Erase your account — delete it from account settings. Your account, sign-in tokens, personal nav logs and tours are removed — a tour goes with its outline, its notes and its record of what you flew. Two things are kept, both detached from you and holding nothing that identifies you: the routes you created — the bare lists of waypoints, without the nav logs around them — which may feed the shared route collection the terms describe; and any problem you reported, kept as an anonymous record of a fault so that fixing it does not depend on your account still existing.

You also have the right to lodge a complaint with your national data protection authority. Ours is the Swedish Integritetsskyddsmyndigheten (IMY) .

Everything you store — your account, plans, tours and screenshots — is kept on one server rented from one.com in Copenhagen, Denmark, inside the EU. It is copied each night to an off-site backup, encrypted with a key that never sits on that server; the backups are kept for up to five weeks and then deleted.

We keep account data for as long as your account exists. A sign-up whose email address is never confirmed is deleted automatically after 7 days, together with everything stored under it — the flight plan it was working on, any plans it kept and any tours it started — and sign-in tokens expire after a set time. Error diagnostics, which may contain incidental personal data, are purged automatically after a few months. When you delete your account, your personal data is removed immediately, screenshots included; copies in the encrypted backups age out within five weeks.

The beta ending is not a retention event. An account made during the beta is an account, and the plans and tours in it are kept on the same terms as any other. We set no date at which beta data is cleared.

For any privacy question or data request, contact us at info.simnavlog@virtualvoid.se . We answer data-subject requests within one month (GDPR Article 12(3)).

We may update this policy as the service evolves. The date at the top shows when it last changed.