Privacy Policy

1. Controller

Athmos Media OÜ
Sepapaja tn 6, 15551 Tallinn, Estonia
Registry code: 17413806 · Managing director: Cedric Constantin Radeke
Email: support@airmancompanion.com

This policy describes how we process personal data when you use our website, learning platform, our iPhone and Android apps, and the Toralf – Airman Companion Chrome extension.

2. Data we process

• Account & auth: email address, authentication tokens (via Supabase). Magic-link / OTP login on the website and in the extension.
• Learning platform: profile and bundle-related data as described when you register (e.g. flight school or student programmes).
• Toralf (AI): text you send and, if you choose, images or screenshots you upload. These are sent to our servers and to Anthropic (Claude) to generate answers. We track usage limits (requests / cost per billing period); we do not use your chats to train public models (Business API terms).
• Payments: processed by Stripe on the website and by Apple for the in-app purchase on iPhone (section 4). We never see your payment details and do not store card numbers.
• Technical data: browser type, timestamps, security logs. We minimise IP retention.

3. Toralf Chrome extension

When you install and use our official extension from the Chrome Web Store:

• Side panel: the UI runs locally as part of the extension package (HTML/CSS/JavaScript). No remote code execution from third-party scripts.
• chrome.storage.local: stores session tokens and optional settings (e.g. API base URL for development) on your device only. Not used for advertising.
• Screenshots: captured only when you click the screenshot action; the image is sent to our API for Toralf to analyse, like an uploaded image.
• Network: HTTPS requests to Airman Companion (chat, extension login) and Supabase (authentication / token refresh). Host permissions are limited to our domains, Supabase, and localhost (development builds only).

Purpose: provide Toralf to logged-in customers alongside their normal browsing — not for tracking browsing history for ads or resale of data.

4. The iPhone and Android apps

Airman Companion is also available as an app on the App Store (iOS) and on Google Play (Android). It is the same service and the same account as in the browser; everything in this policy applies there as well. This section says what the app does in addition — and what it does not do.

What the app sends to us

• Your email address — for signing in and managing your account. The app cannot be used without an account.
• Your user ID — a random string your device identifies itself with on every request.
• Your learning progress — chapters read, questions answered, results. This keeps every device at the same point and lets the study plan follow it.
• What you write to Toralf — your messages to the AI instructor and its replies, so the conversation continues the next time you open it.
• A device identifier — a string we recognise this device by; it says nothing else about you. It travels in the X-Airman-Geraet header and serves only to keep the same device from starting the free trial over and over. On iPhone it is a random value in the keychain, on Android the system's own device identifier. We store a checksum of it, never the value.

These five are required to use the app. Transmission is encrypted throughout (HTTPS). We pass none of it on for advertising, and no profile about you is built from it.

One of them leaves our server: what you write to Toralf goes to Anthropic PBC (USA) — there is no other way to produce an answer. Anthropic processes the messages on our behalf under the Business API and does not use them to train models; details in section 6. The other four — email address, user ID, learning progress and device identifier — stay on our servers in Germany.

Only when you trigger it yourself

Both apps have screens on which you actively tell us more. If you do not open those screens, you send none of it:

• What you write to support — when you send us a message. iPhone and Android. That includes a reported answer from Toralf: it reaches us together with the question you asked before it, so that we can judge it.
• A profile picture — when you pick one in the settings. The app opens the system's own picker for this and gets no access to your photos, only the single image you tap; it does not take videos. You can remove it in the same place, and it is then gone from our side too. iPhone and Android.
• Name and delivery address — when you order a headset. We need them to ship it. iPhone only.
• Phone number — when you ask for a call back about insurance. iPhone only.

All four are voluntary, and whoever does not use them does not hand them over. The Android app does not have the headset and insurance screens; it therefore sends the five items above, a profile picture if you pick one, and your support messages if you write to us.

What the app does not do

• No location. The app never asks for location permission.
• No advertising tracking. No advertising or analytics library is built in; there is no advertising ID and no cross-device profile.
• No address book, no camera, no microphone. For the profile picture the app opens the system's picker; your photo library stays closed to it.

Buying inside the app

On iPhone the course can be bought inside the app. Apple is the seller in that case. Payment happens in Apple's own sheet: we see neither your payment method nor a card number nor your name, and there is no payment provider of ours inside the app. From Apple we receive only a signed receipt for a purchase, carrying an identifier for the transaction, the product ID, and whether it comes from Apple's test environment. We verify it on our server, use it to unlock your access, and later recognise a refund by it. It is a one-time purchase, not a subscription.

The Android app has no purchase path. Anyone buying on this website pays through Stripe as before (section 6).

What stays on the device

Your sign-in, downloaded course content for offline reading and your settings (such as the font size) are held locally on your device. Signing out deletes the personal parts of that. Removing the app removes them as well — your account is not affected and is not deleted.

The stores themselves

Downloading, installing and any crash reports are handled by Apple and Google on their own responsibility. What arises there does not reach us by name, at most as a number. The privacy notices of Apple and Google apply.

5. Purposes & legal bases (GDPR)

We process data to deliver the contract or pre-contract steps you request (Art. 6(1)(b) GDPR) — e.g. access to courses, Toralf, bundles, and extension login. Some processing relies on our legitimate interest in securing and improving the service (Art. 6(1)(f) GDPR), such as abuse prevention and limited logging.

6. Processors & transfers

We use vetted providers, including:

• Supabase — database & auth (EU region: Frankfurt, Germany).
• Vercel — hosting (may involve US entity; safeguards such as EU Standard Contractual Clauses where applicable).
• Stripe — payments (USA) · stripe.com/privacy
• Resend — transactional email (e.g. login codes).
• Anthropic — AI responses (USA, Business API).

Where data is transferred outside the EEA, we rely on appropriate safeguards (e.g. SCCs) as required by GDPR.

WhatsApp (Meta). From the learning area we link to a WhatsApp group. It is a link and nothing more: nothing from WhatsApp is embedded in our pages, no pixel and no script loads, and opening our pages sends nothing to Meta. Only when you follow the link and join does Meta process your data under its own terms — and your phone number becomes visible to everyone else in that group. You can leave at any time inside WhatsApp; we cannot do that for you. · whatsapp.com/legal/privacy-policy-eea

7. Retention

We keep data only as long as needed for your account, legal obligations (e.g. invoices), or security. Extension-local storage can be cleared by removing the extension or using Chrome's site data controls.

8. Your rights

You may request access, rectification, erasure, restriction, portability, and object where applicable (Articles 15–21 GDPR). Contact: support@airmancompanion.com. You may also lodge a complaint with a supervisory authority.

9. Children

Our services are aimed at flight students and schools. If you believe we have processed a child's data without proper consent, contact us and we will address it.

10. Changes

We may update this policy; the "Last updated" date will change. Material changes will be communicated as required by law.