Version 1.7 — in force from 7 November 2026. (Version 1.6 was in force from 24 October 2026; Version 1.5 from 22 October 2026; Version 1.4 from 17 October 2026; Version 1.3 from 16 October 2026; Version 1.2 from 14 October 2026; Version 1.1 from 9 October 2026; Version 1.0 from 27 September 2026.)
This policy is written under Israeli law, and in particular the Protection of Privacy Law, 5741-1981 (including Amendment 13, in force since 14 August 2025) and the regulations made under it. It is the notice required by section 11 of that Law.
Aviators is a flight-training and flight-logging app for student pilots, private pilots and flight instructors in Israel. This policy tells you exactly what the app collects, why we collect each item, who else can see it, how long we keep it, and how you get it back or get rid of it.
If anything here is unclear, write to us before you sign up. Our address is at the end.
1. Who is responsible for your data
Operator (the "database owner" under the Law): Omer Weiner.
Contact for anything in this policy:support@aviators.org.il.
Privacy contact: the same address. Write "Privacy" in the subject line and we will route it accordingly.
We have not appointed a privacy protection officer (ממונה על הגנת הפרטיות). If the app grows to the point where the Law requires one, we will appoint one and name them here.
2. The short version
We collect what an aviation logbook and a training-progress tracker need, and nothing else.
We run no analytics, no advertising, no crash-reporting and no tracking of any kind. There is no Google Analytics, no Firebase, no Meta SDK, no advertising identifier, and no profiling of you.
We never sell, rent or trade your data, and we never share it for anyone else's marketing.
Your position is used on your phone to draw the map. It leaves your phone only when you record a track and save it — a saved recording is your own flight track, kept in your account so you can open it on any device, and deleted with your account. A recording can never be shared — share codes carry drawn designs and routes only, never a flight track. Simply looking at a map tells no server anything: the map data is built into the app. One thing does say roughly where you are: to set the altimeter, the app asks for the weather at the aerodrome nearest you (section 4.5).
Calendar sync is off until you turn it on. If you do, the app looks for the flight bookings and ground lessons your school sent you, in the calendars on your phone, in a Google Calendar you connect, or both, and offers each one for you to add to your logbook. Everything else in your calendar is ignored and never stored.
Your instructor sees your training data only after both of you approve the link, and either of you can end it.
A flight you log with an instructor appears in their logbook too, and a lesson an instructor logs with you appears in yours — one shared entry, without a link request. You can block anyone whose flights you do not want.
If you are an instructor, the students you are linked with can see when you are busy, never with whom or where, and you can turn that off in Settings.
You can delete your account and everything in it from inside the app, at any time, without asking us.
3. The legal basis we rely on
Israeli law recognises two lawful bases for processing personal data: your informed consent, and a specific authorisation in law. There is no "legitimate interest" basis in Israel, and we do not claim one.
Everything described in this policy is done on the basis of your consent, given as section 8 describes. Where we are required by another law to keep or produce information — for example a lawful order of a competent authority or court — that law is the basis, and we say so where it applies.
Consent is not permanent and not unlimited. If we ever want to use your data for a purpose that is not listed in this policy, we will ask you again, before that use starts.
4. What we collect, why, and for how long
Every item below is listed with the purpose it is collected for. We do not use any of it for a purpose that is not written next to it.
4.1 Account and identity
Email address. To create your account, sign you in, verify that the address is yours, let you reset your password, and send you service messages about your own account. Required — without it there is no account.
Password. Stored only as a cryptographic hash by our authentication provider. We never see or store your actual password. Required, unless you sign in with Apple or Google (below).
Apple account identifier, if you choose "Sign in with Apple". Apple gives us a permanent identifier for you and the email address you choose to share — either your real address or an Apple private relay address. We do not receive your Apple password, and we cannot see anything else in your Apple account. Required only if you use that sign-in method.
Google account identifier, if you choose "Sign in with Google". Google gives us an identifier for you, your email address and the name on your Google account. We do not receive your Google password. Signing in asks for nothing beyond your email address and basic profile — not your contacts, not your Drive, not your activity, and not your calendar unless you separately connect it for calendar sync (section 4.8). Required only if you use that sign-in method.
First name and surname. To identify you to yourself, to your instructor, and to students who search for an instructor. Required.
Phone number. So that we can reach you about your account. Required. It is stored in a separate, locked table: no other user of the app can see your phone number, including your own instructor. Each phone number may be registered to one account only.
Account type (student, private pilot, or instructor). Determines what the app shows you and what permissions you have. Required.
Pilot licence number, if you have one. To identify you as a licence holder to an instructor you have linked with, and for your own records. Optional — a student pilot who has not yet been issued a licence can open an account and use the app without it.
Instructor qualifications and instructional scopes, for instructor accounts. So students can see what you are qualified to teach. These are details you declare yourself when you register: we do not check them against any register before the account is enabled, and a student should confirm an instructor's qualifications independently. Required for instructor accounts.
Profile photo, if you choose to add one. Shown to you and to other users in the in-app directory. Optional.
4.2 Your flying and training records
Flight logbook entries: date and times, departure and destination aerodromes, aircraft type and registration, flight type, flight hours by category, landings, the role you flew in, the instructor or co-pilot you flew with, and your own notes. This is the core of the service.
Instructor grading and signatures: per-skill scores, written feedback, and the record of a requested or given instructor signature.
Your own self-assessments of a flight.
Shared flights. When a student or private pilot logs a flight with an instructor, or an instructor logs a lesson with a student or private pilot, it is one shared entry in both logbooks — details and notes alike. If one of you changes it, the other is asked to accept the change; until they do, or if they decline or do not answer within 14 days, they keep their own version. If one of you removes it, it leaves only that person's logbook, and the other is told. Two private pilots who fly together keep separate copies, as before.
Debrief scores given on a flight, by the category chosen (for example circuits or navigation), and grading forms an instructor creates: the form's name and the names of its skills.
The people you have blocked.
Notifications in the app about shared flights: which flight, what happened to it, who did it, when, and whether you have read it.
Flights you import from a spreadsheet. If you use "Import logbook", the file (Excel or CSV) is read on your phone; the file itself is never uploaded. What is stored in your account is each flight you chose to import, marked as imported, plus: the name of the file, the number of rows read and skipped, the way you matched the file's columns to ours (so a second file with the same columns is matched for you), and the names of the instructors, co-pilots or other people written in the file, each with the role it was written under. Those names are kept as text in your own record, may be matched by you to a user in the directory, and are never shown to the person named — a person you match gets no access to your record. You can undo an import, which deletes exactly the flights it added.
Where you are in the syllabus, if you tell the app you are already part-way through training.
Syllabus progress, ground briefings, and theory exam records — subject, status, score, date, and any certificate or payment document you attach.
Aircraft class records and checkouts you record for yourself.
Routes, markers and map layouts you draw and choose to save, and flight tracks you record and choose to save (the sampled positions, the start and finish times and the distance). You can share a drawn design or a route with another user through a share code; a recorded flight track can never be shared.
Pre-flight risk flags the app raises for a planned flight date, based on weather and NOTAM conditions for that date.
In-app messages between you and an instructor or student, and the status of link requests between you.
If you are an instructor: your availability — the working hours and days off you choose to set, and whether you share your schedule with your students. Setting hours or days off is optional.
Purpose: to provide the service — keeping your records, showing your progress, and letting a linked instructor supervise your training. Nothing in this category is used for any other purpose.
4.3 Documents you upload
Files you add to your document folder — for example a medical certificate, a licence, a rating certificate, an examination certificate or a receipt — together with the name you give the document and its issue and expiry dates.
Purpose: to store them for you and to remind you before one expires, if you asked for that reminder.
A medical certificate is health information. Under Israeli law health information is "data of special sensitivity", and we treat this whole folder as such. These files are stored in a private area that is not publicly reachable; access happens only through short-lived links issued to your own signed-in session. Uploading documents is entirely optional — the app works without them.
4.4 Technical data
Session data needed to keep you signed in, held in your phone's encrypted storage (the iOS Keychain or the Android Keystore).
A record of the devices signed in to your account — a random device identifier, a device label, and the time it was last active. Purpose: to cap how many devices can use one account at once and to let you see where you are signed in. We do not use it to locate you.
A background-check code for each phone you are signed in on — a random code, which our server keeps only as a one-way code, with the time it was last used. It lets the phone check for new shared-flight notifications while the app is closed, without your sign-in session, and it can read nothing else. It is deleted when you sign out on that phone; at most five phones per account keep one.
IP address, for abuse control only. When you use an action that is rate-limited — for example checking whether a phone number is free during registration — your IP address is used to enforce a short cooldown. It is held for the length of that cooldown, in minutes, and then cleared. We do not build a record of your IP history, and we do not use IP addresses to locate or profile you.
Authentication logs kept by our authentication provider (sign-in times, IP address, device type), for security and fraud investigation.
4.5 Location and phone sensors
This is the section pilots ask about, so we will be blunt about it.
Live position, while you fly, stays on your device. It draws your position and heading on the map. It is not sent to our servers, it is not sent to anyone else, and it is held only in the memory of the running app.
Live QNH. To set the altimeter, the app asks for the latest weather report of the aerodrome nearest you. That request carries the aerodrome's code, not your position, and is not stored in your account — but the code shows roughly where you are: to our weather cache and, when the report is not cached there, to aviationweather.gov (section 6.3).
A recording you start yourself is the exception, and you should read this bullet carefully. If you press Record on the map, the app samples your position while recording. When you save that recording, the track it produced — the list of positions, the start and finish times, and the distance — is stored in your account on our servers, so you can open it on any device. This is precise location data about you, and Israeli law treats it as data of special sensitivity. It is stored only when you choose to save it, only you can see it, you can delete any recording from the Maps screen at any time, and every recording is deleted with your account. A recording cannot be shared, by design. There is no share button on a recording, and a share code never carries a flight track — not even when the recording is linked to a design you are sharing. Drawn designs and routes are things you made up; a track is a record of where you physically flew, and handing someone a permanent copy of that is not something we want a single tap to do. Your recordings are visible to you alone.
The maps are offline. The map data is built into the app, so displaying a map does not tell any server where you are looking or where you are.
Motion and compass sensors are read on the device for heading and barometric altitude. That data is also never transmitted.
You can refuse the location permission and revoke it at any time in your phone's settings. The map still works; it simply will not show your own position.
What we do store is where you flew, not where you are. Your logbook records the departure and destination aerodrome, date and times of every flight, and any routes, markers and map layouts you choose to save are stored on our servers. Under Israeli law location information is data of special sensitivity, and we hold it to the same standard as your medical documents: per-row access control, no use for any purpose except showing you your own records and showing your training to the instructor you approved, no sale, no profiling, and deletion with your account.
4.6 If you write to us
If you email us we keep your message and the address you sent it from, in order to answer you. You do not need an account to write to us.
4.7 Feedback sent from the app
What you send: the message you write, the category you choose (bug, idea or other), the app language, and the time. It is stored against your account, so we can reply and so it is deleted with your account.
Device details, which you can switch off. The feedback screen has a box, ticked by default, that adds the app version and build, the operating system and its version, and the device model. Purpose: to reproduce the fault you are reporting. Untick it and none of it is sent.
A draft you have not sent is kept on your phone only, and removed once you send it.
Feedback is visible to you and to the operator only. Do not put anything in it that you would not want us to read, such as another person's details.
4.8 Calendar sync
Optional, and off until you turn it on in Settings.
What it does. Flight schools send a calendar invitation for each booking. Calendar sync finds those invitations and offers each one for you to confirm: a flight booking becomes an upcoming flight, and a ground lesson with no aircraft becomes a ground briefing. After the booked time ends, the app asks whether you flew. Nothing counts until you confirm it — it does not count towards your hours or your currency.
Reading the calendars on your phone (optional). If you turn on "Calendars on this phone", the app reads the calendars your phone shows (for example iCloud, Outlook, Exchange or Google calendars), or only the ones you pick, from today to about four months ahead. This works whatever email address your school sends its invitations to. The app recognises the bookings on your phone, and sends us only those — every other event stays on your phone and never reaches us. The phone reads when you open the app, so bookings arrive then. Access is read-only: the app never changes or deletes an event. Separately, "Add to calendar" on a theory exam writes the one reminder you asked for.
Connecting a Google Calendar directly (optional, separate from Google sign-in). This lets bookings arrive while the app is closed. Google asks you to allow read-only access to the events on calendars you own. Google then tells our server when your calendar changes, our server reads the changed events, keeps only flight bookings and ground lessons, and discards every other event without storing it. The access key Google issues is stored encrypted on our server and is used for nothing else.
What is stored for each booking you keep: the date, start and end time, aircraft registration and type (or, for a ground lesson, the subject), aerodromes or place, the school name you give the sender, the names of the people written in the booking, the notes written in the booking, and a one-way code of the calendar event, so that the same booking is not added twice and so that a change or cancellation in your calendar updates it. For the school, we also keep a one-way code of the address its invitations come from, so its next invitations are recognised and you can mark it as trusted.
Email addresses of people invited to a booking are compared, as one-way codes, only against users you are already linked with — to recognise your instructor or student. They are not stored and are never compared against the rest of the directory.
If you and a user you are linked with have the same booking, the app links the two entries, the same way a flight you record with your instructor is linked today (section 6.1).
Reminders. On Android the reminder is created on your phone. On iPhone, when the app is closed, our server asks Apple's push service to deliver it; Apple receives your device's push address and the reminder text, which names the aircraft and the time and no person.
Stopping. Turn calendar sync off, or disconnect Google, in Settings at any time; you can also remove Aviators' access from your Google account's security page. We then stop reading and delete the access key. Bookings you already confirmed stay in your logbook, as your own flights or ground briefings. If you switch from one source to the other, the bookings the old source added that you have not confirmed yet are removed; when you disconnect Google, you choose whether to remove them.
Google user data. Our use and transfer to any other app of information received from Google APIs will adhere to the Google API Services User Data Policy (https://developers.google.com/terms/api-services-user-data-policy), including the Limited Use requirements. Calendar data is used only to offer your flight bookings and ground lessons for your logbook. It is not used for advertising, it is not sold, it is not used to train any artificial intelligence model, and no person at Aviators reads it, except with your explicit permission to investigate a problem you report, or where the law requires it.
5. Is providing your data required, and what happens if you refuse
Israeli law requires us to tell you this plainly.
No law obliges you to give us any of this data. You give it voluntarily, under a contract with us, so that we can provide the service.
However:
Email, password (or Apple sign-in), first name, surname, phone number and account type are required to hold an account. If you do not provide them, we cannot open an account and you cannot use the app. Nothing else follows from that refusal: we do not contact you, and we keep no record of you. If you begin a registration and never confirm your email address, the part-made account is deleted automatically after 48 hours (section 9). Checking during registration whether a phone number is already in use briefly records the network address the check came from, for a few minutes, so that the check cannot be abused.
Instructor qualification details are required for an instructor account. Without them the account is a regular account.
Everything else is optional, including your licence number. Refusing a profile photo, a licence number, a document upload, location access, calendar access, or notifications costs you only the specific feature involved. It never affects the rest of the app, and it never affects your training records.
If you later withdraw your consent, the only way to give effect to that is to close the account, and closing it destroys your logbook, gradings and documents irreversibly. Export first.
Refusing marketing messages costs you nothing at all. It is not a condition of using the app and never will be.
6. Who else can see your data
We disclose your data only to the recipients below, only for the purposes stated, and to no one else.
6.1 Other users of the app
An instructor you are linked with sees your profile — including your email address, licence number and flight hours — your complete flight logbook, including flights you did not fly with them, your gradings, your self-assessments, your syllabus progress and your messages with them. They need your whole logbook because your training stage is calculated from your total hours by type. Flights you imported from a spreadsheet are part of that logbook, but an import never creates a copy in anyone else's logbook and never asks anyone to sign it. They do not see your phone number, your uploaded documents or your theory exam records. The link requires both of you to approve it, neither side can create it alone, and either side can end it. When it ends, that access ends.
A student you are linked with, if you are an instructor, sees when you are busy: the start and end times of the flights and ground briefings you take part in, and whether each one is a flight or a ground briefing, together with any working hours and days off you set. They never see who a session is with, where it goes, or anything else about it — except sessions they are on themselves. This lets them plan lessons at times you are free. You can turn it off at any time in Settings ("Share my schedule with students"); a student then sees only their own sessions with you. It ends when the link ends.
Any signed-in user browsing the in-app directory sees only your first name, surname, account type and profile photo. They cannot see your email address, your phone number, your licence number, your documents, your logbook or your grades.
An instructor, student or private pilot you share a flight with (section 4.2) sees that flight — its details, notes and any grading on it — with your name and profile photo. This needs no approved link: anyone can name an instructor on a flight they log, and an instructor can name a student. It is limited to a few flights a day, and you can block a person in the app: their flights, messages and requests then stop reaching you, and they are not told. A shared flight shows that one flight, not the rest of your logbook.
A pilot you record as a co-pilot is shown that flight entry and can add a copy of it to their own logbook.
A student linked with an instructor, or who has flown with them, sees the grading forms that instructor creates and can score flights with them.
A user you send a share code to can open the map layout or route that code refers to, until the code expires. A share code never carries a recorded flight track. Nothing else in your account is reachable with a code.
Anyone, without an account, can find out from the registration screen whether a given email address or phone number already belongs to an Aviators account — that is how the form can tell you a number is taken before you submit it. It reveals nothing else: no name, no profile, no other field, and it is rate-limited.
6.2 Service providers who process data for us
These companies process data on our instructions and are contractually restricted to doing so. This is the complete list.
Supabase Inc. — our database, authentication and file storage provider. It holds effectively all of the data described in section 4, on infrastructure operated by Amazon Web Services.
Cloudflare, Inc. — serves our website, including this policy page and the account-deletion page. It sees the IP address of anyone who opens those pages. It does not process any account data.
Apple Inc. — only if you use "Sign in with Apple". Apple performs the sign-in and tells us the identifier and the email address you chose to share.
Google LLC — only if you use "Sign in with Google". Google performs the sign-in and tells us your identifier, your email address and your name. It learns that you use Aviators; it receives nothing about your flying, your training or your documents.
Google LLC, for calendar sync — only if you connect a Google Calendar (section 4.8). Google provides the calendar events and tells our server when they change. It receives nothing from us about your flying.
Apple Inc., for notifications — only on iPhone. Apple's push notification service delivers a reminder when the app is closed. It receives your device's push address and the reminder text.
Google LLC and Apple Inc. as app stores — they distribute the app and know that you installed it. That relationship is between you and them, under their own privacy policies, not ours.
6.3 Aviation data sources
The Aviation Weather Center of the United States National Oceanic and Atmospheric Administration (aviationweather.gov) supplies METAR and TAF weather reports. When your device requests a report directly, that server receives the aerodrome code requested and your device's network address. Some requests go through our own server instead, which caches reports for every user; on that path the weather service sees our server's address, not yours. Either way it receives no account data, no name and no identifier of any kind from us.
6.4 Links out to other sites
The app contains links to the Civil Aviation Authority of Israel, the Israel Meteorological Service and other aviation sites. Opening one takes you out of the app and onto that site, under its own privacy policy. We do not pass anything to them.
6.5 Legal disclosure
We will disclose data where we are required to by a lawful order of a competent Israeli authority or court. Where we are permitted to tell you that this has happened, we will.
6.6 What we never do
We never sell, rent or trade your data.
We never pass it to advertisers, data brokers, insurers, employers or aviation authorities on our own initiative.
We never use your training records to make decisions about you other than showing them to you and to the instructor you approved.
7. Where your data is stored, and transfers outside Israel
Your data is stored outside Israel. We say so plainly because you are entitled to know before you sign up.
Our database, authentication and file storage run on Supabase, on Amazon Web Services infrastructure in the eu-central-1 (Frankfurt, Germany) region. Our website is delivered by Cloudflare through servers in many countries, including inside Israel.
Transfers out of Israel are governed by the Protection of Privacy (Transfer of Data to Databases Abroad) Regulations, 5761-2001. We rely on two grounds:
Your consent to the transfer, which you give when you accept this policy knowing where the data goes; and
Contractual undertakings by each provider to protect the data to a standard no lower than Israeli law requires, in the data processing agreement we have signed with them.
Our providers' support staff may access systems from other countries in order to operate and maintain them. We treat that access as a transfer and it is covered by the same agreements.
8. Consent — what you agree to, separately
Israeli privacy guidance asks that agreement be given for each purpose separately rather than bundled into a single act. We are honest about where we currently stand against that standard.
Service terms and this policy — today you accept both together when you create an account, through the notice on the registration screen. Both documents are linked there and on the sign-in screen, are readable in full before you sign up, and are published on our website. The version in force is the one numbered at the top of this document. We are working towards a separate, recorded acceptance of each document, and we will update this section when it is in place.
Location access — asked for by your phone, the first time you open a map. Refusable, revocable, and it affects only the map.
Calendar access — off until you turn on "Calendars on this phone" in calendar sync, or until you tap "Add to calendar" on a theory exam. The phone's calendar permission is used to read your school's bookings (section 4.8) and to write that theory-exam reminder. Connecting Google is a separate screen shown by Google. Refusable, revocable, and it affects only those features.
Notifications — asked for separately by your phone. You can switch them off per document or entirely.
Marketing messages — we do not send any. If that ever changes, it will be a separate choice, off by default, never a condition of using the app, and we will ask before sending anything.
If we change what we do with your data in a way that goes beyond this policy, we will ask you again rather than rely on the consent you gave today.
You may withdraw a consent at any time. Withdrawing consent to the service means closing your account, because the service cannot run without the data it is built on. We may keep a minimum of information where another law requires it, or to defend a legal claim, and we will tell you if that applies.
9. How long we keep things
Your account and everything in it: for as long as your account exists.
A registration that is never confirmed: deleted automatically after 48 hours.
After you delete your account: your profile, logbook, grading, documents, messages, uploaded files, phone number and session records are deleted. Backups held by our hosting provider are overwritten on that provider's backup cycle, which does not exceed 30 days; after that cycle completes no copy of your data remains in them.
Rate-limiting records: minutes, then cleared.
Authentication logs held by our authentication provider: kept for that provider's standard security-log period. We do not use them for anything except investigating a security or fraud incident.
Map layouts and tracks published with a share code: deleted automatically 3 days after publication.
Device records: until you sign that device out, or until it is displaced by a newer device under the per-account device limit.
Emails you send us: up to 24 months after we have answered you, in case you come back to us about the same matter.
Feedback sent from the app: for as long as your account exists, and deleted with it.
Import records (file name, counts, column matching): for as long as your account exists, and deleted with it. "Undo import" removes the flights, and the record of the import stays so that you can see that it happened.
Shared flights: for as long as either of you keeps one. If one of you deletes their account, the other keeps it as their own flight (section 11).
Change requests on a shared flight: kept with the flight and deleted with it; one not answered within 14 days counts as declined.
Notifications in the app: for as long as your account exists.
Blocks: until you unblock the person, or until either account is deleted.
Background-check codes: until you sign out on that phone.
Calendar bookings: a flight booking you confirm becomes a flight in your logbook, and a ground lesson you confirm becomes a ground briefing, and each is kept like any other entry of that kind. A booking you dismiss, or that is cancelled in your calendar before you confirm it, is deleted within 30 days; only its one-way code is kept, so that it is not added again.
Google calendar access key: until you disconnect Google, turn calendar sync off, or delete your account.
Your device's push address: until that device signs out.
Anything we are required by law to keep: for the period that law requires, and no longer.
10. Your rights
Under the Protection of Privacy Law you have the following rights, and we will honour them.
The right to inspect your data (זכות עיון). Most of it you can see in the app at any time. For anything else, write to us and we will provide it within 30 days.
The right to correct data that is incorrect, incomplete or out of date (זכות תיקון). Your profile, phone number, licence number and your records are editable in the app. If something you cannot edit is wrong, tell us and we will fix it or tell you why we disagree — and if we refuse, you may apply to a court.
Deletion. The Law gives a right to have data erased in defined circumstances. Beyond that, we let you delete your whole account and everything in it yourself, at any time and for any reason — see section 11.
The right to withdraw consent, as described in section 8.
The right to complain to the Privacy Protection Authority (הרשות להגנת הפרטיות) at the Ministry of Justice, and the right to go to court. Nothing in this policy or in our Terms of Use limits that right in any way.
To use any of these, write to support@aviators.org.il. We may need to confirm that you are the account holder before we act, in order to protect you from someone else making the request.
11. Deleting your account
You do not need our permission and you do not need to ask.
In the app: Profile → Settings → Delete account. It removes your profile, logbook, grading, documents, messages, uploaded files, phone number and sign-in credentials. This is immediate and cannot be undone.
If you no longer have the app installed: the instructions are at https://links.aviators.org.il/delete-account. That route is a request by email from your registered address; we verify that it comes from you, complete the deletion within 7 days, and confirm by email.
Export anything you want to keep before you delete — the app can export your logbook.
One thing does not disappear, and you should know why: a flight you flew with an instructor, a student or another pilot is part of their logbook too. A flight you shared with them stays in their logbook as their own flight, in the version they had, without your name on it; a copy another pilot added to their own logbook stays theirs. Written feedback and an overall grade stay with the flight they belong to; per-skill scores given by you or about you are deleted. Every flight only you had is deleted.
12. Keeping your data safe
We apply the security measures required by the Protection of Privacy (Data Security) Regulations, 5777-2017, at the level appropriate to a database holding data of special sensitivity. In general terms:
All traffic between the app and our servers is encrypted in transit. The app also restricts which certificate authority it will accept for its own backend, on both Android and iOS, as a further defence against an intercepted connection. It is an extra layer, not a guarantee.
Access to your rows is enforced by the database itself, per row, per user, through row-level security — not by the app asking nicely. Every table holding user data has row-level security enabled, and rows you do not own are not returned to you.
Documents and profile photos are stored in private buckets and reachable only through short-lived links issued to your own session.
Sign-in tokens are held in the iOS Keychain or the Android Keystore.
Sensitive actions are rate-limited on the server.
Access to the production database is restricted to the people who operate the service, and we keep the internal security procedure the Regulations require.
No system is perfectly secure. If a security incident occurs that the Regulations require us to report, we will report it to the Privacy Protection Authority immediately on discovery, and where the Authority so directs or where we judge it right, we will tell you directly.
13. Notifications and marketing
Service messages — a document nearing expiry, a flight booking waiting for you to confirm, a flight someone shared with you, changed or removed, a signature request, a link request, an account or security notice. These come with the service. Reminders can be switched off per document or altogether. While the app is closed, your phone checks for shared-flight notifications every so often and shows them with the other pilot's first name, the aerodromes and the date — on a locked screen too, depending on your phone's settings.
Marketing messages: we do not send them. We do not send advertising by email, SMS, WhatsApp or push notification, and we do not give your details to anyone who does. If we ever start, it will be governed by section 30A of the Communications (Telecommunications and Broadcasting) Law, 5742-1982: we will ask for your active agreement first, every message will be marked as an advertisement, identify us, and carry a one-tap way to stop — and if you ask us to stop, we stop immediately and permanently.
14. Children
Aviators is for people training for or holding a pilot licence and is not directed at children. You must be at least 16 to hold an account. We do not ask for your date of birth, so we cannot check this — it is a condition of using the app and we rely on you. If we learn that we hold data about someone younger, we will delete it. If you believe we do, write to us.
15. Automated decision-making
We do not make automated decisions about you that have a legal or similarly significant effect, and we do not profile you. The app performs calculations and raises pre-flight risk flags for information only — every one of those is advisory, a human always decides, and none of it is reported to anyone.
We do not use your data to train any artificial intelligence or machine learning model, and we do not give it to anyone else for that purpose.
16. Changes to this policy
If we change this policy we will update the version number and the date at the top. For a change that affects what we collect, why, or who receives it, we will tell you inside the app before the change takes effect, and where the law requires it we will ask for your consent again rather than assume it.
17. Governing law
This policy is governed by the law of the State of Israel.
This policy is published in Hebrew and in English. In the event of any inconsistency between them, the Hebrew version prevails.
18. Contact
Email: support@aviators.org.il
Operator: Omer Weiner, Israel.
Supervisory authority: the Privacy Protection Authority, Ministry of Justice.