Evästeilmoitus

Vaeroly uses as few cookies as possible.

The cookies Vaeroly sets

• Sign-in cookie (vaeroly_session, up to 14 days): keeps you signed in and carries a security token that protects forms from forgery. It is essential, is only sent over HTTPS and can't be read by scripts. Signing out ends your sign-in; the next form you open starts a new, signed-out one. Its contents are signed, so they can't be changed, but not encrypted: it holds your account number and that token and, for a moment, what the next page needs to show, such as a "Welcome aboard" message with your name or what you typed into a form that has to be shown again.
• Theme (theme, 1 year): set only when you pick light or dark, so pages open in your choice.
• Language (lang, 1 year): set only when you pick a language.
• EFB window (vaeroly_efb_window, 1 year): set only inside the Vaeroly app's own EFB window, so pages outside the EFB show a way back to it. It holds the short name of the airline whose EFB was open.

Cookies set by our hosting

• Server protection cookie (named server_session_…, about 10 days): set by the web server's protection layer in front of the site, which blocks floods of automated requests. It holds no personal data and isn't used for tracking.
• Network security cookie (such as __cf_bm, 30 minutes): our network provider may set it to tell people from bots.

What we don't use

No advertising, analytics or tracking cookies. Visits are counted by Cloudflare Web Analytics, which uses no cookies and doesn't follow you to other sites. The sign-in and security cookies are essential to running the site safely, and the theme and language cookies only remember a choice you made, so there is nothing to accept or decline.

Things your browser keeps

Your browser may also remember small preferences in its own storage, such as the map layer or which menu sections are open. Those never leave your device.

Other sites

Maps load tiles from OpenStreetMap / CARTO, and links to Discord, SimBrief, VATSIM or IVAO take you to sites with their own cookie policies.

Contact

Questions: [email protected]. See also the Privacy Policy.