WingLog ← Home RU

Document

Privacy policy

Effective from 08.11.2026

Short version: the logbook works without an account and keeps everything on your device. An account is optional: it is needed for internet sync, pilot groups and WingLog Pro. With an account, the server receives your email address and whatever you choose to send to other pilots. Details below.

What data the app collects

Without an account — none. Flights, equipment, spots, tracks and photos stay on your device; the developer does not receive them.

You don't have to create an account. If you do, the WingLog server receives only what is described in "Account", "Sync and cloud backup", "Pilot groups and track sharing" and "Notifications".

There is no third-party analytics and no ad networks in the app; nothing is tracked, either inside the app or across other apps on the device. The developer learns how many people use the app from anonymous marks with no identifier, which the version from the website sends along with the update check (details in "Checking for updates").

Where the data is stored

Flight records, equipment, spots, IGC tracks and photos are stored locally on your device: on Android — in the app's private storage, which other apps cannot access; on Windows and Mac — in the app's data folder in your user profile. It is an SQLite database plus files next to it.

On Android, uninstalling the app deletes all this data for good — keep a backup separately if you need one. If you are signed in, the logbook stays in the cloud copy and on your other devices.

Account (optional)

The logbook works without an account, as before. An account is needed for internet sync, pilot groups and WingLog Pro.

For an account we store your email address, the dates you signed up and last signed in, your connected devices (device name and type), your Pro expiry date if you paid for Pro, and the groups you belong to. You sign in with a one-time code sent by email; there are no passwords. Sign-in keys are stored on the server only as hashes. The IP address at sign-in is used to stop anyone guessing the code by brute force. One account works on up to 5 devices.

You can delete your account in the app: Settings → Account → Delete account. This also deletes your devices, your sync data, the tracks you sent and the tracks sent to you. Flights you sent to an instructor for an exercise stay in the group's training journal until the group is deleted.

Sync and cloud backup

Logbook entries and flight files are encrypted on your device with your account key (XChaCha20-Poly1305). For sync, encrypted packages are kept in Yandex Object Storage (Russia) until they reach your other devices, and for no longer than 30 days.

Cloud backup. While you are signed in, the app keeps an encrypted copy of your logbook — entries, tracks and photos — in the same storage, plus copies for the last 30 days. Photos in the backup are reduced to Full HD; free accounts get up to 300 MB of photos, WingLog Pro up to 1 GB. This lets you bring the logbook back on a new device after signing in by email.

So that the backup can be restored without your old device, the account key is also stored on the server — encrypted with a separate server key and kept apart from the backup itself. The server gives it only to your device after you sign in with the code from your email; your other devices are notified about every sign-in from a new device. Technically the developer can decrypt the backup, but does not do so and does not pass it to third parties, except where the law expressly requires it.

You can delete the backup: Settings → Cloud backup → Delete the cloud backup. The backup is also deleted together with your account, and if you do not sign in for 12 months — you get an email 30 days before.

Pilot groups and track sharing

In a pilot group, members see the name you entered when you joined. Your phone number, full name or other details are not needed.

When you yourself send a flight to a pilot or to a group, the recipients see its track: exact coordinates and times, altitude, takeoff and landing places, duration and distance. A pilot sees what was sent to them personally; a group sees what was sent to the group. In a group with a training program, the instructor sees the flights a student sends for an exercise and grades them.

Group tracks are not encrypted on your device, because every member has to be able to see them. On the server the files are encrypted with a server key, stored in Yandex Object Storage (Russia) and given only to the people you sent them to. How long tracks are kept: a group track for 12 months, a personal track for 6 months, a flight sent for an exercise for 12 months. After that the file is deleted from the server.

You can withdraw a track you sent at any time, and it disappears for its recipients. Copies a recipient has already saved on their device (for example, by opening it in a session) cannot be deleted. The app adds the takeoff place of a received track to your "Spots" on the device if you don't have that place yet.

Debrief. A pilot you sent a track to can add notes to it and send them back to you: text, a moment in the flight, a camera view and a drawing. Only you can see them.

Reports and blocking. You can report a pilot: the report, with its reason and your comment, goes to the developer by email. You can block a pilot so they can no longer send you tracks. A group's creator can remove a member.

Group competitions. Together with a flight sent to a group, its XC points (calculated on your device), the wing class from your equipment: A–D, CCC or tandem, — and the launch type go too: motor flights count only in the group totals, groundwork nowhere. Flights sent to a group make up the group totals, the season table, spot records, challenges and the flight of the week — the group's members see them. The flight's numbers (day, launch place, duration, distance, points, wing class) are kept even after the track itself is deleted in 12 months — until you withdraw the flight, delete your account or the group is deleted. The group's creator may leave a flight out of the scoring — you will see a note and the reason.

