1. Who is responsible
The operator of this site has not entered their details yet. Until they do, the legal notice is the place to look.
2. Visiting the site
Public profiles can be read without an account. Reading them stores nothing about you: the site sets no cookie for it, writes no log of the pages you view, and loads no scripts, fonts or styles from anywhere else - no analytics, no advertising, no tracking, no social-media buttons. The two outside sources a page may use - optional map views, each loaded only if a viewer chooses it - are described in sections 9 and 10.
To send you a page, the server necessarily handles your IP address and the request itself (the address of the page, your browser's identification). This application keeps no record of page views.
3. Your account
When you register, the site stores:
- Username - chosen by you and public: it is the address of your profile.
- E-mail address - to sign in, to confirm the account and to reset the password. It is shown on no public page.
- First and last name - asked for at registration and shown on no public page.
- Password - only as a one-way hash (Argon2id, or bcrypt where the server lacks it). Nobody can read it, the operator included.
- When the account was registered, when it last signed in, and whether its address is confirmed.
Your name, your e-mail address and these times are visible to you and to the site's administrators (in the list of accounts), to nobody else - except the month and year of your registration, which a published profile shows as "Member since" (section 4).
An account whose e-mail address was never confirmed, that never signed in and holds nothing is removed after 30 days.
4. What you enter, and what is public
The flights, duties, recorded tracks and uploaded files, your aircraft, airlines and settings are stored with your account to keep your logbook and work out its statistics. Crew names or codes of colleagues, passenger, cargo and fuel figures, registrations, the purpose of a flight, callsigns, filed flight plans and notes stay private: they appear on no public page, in no public data and in no figure shown to other accounts – except the route of a flight the pilot chooses to show on a Follow My Flight page: then its waypoints, airways and procedures (nothing else of the plan) are shown there, also on the public address.
Administrators. To help you - when you ask for support, to fix a fault, or to set up an account for you - the site's administrators can open any account and work in it as its owner does: they see the private pages with everything listed above and the profile, published or not, and they can change what is in the account, as you can. While they work in an account, a band at the top of every page reminds them whose account it is. The audit log records who opened which account and when, every change made while it was open (the page and the time, not what was typed), and when it was closed - by going back, by signing out, or because the administrator's session ended or their role was taken away; an account left open closes with the administrator's session at the latest, and if that session simply runs out, no time of closing is recorded. An administrator never learns your current password: a form that asks for it asks for the administrator's own. But they can set a new one, which ends every session of your account, and they can ask for the account's deletion as you can. They can also publish or unpublish your profile and switch your public Follow My Flight address on or off, as you can.
Public profile. A new account's profile is published from the start; you can unpublish it in Settings at any time, and publish it again. An account an administrator set up for you starts unpublished, until you or an administrator publishes it. A published profile shows your username, the month and year you registered ("Member since"), the one-line profile text if you write one in Settings, and, for each flight, the date, the flight number, the route and the times, the aircraft type and the airline, distances, altitudes, speeds and the recorded track - and the statistics made from these. In Settings you can also ask search engines not to index your profile.
Friends and teams. Other accounts can add yours to their friends, which shows them what your public profile shows and nothing more (only your username while the profile is unpublished), or to a team they created. A team shows its members each other's totals - flights, hours, distance, airports, countries, airlines, aircraft types - never a single flight. You can leave any team.
A flight you delete waits 30 days under "Recently deleted", where you can restore it, and is then removed for good.
5. Cookies and browser storage
The site uses three cookies of its own: two needed for signing in, and one for a pilot's flight schedule protected by a password (section 8) - none of them used for anything else:
| Cookie | What it does | How long |
|---|---|---|
faistat |
The session: keeps you signed in and protects forms against forgery. Set only when needed - when you open the sign-in or registration form or another form, when you open a private page (to bring you back to it after signing in), and while you are signed in. | Until you close the browser. A sign-in ends after 8 hours without activity and after 30 days at the latest. |
faistat_fp |
Ties your session to this browser, so that a stolen session cookie alone is useless. Set when you sign in. | 30 days; removed when you sign out. |
faistat_tm |
Remembers on this device that the password of a pilot's protected flight page was entered, so you are asked only once. Set only after you enter that password, and sent only to that page's address. It holds a time and a signature - no password and nothing about you. | Up to 400 days, renewed when you open the page after 30 days; it stops working at once when the pilot changes the password or signs every device out. |
All three are strictly necessary for a service you asked for, so they need no consent (§ 25(2) no. 2 TDDDG). There are no other cookies, and so no cookie banner.
The site's scripts remember a few display choices in your browser's local storage. They never leave your browser, and you can delete them there at any time:
theme- Light or dark display, once you choose one in the header; removed again when you go back to the system setting.timemode- Whether times are shown in UTC or local time, once you switch it.flight-form.unit.cargo_unit, flight-form.unit.fuel_unit- The weight unit you last chose for cargo and fuel in the flight form (signed-in area).fmf-units- Follow My Flight family page: whether heights and speeds are shown in metres and km/h or in feet and knots, once you switch it.fmf-basemap- Follow My Flight family page: which map view you chose - "Einfach", "Detailkarte" or "Satellit" (in English "Simple", "Detailed map" or "Satellite"; see "Map images from OpenStreetMap" and "Satellite images from EOX"), once you choose one. It replaces the earlier fmf-tiles (whether the "Detailkarte" was switched on), which the page removes the next time it is opened.fmf-follow- Follow My Flight family page: whether the map keeps following the aircraft, once you switch it.
Only if you switch on push notifications on a Follow My Flight family page, your browser also keeps a small script of this site for that page (a service worker) and the subscription with its push service (section 8). Both are needed for the service you asked for (§ 25(2) no. 2 TDDDG); switching push off on the page removes them.
6. Security records
- Sign-in attempts. Every attempt to sign in, every registration and every request for a confirmation or password-reset e-mail is recorded with the time, the IP address and the account concerned (for a name that matches no account: what was typed), to limit repeated attempts. Deleted after 30 days. So is every password entered on a pilot's protected flight page, wrong or right - with the time and the IP address (an IPv6 address shortened to its /64), never what was typed -, to stop guessing (15 minutes of limits) and to let an address that opened the page before keep doing so.
- Audit log. Security-relevant actions - signing in and out, failed sign-ins with the name or address that was typed, registration, password changes and resets, changes to settings and profile visibility, deleted flights, exports, backups and administrative actions - are recorded with the time, the account and the IP address, so that misuse can be traced. Entries are deleted after 400 days. The IP address in them is removed after 30 days; what stays is a keyed hash of it, which shows whether two entries came from the same address without showing the address. Entries written up to 5 Oct 2026, before this rule existed, keep their address until they are deleted.
- Error log. When the program fails, the time, the page requested and the technical details are logged so that the fault can be repaired - without your IP address. Each monthly log is deleted 90 days after its last entry.
- Mail log. When an e-mail cannot be handed over for delivery, the time, the recipient address and the subject are logged. Deleted after 30 days.
7. E-mail
The site writes to you about your account: a link to confirm your address when you register; a link to reset your password when you ask for one (it works for 4 hours, is stored only as a hash and removed once it has expired); if an administrator sets up an account for you, a welcome with a link to choose your password (the same, but working for 72 hours); a notice when somebody tries to register with your address; and a confirmation when you ask for your account to be deleted.
Recap e-mails. In the first days of each month (normally on the 1st) the site sends you a summary of your flights in the month before, and in the first days of January one of the whole year before (in place of the one for December). They go only to accounts with a confirmed e-mail address that have flights in that month or year, and hold only your own flight statistics - nothing about anybody else. They are on unless you switch them off: in Settings at any time, or with the link at the foot of every recap, which works without signing in.
No newsletters, no advertising. The messages leave through the mail server of the host (section 11).
8. Follow My Flight
Follow My Flight lets a pilot with an account here share a duty day, or a trip of several days, with family and friends: a page shows where the aircraft is, the flights and a few lines from the pilot.
- What a duty day records. Only during the pilot's duty - from its start until the pilot ends it or, if the pilot does not, at the latest 3 hours after its planned end (the pilot can choose 1 to 24 hours), never before and never after - the server asks public ADS-B networks for the position of the aircraft the pilot entered for the day, and stores what they report (time, position, height, speed, heading) with that day. For a pilot who has entered their own Flightradar24 or FlightAware key in their settings, while those networks receive nothing of the aircraft (and, when the site suspects that the aircraft is heading for another airport than planned, also while they do), these commercial services are asked as well, with that pilot's own key, and what they report is stored the same way. Around each take-off and landing those networks have not seen for certain, Flightradar24 is also asked for its record of when the flight took off and landed - with the pilot's own key or, for a pilot without one, an administrator's while he lends it (below) - and that also while the networks receive the aircraft, unless they have just seen it at the gate or climbing away, or in the air or down at its arrival until a quarter of an hour after its expected landing; the times it reports are stored with the flight. While a flight is in the air - the pilot's own, and one the pilot takes as a passenger (below) - Flightradar24 is also asked, with that pilot's own key, for the time it expects the flight to land: by the aircraft's registration, soon after the take-off and then about every 15 minutes, more often towards the landing - also while those networks receive the aircraft; the position in its answer is stored the same way. For the pilot's own flights this is done only while one of the pilot's links shows that day or trip. With it the site keeps what the pilot entered: the flights (airports, times, aircraft), short messages, and the name and picture the pilot chose for the page. And photos of the pilot's own aircraft, each with the photographer's name where the pilot gives one: a photo is shown on the page only while the pilot flies that aircraft or is about to, and only on days that show its registration. The picture and the photos are kept without their location, camera or time, and are in no backup. Nothing is recorded about anybody else on board.
- What a trip records. A trip of several days takes its times from its flights. Its aircraft's position is fetched only around the pilot's own flights - from 3 hours before each departure until 1 hour after its landing is received; when the last flight lands somewhere other than planned, until 6 hours after its expected arrival, in case it flies on; when no landing is received, at the latest 6 hours plus the review hours above after its expected arrival - and nothing between the flights or overnight. For a flight the pilot takes as a passenger nothing is fetched either, unless the pilot has entered their own Flightradar24 key: then its flight number is sent to Flightradar24 to show that airline flight live, from half an hour before its departure until it has landed, at the latest an hour after its expected arrival (a flight late and still on its way then, up to three hours longer). For that, the airline aircraft's Mode-S address is sent to the free networks named below, and its registration to Flightradar24 while they receive none - and, in the air, also while they do, for its expected arrival (above); its positions are stored with the trip. From them, and from Flightradar24's record of that flight, the site takes when it took off and landed, shows it on the page and sends the e-mails about it like those of the pilot's own flights. After a landing, for a pilot who has entered their own Flightradar24 key, Flightradar24 is asked once for the track that flight flew - the pilot's own and one taken as a passenger - and its measured points are drawn on the map, which then names Flightradar24. What is stored, and what else the site keeps, is the same as for a duty day.
-
Who can see it. People who have one of the pilot's secret links and,
while the pilot has switched it on, anybody who opens the public address
/follow/<username>on this site. That address is made of the pilot's public username - which also leads to the pilot's profile - and cannot be kept secret. Only days and trips the pilot published are shown - a trip from up to 7 days before it begins (3 hours before its first flight) until 24 hours after it ended, shortly after its last landing; while none is, a link shows that nothing is shared. A secret link is 64 characters that cannot be guessed; the pilot can let it expire or revoke it at any time, and switch the public address off, after which it answers like a page that does not exist. The page shows only what the pilot released: never the pilot's real name or e-mail address, the aircraft's transponder (Mode-S) address, crew or passengers - and the account's username only in the public address; the registration, the flight number and the duty times only where switched on, except the flight number of a scheduled flight the pilot takes as a passenger, which is shown; the planned route (waypoints, airways and procedures of the filed plan), where the pilot shows it; and, if the pilot chooses, a delayed or an approximate position. A pilot's flight schedule protected by a password (below) is seen by whoever the pilot gives its password to. -
Opening a family page. It - the public address too - sets no cookie,
starts no session and asks search engines not to list it. The site counts how often a link is opened - at most
once every five minutes - and when it was last opened, so the pilot sees whether it is
used; it records neither who opened it nor their IP address. Three display choices stay
in your browser (section 5). Your browser loads nothing from other
sites unless you choose the map view "Detailkarte" or "Satellit" ("Detailed map" or
"Satellite" on a page in English, sections 9 and 10). Unlike a family page, a pilot's flight schedule protected by a password (below) sets the
cookie
faistat_tmonce its password is entered. -
A flight schedule protected by a password. A pilot may show family and
friends a page with their duty roster as a calendar, their current flight - live while it is
followed as above - and a map of the routes they have flown, at an address of its own under
/track-me/…on this site. It opens only with a password the pilot gives out; before that it shows nothing about the pilot. The server - never your browser - fetches the roster from the crew-scheduling system of the pilot's airline (LEON,*.leon.aero) with a private link only the pilot enters, about every 15 minutes (every 5 minutes around a duty), and sends LEON nothing else. It keeps every entry of the roster that has a route - flights, transfers, simulator sessions, and the few the site does not recognise or that last all day, which the page never shows - with its times, airports, the aircraft's registration and the flight's callsign and, for a flight as a passenger, the airline; never a note, crew or passengers. It keeps them also once LEON no longer lists them and after the pilot removes the roster's link, until the account is deleted (then in the backups until they are removed); the operator deletes them earlier on request (section 1). The page shows the registration and the flight number only where the pilot switches them on, transfers and simulator sessions only as what they are ("mit der Bahn", "Simulatortraining"), and, if the pilot chooses, the pilot's older flights from the logbook on the route map - as pairs of airports, nothing else of them. Opening it records nothing about you: it starts no session, and the site counts only how often it was unlocked. Once you enter the right password, the cookiefaistat_tmremembers it on this device (section 5); every password entered is recorded like a sign-in attempt (section 6). -
Other services the server asks. The server - never your browser -
contacts these services and sends each only what is listed here; never a name, an
e-mail address or the IP address of anybody who looks at the page:
adsb.fi,ADSB.loland theOpenSky Network- the aircraft's Mode-S address, for its position (OpenSky at times also the area around its last known position, and the address again for the flown track) - for a flight as a passenger shown live also the airline aircraft's;adsbdbandhexdb.io- a registration or a Mode-S address, for the aircraft's type and its Mode-S address;Open-Meteo- an airport's coordinates, for the weather there;LEON(*.leon.aero) - only for a pilot who entered their own roster link there: that link, to fetch their roster for the page protected by a password;FlightAware AeroAPI- for a pilot who has entered their own FlightAware key: a registration, for the aircraft's scheduled flights (once more when the site suspects a diversion), and FlightAware's own reference of the flight, for its position while the networks above receive none.Flightradar24- for a pilot who has entered their own Flightradar24 key: the aircraft's registration, for its position while the networks above receive none, and while a flight is in the air - also while they receive it - for the time Flightradar24 expects it to land; when the site suspects that the aircraft is heading for another airport than planned, up to 3 times a flight its registration again - also while the networks above receive it - for where Flightradar24 has it heading and the position it reports; for a flight as a passenger its flight number, to find that airline flight, and then that aircraft's registration in the same way, and Flightradar24's own reference of that flight, for its record of when it took off and landed; after a flight landed, once, its reference, for the track it flew. Around the take-offs and landings of the pilot's own flights also the registration - or else the callsign or flight number - with the time of the flight, for Flightradar24's record of when it took off and landed.
- E-mail notifications. On every secret link of a pilot, a visitor can ask for an e-mail when the duty starts, a flight takes off or lands and the duty ends - for a trip of several days only when a flight takes off or lands. On the public address, where the pilot allows mails there, anybody may ask for them. An address that chooses "Neue Flüge" ("New flights") also gets an e-mail when the pilot adds flights: one for several, 5 minutes after the last one added (at the latest 30 minutes after the first), and only once a page of that link shows them - a flight the pilot takes as a passenger with the flight number only where the page shows it. An address may also choose an e-mail about 30 minutes before a departure and before a landing and when a departure time moves by 15 minutes or more (at most 3 times a flight) - on a trip as well - and, where the pilot has entered their own FlightAware or Flightradar24 key, when one of those services confirms that a flight is heading for another airport than planned. These mails tell no more than the page shows. The address is stored with the link and the events chosen and used for these mails only. Nothing is sent until it is confirmed with the link in a confirmation mail (double opt-in); that link works 7 days, and an address never confirmed is deleted after 7 days. At most 60 mails a day go to one address, and every mail has a link to unsubscribe with one click; a mail about an event also links a page where the address can change what it hears about, for every page of the pilot it signed up on. The address is deleted then, and also when the pilot revokes or deletes the link or stops allowing mails on the public address, and 30 days after the link expired. To limit misuse, a request for notifications is recorded with the time and the IP address, like a sign-in attempt (so is a change saved on that page), and deleted after 30 days; confirming and unsubscribing are written to the audit log with the time and the IP address, but without the e-mail address (section 6). Which notification went to which address is kept 90 days, so that none goes twice. For the pilot's own pages the site also keeps, for 30 days, what became of each notification for each address - sent, refused by the mail server, or why it was not sent - with the address shortened to its first letters (such as "t***@g***.de"); and the pilot can send a test notification to their own address or, after confirming it, to the addresses of one link (at most 5 a day). When a take-off, a landing or a notification that should have come in has not, or the scheduled job has stopped, the site mails an alarm to the pilot and to the site's administrators: it names the flight (its route and number, whether it was flown as a passenger, the callsign seen) and never a family member's address. The mails leave through the mail server of the host (section 11).
- Push notifications. On every secret link, and on the public address where the pilot allows notifications there, a visitor can also switch on push notifications in their own browser, for the same events and by the same rules as the e-mails: after a tap on the page the browser asks whether the page may show notifications, and only a yes switches them on - that is the consent. The browser then gives the site an address at its push service and two keys; the site stores them with the link, the language and the events chosen, and uses them for these notifications only. Each message is sealed on the server with keys only that browser holds (end-to-end encryption), and goes through the push service of the browser's maker: Google (Firebase Cloud Messaging) for Chrome, Edge on Android and most browsers on Android, Mozilla for Firefox, Apple for Safari, Microsoft for Edge on Windows - companies that may process data in the United States. The push service receives that address, the time and size of each sealed message, this server's IP address and the site's public key - never the message itself, a name or an e-mail address. At most 60 notifications a day go to a browser for each page it switched them on for (each page is a subscription of its own). The subscription is deleted when push is switched off on the page, when the pilot revokes or deletes the link or stops allowing notifications on the public address, 30 days after the link expired, when the push service reports that it has ended, and after 365 days without a notification. To limit misuse, switching on, and a renewal of the subscription by the browser, are recorded with the time and the IP address, like a sign-in attempt, and deleted after 30 days. Which notification went to which browser is kept 90 days, so that none goes twice. What stays in the browser is said in section 5.
-
Notifications by SMS or WhatsApp. A pilot who has entered their own API key of
the SMS service seven.io in their settings can offer these on their pages - on every secret
link and on the public address where it allows notifications - for the same events as the e-mails except the notices before a departure and before a landing, about a new departure time and
about a diversion, which never go by SMS or WhatsApp, and by the same
rules. A visitor who wants them gives a German, Austrian or Swiss mobile
number and chooses SMS or WhatsApp and the events; a 6-digit code is sent to that number on
that channel, valid 10 minutes, and only once
it is typed on the page is the number signed up - that is the consent. The number, the
channel, the events chosen and the language are stored with the link, the code only as a
keyed hash. To send the code and every notification, the number and the text are passed to
seven.io GmbH, Kiel, Germany, which sends them on the pilot's own seven.io account, as the
pilot's processor - the pilot pays for every message. A WhatsApp message is passed on by
seven.io to WhatsApp (WhatsApp Ireland Ltd., part of Meta), which delivers it from the
pilot's WhatsApp Business account and may process data in the United States. Every message
ends with a short link (
/s/…) that stops the messages with one press; the number is deleted then from every page of that pilot, and also when the pilot revokes or deletes the link or stops allowing notifications on the public address, 30 days after the link expired, when the pilot switches that channel off or removes their seven.io key, after 180 days without a message, when the SMS service reports that it is no valid number, and - never confirmed - after 24 hours. At most 20 messages a day go to one number, and at most 2 codes in 24 hours. To limit misuse, a request for a code is recorded with the time, the IP address and a keyed hash of the number (never the number), and every code typed on the page with the time and the IP address, like a sign-in attempt, and deleted after 30 days; confirming and stopping are written to the audit log with the time and the IP address, but without the number (section 6). Which message went to which number is kept 90 days, so that none goes twice. - How long. The positions of a duty day are deleted 30 days after the day ended, those of a trip as long after the trip ended; the pilot can choose between 1 day and 365 days. The day itself, its flights and messages stay until the pilot deletes them.
9. Map images from OpenStreetMap
The maps on this site are drawn from land outlines that this site serves itself (Natural
Earth), and the globe's picture of the Earth comes from this site too (NASA). The map code
also offers an optional background layer of OpenStreetMap map images, which is off unless
a viewer switches it on. Only then does your browser load images from
tile.openstreetmap.org, run by the OpenStreetMap Foundation (United
Kingdom), and in doing so sends it your IP address and the usual details of a browser
request - which images it asks for, and so which area you look at; as the page asking,
only this site's address, never the address of the page itself. Their privacy policy:
osmfoundation.org/wiki/Privacy_Policy.
On a Follow My Flight family page this layer is the map view "Detailkarte" ("Detailed
map" on a page in English), not shown until you choose it; the page remembers the view
you chose in your browser (section 5).
10. Satellite images from EOX
The map code also offers an optional satellite view: a cloud-free picture of the Earth made
from Copernicus Sentinel-2 data (EOxCloudless 2025), with place names, borders and roads
drawn over it. It is off unless a viewer chooses it. Only then does your browser load these
images from tiles.maps.eox.at, run by EOX IT Services GmbH, Thurngasse 8/4,
1090 Wien, Austria, and in doing so sends it your IP address and the usual details of a
browser request - which images it asks for, and so which area you look at; as the page
asking, only this site's address, never the address of the page itself. Their privacy
policy: eox.at/privacy-notice.
On a Follow My Flight family page this is the map view "Satellit" ("Satellite" on a page
in English), not shown until you choose it; the page remembers the view you chose in your
browser (section 5).
11. Hosting
The site, its database, the uploaded files and the backups are hosted by ALL-INKL.COM - Neue Medien Münnich, Hauptstraße 68, 02742 Friedersdorf, Germany, which processes them on the operator's behalf as a processor under Art. 28 GDPR.
12. Backups
The database and the uploaded files are backed up on the server, encrypted. Kept are the newest 30 daily, 12 weekly and 12 monthly backups - about a month, a quarter and a year; older ones are removed. A backup the operator makes by hand is kept until the operator deletes it. A backup holds the data as it was on its day, so something you delete stays in the backups made before until they are removed in turn.
13. Legal bases
- Art. 6(1)(b) GDPR - providing the service you signed up for: your account, your logbook and its statistics, the public profile while you keep it published, and the e-mails about your account - the recap e-mails too, while they are switched on; and Follow My Flight for the pilot who uses it.
- Art. 6(1)(a) GDPR - consent: the Follow My Flight e-mail notifications, given with the confirmation and withdrawn at any time with the unsubscribe link in each of them; and its push notifications, given with the browser's own question on the page and withdrawn at any time by switching them off there or in the browser's settings; and its notifications by SMS or WhatsApp, given with the code typed on the page and withdrawn at any time with the link at the end of each message.
- Art. 6(1)(f) GDPR - the legitimate interest in a site that is secure and keeps working: delivering the pages, limiting sign-in attempts, the audit, error and mail logs, and the backups; and, when a viewer chooses them, the OpenStreetMap map layer and the EOX satellite view.
14. Your rights
- Access (Art. 15 GDPR) - most of it you see in your private area; the export below gives you all of your data.
- Rectification (Art. 16) - you can correct your flights and your profile yourself, or ask the operator.
- Erasure (Art. 17) - you can delete flights yourself, and "Delete my account" on your profile page deletes the account with everything in it: the profile is unpublished at once and the account deleted after 7 days, unless you cancel before.
- Restriction of processing (Art. 18).
- Data portability (Art. 20) - "Export" in your private area gives you your flights as JSON or CSV.
- Objection (Art. 21) to processing based on legitimate interests.
- Complaint to a data protection supervisory authority (Art. 77), for example where you live or where the operator is based.
For anything you cannot do yourself, write to the operator (section 1).
15. How long what is kept
| What | Kept |
|---|---|
| Your account and everything you entered | Until you delete it or the account (then in the backups until they are removed) |
| Sign-in attempts and the limits on sign-in, registration and account e-mails, with the IP address | 30 days |
| Audit log of security-relevant actions | 400 days; the IP address in it is removed after 30 days |
| Mail log of refused or failed deliveries, with the recipient address | 30 days |
| Error logs (no IP addresses) | 90 days after the last entry of the month |
| Password-reset links | usable for 4 hours (the welcome link of an account an administrator set up: 72 hours), removed once expired (checked daily) |
Session cookie faistat | Until the browser is closed; a sign-in ends after 8 hours without activity, 30 days at the latest |
Cookie faistat_fp | 30 days; removed when you sign out |
Cookie faistat_tm | Up to 400 days, renewed when you open the page; ends at once when the pilot changes the page's password or signs every device out |
| Backups | About a month (daily), a quarter (weekly), a year (monthly) |
| Follow My Flight: the aircraft positions of a duty day or a trip | 30 days after the day ended (the pilot can choose 1 to 365 days) |
| Follow My Flight: e-mail addresses for notifications | Until unsubscribed, or until the pilot revokes or deletes the link or stops allowing mails on the public address; 30 days after the link expired; never confirmed: 7 days |
| Follow My Flight: which notification went to which address | 90 days |
| Follow My Flight: what became of each notification, with the address shortened (the pilot's delivery log) | 30 days |
| Follow My Flight: push subscriptions (a browser's push address and keys) | Until switched off on the page, or until the pilot revokes or deletes the link or stops allowing notifications on the public address; 30 days after the link expired; when the push service reports it ended; after 365 days without a notification |
| Follow My Flight: which push notification went to which browser | 90 days |
| A flight schedule protected by a password: the entries of the pilot's roster | Until the account is deleted (then in the backups until they are removed), also once the roster no longer lists them or its link is removed; earlier on request to the operator |
| Follow My Flight: mobile numbers for SMS or WhatsApp notifications | Until stopped with the link in a message, or until the pilot revokes or deletes the link or stops allowing notifications on the public address, switches the channel off or removes their seven.io key; 30 days after the link expired; after 180 days without a message; never confirmed: 24 hours |
| Follow My Flight: which SMS or WhatsApp message went to which number | 90 days |