Privacy Notice
Dine Dialog Meetup · Last updated: 29 July 2026 · Effective: 29 July 2026
This Privacy Notice explains what personal data the Dine Dialog Meetup app (the “App”) collects, why, and what you can do about it. It covers the event dashboard and group chat you access with an invite code.
The App is operated by Omanaa, Noida, India, trading as Dine Dialog. For the purposes of the Digital Personal Data Protection Act, 2023, we are the Data Fiduciary and you are the Data Principal.
This notice is specific to the App. Data you gave us when you bookedyour seat — your name, phone number, and email — is covered by the Dine Dialog Privacy Policy. The two work together.
1. In short
The App deliberately collects as little as possible:
- There is no account, no password, and no email or phone number in the App. You get in with a one-off invite code tied to your seat.
- We do not use advertising trackers, analytics tools, or third-party cookies in the App.
- We do notcollect your GPS location. “On my way” and your ETA are values you type in yourself.
- We do not sell or rent your data to anyone.
2. What we collect, and when
| Data | What it is | When we get it |
|---|---|---|
| Seat & invite code | The seat assigned to you at a table, and the unique code that opens it | Created by the organiser when the event is set up |
| Display name | The name shown to your table. Defaults to a neutral seat label (e.g. “Person 3”) until you change it | Only if you choose to set one |
| Gender badge | An optional badge (She / He / They) beside your name in chat. Defaults to undisclosed | Only if you choose to declare it. Entirely optional |
| Attendance status | Whether you are coming, your estimated arrival time in minutes, and whether you are on your way or have arrived | When you set it yourself in the dashboard |
| Chat content | Messages you send, replies, emoji reactions, and which messages you have read | When you post or react in the group chat |
| Safety data | Reports you submit (with any reason you type) and the guests you have blocked | When you report a message or block someone |
| Push subscription | A browser-issued address and keys that let us send you a notification. It does not identify you personally | Only if you allow notifications when your browser asks |
| Session cookie | A secure, HttpOnly cookie holding your seat and event reference, so you stay signed in | When you enter a valid invite code |
| Technical data | Your IP address and basic request details, used transiently for rate limiting and abuse prevention, and last-seen timestamps | Automatically, as you use the App |
Your gender badge is optional and self-declared. You can leave it undisclosed, and you can change or clear it at any time. We use it only to render the badge beside your name in chat and, where relevant, to help the organiser keep a balanced table.
3. Why we use it
- To run the event. To show your table who is coming, who is on their way, and where to go.
- To deliver the chat. To transmit your messages to the other guests at your table in real time, and to notify you of new ones if you have allowed notifications.
- To keep you signed in. The session cookie is strictly necessary for the App to work.
- To keep the space safe. To act on reports, apply your blocks, moderate content, and enforce our Terms of Use.
- To prevent abuse. To rate-limit requests and block automated or malicious traffic.
- To meet legal obligations. To comply with the IT Act and IT Rules, respond to lawful requests from courts or government agencies, and establish or defend legal claims.
We do not use anything from the App for advertising or marketing, and we do not profile you.
4. Our legal basis
We process this data on the basis of your consent, which you give by entering your invite code and joining the event dashboard having been shown this notice, and for the legitimate usespermitted under the DPDP Act — including providing the service you have asked for and complying with our legal obligations. Your consent is free, specific, informed, and you may withdraw it at any time (see Section 8).
5. Who can see your data
- The other guests at your table. Your display name, gender badge if you set one, attendance status and ETA, and your messages and reactions are visible to everyone with a seat at that event. Please treat the chat as a room you are speaking in, not a private message.
- The Dine Dialog organiser. Organisers can see the dashboard, the chat, and reports, so they can run the event and act on safety issues.
- Our infrastructure providers. The App runs on Vercel (hosting) and Supabase (database and real-time messaging). Notification delivery uses the push service built into your own browser (such as Google or Apple). These providers process data on our behalf, under contract, and their servers may be located outside India. We rely on them only as permitted under applicable law.
- Law enforcement and courts. Where we are legally required to disclose, or where we believe in good faith it is necessary to prevent harm.
Blocking is private: the person you block is not told, and we do not share your block list with them. Reports are not anonymous to us— we record which seat filed a report so we can follow up — but we do not disclose the reporter’s identity to the reported guest.
6. How long we keep it
- Chat, seat, and status data is retained while the event is live and for a limited period afterwards so we can deal with any complaint arising from it, after which the event is archived or deleted.
- Reports and moderation records are kept longer where needed to handle repeat behaviour or a legal claim.
- Your session cookie expires after 15 days, or immediately when you log out.
- Push subscriptions are deleted when you turn notifications off, when your seat is removed, or when your browser invalidates them.
- We retain information for 180 days after your access ends, or longer where required, for the purposes of investigation as contemplated by the IT Rules.
7. How we protect it
Access to the App is gated by a unique invite code and a signed, HttpOnly, secure session cookie that JavaScript cannot read. Data is encrypted in transit. Access at the database level is restricted so that you can only reach data for the active event you belong to, and requests are rate-limited to resist abuse. No system is perfectly secure, and we cannot guarantee absolute security — but if a breach occurs that is likely to affect you, we will notify you and the Data Protection Board of India as the law requires.
8. Your rights
As a Data Principal, you have the right to:
- Access the personal data we hold about you and a summary of how it is processed;
- Correct or updateinaccurate data — you can change your display name, gender badge, and status yourself in the App at any time;
- Request erasure of your data where it is no longer needed for the purpose it was collected;
- Withdraw consent— you can log out, turn off notifications in your browser, or ask us to remove your seat. Withdrawing consent does not affect processing already carried out;
- Nominate another person to exercise your rights in the event of your death or incapacity;
- Raise a grievance with us and, if unsatisfied, escalate to the Data Protection Board of India.
One practical limit: because the chat is a shared conversation, deleting your messages does not remove them from other guests’ memory of the conversation, and we may need to retain a copy of a reported message for safety or legal reasons even after you ask us to erase your data.
9. Children
The App is for adults aged 18 and over. We do not knowingly process the personal data of anyone under 18. If you believe a minor has access, contact us and we will remove it.
10. Changes
We may update this notice. When we do, we will change the “Last updated” date at the top of this page. Where a change is significant, we will tell you in the App.
11. Contact & grievance redressal
To exercise any right, or to complain about how we handle your data, contact our Grievance Officer:
- Grievance Officer: Muklit Chopra
- Email: hello@dinedialog.com
- Phone / WhatsApp: +91 99903 42564
- Address: Omanaa, Noida, Uttar Pradesh, India
We will acknowledge your grievance within 24 hours and resolve it within 15 days. If you are not satisfied with our response, you may escalate to the Data Protection Board of India.