A

AtlasCrew — Privacy Policy

Last updated 18 November 2026

AtlasCrew is work software. A company signs up, invites its employees, and uses it to assign tasks, post announcements, keep employee records and manage leave. This policy explains what we hold, why, and what you can do about it.

The short version. We collect what is needed to run the app: your phone number to sign you in, your name so colleagues know who did what, and the employment records your employer keeps — job title, department, hire date, work contact, emergency contact, leave balances.

AtlasCrew holds no pay, no bank details and no identity document numbers. Not restricted, not masked — those fields do not exist in the product. AtlasCrew is not a payroll system and never moves money. We do not sell data, we do not advertise, and we do not build profiles of you.

1. Who is responsible

AtlasCrew is operated by Mohamed Awaden, trading as Awaden Software, established in Egypt. Contact: support@atlascrew.io.

For data your employer puts into AtlasCrew, your employer is the data controller and we are the processor. Your employer decides which of the available records to keep about you. We provide the software and the safeguards; we do not decide what goes in. If you are an employee asking to see, correct or delete an employment record, start with your employer. For your own account, you can act directly — see section 6.

What your employer cannot do is record your pay, your bank details or your national ID or passport number in AtlasCrew, because the product has nowhere to put them. If someone has asked you for those for work purposes, whatever they are using for it, it is not this.

2. What we collect

DataWhySource
Phone number Your sign-in name. Verified by SMS code the first time and whenever you reset your password. You
Password To sign in. Stored by Firebase Authentication as a salted hash — nobody at AtlasCrew can read it. You
Name, job title, department So colleagues can see who a task belongs to You or your employer
Tasks, hours logged, deadlines, status The core function of the app You and your managers
Site or location name — free text To say where a job is. We do not use GPS and do not track your location. Typed by a manager
Avatar — optional So colleagues recognise you. You pick one of the illustrations built into the app; we store only which one. No photo of you is taken or uploaded. You
Photos you attach as proof of work Evidence a job was completed Your camera, only when you choose
Posts, comments, likes The company feed You
Leave balances and requests To record time off and who approved it You and your managers
Push notification token To send you a notification when work is assigned Your device
Crash reports and diagnostics To fix crashes. Device model, OS version, stack trace. Firebase Crashlytics

2.1 Employee records

If your employer uses the employee-record features, AtlasCrew also stores the following. All of it is optional and entered by a person — AtlasCrew never reads it from your device, and a company that leaves these fields blank has none of it stored.

DataWhyWho can read it
Employee number, hire date, contract type, employment status, work location, reporting manager The employment record itself Everyone in your company
Work phone, personal phone, email address, home address So colleagues can reach you Everyone in your company
Emergency contact name, phone and relationship To reach the right person if you are hurt at work. On a site, this is the field that matters most. Everyone in your company
Blood type, if your employer records one Optional. Held because some employers ask for it; see the note below about what it is and is not good for. You, the company owner, and their HR staff. Not your manager, not your colleagues.
Licence and permit names and expiry dates So a manager can see a certificate is about to lapse. The document numbers are not stored here. Everyone in your company
HR notes — free text Whatever your employer chooses to record Everyone who can see your profile. The app says so on the field.
No pay, no bank details, no identity numbers. AtlasCrew has no field for your salary, your allowances, your bank account, your national ID number or your passport number. This is not a permission setting you could be granted — the product does not have anywhere to store them.

Until 11 October 2026 it did, in a separate record restricted to the company owner, their HR staff and you. We removed the fields and deleted the records. The reasoning was simple: AtlasCrew never paid anyone, so holding the figures bought no feature while carrying real risk for you. Pay and identity numbers are treated as sensitive personal data under most data protection regimes, including the GDPR, and the safest way to protect data is not to have it.

What this means in practice: there is no breach of AtlasCrew that can expose your pay or your bank account, because we do not know them.

What we do not collect

3. Who can see your data

Inside AtlasCrew, data is isolated per company. A member of one company cannot read another company's data — this is enforced by database rules on our servers, not by the app.

Within your company:

4. Who we share with

We do not sell data. We use these processors:

Our payment provider does not receive employee data. Billing is between us and the company owner; the number of paid seats is the only thing about your workforce that reaches them, and it is a number, not a list.

We disclose data to authorities only where legally required, and will tell the affected company unless the law forbids it.

5. How long we keep it

Your employer is probably required by employment or tax law to keep payroll and identity records for some years after you leave. Those records live in whatever system they use for payroll — never in AtlasCrew — and what they do with them is governed by their own policy, not this one.

6. Your rights

You may access, correct, delete or export your data, and object to processing. These rights are given by the GDPR where it applies to you, by the UK GDPR, and by the data protection law of the country where we are established (Egypt's Personal Data Protection Law No. 151 of 2020). We apply them to everyone, wherever you are, rather than only where a statute compels us.

Correct your own details, from inside the app

Open your profile and edit your personal phone, email, home address, emergency contact and blood type. You do not need to ask anyone. The employment fields are your employer's record, so ask them to correct those.

Delete your account, from inside the app

Settings → Account → Delete account. This erases your profile, your contact and emergency details, your leave records and your membership, including anything stored beneath them. Work you completed stays with the company, because it belongs to your employer's business records; your name is removed from it.

Export everything

A company owner can export all company data as JSON from Settings → Your data → Export everything. It covers every collection AtlasCrew holds — members, tasks, posts, requests and reports — so it is a complete answer to an access request.

For anything else, email privacy@atlascrew.io. We answer within 30 days.

7. Security

8. Children

AtlasCrew is for workplaces and is not directed at anyone under 16. We do not knowingly collect data from children. If you believe we have, contact us and we will delete it.

9. Where your data is stored, and international transfers

AtlasCrew runs on Google Cloud. Our application servers are in the European Union (europe-west1). Our database is in Google's United States multi-region, and photos you attach are stored in the European Union.

So wherever you use AtlasCrew from, your data is transferred to and stored in the United States and the European Union. These transfers rely on Google Cloud's Standard Contractual Clauses, and Google Cloud is certified under the EU–US Data Privacy Framework. Data is encrypted in transit between every one of these locations.

10. Changes

If we change this policy in a way that materially affects you, we will notify company owners by email and show a notice in the app before the change takes effect. The date at the top always reflects the current version.