Reactions. The icon you put under a track is seen by the group's members (under a personal track — by its sender) together with your name in the group. You can remove a reaction at any time.

Tournaments. If you take part in a group tournament, your name in the group, wing class, place and result are seen by the group's members, and the organiser can export a PDF report with them. On the public results page winglog.pro/t/<code> your name appears only if you agreed to it when registering, otherwise it shows "The participant hid their name". There are no tracks or launch places on that page. You can hide your name or leave the tournament at any time before the results are final. In task tournaments (route, checkpoint collection, speed section, speed over a triangle, GPS landing, declared route) your device works out the task result from the track — time, distance, points taken, distance from landing to the target — and sends only these numbers to the server. A declared route (points, day and time of the declaration) is kept on the server until you delete your account. In a landing accuracy tournament, round results are entered by judges appointed by the group's creator.

Challenges 2.0. Group challenges include only those who pressed "Join" (in "Together" and secret challenges — the whole group); their name, value and medal are seen by the group's members. Duel: the challenge, your answer, the score and the stake are seen by you and your rival, ongoing and finished duels by the group's members; for a "growth" duel the server computes your average month from your group flights. Pilot's word — your goal, its progress and reactions to it are seen by the group's members; you can take the word back at any time. A spot crown ("King of the hill") and titles are computed from group flights and seen by its members; the group's creator can turn crowns off. With a flight sent to a group, the local takeoff time goes too — for tasks like "takeoff before 10 am". The trail you choose is stored in your account and seen by those who view your track in a group.

WingLog challenges for everyone. Only with your consent the app sends the numbers of your flights for the last 400 days to the server: day, local takeoff time and place, duration, distance, points, figure and launch type — without the track and without your name. They make up your medals and the challenge totals; other participants see only the totals. You can leave at any time — the numbers are deleted at once.

The personal monthly goal is computed on your device and is not sent anywhere.

Personal achievements are computed on your device from your logbook. If you are signed in, the app sends the server only the list of medals you have earned — their keys (for example, "XC per flight, silver"), without flights, dates or numbers. From these lists the server counts what share of WingLog pilots has a medal (you see only percentages) and returns the numbers for the "Community" medals from your tracks, reactions, crowns, duels and tournaments in groups. Your showcase — up to three medals you choose — is seen by the members of your groups. The list is deleted together with your account.

Story cards are drawn on your device. For the "Map" design the app downloads elevation tiles (Mapterhorn) of the place where you flew — the same way as for the 3D view.

Notifications

To send notifications (a new track, a debrief, a grade, a task), we store your device's notification token. Depending on your phone, notifications are delivered through Firebase Cloud Messaging (Google) or RuStore Push (VK). The text of a notification may contain the name a pilot entered in the group and the group's name. The RuStore SDK itself sends crash reports and delivery statistics to VK. You can turn notifications off in your phone's settings, or mute a single group with "Mute notifications".

WingLog Pro and payment

Pro payments are handled by Robokassa. You enter your card details with Robokassa — the developer never receives or stores them. Robokassa reports that the payment went through, the amount and the period, and Robokassa sends you the receipt.

Support

To answer support requests, the developer can see an internal accounts table: email, sign-up date, last activity, devices, Pro expiry and groups. The contents of your sync data are not available to the developer — they are encrypted.

Internet: maps, terrain and weather

The app uses the internet to load map images (tiles), terrain for the 3D player, to show the weather at the launch spot and to check for updates (more on that below).

While one of these screens is open, the coordinates of the visible area and the device's IP address are passed to the servers of the corresponding service — this is an ordinary technical request for a picture, with no name and no other personal information. The terms of the services themselves are on their sites (wiki.osmfoundation.org/wiki/Privacy_Policy for OpenStreetMap, opentopomap.org, esri.com, mapterhorn.com, eox.at).

Weather at the launch spot — on your request

The “Weather” item in a spot's menu sends that spot's coordinates to the windy.com service to show the weather right there. It happens only when you yourself tap that item — there are no background or automatic requests to Windy.

On Android the Windy map opens right inside the app, on Windows — in an external browser. Windy is a third-party service, and its own terms and privacy policy apply to it (windy.com).

The “Share” icon on the weather screen passes the spot's name, its coordinates and a map link to the app (messenger, email, etc.) that you choose yourself in the system menu — only when you tap it.

Update check

In the version downloaded from the WingLog website (winglog.pro, formerly winglog.ru; APK, Windows installer and Mac archive), on the first launch of the day the app requests one small file from this site with the number of the latest released version, to tell you that an update is out. The request has no device identifier, no name and no data from the app. As with any visit to a site, the hosting may record the IP address and time of the request in an ordinary server log. There is no background work for this: the check happens only at the moment the app launches.

