Privacy policy

• No sign-up, no login, no profile. We do not know who you are.
• Weight and balance, E6B and METAR decoding all run on your device. The numbers you type are never sent to us.
• We set no cookies and no advertising identifiers, and we run no ad network or affiliate tracker.
• Saved loadouts, your last numbers and your theme choice are kept in your browser and never sent to us. A saved home airfield and your recent airports are kept there too, but they are used to look weather up: the METAR page sends a saved home airfield's ICAO code to our weather lookup when it opens, and a recent airport's code when you tap it (section 3).
• Two things do reach a server: our own cookieless usage events, which carry no identifier and none of your numbers, and an airport's ICAO code - when its weather is looked up, and after a METAR decode, to fetch its runways for the wind table.
• We do not sell or share personal data, and we do no profiling.

KeepBlueUp is operated by Gaperi Consult S.R.L., a company registered in Romania with its registered office in Brasov. Gaperi Consult S.R.L. is the data controller for the processing described here. The full trader-identification details are on the terms page.

You can reach us about anything in this policy at contact@keepblueup.com. We have not appointed a Data Protection Officer, and are not required to.

Because the controller is established in the EU, the GDPR applies to this processing for every visitor, wherever you are. This policy is not scoped to European users.

Every calculation happens in your browser, and using the tools sends none of the following to our server, or to any service we use:

• aircraft empty weight, empty-weight arm, station weights and fuel;
• the pass or fail result and the centre-of-gravity position;
• E6B inputs - altitude, temperature, pressure setting, wind, airspeed;
• the text of any METAR or TAF you paste in (to show the wind on each runway, the page does ask for that airport's runways by its code - section 5);
• your name, email address, licence details, or any account data.

If you share a link to your numbers, the link itself carries them, wherever you send it - the numbers sit after a "#" in the address, a part your browser does not send to us when the link is opened.

There is no contact form and no newsletter. If you email us, we hold that email to answer it, and nothing more.

KeepBlueUp uses your browser's localStorage to make the tools work the way you left them:

• things you save on purpose - named loadouts and a home airfield;
• things it keeps for you as you go - your last weight-and-balance numbers, so the form reopens with them, and the airports you looked up recently, shown as one-tap buttons;
• your light or dark theme choice (under gaperi-theme; everything else sits under the keepblueup: prefix).

If you install the app or use it offline, your browser also keeps a copy of the site's own files (the pages, scripts and icons) in its offline cache. That copy holds nothing you typed.

That data is written and read by your browser. The airport codes in it are also used to make requests: each time the METAR page opens - unless a link names another airport - it looks up the weather for a saved home airfield, sending that airfield's ICAO code, and tapping a recent airport sends that airport's code. Those are the lookups of section 5. The rest - loadouts, your last numbers, your theme choice - is never sent to us or to any service we use; a link you choose to share carries your numbers wherever you send it (section 2). There is no sync, no backup and no telemetry attached to any of it. You can erase all of it by clearing site data for this domain in your browser settings, and the tools keep working normally without it.

Why this needs no consent banner: Article 5(3) of the ePrivacy Directive covers storing or accessing information on your device, and exempts what is "strictly necessary in order for the provider of an information society service explicitly requested by the subscriber or user to provide the service". Each of these writes and reads serves a tool you are using, for that tool to work as you expect - including reading a home airfield you saved so that its weather loads when you open the METAR page, and a recent airport you tap so that its weather loads. For everything else stored here there is a second reason: the EDPB has confirmed (Guidelines 2/2023, paragraph 44) that information generated and used inside the device is not a "gaining of access" as long as it does not leave the device, and the site never sends those items off the device - a link you choose to share is yours to send, and the numbers in it never reach us (section 2).

We count how the tools are used with our own usage events, not a third-party analytics service: no outside script, no cookie, no fingerprinting, and nothing stored on your device for it. When you open a page or use a feature, your browser sends one small event to our own server. It carries only:

• the event name - for example "page viewed", "weight and balance computed" or "link shared";
• the page path only, such as /wb or /e6b - never the rest of the address. The numbers of a shared load and the airport of a /metar station link travel after a "#" in the address, and an event never includes that part. Of the part after a "?", an event takes only the two kinds of tag in the next items, and nothing else;
• the domain of the website that linked you here, if any (such as m.youtube.com) - never the full address you came from;
• how the visit arrived: the short link from one of our videos, if you came by one (keepblueup.com/xwind adds ?ref=xwind to the address), and any campaign tags (utm) on the link you followed;
• for a link to your numbers that was shared, or a shared or station link that was opened, the tool's name (wb, e6b or metar) - never the numbers or the station;
• for a vote for the next aircraft profile, the aircraft type's key from our fixed list (such as dr400);
• for a click on a partner link, the partner's name - there are no partner links today (section 12);
• a counter of how many times that event has happened since the site was opened in that tab, which starts again whenever the page is reloaded or reopened.

Our server adds the time the event arrived and the country, which Amazon CloudFront, our content delivery network, derives from your IP address. The event record itself carries no identifier, no IP address and no user-agent: apart from that country, our server reads the request's headers only to filter out automated and forged requests, and stores none of them. Nothing in an event links one visit to another, so we count page loads, never people. And nothing you type into a tool is in it - no number, airport code, loadout name or result (section 2).

Browsers that send Global Privacy Control or Do Not Track, and automated browsers, send no usage events at all. The events are stored in our own AWS account in Frankfurt, Germany (eu-central-1), and deleted automatically after 12 months.

• Legal basis: Article 6(1)(f) GDPR, our legitimate interest in knowing which tools are used, whether they work, and which links and videos bring pilots to them. An event identifies no one, so the impact on you is minimal.
• To opt out, turn on Global Privacy Control or Do Not Track in your browser, or block requests to keepblueup.com/api/e: your browser then sends nothing, and the tools work identically. Because an event identifies no one, we cannot pick yours out of the log afterwards (section 10).

Decoding a METAR or TAF you paste happens in your browser, and the report text is never sent anywhere. Two lookups do send an airport's ICAO code: looking an airport's weather up by its code - when you type one, tap a suggested or recent airport, open a station link such as keepblueup.com/metar#LROP, or open the METAR page with a home airfield saved (section 3) - and, after any METAR decode, pasted or looked up, fetching that airport's runways to show the wind on each one. Those lookups and the usage events of section 4 are the only requests the tools make.

What happens in either lookup:

• Your browser sends the airport code to a small function we run on Amazon Web Services in Frankfurt, Germany (eu-central-1).
• As with any web request, that server sees your IP address and browser user agent alongside the code.
• Our server then asks the US National Weather Service Aviation Weather Center (aviationweather.gov) for that report. That second request is made by our server, so your IP address is not sent to the United States - the airport code is.
• After a decode, the page asks the same function for that airport's runway list and elevation (from aviationweather.gov, cached for a day), to show the wind on each runway. The same applies: the airport code travels, your IP address does not leave our server.
• The raw report comes back and is decoded in your browser. The report text itself is cached for up to a minute - in the function and at the CloudFront edge - so repeated lookups do not hammer the upstream service. The cache holds the report, not who asked for it. We do not build a history of what you looked up.

Legal basis: Article 6(1)(f) GDPR - performing the lookup you asked for and keeping the endpoint available and abuse-free. An airport code on its own is not personal data, and because we keep no request log (section 6) it is not stored alongside your IP address.

The site is delivered by Amazon CloudFront from storage in Frankfurt. We have not switched on CloudFront or API Gateway access logging, so we keep no per-request log: no record of your IP address, and none of the airport codes you look up. The usage events of section 4 count the pages that are opened, without any IP address or identifier.

Two logs are kept, both in Frankfurt and both deleted automatically (the retention is set in the infrastructure code, not by hand):

• The usage-event log - the events of section 4, kept for 12 months. The function that writes it adds its own technical records (start, end, duration and any error of each run), which carry no IP address and nothing from the request.
• The weather function's technical records - start, end, duration and any error - with no IP address and no airport code, kept for 30 days.

Amazon Web Services processes request data as our processor to deliver the site and protect it, for example against denial-of-service attacks.

Legal basis: Article 6(1)(f) GDPR, our legitimate interest in security and availability.

• Amazon Web Services EMEA SARL - hosting, content delivery, the weather-lookup function, and the usage-event function and its log. Region eu-central-1 (Frankfurt, Germany).
• Cloudflare, Inc. - the DNS for keepblueup.com, and Email Routing: mail sent to contact@keepblueup.com passes through Cloudflare, which forwards it to our mailbox. Cloudflare does not sit in front of the website - your page requests go straight to Amazon CloudFront.
• Email - the forwarded mail is kept in our mailbox, with our email provider, so that we can reply to you.

We do not sell personal data, we do not share it with advertisers or data brokers, and we run no ad network or affiliate tracking today.

Everything we store - the site's files, the usage-event log and the weather function's technical records - is in Frankfurt (eu-central-1). Amazon CloudFront answers each request, a usage event included, from an edge location near you, which may be outside the EU. The only data we ourselves send outside the EU is the airport code sent to the US National Weather Service for the lookups described in section 5. That request contains a public airport identifier and no identifier of yours. An email you send us is received by Cloudflare's mail servers, which may be outside the EU, before it is forwarded to our mailbox (section 7).

Where a provider is part of a US-headquartered group, transfers rely on that provider's standard contractual clauses and, where applicable, its certification under the EU-US Data Privacy Framework.

• On-device data: until you clear it. We cannot delete it for you, because it is stored only in your browser.
• Usage events: 12 months, then deleted automatically. An event carries no identifier, IP address or user-agent (section 4).
• Technical records: 30 days for the weather function; the usage-event function's are kept with the events, for 12 months (section 6).
• Emails you send us: kept as long as needed to handle the matter.

Under the GDPR you have the right to access your personal data, to have it corrected or erased, to restrict or object to processing, and to data portability. Where we rely on legitimate interests, you can object at any time.

In practice there is usually nothing for us to look up: with no accounts and no identifiers, we normally cannot connect a request to a specific visitor. Where we genuinely cannot identify you, Article 11 GDPR applies and we may have to tell you so rather than invent a match. If you can point us at a specific request - for example a timestamp and IP address - we will act on it.

Write to contact@keepblueup.com. You also have the right to complain to a supervisory authority: in Romania that is the ANSPDCP (dataprotection.ro), and if you live elsewhere in the EU or EEA you may complain to your own national authority instead.

There is no automated decision-making with legal or similarly significant effects, and no profiling.

KeepBlueUp is aimed at pilots and student pilots and is not directed at children. We knowingly collect nothing from them - and, having no accounts, we collect nothing identifiable from anyone.

None of this applies today. There are no ads on KeepBlueUp, no affiliate links, no consent banner and no advertising cookies. This section exists so the intention is on the record before anything changes, and because the change would be a rewrite of this policy rather than a footnote to it.

If we ever introduce display advertising or affiliate links:

• We would ask for your consent before any advertising or affiliate script loads, through a proper consent tool - not a banner that assumes a yes. Under EDPB Guidelines 2/2023 (paragraphs 49 to 51) affiliate tracking links and pixels fall inside Article 5(3) of the ePrivacy Directive, so they need consent too.
• We would publish, before switching anything on, which network is used, what it stores on your device, and where it sends data.
• We would add the opt-out controls US state privacy laws expect, including a "Do not sell or share my personal information" control, and honour the Global Privacy Control signal.
• Declining would keep every tool fully working. The calculators would never be paywalled behind consent.
• Nothing in the keepblueup: localStorage namespace would ever be sent to an advertising or affiliate network, or attached to an advertising identifier. That is the line that keeps section 3 true.

The current advertising and affiliate policy, including how any commercial relationship would be disclosed, is in section 12 of the terms.

If we change what we collect, we will update this page and move the date at the top. For a change that materially affects you - advertising being the obvious one - we will say so prominently in the product rather than quietly editing this page.

Gaperi Consult S.R.L., Brasov, Romania. contact@keepblueup.com.