Effective date: 24 August 2026
Last updated: 24 August 2026
This Privacy Policy explains how we collect, use, share, store, and delete personal information when you use the ATLO Customer App, ATLO Staff App, website, and related services.
Who we are
What this policy covers
Consent and legal basis
Information we collect
App permissions
Location information
How we use information
How we share information
Third-party services
Where data is stored
How long we keep data
Security
Account deactivation and deletion
Your rights
Children
Cookies and similar technologies
Advertising, tracking and analytics
India-specific disclosures
Google Play Data Safety summary
Apple App Privacy summary
Changes to this policy
Contact and grievance officer
This Privacy Policy is issued by:
Legal name: ATLO Hospitality Service Private Limited
Brand names: ATLO, Atlo, Atlo Hospitality
CIN: U78100HR2024PTC125008
Registered office: N4, 001, Vatika Lifestyle Homes, Narsinghpur, Gurugram, Haryana, India – 122004
Email: atlohospitality@gmail.com
Website: https://atlo.co.in
In this policy, “ATLO”, “we”, “us”, and “our” mean ATLO Hospitality Service Private Limited. “You” means a customer, staff member, website visitor, or other user of our services.
ATLO is a hospitality manpower platform. Customers (hotels, restaurants, events, and other businesses) book trained hospitality staff. Staff members register, complete verification, accept jobs, complete shifts, and receive payouts.
This policy applies to personal information processed through:
ATLO Customer App (Android and iOS) — for businesses that book hospitality staff
ATLO Staff App (Android and iOS) — for hospitality professionals who take jobs
ATLO website and any one-page legal / support sites we publish
ATLO admin panel used by authorised ATLO personnel
Emails, SMS, WhatsApp, in-app chat, push notifications, and customer-support communications
Payments, wallets, invoices, KYC / document verification, and job-location verification
This policy is intended to meet the public-privacy-policy requirements of:
Google Play User Data policy and Data Safety disclosures
Apple App Store Review Guidelines (including Guideline 5.1 – Privacy, and in-app account deletion)
The Digital Personal Data Protection Act, 2023 (India)
The Information Technology Act, 2000 and the SPDI Rules, 2011, to the extent applicable
This document describes our actual product behaviour. It is not legal advice. Before publishing, replace the grievance officer name with your final company details and have counsel review if required.
By creating an account, tapping accept, or otherwise using the apps or website, you agree to this Privacy Policy.
We process personal data on one or more of the following bases:
Consent — for optional permissions such as camera, photos, notifications, precise location, and marketing messages. You can withdraw optional consent in device settings or in the app.
Contract — to create your account, fulfil bookings, verify identity, complete jobs, process payments and payouts, and provide customer support.
Legitimate uses / legal obligation — to detect fraud, comply with tax, labour, KYC, banking, law-enforcement, and store-policy requirements, and to keep records that Indian law requires us to retain.
If you do not provide information that is required to operate the service (for example a phone number for login, or KYC documents for staff onboarding), we may not be able to create or keep your account, assign jobs, or pay you.
We collect information that you give us, information created when you use the apps, and information from third parties (payment banks, SMS gateways, maps, and cloud providers). The exact fields depend on whether you are a Customer or Staff user.
Full name, first name, last name, title — Customer and Staff — account, bookings, invoices, display to the other party
Mobile number (primary, alternate, manager / staff contact numbers) — Customer and Staff — login, OTP, job coordination, support
Email address — Customer and Staff — login recovery, OTP, invoices, support
Password and MPIN (stored in hashed form) — Customer if set, Staff — authentication
Profile photo and cover image — Customer and Staff — profile display, job identification
Unique user ID, referral code, referred-by user — Customer and Staff — account identity, referral rewards
Account status (Active / Pending / Block / Deactivate) — Customer and Staff — access control and safety
Language preference — Customer and Staff — app experience
Business profile: business name, business type, description, restaurant / venue name
Business address: street, landmark, town, city, state, country, postcode / PIN
Tax and registration: GST number, company registration number, business name and address as on PAN
Invoice details: invoice name, invoice address, city, country, PIN, invoice notes
Job / site contacts: on-site contact name and phone for a booking
Demographics: date of birth, age, gender, religion (if provided)
Physical attributes: height and weight (if provided, for uniform / role matching)
Work preferences: job categories and subcategories, job type, travelling distance, preferred hour range, unavailability dates
Ratings: customer ratings, comments, category-wise average score
To verify identity, eligibility, and statutory compliance, we may collect copies and related flags for:
Aadhaar card (front and back images)
PAN card / licence / passport image
Address proof
Police verification certificate
Educational documents: Class 10, Class 12, graduation, and post-graduation mark sheets (where requested)
These are sensitive personal data / government identifiers. We use them only for verification, compliance, dispute handling, and payouts. We do not use them for advertising.
Saved addresses (name, full address, city, state, country, PIN, parking access)
Job-site coordinates (latitude and longitude) attached to bookings and carts
User location coordinates stored on the profile, if provided
Cart and booking details: category, subcategory, dates, start/end times, working hours, quantity, pax / kids / adults, price, tax/VAT, coupons, remarks
Outfit, equipment, and mobility requirements
Job status (Pending, Accepted, Started, Completed, Cancelled) and timestamps (start time, end time, time taken)
Customer approval of a shift, where the service category requires approval before a staff member can end the job
Staff assignment and acceptance records
Broadcasts, “notify me” requests, training videos viewed, FAQs, and inquiries (name, email, phone, message)
Wallet balance and wallet credit / debit history — Staff and, where applicable, customers — earnings, refunds, adjustments
Bank account name, account number, IFSC, bank name, branch, bank address — Staff — salary / job payouts
UPI ID / Virtual Address — Staff — UPI payouts
Razorpay order ID, payment ID and signature — Customers — collecting booking payments
Saved cards via Stripe (customer ID, setup intent, card brand/last digits as returned by Stripe) — Customers — storing payment methods; we do not store full card numbers on our servers
Payout transaction records (IMPS / NEFT / RTGS / UPI), amount, status, remarks, payer/payee VA, device / profile identifiers used by the bank API — Staff — settling wallet payouts through our banking partner
Invoices, GST, and commission / referral amounts — both — billing and accounting
Card numbers, CVV, and UPI PINs are processed by the payment provider. ATLO does not store full card PAN or CVV on its own database.
When a staff member ends a job, the Staff App may send GPS samples collected during the shift (coordinates and recorded time). If any sample is outside the allowed radius of the job site (default about 200–500 metres, configurable by ATLO), we store those samples in a staff location log for that staff member and booking. Administrators can review the log to confirm whether the staff member was at the designated site. See Section 6.
Customers and staff may message each other. We may store:
Text, emoji, replies, forwards, starred messages, read/delivery status
Images, video, audio, files
Shared location (latitude / longitude)
Shared contacts (name and number)
Payment-related chat events and polls
Mute, lock, archive, block, and report flags
Chat reports may be reviewed by ATLO to enforce safety rules.
FCM / device push-notification token
App-generated authentication tokens (JWT)
IP address, date/time, and basic server logs when you call our APIs
Device identifiers that a payment / payout partner may require to complete a transfer
File uploads (profile photos, KYC documents, chat media) stored on cloud object storage
SMS OTPs via Twilio (login / verification)
Email OTPs and transactional mail from our company mailbox
Push notifications (job assigned, job started, approval required, payout, admin broadcasts)
In-app notification history (title, body, image, date/time)
We do not ask for contacts from your full phone book except when you choose to share a contact inside chat.
We do not require access to your calendar, health-kit, or microphone except if you record/send audio in chat or the OS permission is needed for a feature you use.
We do not sell personal information.
The mobile apps may request the following device permissions. You can refuse optional permissions; some features will then not work.
Phone number / SMS (OTP) — Both apps — Account registration, login, and verification. OTP is sent to your registered Indian mobile number.
Camera — Both apps — Profile photo, KYC document capture, chat image/video.
Photo library / storage / files — Both apps — Uploading profile images, KYC documents, address proof, certificates, and chat attachments. Maximum upload size on the API is 100 MB per file.
Precise location (GPS) — Customer: job site pin. Staff: job attendance / site verification. Used only for service delivery, not for ads. See Section 6.
Approximate location — Both, if granted — May be used as a fallback when precise GPS is unavailable.
Notifications (push) — Both apps — OTPs are by SMS; push is used for jobs, approvals, chat, wallet, and admin alerts. You can disable push in OS settings. We then clear or stop using your device token.
Network / internet — Both apps — Required to use the service.
Microphone — If you send voice notes in chat — Only while recording a message you choose to send.
On iOS, the permission prompt text (location, camera, photo library, microphone, notifications) must match this policy. On Android 6+, runtime permissions are requested in context.
We collect precise location to run hospitality jobs — not to advertise, not to sell, and not to build marketing profiles.
When a customer creates a booking or saved address, the app may attach GPS coordinates of the venue. Staff need this to reach the correct site. Administrators use it to manage the order.
During an active job, the Staff App may record GPS samples (latitude, longitude, and time).
Those samples are sent to our servers when the staff member attempts to end the job.
We compare each sample with the job-site coordinates using distance calculation. The allowed radius is typically 200 metres (server-configurable, up to about 500 metres).
If all samples are inside the radius, we do not keep a separate location-violation log for that attempt.
If any sample is outside the radius, we store the samples in a staff location log linked to that staff member and booking. ATLO administrators can view the log (including distance from the site) to handle attendance disputes.
Ending a job may also require the customer’s in-app approval for certain service categories.
We do not continuously publish a staff member’s live location to other customers as a public map. Location is used for job verification, safety, dispute resolution, and fraud prevention.
You can turn location off in device settings. If you do, you may be unable to start or complete jobs that require site verification.
We use personal information to:
Create, verify, authenticate, and secure accounts (OTP, password, MPIN, JWT).
Onboard staff, review KYC documents, and decide account status (Pending / Active / Block).
Let customers search categories, build a cart, apply coupons, and place bookings.
Assign, accept, start, approve, and complete jobs; calculate working time and pay.
Show limited profile information (name, photo, phone as needed for the job) to the other party on a booking.
Process customer payments (Razorpay / Stripe) and staff payouts (wallet, UPI, IMPS, NEFT, RTGS via our bank partner).
Issue invoices and maintain GST / accounting records.
Send SMS, email, and push notifications that are necessary for the service.
Operate in-app chat and handle reports / blocks.
Verify that staff attended the designated job site.
Run referral rewards and commissions.
Provide ratings and improve matching of staff to roles.
Prevent fraud, abuse, duplicate accounts, and payment failure.
Comply with law, court orders, tax, labour, and store-review requirements.
Respond to support inquiries and grievances.
Maintain backups, logs, and security monitoring of our servers.
We do not use your KYC documents, bank details, or precise job-location logs for third-party advertising.
We share personal information only as needed to operate ATLO:
The other party on a job (customer ↔ staff): name, profile photo, phone (as needed), job time/address, chat messages you send — to perform the booking
ATLO administrators and authorised employees: account, KYC, bookings, location logs, payouts, chat reports — operations, verification, support, disputes
Payment processors and banks: name, phone, email, amount, bank/UPI details, payment tokens — to collect fees and pay staff
Cloud, SMS, email, maps, and push providers listed in Section 9: only the data each provider needs — hosting and communications
Professional advisers (auditors, lawyers, accountants): as required — compliance and disputes
Government, police, courts, regulators: as legally required — lawful requests
Successor entity: relevant account and transaction data — merger, acquisition, or restructuring, with equivalent protection
We do not sell personal information. We do not share personal information with data brokers. We do not use personal information for third-party cross-app advertising.
Our apps and backend use the following processors. Each has its own privacy policy. We require them to use data only to provide their service to us.
Cloud database — MongoDB Atlas (or equivalent hosted MongoDB): account, booking, chat, KYC metadata, logs
File / image storage — Amazon Web Services S3: profile photos, KYC files, chat media
Push notifications — Firebase Cloud Messaging (Google): device token, notification title/body
SMS OTP — Twilio: phone number and OTP message body
Transactional email — Google Gmail / SMTP (company mailbox atlohospitality@gmail.com): email address and message content
Customer payments — Razorpay: name, contact, amount, order/payment IDs
Saved cards / setup intents — Stripe: email, name, Stripe customer ID, card tokens
Staff payouts (UPI / IMPS / NEFT / RTGS) — ICICI Bank corporate / payout APIs: name, account/UPI, amount, transaction references
Maps / geocoding — Google Maps Platform: coordinates or address text you submit
Realtime chat transport — Socket.IO on our servers: chat payloads in transit
App stores — Google Play and Apple App Store: whatever you share with Google/Apple under their policies (purchases, crash reports if you opt in to OS sharing, etc.)
If we add a new processor that materially changes how data is used, we will update this policy.
ATLO is based in India. Primary operations and support are in India. Some processors (Google, Apple, Amazon, Twilio, Stripe, MongoDB, Razorpay) may store or process data in India and/or other countries.
Where data is transferred outside India, we do so for the performance of the contract with you and/or under the mechanisms allowed by applicable Indian law, and we take reasonable steps so that the processor protects the data.
Active account profile, bookings, chat, wallet: for as long as the account remains open and as needed to provide the service
OTP: until expiry (typically 5 minutes) or until replaced by a new OTP
Device push token: until you log out, deactivate, delete the account, or disable notifications
Deactivated account: kept in deactivated status. If it stays deactivated for more than 30 days, the account and associated data (including profile images, job history, wallet information, and related records) are permanently deleted
Immediate delete request (in-app Delete Account): the user record is hard-deleted. Associated operational records are removed or anonymised where technically feasible
KYC documents and payout records: may be kept for the period required by KYC, tax, labour, and banking law even after an account is closed, if a legal obligation applies
Staff location-violation logs: until the related dispute/audit is closed, or until account deletion / the retention period required for operational records, whichever is longer
Server logs: typically a short operational period, unless needed for security investigation
Invoices and tax records: as required by Indian tax law (generally 8 years or as then applicable)
Backup copies may persist for a limited time after deletion until they rotate out of our backup cycle.
We use reasonable technical and organisational measures, including:
TLS/HTTPS for API traffic
Password hashing (bcrypt) and JWT access tokens for authenticated routes
Access control so that customer, staff, and admin roles see only what their role requires
Cloud storage and database access restricted to authorised systems
Payment card data handled by PCI-DSS certified processors (Razorpay / Stripe), not stored as full card numbers on ATLO servers
No method of transmission or storage is 100% secure. You are responsible for keeping your phone, OTP, password, and MPIN confidential. Inform us immediately if you believe your account is compromised.
Google Play and the Apple App Store require a way to delete an account. ATLO provides this in both apps.
Customer: in-app control that calls Deactivate Account.
Staff: in-app control that calls Deactivate Account.
We set status to Deactivate and clear the push-notification token. You will not be able to use the app until you log in again (login reactivates a self-deactivated account) or until automatic deletion.
If the account remains deactivated for more than 30 days, it is permanently deleted with associated data. This cannot be undone.
An account blocked by ATLO for policy or fraud reasons is not the same as deactivation and may not be reactivated by simply logging in.
Customer and Staff apps include Delete Account, which permanently removes the account. This cannot be undone.
You may also email atlohospitality@gmail.com from your registered email or with your registered phone number and request deletion. We will verify it is you before deleting.
After deletion we may still keep information we must keep by law (for example invoices, payout proofs, or records of a legal dispute), or information that has been anonymised so it no longer identifies you.
Uninstalling the app does not by itself delete your account. Use Deactivate or Delete, or email us.
Subject to Indian law, you may:
Access the personal data we hold about you (profile, bookings, documents, wallet — available in the apps)
Correct inaccurate profile, address, and bank details in the app
Withdraw consent for optional permissions in device settings
Delete your account as described in Section 13
Nominate (under the DPDP Act) a person to exercise rights in case of death or incapacity, by writing to us
Grievance — complain to our Grievance Officer (Section 22) and, if unresolved, to the Data Protection Board of India
We will not charge a fee for reasonable requests. We may refuse a request that is legally prohibited, that would affect another person’s rights, or that we cannot verify.
ATLO is a business / employment platform. It is not directed at children.
Staff users must be 18 years or older (KYC, police verification, and paid work).
Customer accounts are intended for businesses and adult representatives of those businesses.
We do not knowingly collect personal data from children under 18 for the purpose of creating an account.
A booking may include a count of children attending an event (pax / kids) as operational information. That is not an account for a child and should not include a child’s name or contact details.
If you believe a minor has created an account, email atlohospitality@gmail.com and we will delete it.
Play Store age rating: we intend the apps to be listed as Rated for 18+ / not for children. We do not participate in Designed for Families. We do not use Google AdMob or similar child-directed ads.
The mobile apps use authentication tokens stored on the device, not browser cookies. If you visit our website or this privacy-policy page:
The hosting provider may set strictly necessary cookies or logs (IP, browser type) for security and delivery.
We do not currently use advertising cookies or cross-site trackers on this legal page.
You can control cookies in your browser. Blocking all cookies may affect website features.
ATLO does not sell user data.
ATLO does not use your personal data for third-party interest-based advertising.
We do not share data with third-party advertisers for their own marketing.
We may use first-party operational analytics (for example crash or performance data from Apple, Google, or Firebase, if enabled in a given app build) only to keep the apps stable. If a specific build uses Firebase Analytics, Crashlytics, or similar, that data is used for app functionality and diagnostics, not for ads.
We do not use the data for “tracking” as defined by Apple’s App Tracking Transparency (we do not link your data with third-party data for advertising across other companies’ apps and websites). Therefore we do not currently require an ATT “Allow Tracking” prompt for advertising. If that changes, we will update this policy and the App Store privacy labels.
Data Fiduciary: ATLO Hospitality Service Private Limited.
Data Principals: customers, staff, and other individuals whose data appears on a booking (for example an on-site contact).
Sensitive personal data / government IDs: Aadhaar, PAN, bank account, precise location, and KYC images are processed for verification, payouts, and job attendance — not for advertising.
Aadhaar: we collect Aadhaar images only as identity proof for staff onboarding. We are not an AUA/KUA performing UIDAI e-KYC unless we separately notify you. Do not send Aadhaar OTP to anyone claiming to be ATLO support unless you are inside the official app flow.
Grievance officer details are in Section 22 (required under the IT Act / DPDP framework).
Use this section when filling Play Console → App content → Data safety. Declare collection as collected and not sold. Encryption in transit: Yes. Users can request deletion: Yes.
Name — Collected. Shared with the other party on a job and processors. Purpose: app functionality. Required.
Email address — Collected. Shared with payment / email processors. Purpose: app functionality. Staff: generally required. Customer: if provided.
User IDs — Collected. Shared internally / with processors. Purpose: app functionality. Required.
Address — Collected. Shared with staff assigned to the job. Purpose: app functionality. Required for bookings.
Phone number — Collected. Shared with SMS provider and the other party as needed for the job. Purpose: app functionality. Required.
Photos — Collected. Stored on AWS; shown in profile/chat. Purpose: app functionality. Optional except required KYC for staff.
Videos / audio / files — Collected if you send them in chat or upload documents. Shared with chat counterparty and cloud storage. Purpose: app functionality. Optional.
Voice or sound recordings — Only if you send audio in chat. Shared with chat counterparty. Purpose: app functionality. Optional.
Music files — Not collected.
Other in-app messages — Collected (chat). Shared with the other user; ATLO if reported. Purpose: app functionality. Optional.
Emails (content we send/receive) — Transactional only. Shared with email processor. Purpose: app functionality. Required for security mail.
Contacts — Only if you attach a contact in chat. Shared with chat counterparty. Purpose: app functionality. Optional.
Approximate location — May be collected. Internal use. Purpose: app functionality. Optional.
Precise location — Collected (job site and staff shift verification). Shared with ATLO admin; not sold. Purpose: app functionality. Required to complete location-verified jobs.
Credit card / debit card — Processed by Stripe/Razorpay; we do not store full PAN. Shared with payment processor. Purpose: app functionality / payments. For customer payments.
Purchase history — Collected. Internal / tax. Purpose: app functionality. Required if you book.
Other financial info (bank, UPI, wallet) — Collected (staff payouts). Shared with bank payout partner. Purpose: app functionality. Required to get paid.
National ID (Aadhaar, PAN, etc.) — Collected (staff KYC). Shared with ATLO verification staff; not sold. Purpose: app functionality / compliance. Required for staff activation.
Health info (height/weight if entered) — Only if you enter it on staff profile. Internal matching. Purpose: app functionality. Optional.
Political / religious beliefs — Religion field if you enter it. Internal. Purpose: app functionality if used for matching. Optional.
Device or other IDs — Collected (FCM token; payout device fields if sent). Shared with Firebase; bank API if required. Purpose: app functionality. Push is optional.
Crash logs / diagnostics — If enabled in the app build via Apple/Google/Firebase. Shared with that SDK vendor. Purpose: analytics / functionality. Follow OS settings.
Advertising or tracking IDs for ads — Not collected. Not shared.
Data is encrypted in transit (HTTPS). Users can request deletion in the app.
Use this when completing App Store Connect → App Privacy for each app.
Contact Info (name, email, phone, physical address)
Identifiers (user ID, device token)
Location (precise, coarse)
User Content (photos, video, audio, customer support, other user content / chat)
Financial Info (payment info, other financial info, purchase history)
Sensitive Info (government ID / KYC; religion or health-related fields only if the user enters them)
Usage Data (product interaction — bookings and jobs)
Diagnostics (if Crashlytics or similar is in the iOS build)
App Functionality
Product Personalisation (limited: language, job matching, referrals) — do not select Third-Party Advertising or Developer’s Advertising
Declare that the above data is not used for tracking unless you later add an advertising SDK that tracks across apps.
Apple requires an in-app account deletion flow. Both ATLO apps provide Deactivate Account and Delete Account. Also publish this page URL as the privacy policy URL in App Store Connect.
We may update this Privacy Policy from time to time. The “Last updated” date at the top will change. Material changes will be notified in the app, on this page, or by email/SMS where appropriate. Continued use after the effective date means you accept the updated policy. If we need fresh consent under law, we will ask for it.
For privacy questions, access, correction, or deletion:
Organisation: ATLO Hospitality Service Private Limited
Postal address: N4, 001, Vatika Lifestyle Homes, Narsinghpur, Gurugram, Haryana, India – 122004
Email: atlohospitality@gmail.com
Website: https://atlo.co.in
In accordance with the Information Technology Act, 2000, the IT Rules, and the Digital Personal Data Protection Act, 2023:
Name: [Insert Grievance Officer full name]
Designation: Grievance Officer
Email: atlohospitality@gmail.com
Address: N4, 001, Vatika Lifestyle Homes, Narsinghpur, Gurugram, Haryana, India – 122004
Response time: We aim to acknowledge grievances within 24 hours and resolve them within 15 days, or within any shorter period required by law.
Replace the Grievance Officer name (and add a dedicated phone number if you have one) before you submit this URL to Play Console and App Store Connect. Google and Apple both check that the policy is a working public webpage, lists the operator, describes data collected, and includes a contact method.
© 2026 ATLO Hospitality Service Private Limited. All rights reserved.
This is the official Privacy Policy for the ATLO User App and ATLO Staff App.