From these requests the site counts how many people use the app. Starting with version 1.6.1 the app adds anonymous marks to the request: the platform (Android, Windows, macOS), the installed version number, the flags “first launch today / this week / this month” and “first check after installation”, and at the start of a month — as a single number, how many different days the app was opened in the previous month. Earlier versions add nothing, and the site counts their requests as one per IP address per day. The site stores only overall totals — by day, by hour and by month; the totals are kept without a time limit so that any past day can be opened. It uses the IP address only for a day and only as an irreversible hash — so that one address isn't counted twice and can't inflate the counter — after which the hash is deleted.

The check can be turned off: Settings → Updates → Check automatically. Then the app does not contact the site by itself and sends no marks; the “Check now” button makes one such request on your tap — without marks. In the app-store version (for example, RuStore) there is no such check: updates come through the store.

The app downloads and installs an update only on your “Update” button (since version 1.6.1): it takes the installer for its version from the WingLog website, checks the developer's digital signature and the file's checksum and hands it to the system. On Android you need to allow WingLog “install from this source” once for that; on Windows the installer works without administrator rights and the app opens again after installation; on Mac the app replaces itself with the new version in the same folder and opens again. The “Download from the website” button still just opens the download page in the browser.

Sync over the local network

Sync works only between your own devices that you paired with a 6-digit code yourself. Flights, spots, gear, tracks and photos are transferred directly from one device to another inside your local network — without the developer's servers and without third-party services.

While the sync screen is open or “Sync in background” is on, the device announces itself on the local network under the name shown on that screen (you can change it) — so that the second device can find it.

Android permissions

The app does not request access to location, contacts, the microphone or your whole gallery.

Flight photos

Photos are added to a flight through the system image picker: the app gets only the pictures you picked yourself. The chosen photos are copied into the app's storage — like the rest of the data, locally and without being sent anywhere.

Export and backups — on your command

Export to CSV, PDF, KML/GPX and a ZIP backup are built on the device and saved where you point them — the developer neither receives nor sees these files. What happens to a saved file next depends only on you: if you send it to someone or into another app, that app's or service's terms apply.

The WingLog website (winglog.pro and winglog.ru)

The site uses no ad networks; fonts and images are loaded from this same site. Like any site, the hosting keeps standard technical request logs (IP address, time, page address).

The site uses the Yandex Metrica service (Yandex LLC) for visit statistics. It sets cookies in your browser and receives your IP address, information about your browser and device, the addresses of the site pages you viewed, where you came from, the time spent on the pages and your actions on them — clicks, scrolling, mouse movements. Webvisor is turned on: it records how a page visit goes so that the developer can see where visitors struggle; text typed into fields is not recorded. On the track converter page the content is hidden from recording: your file and the conversion result do not reach Webvisor (the file itself never leaves your device anyway). The developer uses this data only for statistics and for improving the site and does not try to find out who exactly visited. The data is processed by Yandex under its privacy policy. You can opt out at any time: block the counter with a browser extension, forbid cookies for the site, or use Yandex’s Metrica opt-out.

Separately from Metrica, the site itself counts how many times the app was downloaded: when you click “Download”, one is added to the downloads for the day and for the current hour (hourly totals, like daily ones, are kept without a time limit). Next to the download count, where visitors came from is counted: by a mark in the link (for example, ?src=tg in a Telegram channel post) or by the address of the previous page — only its kind (social network, search engine or another site), without the address itself. While the tab is open, this kind of source is kept in the browser tab's memory (sessionStorage) so it isn't lost when moving between the site's pages; close the tab and it is erased. On the site this is also one number per day per source. Only the number itself is stored — without addresses and without information on who downloaded. So that a repeated click isn't counted twice, the site remembers an irreversible hash of the address for a day, then deletes it.

The “Support” button leads to the CloudTips service page — the payment goes through on its side and by its rules; neither the site nor the developer receives your card details.

Children

Without an account the app collects no one's data. Accounts and pilot groups are meant for pilots who decide for themselves what to share; if a pilot is under 14, a parent gives consent to the processing of their data.

Changes to the policy

If anything above changes (for example, a new permission or a new service is added), this text will be updated together with the date at the top of the page.

Data controller

The data controller is Ilya Nikolaevich Boyarshinov, a self-employed individual in Russia (professional income tax payer), taxpayer number (INN) 590611608812. Contact: info@winglog.ru.

Data of users in Russia is stored on servers in Russia: RU-CENTER hosting (nic.ru) and Yandex Object Storage. The only data that leaves Russia goes to Google in the USA, to deliver notifications through Firebase: the device token and the notification text.

You can ask which of your data is stored, ask for it to be corrected or deleted, or withdraw your consent. Write to info@winglog.ru from your account's email address — you will get a reply within 10 working days.

Contact the developer

For questions about data or this policy: info@winglog.ru or direct messages to the Telegram channel @winglog_app.