CrewPay is a personal salary-estimation tool for cabin crew. This policy explains exactly what data CrewPay handles, why, how long it is kept, and how you can delete it.
CrewPay is an independent tool. It is not an official payroll system and is not endorsed by or affiliated with any airline.
1. Data you provide when requesting access
To request access you submit three pieces of information. CrewPay also generates one identifier for you:
- First name
- Last name
- Company email address
- Client ID — generated by CrewPay so the administrator can identify your request
2. Account and approval information
Together with the details above, CrewPay stores your approval status (pending, approved or rejected), the date your account was created and the date it was approved. The administrator can see this information in order to review access requests.
An administrative activity log records approval, rejection and deletion actions (who acted, on which account, and when) so access decisions remain auditable.
3. Roster / PDF data
When you upload a roster, the file is sent to the CrewPay server, the text is extracted, the salary is calculated and the result is returned to your device.
Roster files and extracted roster content are processed in memory for that single request and are NOT stored in the CrewPay database. Nothing from your roster is retained on the server after the response is sent.
4. Salary calculation results and history
Calculation results are stored ONLY on your own device, so you can reopen past results offline. They are not uploaded to or retained on the CrewPay server, and the administrator cannot see them.
Deleting a history entry, or deleting the app, removes that data from your device.
5. Settings you configure
Your crew position, seniority, base airport, exchange-rate preference, theme and privacy-mode preference are stored on your device only. Pay rates themselves are resolved on the server and are not editable by you.
6. Push notification and device information
CrewPay sends exactly one kind of notification, and only to the administrator: an alert that a new user has requested access.
A device push token is registered ONLY when someone signs in to the administrator console on that device. Crew users never register a push token and never receive notifications from CrewPay.
The administrator device token is relayed to the push delivery provider for the purpose of sending that notification. It is not stored in the CrewPay user database and is never shown to other users.
7. Authentication information
Crew accounts are passwordless: after registration your device holds a signed access token, kept in your device secure storage. CrewPay never asks crew users for a password.
The administrator account uses a username and password. The password is never stored in readable form — only a one-way hash held in the server environment — and is never sent to or stored on any user device.
8. Why your data is processed
CrewPay does not use your data for advertising, profiling, marketing or tracking, and does not sell your data.
- To verify that you are cabin crew and to let the administrator approve or reject your access request
- To restrict the app to approved users only
- To calculate a salary estimate from the roster you upload
- To notify the administrator that a new access request is waiting
9. Analytics and tracking
CrewPay contains no analytics SDK, no advertising SDK and no cross-app or cross-site tracking. No advertising identifier is read.
10. Third-party services actually used
No other third party receives your data. CrewPay does not share your personal data with any airline.
- Push notification delivery — used only to deliver the administrator "new access request" alert; receives the administrator device token and the notification text.
- Public exchange-rate sources — queried for the EUR/TRY rate. These requests contain no personal data.
11. Data storage and retention
Account data (name, surname, company email, Client ID, approval status and dates) is stored on the CrewPay server for as long as your account exists.
Roster files and extracted roster data are never stored — they exist only for the duration of the request.
Salary results, history and settings live on your device until you delete them or remove the app.
Administrative activity-log entries are retained so access decisions remain auditable.
12. Account deletion
You can delete your account at any time from inside the app: Settings → Account → Delete Account. No email, phone call or message to support is required.
Deletion is immediate and permanent: your account record and the personal data in it (name, surname, company email, Client ID, approval status) are removed from the server, and your session stops working straight away.
To also remove locally stored results, delete your history in the app or uninstall the app.
13. Security
- All communication with the CrewPay server uses HTTPS.
- Every data endpoint requires a valid access token and an approved account, re-checked on every request.
- Access tokens are held in device secure storage.
- Requests are rate limited, and cross-origin access is restricted.
- Pay rate tables and salary formulas exist only on the server and are never shipped inside the app.
14. Your rights
You can ask what data is held about you, ask for it to be corrected, and delete it yourself at any time using the in-app Delete Account flow. Because roster data and results are never stored on the server, there is no server-side roster history to export.
15. Children
CrewPay is intended for professional cabin crew and is not directed at children.
16. Changes to this policy
If data handling changes, this policy is updated and the date at the top of the page changes with it.
17. Contact
For privacy questions or a data request, contact the CrewPay administrator using the support option in Settings.