Privacy notice

The one thing to take away

Sydeslip does not house or keep your data. Nothing is sent to or stored on a Sydeslip server. Your flying lives in your MyFlightBook account; the few records MyFlightBook has no room for live in this browser, on this device, and nowhere else. Keeping a copy of those is yours to do — Import & export → Back up now writes one to your device.

Sydeslip is an alternate way to read your MyFlightBook logbook. This explains what happens to your information when you use it.

The short version: Sydeslip’s server stores nothing about you. Your logbook stays in MyFlightBook, under your own account. We never see your MyFlightBook password.

There are, however, a few records MyFlightBook does not store, and those live only on your own device. This trade-off is real and worth understanding before you rely on it: because those records are only on your device, they can be destroyed — by you, or by your browser. That is set out below.

Your logbook stays with MyFlightBook

Your flights and aircraft belong to your MyFlightBook account and are governed by your relationship with MyFlightBook, whose own privacy policy applies to them. Sydeslip reads them to draw a page and keeps no copy on any server.

Sydeslip is an independent project. It is not affiliated with, endorsed by, or operated by MyFlightBook.

We never see your password

Signing in happens on MyFlightBook’s own website. You type your password there, and Sydeslip receives only an access token — a key that lets it read your logbook on your behalf, which you can revoke from your MyFlightBook account at any time.

That token is stored in your browser, on your device, and is never sent to a Sydeslip server.

What stays on your device

MyFlightBook has no field for some of the things a pilot needs to keep. Sydeslip stores these in your browser’s own storage, and they are never sent to Sydeslip’s server:

• Your pilot profile — name, photo, contact details, licence number
• Certificates and ratings, including your medical certificate
• Flights you import before signing in — once you are signed in, an import goes to your MyFlightBook logbook instead
• Aircraft profiles — photo, equipment, notes
• Endorsement signatures — including your instructor’s name, certificate number and drawn signature
• Coordinates you enter for airfields the built-in dataset does not list

Two of these deserve particular care

Your medical certificate says something about your fitness to fly. An instructor’s signature is somebody else’s personal data, not yours — they never installed Sydeslip and have no relationship with it.

Both are why Sydeslip keeps these records on your device and offers no cloud, no account and no sharing. It is a deliberate limit rather than a missing feature.

What the server can see

Sydeslip’s server is a stateless pipe. It holds no database, no file storage and no session store, and it sets no cookies. Requests to MyFlightBook pass through it and are forgotten.

Being honest about what that still leaves: our hosting provider (Cloudflare) keeps standard web-server logs — your IP address, the time, the address of the page or data you requested, and your browser’s user-agent string. An IP address is personal data.

What those logs do not contain: your access token, which travels in a request header rather than in a web address and is never written to a log; and the contents of your logbook, because request and response bodies are only ever forwarded, never read or recorded.

There is no analytics, no tracking and no advertising on Sydeslip, and no third-party code runs on the page at all — your browser is instructed to refuse it.

The desktop app asks one question over the internet, and this is the whole of it: when it starts, it fetches a small file saying what the current version is, so it can tell you if yours is out of date. It has no other way to know. That request reaches our hosting provider like any other, so the same logs apply — your IP address and the time. Nothing else is sent: no identifier, no account, nothing from your logbook. Nothing is stored on your machine to recognise you by, and nothing is downloaded or installed.

We do count those requests, and we would rather say so than let you find out: it is how we know roughly how many people use the desktop app, and from which countries. Because nothing identifies an installation, "how many people" is an estimate rather than a number — two pilots behind one router look like one, and one pilot on a changing address can look like several. We decided that was the right trade, and it is why there is no identifier to make it exact.

One exception, and it is a real one: the map

The Map page draws its background from OpenStreetMap, whose tile servers are not ours. When you open that page your browser requests map tiles directly from them, so OpenStreetMap sees your IP address and which tiles you asked for — which is to say, roughly the part of the world you fly in. Your browser also tells them the request comes from Sydeslip — our site address only, not which page you are on — because OpenStreetMap asks every site using its map to identify itself this way. Their use of that is governed by OpenStreetMap’s own privacy policy.

No route, flight, aircraft or personal detail is sent with those requests — a tile request is a map square, not your logbook. But it is a request to somebody else’s server, and it is the only one Sydeslip makes to anyone other than us. If you would rather not make it, simply don’t open the Map page; nothing else in the app reaches a third party. (The desktop app’s version check, described above, goes to our own hosting, not to anyone else.)

Losing your records

This is the part most worth reading twice. Because the records listed above live only in your browser, they are destroyed if you clear your browsing or site data for Sydeslip, if you delete the app from your home screen — on iOS that removes its storage with it — or if you simply use a different device or browser, because nothing is synced anywhere.

Your browser may also clear that storage on its own if the device is short of space, or if you have not opened Sydeslip for a long time. Sydeslip asks your device to keep its storage, which helps, but it is not a guarantee.

Nothing is backed up anywhere unless you do it. Use Import & export → Back up now and keep the file somewhere safe. Sydeslip reminds you periodically, and the reminder is meant.

Your flights are unaffected by any of this — they are in your MyFlightBook account, including ones you imported through Sydeslip, which are added to your MyFlightBook logbook rather than kept here. Back them up there, on MyFlightBook’s own pages.

Your control over it

Take it with you: Import & export produces a complete JSON backup and a CSV, so nothing is ever trapped here. Erase it: the Profile page removes every Sydeslip-owned record on the device in one action, and does not touch anything in MyFlightBook. Revoke access: you can withdraw Sydeslip’s access to your logbook from your MyFlightBook account at any time, independently of anything here.

The records listed above are on your device rather than on a server, so there is nothing for us to look up, correct or delete on your behalf — those controls are in your hands rather than ours. The one thing held on our side is the web-server logs described above. If you want to ask about those, or exercise a right you have over them, use the contact address below.

Complaining about it

It is worth restating what a complaint here could be about, because it is very little: we do not keep your data. It is not sent to or stored on our servers. Your flying lives in your MyFlightBook account, and the rest lives on your device. The only thing held on our side is the short-lived web-server logs described above.

With that said: if you are in the EU or EEA you have the right to complain to a data protection supervisory authority. Sydeslip is operated from Sweden, so ours is the Swedish Authority for Privacy Protection — Integritetsskyddsmyndigheten (IMY), at imy.se. You can also complain to the authority in the country where you live.

A complaint about the flights themselves belongs with MyFlightBook, who hold them, and their own privacy policy applies to them.

Children, changes and contact

Sydeslip is for pilots keeping their own flying records and is not directed at children.

If this notice changes materially, the date above changes with it, and the change is described in plain language.

Sydeslip is operated by Gavin Jeffries, in Sweden. Contact: privacy@sydeslip.com.

Terms of use · Back to sydeslip.com