This is an English translation of the Korean original (https://crewcrew.app/privacy.html). If they differ, the Korean version prevails.
Notice of revision (9th revision · announced and effective 3 October 2026) — We have added three new optional features (family flight alerts, duty code answers and company code list photos) to the information we collect (1) and to retention and deletion (4), and listed what family flight alerts send through app push notifications (Expo) in the transfer table (5). All three are used only if you turn them on or choose them yourself.
Notice of revision (8th revision · announced and effective 1 October 2026) — We now name the responsible department (crewcrew Customer Support) as the privacy officer instead of an individual, and added a link to this English translation. The personal information we process and how we use it have not changed.
Notice of revision (7th revision · announced and effective 30 September 2026) — With the new optional Flight Saju ‘crew compatibility’ feature, we have added an item to the information we collect (1-3) and to retention and deletion (4). This feature is used only if you turn it on yourself, and, as before, we do not store your date of birth.
Notice of upcoming revision (6th revision · announced 29 September 2026 · effective 7 October 2026) — (1) We have stated, in the information we collect and in a new item (2-2), that if you connect a company calendar link, we store that link address encrypted and periodically (about every 3 hours) use that address to connect to the server of the company crew portal that issued the link and fetch your duties. If you disconnect it or delete your account, the link address is deleted immediately. (2) Import from phone calendar (optional · from the app version that includes this feature): we have described that the events in the calendars you choose are read only on your phone and turned into duties, that only the duty schedule is saved and the original event text is not sent to our server, and how to turn off the permission. (3) We have set out Send feedback and the "crewcrew team" messages sent by the operator in the information we collect and the purposes of use. (4) We have corrected the title of Section 2 to match its content, added calendar files (.ics) to the original rosters we keep, and added the layover weather and exchange rate lookup services to the places that receive only non-personal information.
Notice of upcoming revision (5th revision · announced 28 September 2026 · effective 5 October 2026) — (1) In line with the amended Personal Information Protection Act (Article 28-8, in force from 11 September 2026), we have expanded the table of entrustment of processing and transfer abroad to include each recipient's contact details, transfer method, retention period and legal basis. We have newly added subscription payment verification (RevenueCat · USA), app push delivery (Expo · USA) and crew taxi place search (komoot · Germany). (2) We have corrected the retention period of Anthropic, to which we entrust AI text recognition, from "not kept after processing" to its actual policy: "deleted automatically within 30 days · not used for training". (3) In a new item (2-1), we have explained that photos of rosters and payslips may contain sensitive information such as sick-leave and medical-check codes and union dues, and how we handle it (no separate use · stored only as general types). (4) We have added paid subscription and purchase information and the crew taxi disclosure scope to the information we collect, and stated the retention period for paid subscription and purchase records (5 years after account deletion). (5) We have aligned the minimum age for sign-up with the Terms of Service and the sign-up screen: 18 or over (7).
Notice of upcoming revision (4th revision · announced 28 September 2026 · effective 5 October 2026) — If you report a recognition error on a roster, we will keep that roster's original (photo or PDF) and its recognition record for one year from the date of the report, to correct the error and confirm that it does not recur, and then delete them automatically (for reports made on or after 5 October 2026 · deleted immediately if you delete your account). Rosters you do not report are deleted as they are now: originals after 30 days and recognition records after 90 days.
Notice of revision (20 September 2026) — Ads (Google AdMob) are being added to the app. An ad is shown once when you upload a roster, and for this your advertising identifier (Android AAID · iOS IDFA) is sent to Google. On iOS we ask for tracking permission first, and even if you do not give it you can still use every feature of the app (ads will only be less personalized). We do not provide user information such as rosters, pay and flight records to advertisers.
(19 September 2026) We keep original rosters (photos and PDFs) for 30 days to check and reprocess recognition errors and to answer inquiries, then delete them automatically.
9th revision effective 3 October 2026 (family flight alerts · duty code answers · company code list photos — items collected and retention periods added) · 8th revision effective 1 October 2026 (privacy officer listing · English translation) · 7th revision effective 30 September 2026 (optional 'crew compatibility' flight-saju feature) · 6th revision scheduled to take effect 7 October 2026 (calendar link address · reading the phone calendar · feedback and team messages · title of Section 2) · 5th revision scheduled to take effect 5 October 2026 (transfer-abroad table restructured · RevenueCat and others added · Anthropic retention period corrected · new sensitive-information item · payment records kept 5 years · sign-up age 18) · 4th revision scheduled to take effect 5 October 2026 (originals and recognition records of rosters with a reported recognition error kept for 1 year) · 3rd revision effective 20 September 2026 (introduction of ads · advertising identifiers · before that, 19 September 2026, 2nd revision — original rosters (photos and PDFs) kept for 30 days · PDF upload added · same day, 1st revision: optional consent to share photos to improve recognition · recognition records kept for 90 days; earlier effective date 27 July 2026) · Operator: Aviators (에비에이터스), business registration no. 175-22-02662 · Contact: toga.support@gmail.com
If you write a post looking for travel companions yourself, the following is shown to other users: destination, travel dates, number of people wanted, the introduction you wrote, and the display name and airline in your profile. Your roster (flight numbers, airports, times, layover hotels) is not shown and is not stored for this.
Contact details (an open chat link) are given only to users the organizer accepts. Posts disappear from the list automatically after the trip end date, and the organizer can delete or close them at any time.
If you post to gather crew to share a ride, the departure city (airport), direction, departure time, pickup point (the name and position of a spot you searched for or picked on the map), destination, one-line memo and number of riders, together with the display name, airline and role in your profile, are shown only to crew who are in that city on that day. Your roster itself is not shown. We do not use your device location (GPS); for the pickup point, we store only the spot you choose yourself. Posts disappear from the list after the departure time, and the person who posted can delete them at any time.
If you turn on ‘Show my type to crew friends’ on the Flight Saju result screen, we do not store your date or time of birth; we store only the result values needed to calculate compatibility (the two-character day pillar, zodiac animal and MBTI). These values and your display name are visible only to users in the same ‘Our calendar’ group or connected as friends who have also turned on this feature. If you turn the switch off, they are deleted immediately.
If you upload rosters or payslips as photos, they may also contain the following sensitive information (Article 23 of the Personal Information Protection Act of Korea).
crewcrew does not use this information separately for any purpose. Roster recognition results store sick leave, medical checks and trade union activities on your calendar only as general duty types such as "Leave" or "Ground duty", and in the record of the original codes the AI read (the recognition record), these entries are also converted to general duty types before they are stored. For payslips, deductions other than tax and the four national social insurance contributions are calculated only as a single total, without an item breakdown. However, the original photo (30 days), and the roster and recognition result you send when you report a recognition error (one year from the date of the report), may still contain these entries as they are; they are deleted automatically when the periods in Section 4 end. Photos are sent to Anthropic (Section 5) for text recognition and are deleted within 30 days. You may cover your name, employee number or such entries before uploading (you can then enter the covered days on the calendar yourself).
Automatic import from a company calendar link — If you paste the calendar subscription address issued by your company's crew portal, crewcrew's server, periodically (about every 3 hours) and whenever you tap "Fetch now" in the app, uses that address to connect to the server of the crew portal (or its operator) that issued the link and download the calendar file. A record of crewcrew's server access (IP address and program name) remains on that server; crewcrew does not send your information to that server (it only makes a request to the link address). The downloaded file is read by rules, without AI, and only duties dated today or later are added or changed; for past dates, only the empty fields (airports, times, etc.) of duties already on your calendar are filled in. We do not store the original calendar file, and lines in the description field such as crew lists and employee numbers are discarded when the file is read. The link address is stored encrypted and is deleted immediately when you tap [Disconnect] or delete your account, after which we no longer connect to it. Duties already on your calendar remain as your duty schedule (and are deleted when you delete your account). When the link changes your duties, group members may receive a duty change notification, depending on your group sharing settings.
Import from phone calendar (from the app version that includes this feature) — This feature imports duties that your company's crew app has put in your phone's calendar. We ask for calendar access permission only when you first tap the button, and we only read (we never write to or change your calendar). To suggest which calendar holds your duties, the app scans calendar names and the titles of events on nearby dates on your phone only. When importing, the events of the calendars you choose (title, start and end times, location, notes) are turned into duties on your phone, and then only the duty schedule is saved. Original event text, events in calendars you did not choose, and crew lists in notes are not sent to our server. Only when a duty entry cannot be read, the shape of the event title (flight numbers, airports, times and numbers replaced with placeholders and ordinary words removed, leaving only duty codes, e.g. "[flight no.] [airport]-[airport]") is sent as an error record so we can learn the format. Information about the calendars you chose is stored only on that phone, and when you open the app, about once every 3 hours, they are read again without a permission prompt and only duties from today onward are updated. To stop using it, tap [Disconnect] in the app, or turn off the permission in your phone's settings (iPhone: Settings → crewcrew → Calendars / Android: Settings → Apps → crewcrew → Permissions → Calendar); we will then no longer read it.
Providing the schedule calendar (including importing and updating duties from a company calendar link or your phone calendar), estimating pay, managing flight records, group sharing, running the community and protecting users (handling reports and blocks) (the operator may view Lounge posts and comments, including company lounges; direct messages are viewed only for conversations a user has reported, and only to handle that report), sending notifications, answering feedback and sending service-related notices and information ("crewcrew team" messages and notifications in the app — we do not send advertising information for commercial purposes without separate consent), providing paid services (checking subscription and purchase status and applying benefits), showing in-app ads, and improving the service and responding to errors.
When you delete your account, your account and all your data (duties, pay, records and community activity) are deleted immediately. You can do this yourself in the app at [My → Delete account]. A company calendar link address is deleted as soon as you disconnect it or delete your account. Flight Saju result values (day pillar, zodiac animal, MBTI) are deleted as soon as you turn off sharing or delete your account. The phone calendar connection information (the calendars you chose) exists only on your phone and is removed by [Disconnect] or by deleting the app. Original rosters and error-report images are deleted automatically after 30 days; recognition-improvement photos and recognition records after 90 days (the originals and recognition records of rosters with a reported recognition error, one year from the date of the report, for reports made on or after 5 October 2026); and usage logs once they are older than 90 days. Captain confirmation signatures (name, license number and signature image) are kept for three years from the date of signing as evidence of flight experience and then destroyed; if the user who requested the signature deletes their account, they are deleted at the same time. A captain who signed can ask us to delete it at any time at toga.support@gmail.com. Paid subscription and purchase records (product, payment status, time and amount) are kept for five years even after account deletion, to deal with payment disputes and to keep transaction records as required by the Act on the Consumer Protection in Electronic Commerce, etc. of Korea, and are then deleted. Family flight alert settings are deleted immediately when you turn the alerts off or delete your account, and the record of sent alerts is deleted automatically after 30 days (immediately if you delete your account). Duty code answers are deleted when you delete your account. The ‘code → duty type’ rules decided from the collected answers (e.g. OD → ground duty) remain as information that cannot identify any individual. Company code list photos and the record of uploads are kept for one year from the upload date, then deleted automatically (immediately if you delete your account).
To provide the service, we entrust processing to the companies below. Where a company's servers are outside Korea, personal information is transferred abroad. In accordance with Article 28-8(2) of the Personal Information Protection Act, we set out the recipient, contact details, purpose, items, timing, method, retention period and legal basis. All transmissions use encrypted connections (HTTPS), and we have a data processing agreement (DPA) with each company.
| Recipient (country) | Contact | Purpose of transfer | Items transferred | Timing and method | Retention and use period | Legal basis |
|---|---|---|---|---|---|---|
| Anthropic PBC USA (548 Market St, PMB 90375, San Francisco, CA) Storage: USA · Computation (inference): region not fixed (one of the regions Anthropic operates, such as the USA, Europe, Asia or Australia) | privacy@anthropic.com dpo@anthropic.com | Text recognition (AI) of rosters, payslips, flight records and application forms | Uploaded photos, PDFs and Excel table text (rosters, payslips, flight records, blank forms) · the event text of a calendar file (.ics), only when it cannot be read by rules (crew list lines excluded). Duties imported from a company calendar link or your phone calendar are not sent · the profile name, used to find your own row, only when the roster is a team roster showing several people together | Immediately on upload · API transmission | Deleted automatically within 30 days under the recipient's policy · not used to train models | Article 28-8(1)(iii) of the Act (entrustment of processing to perform a contract) |
| Supabase Pte. Ltd. Singapore company · servers in the Republic of Korea (Seoul) region | privacy@supabase.com | Data storage, account authentication, file storage | All information in Section 1 | When stored · kept on servers in Korea; may be accessed from abroad for the company's operations and technical support | Periods in Section 4 (deleted when you delete your account) | Item (iii) (entrustment) |
| Vercel Inc. USA (440 N Barranca Ave #4133, Covina, CA) | privacy@vercel.com | Hosting the web app and information pages | Access records (IP address, browser information) | When you visit the web · automatic | According to the recipient's policy | Item (iii) (entrustment) |
| 650 Industries, Inc. (Expo) USA (624 University Ave, Palo Alto, CA) → Apple Inc. (USA) · Google LLC (USA) | Expo: legal@expo.dev · expo.dev/contact Apple: privacyoffice_korea@apple.com (Apple Services Pte. Ltd. Korea branch, +82-2-737-0448) Google: domestic agent in Korea, Google Korea LLC (+82-2-722-7778, data-access-requests@google.com) | Delivering app push notifications | Push token; notification title and content (tomorrow's flight number, airports and show-up time; alert text for comments, messages, crew taxi, travel buddies and duty changes; for family flight alerts, the crew member's nickname, flight number, and departure and arrival cities and times) | When a notification is sent · through Expo's servers to Apple (APNs) and Google (FCM) | Expo: deleted immediately on delivery (not stored) · Apple and Google: according to each company's policy | Item (iii) (entrustment) |
| Plus Five Five, Inc. (Resend) USA · sending servers in the Japan (Tokyo) region | support@resend.com | Sending company email verification emails · operator alert emails (only when an app push fails) | Company email address and verification code · (operator alerts) member email address, content of reported posts and feedback | When verification is requested or an alert occurs · API transmission | Email logs kept for 30 days, then deleted (recipient's policy) | Item (iii) (entrustment) |
| RevenueCat, Inc. USA (1032 E Brandon Blvd #3003, Brandon, FL) | compliance@revenuecat.com legal@revenuecat.com | Checking subscription and purchase status (verifying store receipts) and applying benefits | App user ID (account identifier), store receipts and purchase tokens, device type and OS, time of last use | When the app starts and at payment · SDK/API transmission | According to the recipient's policy (deletion procedure when the contract ends) | Item (iii) (entrustment) |
| Google LLC / Google AdMob USA (1600 Amphitheatre Pkwy, Mountain View, CA) | Domestic agent in Korea, Google Korea LLC (+82-2-722-7778, data-access-requests@google.com) · inquiries googlekrsupport@google.com | Showing and measuring in-app ads | Advertising identifier (AAID, IDFA), device, OS and network information, ad impression and click records | When an ad is shown · SDK transmission | According to Google's policy (How Google uses data) | Item (iii) (entrustment) · on iOS, personalized ads only with tracking permission (ATT) |
| komoot GmbH (Photon map search) Germany (Kienberger Allee 4, 12529 Schönefeld) | Contact form at support.komoot.com (category "Privacy") | Searching for crew taxi pickup points and showing place names | The search term you enter (up to 80 characters) and reference coordinates (the city's airport or the center of the map — not your device location) | When you tap the search button · API call through crewcrew's server (your IP address and account information are not sent) | According to the recipient's policy | Item (iii) (entrustment) |
Places that receive only non-personal information: flight schedule lookups, AeroDataBox (Canada, via RapidAPI) — flight number and date only · airport weather, NOAA aviationweather.gov (USA) — airport code only · Google AdMob revenue reports — aggregate figures for the operator's account only · layover weather, Open-Meteo — coordinates of the layover city's airport only · exchange rates, open.er-api.com — currency code only (these two are requested directly from the app, so your device's IP address reaches them). With Kakao, Google and Apple sign-in, those services provide crewcrew with your email address, nickname and profile photo with your consent; crewcrew does not send your information to them. If you connect a company calendar link, crewcrew's server downloads the calendar file from the crew portal server you specified and does not send your information to that server (2-2).
Except where required by law, we do not sell or provide personal information to third parties. If you do not want your information transferred abroad, you can refuse by telling us at toga.support@gmail.com or by deleting your account. However, because the entrustments above are essential to providing the service, if you refuse you will not be able to use the related features, such as automatic photo recognition, notifications, paid subscriptions and crew taxi place search.
You can ask to access, correct or delete your personal information, or to suspend its processing, through the in-app features (the [My] tab) or at the contact below, and we will act on it without delay.
This service is a tool for aviation professionals, and under Article 7 of the Terms of Service only people aged 18 or over may sign up. We therefore do not collect personal information from children under 14, which would require the consent of a legal guardian.
We apply encryption in transit (HTTPS), per-account access control (Row Level Security) and the principle of data minimization. Company calendar link addresses are stored encrypted with a key kept in a separate secure store (Vault); only the server's sync function can decrypt and use them, and even your own screen shows only the host name.
Aviators (에비에이터스), crewcrew Customer Support (privacy) · Email toga.support@gmail.com
If this policy changes, we will give notice in the app and on this page at least 7 days before the change takes effect.