This policy explains how PassOut handles your personal data on the website passout.live and in the PassOut app for Android and iPhone. It is written to meet the Digital Personal Data Protection Act, 2023 ("DPDP Act"), the Digital Personal Data Protection Rules, 2025, and the Information Technology Act, 2000 and its rules.
1Who we are and how to reach us
PassOut is run by Concept Crafters (Concept Crafters), Nashik, Maharashtra, India - GSTIN 27AATFC6034D1ZF. Registered office: Concept Crafters, Mahalaxmi Nagar, Jatra Hotel, Nashik, 422003. For the data described here, Concept Crafters is the data fiduciary: we decide why and how your data is used, and we are responsible for it.
The person who answers questions and requests about your data is our Grievance Officer, Digvijay - email support@passout.live. You can also use Help or write to support@passout.live.
2What we collect
Your account
- Name, mobile number and/or email (at least one of mobile or email), and a password, which we store only in scrambled ("hashed") form. Accounts made at checkout ask for name, mobile and email.
- Optional: your city, state, PIN code and address, and a profile photo.
- When you sign in, we record the date and time, your IP address, and your browser and operating system. In the app we also record the device name your phone reports (for example "Samsung SM-A515F" or your iPhone's name), so you can see and end your signed-in devices.
Your bookings
- The events and tickets you book, prices, coupons and add-ons, and your booking history.
- Attendee names and emails you enter for each ticket (optional - ticket 1 uses your own).
- Payment status and references from our payment partner (order and payment IDs; paid, failed or refunded). We never receive or store your card number, UPI PIN or bank login.
- Tickets and entry: your QR codes, and when, at which gate and on which scanner a ticket was checked in.
- Refund requests: your reason, and the UPI ID or bank account (holder name, account number and IFSC) you give for the refund. The account number is stored encrypted.
Sports events (runs, rides, swims, treks, tournaments)
Only for these events, and only the fields the organiser switches on: date of birth, gender, T-shirt size, city, club, best time, name on bib, blood group, emergency contact, medical conditions or allergies, ID type and the last 4 digits of an ID (never the full number), an optional photo, answers to the organiser's own questions (including files), team member names and dates of birth, a parent or guardian's name, mobile and consent for under-18 participants, and the time, version and IP address when you accepted the event's waiver.
The health and other sensitive details (date of birth, blood group, emergency contact, medical details, ID last 4 digits, guardian details) are stored encrypted and used only to run the event safely: age and gender categories, kit, bibs, first aid and results. They are shared only with that event's organiser, and only if you tick a separate box - "I agree to share these details with the organiser for safety at the event." - which is never ticked for you and is needed only for events that ask blood group, medical or emergency details. We record when you ticked it.
If you contact us
- What you write through Help or the contact form (name, email, subject, message) and any files you attach.
- Your email, if you subscribe to our newsletter.
Organisers and their staff
- Organisation name, contact person's name, email, mobile, address, public description, logo, cover photo and social links.
- KYC: legal name, business type, PAN, PAN card, address proof, cancelled cheque or passbook, and optionally GSTIN and GST certificate.
- Bank account for payouts: holder name, account number (stored encrypted), IFSC and bank name.
- Gate staff names and mobile numbers, and details organisers type in for guest lists and box-office sales (a name, and optionally a mobile and email).
Data created when you use PassOut
- Web sessions: your IP address and browser while you are logged in.
- One-time codes: the mobile or email a code was sent to, when, from which IP address, and the number of tries. We keep only a scrambled form of the code itself.
- Message records: who we sent an SMS, email or notification to, what it said, and whether it was delivered (one-time codes are hidden in these records).
- Account change records: when an account is changed, banned or deleted, we record who did it and the details before the change, to protect accounts and investigate problems.
- Event page counts: when an event page or its pass picker is opened, on the website or in the app, we add one to a daily count for that event, with where the visit came from (for example a search engine, Instagram, an organiser's link, website widget or QR poster), website or app, phone or computer, and the city you picked. These counts don't include who you are, your IP address or any device ID, and use no cookies. Organisers see the totals for their own events.
- Promoter credit: if you arrive through an organiser's promoter link, the promoter's code is saved with your booking so the right promoter gets the credit.
- Organisers you hide: if you hide an organiser, we keep that choice so their events don't show to you.
Location
- You choose your city yourself to see nearby events. We don't track where you are.
- The PassOut app never asks for your location.
- On the website's map page, "near me" uses your browser's location only if you allow it, and only inside your browser - it is never sent to us. Organisers placing a venue on the map can also let their browser find it.
3Data from the PassOut app
- Device ID: a random ID the app creates when it is installed - not your phone's IMEI, serial number or advertising ID. The app sends it with each request; our server uses it only in scrambled form to apply fair limits on one-time codes and spot misuse, and doesn't store it.
- Push notification token: if you allow notifications, Google's Firebase Cloud Messaging gives the app a token so we can send you booking, ticket, refund and support updates. The app explains this before your phone asks. The token is deleted when you sign out, when it stops working, after 90 days without use, or when you delete your account.
- App integrity check: the app uses Firebase App Check (Google Play Integrity on Android, Apple App Attest or DeviceCheck on iPhone) to prove that a request for a one-time code comes from the genuine PassOut app. This sends a short-lived token about the app and device, not your personal details.
- Camera and photos: used only when you choose to - to take or pick a profile photo, attach photos to a support request or a sports booking, upload event posters, photos, videos or documents (organisers), or scan ticket QR codes at the gate (organisers and gate staff). The app explains why before your phone asks for camera access. Only the photos and files you choose reach us; when scanning, the QR code is read on the phone and no camera image is kept. The microphone is used only while you record a video to upload.
- One-time code autofill (Android): Google's SMS User Consent asks you before the app reads a PassOut code message. The app never reads your other SMS.
- Offline passes: your passes, and for gate staff the event's entry list, are saved on the phone so they work without internet. The scanner list is removed from the phone 24 hours after the event's scan window closes.
- Crash reports: if the app crashes or hits a serious error, it sends a crash report to Google's Firebase Crashlytics so we can fix it: what went wrong in the app's code, the app version, the screen you were on (without any booking or event numbers), and the phone's model, system version, memory and free space. Each report carries a scrambled form of your account number (so we can tell how many people a crash affects) - never your name, phone number or email. Crash reports are sent only from the app downloaded from the stores, and you can turn them off in Profile -> Send crash reports.
- The app has no ads, no advertising ID and no third-party analytics or tracking tools, and never reads your contacts, call logs or calendar.
4Why we use it
We use your data only to:
- create and run your account and let you log in securely;
- process bookings and payments, issue tickets, check you in at the gate, and handle cancellations and refunds;
- send you messages about your account and bookings (see the SMS & Communication Policy);
- let organisers run their events, check organisers' identity (KYC) and pay them;
- answer your questions and complaints;
- prevent fraud, misuse and fake bookings, and keep PassOut secure;
- keep records and meet our legal and tax duties, such as GST.
We use your data because you asked us for a service (for example a booking), because the law requires it (for example tax records), or with your consent. We don't use your data for advertising, and we don't send promotional messages.
5Who sees your data
We share only what is needed:
- The organiser of an event you book sees, for that event: your name, email and mobile number, the attendee names on your tickets, ticket types, amounts, and check-in times and gates. They can download this as a list. If you ask for a refund, they also see your reason and the UPI ID or bank account you gave, because the organiser sends the refund. The organiser may call or message you about the event.
- Sports events: the organiser sees all the participant details they asked for, including health and emergency details, and can download them to run the event safely. Each download is recorded.
- Gate staff working the event see attendee names, booking IDs and ticket status while scanning.
- Organisers you follow see your name, the date you followed and how many of their events you booked - never your email, and your mobile number only partly hidden.
- Cashfree Payments, our payment partner: your name, email, mobile and the amount, to take payments and send refunds.
- Fast2SMS, our SMS partner: your mobile number and the message text (for example a one-time code or booking ID).
- Hostinger hosts our website and database and sends our emails, so it stores the data described here for us.
- Google (Firebase) delivers app notifications (your push token and the notification text), checks app integrity (Firebase App Check) and receives app crash reports (Firebase Crashlytics, as described above).
- Backup storage: every night an encrypted copy of our database and uploaded files is stored with a cloud storage provider, away from our main server, so PassOut can recover from a server failure. The provider can't read it - only we hold the key.
- Maps and videos on event pages: the Google Maps venue map loads from Google only if you accept it, and event videos come from YouTube (privacy-enhanced mode) or Vimeo (do-not-track mode). The map page uses OpenStreetMap.
- Organisers' payouts are sent by bank transfer from our bank account.
- Government and law enforcement, when the law requires it - for example a court order or a lawful request under the IT Act.
We never sell your personal data, and we don't share it with advertisers or data brokers. Some providers, such as Google, may process data outside India; we use them only as the DPDP Act allows.
6How long we keep it
| Data | How long |
|---|---|
| Account details | Until you delete your account (see below) |
| App sign-ins and push tokens | Until you sign out, or 90 days without use |
| Website log-in sessions | 2 hours without activity, or 30 days if you tick "Keep me logged in" |
| Sports health and safety details (date of birth, blood group, medical, emergency contact, ID last 4, guardian, photo, uploads) | Deleted 90 days after the event. Name, bib, category and result stay with the event's results |
| Sign-in records, one-time code records and message records (SMS, email, push, in-app) | Deleted after 12 months |
| Support requests, their messages and attachments | Deleted 24 months after the request is closed |
| Push tokens | When you sign out, or after 90 days without use |
| The UPI ID or bank account you give for a refund | Deleted 6 months after the refund is sent (or after the request is declined or withdrawn). The last 4 digits stay with the refund record |
| Bookings, payments, refunds, invoices, payouts and the ledger | 8 years, because GST and tax law require it. After that the records stay only as numbers: names, emails, phone numbers, addresses and payment details in them are removed |
| Organiser KYC documents | 5 years after the organiser account is deleted, then erased |
| Items an admin moves to Trash | Permanently deleted after 30 days (except anything with bookings or payments) |
| Account change records (who changed or deleted an account, and the details before) | Kept to protect accounts and investigate problems |
| Organisers you hid | Until you unhide them or delete your account |
| App crash reports (Firebase Crashlytics) | 90 days |
| Server error records (with personal details removed) | 90 days |
| Encrypted backups | Daily copies 30 days, monthly copies 12 months. Data deleted from PassOut is gone from the backups once those copies expire |
These periods are applied automatically every day.
7Deleting your account
You can delete your account in the app (Profile -> Edit profile -> Delete account; organisers: More -> Delete organiser account), in Account settings on the website, or without the app or a log-in at passout.live/delete-account. Each way checks it's you with a one-time code. What is deleted, and what the law makes us keep, is explained in Account & Data Deletion.
8Your rights
Under the DPDP Act you have the right to:
- Access: ask for a summary of the personal data we hold about you and who we shared it with.
- Correct and update: fix data that is wrong or incomplete. You can change most details yourself in your profile.
- Erase: delete your account and data, except what the law makes us keep.
- Withdraw consent: stop any use based on your consent. This doesn't affect what was done before.
- Nominate: name another person who can use these rights for you if you die or can't act yourself. Send their name and contact through Help.
- Grievance: complain to us, and if you're not satisfied, to the Data Protection Board of India.
How: use Help from your account, or email support@passout.live. We may ask you to confirm it's you. We acknowledge within 24 hours and reply within 15 days. See Grievance Redressal.
9Security
- All traffic to PassOut uses HTTPS (encryption in transit); plain http addresses are redirected.
- Passwords are hashed, and one-time codes are stored only in scrambled form.
- Bank account numbers (organiser payouts and buyer refunds) and sports health details are encrypted in our database.
- KYC documents, sports uploads and support attachments are kept in private storage, shown only to the account they belong to and our team.
- Signed QR codes, so tickets can't be forged; limits on log-in and code attempts; a record of admin actions.
- Encrypted nightly backups kept away from our main server, and round-the-clock checks that alert our team if something stops working.
- Only staff who need your data for their work can see it.
No system is 100% secure. If a personal data breach happens, we will tell the people affected and the Data Protection Board of India, and report it to CERT-In, as the law requires - with what happened, what it means for you and what we are doing about it.
10Children
PassOut accounts are for people aged 18 or over. We don't ask your age when you sign up, so please don't create an account if you're under 18 - a parent or guardian can book for you from their own account. For sports events, the person booking enters each participant's date of birth, and under-18 participants need a parent or guardian's name, mobile and consent. We don't track children or show them ads. If you think a child has an account, tell us through Help and we will delete it.
11Cookies
The website uses a few cookies to keep you logged in and secure. See the Cookie Policy.
12Changes to this policy
The "Last updated" date at the top shows when this policy last changed. If a change is important, we will tell you by email, SMS or a notice on PassOut before it applies, and ask for your consent again where the law requires it.
13Grievance Officer
- Name: Digvijay
- Company: Concept Crafters (PassOut), Nashik, Maharashtra, India - GSTIN 27AATFC6034D1ZF
- Address: Concept Crafters, Mahalaxmi Nagar, Jatra Hotel, Nashik, 422003
- Email: support@passout.live
Process and timelines: Grievance Redressal.