Privacy Policy
Version 1
This policy explains what personal data BDQ Social collects, why we collect it, who receives it, how long we keep it and how you can see, correct or delete it. BDQ Social is run by Digitanomics LLP, which is responsible for your data. We collect only what we need to run our events, sell tickets and stalls, and keep our services safe. We do not sell your data, and we use no advertising trackers.
Last updated: 12 November 2026
Who we are
BDQ Social (bdqsocial.com) is operated by Digitanomics LLP (LLPIN: ACO-0046), a limited liability partnership registered in India.
- Registered office: GF 10, 11, Arize House, Beside Venus Hospital, Old Padra Road, Vadodara, Gujarat 390020
- Phone: +91 98794 48835
- Email for privacy questions, data requests and complaints: hi@bdqsocial.com
- Website: bdqsocial.com
Under India's Digital Personal Data Protection Act 2023 (the DPDP Act), Digitanomics LLP is the data fiduciary for the personal data in this policy: it decides why and how the data is used and is responsible for it. In this policy, "BDQ", "we" and "us" mean Digitanomics LLP, trading as BDQ Social.
We follow the DPDP Act and its Rules, the Information Technology Act 2000 and its rules on reasonable security practices and sensitive personal data, and the Consumer Protection (E-Commerce) Rules 2020.
What this policy covers
This policy covers our website, your BDQ account, ticket purchases, entry to our events, vendor applications and stall bookings, the artists and sponsors we work with, and the messages we send. Vendors should also read the Vendor Data Policy. For cookies and browser storage, see Cookies & Local Storage.
What we collect and why
For each kind of data below, we say what we collect, why, on what basis, who else receives it and how long we keep it. The basis is one of these:
- Service: you gave us the data to get something from us, such as a ticket or a stall, and we use it only for that. The DPDP Act treats this as a legitimate use.
- Consent: you agreed to it separately, by ticking an empty box or choosing to take part. You can withdraw it at any time.
- Legal duty: a law requires us to keep or use the data.
Every form that asks for your phone number or email shows a short notice saying what we collect, why and who receives it, and we record the version of that notice. You can choose not to give us data, but we may then be unable to provide the service that needs it, such as a ticket.
Sign-in and your account
- What: your mobile number (Indian +91 numbers only), and your name and email address if you add them.
- Why: to sign you in with a one-time code (OTP), keep your tickets in your account, and contact you about your orders.
- Basis: service.
- Shared with: Google Firebase Authentication, which sends the one-time code to your phone by SMS and confirms your number.
- Kept: your account details while your account is open; records of sign-in codes for 30 days.
Orders, payments and receipts
- What: what you bought, the amounts, any discount, coupon, presale or referral code used, the phone number and email address on the order, the payment reference numbers and status from Razorpay, and your receipt. Online checkout asks for your email address so we can send your tickets. If you buy at our box office or staff issue you a ticket, we record your phone number, and your email only if you give it.
- What we never receive: your card number, card security code, UPI PIN or bank login. You enter these on Razorpay's checkout, and they stay with Razorpay.
- Why: to take payment, issue your tickets and receipt, prevent fraud, and keep the accounts we must keep.
- Basis: service, and legal duty for the accounting records.
- Shared with: Razorpay, which takes the payment for Digitanomics LLP as the merchant. If you dispute a payment with your bank, the dispute is handled through Razorpay, and we send Razorpay the order and entry records it needs as evidence.
- Kept: 8 years.
Tickets, entry and re-entry
- What: your tickets (each with a QR code, the number of people it admits and the days it is valid) and a record of each scan at the gate: in or out, the time, the gate device and the result. Tickets do not carry attendee names.
- Why: to deliver your tickets, check them at the gate, stop copied or forged tickets, and allow same-day re-entry.
- Basis: service.
- Shared with: our email service, which delivers your tickets.
- Kept: your tickets: 8 years, with your order. Gate scan records: 1 year after the edition.
Ticket transfers and gifts
- What: when you transfer or gift a ticket, a single-use claim link, and the account of the person who claims the ticket with a one-time code. The ticket then gets a new QR code, and the old one stops working.
- Why: to move the ticket safely to the new holder.
- Basis: service.
- Shared with: no one outside BDQ, apart from the services that run our systems.
- Kept: 8 years, as part of the ticket record.
Waitlist
- What: your phone number or email address, the edition, and whether you are waiting for a ticket or a stall.
- Why: to tell you when tickets or stalls open.
- Basis: consent.
- Shared with: the service we use to send you the message.
- Kept: until that edition ends, or sooner if you ask us to remove you.
Messages you send us
- What: your name, email address and message, and, if you add them, your phone number, the topic and an order reference.
- Why: to answer you.
- Basis: consent.
- Shared with: no one outside BDQ, apart from the services that run our systems.
- Kept: 1 year after our last reply to you.
Vendor applications and stall bookings
- What, from the vendor interest form: your brand name, category, products, contact name and phone number, and, if you add them, your email address, Instagram, website and city.
- What, from a vendor account: your phone number for sign-in; your brand profile; your KYC details; your acceptance of the participation agreement; our team's record of your call-back; and your bookings and payments.
- Public brand profile: your brand name, category, what you sell, story, website, Instagram and images are shown on our website. Your legal or registered name, contact person, WhatsApp number, email address and city stay private.
- KYC: your PAN (all vendors), your FSSAI licence or registration number (food and drink vendors), your GSTIN if you choose to give it, and images of these documents. We use KYC only to verify you. We do not collect GST or issue tax invoices.
- Agreement record: your typed name, the agreement version, the time, your IP address, the stall fee and the signed PDF.
- Why: to review your application, verify you and your licences, make the call-back, book your stall, take payment, show your brand to visitors, and keep proof of the agreement.
- Basis: service, and legal duty for the accounting records.
- Shared with: Razorpay for payments; Cloudflare, which keeps your documents in a private store.
- Kept: KYC documents and numbers are deleted 1 year after your last event, after which we keep only the result of the check. Bookings and payments: 8 years. Your account and profile: while your account is open. Agreement records and call-back notes: 8 years, with your bookings. An interest form that does not lead to a booking: 1 year after the edition you applied for.
Leads you share with a vendor
- What: at a stall, you can scan the vendor's code and share your contact on our lead page: your phone number or email address, and your name if you give it.
- Why: so that vendor can contact you.
- Basis: consent. The consent screen names the vendor, and only that vendor receives your details.
- Shared with: that vendor. A vendor can export only its own leads. Once it has your details, the vendor is responsible for how it uses them: only for the purpose shown to you, stopping when you ask, and deleting them when you ask. You can ask the vendor directly. If you ask us, we delete our copy and pass your request to the vendor, who must act on it.
- Kept: our copy, which the vendor sees in its vendor portal: 1 year after the edition in which you shared it, or sooner if you ask us to delete it. It is then removed from the vendor portal too.
Marketing messages and event reminders
- What: your email address, your consent (the version of the wording you agreed to and when), and your unsubscribe if you make one.
- Why: to send you news and offers from BDQ, and reminders 24 hours and 2 hours before an event.
- Basis: consent only. The marketing box is separate from the terms box and starts unticked. You do not need it to buy a ticket.
- How to stop: use the one-click unsubscribe link in any marketing email, or email hi@bdqsocial.com. We keep unsubscribed addresses on a do-not-send list so that we do not message you again.
- Channels: email only. We send no marketing by SMS. We will update this policy before we use any other channel.
- Shared with: our email service.
- Kept: until you unsubscribe, or after 2 years with no activity from you.
Photos and video at our events
- What: BDQ photographs and films its events. You may appear in photos and video.
- Why: to show our events in our marketing.
- Basis: consent. Entering a BDQ event means you agree to this, as our Terms and Conditions also say. Signs at the entrance tell you that we photograph and film.
- Your choice: you can opt out at any time. Tell our staff at the event, or email hi@bdqsocial.com. We will then not publish photos or video in which you can be identified.
- Children: We do not publish photos or video in which a child under 18 can be identified unless a parent or guardian has agreed.
- Kept: in our event archive, for as long as we use it to show our events. Once you opt out, we publish no identifiable image of you.
Device, network and security data
- What: when you use our sites, your IP address and browser details reach Cloudflare, which serves and protects them. Bot checks (Cloudflare Turnstile) on our forms look at device and browser signals. Our rate limits count requests per IP address or phone number while the limit applies. Our own logs record the page or action, the result, the timing and a request number, and leave out your name, phone number, email address and ID numbers. Error reports go to Sentry with names, phone numbers, email addresses and the query part of web addresses removed; a report can include our internal account number and your browser type. We plan to count visits with Cloudflare Web Analytics, which uses no cookies.
- Why: to keep our services running, block abuse and fraud, fix errors, and meet India's cyber-security rules.
- Basis: service, and legal duty for security logs.
- Shared with: Cloudflare and Sentry.
- Kept: security logs for 180 days.
Consent records
- What: when you agree to something, or withdraw it, we record the purpose, the version of the wording, where you agreed and the time.
- Why: to show what you agreed to and to honour a withdrawal.
- Basis: legal duty.
- Kept: as long as we keep the data the consent covers. A withdrawal, such as an unsubscribe, is kept as long as we need it to stop messaging you.
- Wording: the exact words we ask you to agree to are in Consent wording.
Artists, crews and sponsor contacts
When we book an artist or agree a sponsorship, we sign an agreement with the artist or the sponsoring business through a one-time e-sign link.
- What, from artists: your name and stage name, phone number and email address, your booking details and fee, the bank account details we pay you into, and your PAN.
- What, about an artist's crew and guests: their names and mobile numbers, so we can issue their passes and tickets. We do not collect their bank details or PAN. The artist tells them that they are giving us these details.
- What, from sponsors: the names, job titles, phone numbers and email addresses of the sponsor's authorised person and contact people, and the names of sponsor staff who need passes.
- E-sign record: the typed name of the person who signs, the date and time, the version of the agreement, the internet (IP) address used to sign, and a PDF of the signed agreement.
- Why: to manage the booking or sponsorship, issue passes, pay artists, deduct and report tax on artist fees (TDS), keep proof of the agreement, and keep the accounts we must keep.
- Basis: service (the agreement), and legal duty for tax and accounting records.
- Who sees it: only the BDQ team members who manage that booking, sponsorship or payment. Our bank receives the account details needed to make an artist's payment. The income-tax authorities receive an artist's PAN and the tax deducted when we report it. Signed agreements are kept in a private store on Cloudflare. We do not share an artist's personal data with sponsors without the artist's consent, and we never give sponsors our attendees' personal data.
- What is public: only an artist's public profile and set details, and a sponsor's name and logo as the sponsorship agreement allows. We never publish an artist's real name (if it differs from the stage name), phone number, email address, fee, bank details or agreement.
- Kept: payment records, PAN and the signed agreement with its e-sign record: 8 years, as accounting law requires. Bank details: until the last payment under the agreement is made, after which they remain only in those payment records. Crew, guest and sponsor-staff names and numbers: 1 year after the event.
Who we share data with
We use these services to run BDQ. Each receives only what it needs for the job listed.
- Cloudflare (worldwide network): hosts our websites and apps; protects them with a firewall, rate limits and Turnstile bot checks; stores files, including vendor documents and signed agreements in a private store; runs our background jobs; keeps our logs; sends our email; and, once we switch it on, will count visits without cookies.
- Neon (Amazon Web Services, Singapore): our database, which holds account, order, ticket, vendor and form records. Vendor ID numbers are stored encrypted.
- Google Firebase Authentication (Google, worldwide): sends and checks your one-time sign-in code, with a Google reCAPTCHA check on that step to stop abuse.
- Razorpay (India): takes online payments for Digitanomics LLP and handles payment disputes.
- Sentry (United States): receives error reports from our servers, with personal details removed as described above.
Services we plan to add. We will update this policy before we switch any of them on:
- Amazon SES (Amazon Web Services): backup email delivery if our main email service fails.
- Meta WhatsApp Cloud API: tickets and event messages on WhatsApp, after Meta verifies our business.
- Google Wallet: only if you choose to add your ticket to Google Wallet.
- Your browser's push service: only if you turn on notifications.
We also share personal data:
- with a vendor, only when you share your contact through its lead page;
- with everyone, for the public parts of a vendor's brand profile;
- with our bank, to pay an artist, and with the income-tax authorities, when we report tax deducted from an artist's fee;
- with the government, courts or police, when the law requires it.
We do not sell personal data or share it for advertising.
Data stored outside India
Some of these services store or handle data outside India: our database is in Singapore, error reports go to the United States, and Cloudflare and Google run worldwide networks, so your data may be handled in other countries. Indian law allows this, except to countries the Government of India restricts. We will not transfer personal data to a restricted country.
How long we keep data
- Orders, payments, tickets, receipts and stall payments: 8 years, because the law requires us to keep accounting records for 8 years.
- Gate scan records: 1 year after the edition.
- Vendor KYC documents and numbers: deleted 1 year after the vendor's last event; we then keep only the result of the check.
- Security logs: 180 days, as India's cyber-security directions require.
- Marketing contacts: until you unsubscribe, or 2 years with no activity from you.
- Sign-in code (OTP) records: 30 days.
Other periods are listed with each kind of data in What we collect and why. When a period ends, we delete the data or remove the details that identify you. If you ask us to erase your data, we remove your name, phone number and email address from records the law requires us to keep, and keep only the record itself, such as the order and the amount paid.
Your rights
Under the DPDP Act, you can ask us:
- for a summary of the personal data we hold about you, how we use it, and the list of services we share it with;
- to correct, complete or update your data;
- to erase your data, as described in How long we keep data;
- to withdraw a consent you gave. For marketing, use the unsubscribe link in any marketing email. Withdrawing does not affect what we did before, and if you withdraw a consent a service needs, we may be unable to provide that service;
- to name another person (a nominee) to use these rights for you if you die or cannot act yourself;
- to hear and resolve your complaint (see Grievance Officer).
How to ask: email hi@bdqsocial.com from the email address on your account or order, or give the phone number on it, and say what you want. We may ask you to confirm that it is you before we act. Our team handles each request. A "Delete my account" option in your account and in the vendor portal is coming; it will send us the same request. Until then, email us.
We acknowledge every request within 48 hours and reply within one month of receiving it.
Children
All ages are welcome at BDQ events. Anyone under 18 must be accompanied by an adult. Tickets do not carry attendee names, so we do not collect a child's details to let them in. Children may appear in photos and video we take at our events. We do not publish photos or video in which a child under 18 can be identified unless a parent or guardian has agreed. We use no advertising trackers and show no targeted ads, to anyone. To create an account or buy a ticket, you must be able to make a contract under Indian law, which means being 18 or older. We do not knowingly create accounts for children.
Sensitive personal data
Indian IT rules treat passwords, financial details such as card or bank details, and health and biometric data as sensitive personal data. Customers and vendors give us none of these: you sign in with a one-time code, not a password, and your card, UPI and bank details go to Razorpay, not to us. Only BDQ staff have passwords with us, and we store them only in hashed form (scrypt).
The one exception is artists we pay: an artist gives us the bank account details we pay their fee into. We use them only to pay that artist, as described in Artists, crews and sponsor contacts.
How we protect your data
- All connections to our sites use HTTPS encryption.
- Vendor ID numbers and KYC documents are encrypted (AES-GCM) in a private store. They are read only through our own system, every read is recorded, and ID numbers are shown masked.
- Staff see only what their role needs. Every staff member signs in with a password and a code from an authenticator app.
- Every staff change to orders, tickets, bookings and settings is written to an audit log that cannot be edited or deleted.
- Rate limits and bot checks protect sign-in and our forms.
- Our logs and error reports leave out names, phone numbers, email addresses and ID numbers.
- Customers' card, UPI and bank details never reach us. The only bank details we hold are those artists give us for their payments.
No system is perfectly secure. If a breach affects your personal data, we will tell you without delay, and report it to the Data Protection Board of India and to CERT-In, India's cyber-security agency, as the law requires.
Cookies
We set no cookies on our public website today. When sign-in is switched on, we will use one sign-in cookie to keep you signed in, and only the browser storage our sites need to work. We use no advertising or tracking cookies. Details are in Cookies & Local Storage.
Grievance Officer
- Name: Shah Dhrumil Sanjaybhai
- Designation: Grievance Officer and authorised signatory, Digitanomics LLP
- Email: hi@bdqsocial.com
- Phone: +91 98794 48835
- Address: our registered office, above.
The Grievance Officer also answers any question about how we process your personal data. We acknowledge every complaint within 48 hours, send you a copy of your complaint as we recorded it, and resolve it within one month of receiving it.
If you are not satisfied with our response, you can complain to the Data Protection Board of India.
Consent wording
These are the exact words we ask you to agree to. Each has a version name, and we record the version you saw. When we change the words, they get a new version name, and the old one stays listed here.
Waitlist (version waitlist-0)
Under the form: "We'll use your mobile number or email only to tell you when tickets or stalls open for this edition. To be removed, email hi@bdqsocial.com. Vendors can also write to team@bdqsocial.com. See our Privacy Policy."
Optional box, not ticked for you: "Also send me BDQ Social news, line-ups and offers by email. I can unsubscribe in one click from any email."
Vendor interest form (version vendor-interest-0)
Box you must tick to send the form: "I agree that BDQ Social (Digitanomics LLP) may use these details to review my brand and contact me by phone, WhatsApp or email about selling at BDQ Social. See our Privacy Policy."
Contact form (version contact-0)
Box you must tick to send the form: "I agree that BDQ Social (Digitanomics LLP) may use these details to reply to my message. See our Privacy Policy."
Marketing at checkout and in your account (version marketing-0)
Optional box, not ticked for you and not needed to buy: "Send me BDQ Social news, line-ups and offers by email, mostly in the weeks around each edition. I can unsubscribe in one click from any email."
Sharing your contact with a vendor (version vendor-lead-0)
On a vendor's lead page, a box you must tick to share: "Share my details with [vendor name] so they can contact me about their products. Only [vendor name] gets them. I can ask [vendor name] or BDQ Social to stop at any time."
Changes to this policy
Each version of this policy has a version number and a "Last updated" date. When we change it, we publish the new version on this page. If we want to use your data for a new purpose that needs your consent, we will ask you first.
