Privacy
Privacy Policy
Last updated: 7 October 2026
Everyone's In (a sole proprietorship operated by Saurav Gupta) ("Everyone's In", "we", "us") operates a Business to Business (B2B) marketplace for corporate event bookings in Noida, Uttar Pradesh, India.
1. Data fiduciary
The data fiduciary for this website is Everyone's In (a sole proprietorship operated by Saurav Gupta), Amrapali Silicon City, Sector 76, Noida, Uttar Pradesh 201309.
2. Data we collect
When you request a booking we collect your company name, the authorised contact person's name, work email, phone number, optional billing address, optional Goods and Services Tax (GST) number, your event requirements, the head count and event date, the quoted amount, any special instructions you type such as dietary or accessibility needs, and payment metadata.
If you apply to be a supplier we collect your business and trading name, the owner's name, contact email, phone number, category, city, your Goods and Services Tax (GST), Food Safety and Standards Authority of India (FSSAI) and Permanent Account Number (PAN) registrations where you provide them, and the rest of the application you fill in, which covers capacity, cuisines, service modes, pricing, lead time, cancellation policy, operating days and time slots.
We record which pages are viewed and which steps of the booking flow are reached, with the page path, a timestamp and non identifying details such as a venue identifier or a step number. These records do not contain your name, your contact details or an account, and they do not use cookies.
So that we can count visits rather than page loads, your browser makes a random session number for each browser tab and keeps it in that tab's session storage. It lasts only as long as the tab: the browser deletes it when the tab is closed, although a browser that restores a tab you reopen may bring it back with that tab. It is not a cookie, and it is not used to recognise you on a later visit. Each page and step record from that tab carries the number.
On the first page of a visit we also note how you arrived: the campaign labels in the link you followed, if it had any (the utm_source, utm_medium and utm_campaign parts of the web address), otherwise the name of the referring site that sent you, such as google.com, otherwise that no referring site was reported, which we record as a direct visit. We keep only the name of the referring site, never the full address of the page you came from. From the web address of our own page we keep only the page path and those three labels, never anything else in it. The same labels are attached to every later record in that visit.
We also record whether your browser reported itself as automated, which is how browsers controlled by testing software identify themselves, so that our own tests and other automated visits can be kept out of our visitor counts. A browser that our own team has marked as one of our own keeps an internal marker in its local storage, and every page and step record it sends is flagged as internal, so that our own visits are left out of our visitor counts.
If you send a booking request or an enquiry during a visit, the record of that step carries its booking reference. The page and step records from the same visit can then be linked to that request, and so to the details you gave in it. We use this only to understand which pages and steps led to a request.
Your Internet Protocol (IP) address is read from the network request to count how many requests each network makes, so the booking and supplier forms cannot be flooded. It is converted immediately to a one way keyed value that cannot be turned back into an address, and it is that value, not your address, which is stored. The counters are also used to decide whether to answer a request.
We do not store your Internet Protocol address, and we do not store your browser or device string. Both were previously written to our records and neither is any longer.
We do not store card or bank details. Payments are processed by Razorpay, which handles payment information under Payment Card Industry Data Security Standard (PCI DSS) controls.
3. Why we collect data
We collect data to facilitate bookings, prepare quotes, coordinate suppliers, issue invoices, meet our tax obligations, including Tax Collected at Source (TCS) filing under Section 52 of the Central Goods and Services Tax (CGST) Act, 2017 once suppliers sell through us, provide support and communicate about your booking.
4. Legal basis
We process personal data based on your consent, performance of our service contract and legal compliance obligations under applicable Indian law.
5. Consent and withdrawal
Where consent is required, we collect it through clear affirmative action. You may withdraw consent or request correction or erasure by contacting the Grievance Officer listed below.
6. Who we share data with
- Razorpay, for payment processing.
- The specific venue, restaurant, caterer or activity provider needed to fulfil your booking.
- Tax authorities, where filing or disclosure is legally required.
- Cloud hosting, analytics and operational service providers used to run the website.
We do not sell your personal data.
7. Retention
We keep each kind of record for a stated period rather than indefinitely.
- Booking and invoice records, and the payment metadata attached to them: 72 months from the due date of the annual return for the year they belong to. We use this period because Section 36 of the Central Goods and Services Tax Act, 2017 requires a registered person to retain books of account and records until the expiry of seventy two months from that date. We are not registered for Goods and Services Tax yet, so for now this period is our choice, made so that our records are complete when we register.
- Enquiries and quotes that never became a booking: 24 months, then deleted.
- Supplier applications that we do not proceed with: 24 months, then deleted.
- Page and funnel records: 12 months, then deleted.
- The request counters described in section 2: 24 hours. They hold no name, no address and no contact detail.
You can ask us to delete your data sooner by contacting the Grievance Officer listed below. We will do so unless the record is one we are required by tax law to keep, in which case we will tell you which record and why.
8. Security
We use reasonable security practices to protect information. Payment data is handled by Razorpay. No internet service can guarantee absolute security, but we work to reduce unauthorised access, misuse and loss.
9. Your rights
You may request access, correction, erasure, withdrawal of consent, grievance redressal and nomination rights available under the Digital Personal Data Protection (DPDP) Act, 2023.
10. Cross border processing
Some hosting, payment, analytics or support systems may process data outside India. Where this happens, we use those services for lawful business operations and applicable compliance.
11. Cookies and analytics
We use essential browser storage to remember the bundle you are building so it survives a page reload. We also keep, in the session storage of each browser tab, the random session number and the labels for how you arrived that are described in section 2. The browser deletes both when the tab is closed. A browser that our own team has marked as internal, as described in section 2, keeps that marker in local storage, which unlike session storage is not deleted when the tab is closed: it stays until the marker is removed or the browser's site data is cleared. None of this is a cookie. We do not use advertising cookies and we do not use a third party analytics product. The page and funnel records described in section 2 are written by our own service and stay on our own systems. We do not use this policy page to claim user counts, testimonials or unverified performance data.
12. Changes
We may update this policy when law, platform behaviour or service providers change. The latest version will be posted on this page with the updated date.
13. Grievance Officer
Saurav Gupta (Founder), +91 7417795407 (phone and WhatsApp), Amrapali Silicon City, Sector 76, Noida, Uttar Pradesh 201309. Complaints are acknowledged within 24 hours and resolved within 15 working days.