Privacy Policy
Effective and last updated: 21 November 2026
- We collect only what is needed to create invitations, collect replies and run your events.
- Invite pages can be opened by anyone with the link. Replies and guest lists are visible only to the host.
- We do not sell personal data, show advertising or build advertising profiles.
- You can download your data or delete your account at any time in Settings.
- Questions or complaints go to our Grievance Officer (section 15). We acknowledge within 24 hours and resolve within 15 days.
- Who we are
- Scope and consent
- Personal data we process
- Why we use it
- Guest data added by hosts
- Who can see what
- Sharing and service providers
- Transfers outside India
- How long we keep data
- Security and breaches
- Your rights
- Children
- Cookies and browser storage
- Changes to this policy
- Grievance Officer and contact
1. Who we are
Gathr (“Gathr”, “we”, “us”) is an online service for creating invitations, sharing them by link and collecting replies, available at hellogathr.in and any successor domain (the “Service”). Gathr is operated by Hritvik Rajoria, Gurugram, Haryana, India.
For the personal data of account holders, Gathr is the Data Fiduciary under the Digital Personal Data Protection Act, 2023 (“DPDP Act”). For guest lists and invitation details a host adds about other people, see section 5.
This policy is published under the Information Technology Act, 2000, the Information Technology (Reasonable Security Practices and Procedures and Sensitive Personal Data or Information) Rules, 2011 (“SPDI Rules”), the Information Technology (Intermediary Guidelines and Digital Media Ethics Code) Rules, 2021 (“Intermediary Rules”) and the DPDP Act.
2. Scope and consent
This policy applies to everyone who uses the Service: account holders (“users”), hosts who create events, and guests who open an invite or reply without an account. It does not cover third-party apps you choose to share invites to, such as WhatsApp or Instagram.
By creating an account, creating an event, replying to an invite or uploading content, you consent to the processing described here for the purposes stated. Where you give personal data voluntarily for a specific purpose, for example a guest filling in an RSVP form, we process it for that purpose. You can withdraw consent at any time (section 11). Withdrawal does not affect processing done before it.
3. Personal data we process
| Category | What | Source |
|---|---|---|
| Account | Name, email address, password (stored only as a one-way hash; we can never see it), and, if you use “Sign in with Google”, your Google name, email and profile picture. | You, Google |
| Profile (optional) | Mobile number, photo or avatar, city, state, PIN code, date of birth, gender, occupation, and preferences (events you plan, sports, food preference, festivals, children at home). | You |
| Events | Event name, date, time, venue, map location, functions and schedule, theme, dress code, RSVP questions, card design, card photos, invite message, share link. | Hosts |
| Guest lists | Names, mobile numbers and groups of people a host invites, and when they were sent an invite or reminder. | Hosts (section 5) |
| Replies (RSVP) | Name, mobile number, email (if asked), attendance, number of adults and children, functions attending, and answers to the host’s questions. | Guests |
| Photos | Photos added to an event’s album, and who added them. | Hosts, guests |
| Activity | Invite links you open while signed in, notification and privacy choices, and when you last viewed notifications. | Generated by the Service |
| Technical | IP address (used only for anti-spam limits and deleted after 24 hours), a random device ID stored in your browser, and standard server logs kept by our hosting providers. | Your device |
| Venue search | The words you type when searching for a venue. We don’t read your device’s location unless you choose “use my location”, and then only for that search. | You |
Sensitive data. Apart from passwords (always stored as hashes), we do not ask for financial, health, biometric, sexual orientation or other sensitive personal data. Please don’t enter such data in event details, RSVP answers or photos. Hosts must not ask guests for it.
4. Why we use it
- To create and secure accounts, and to sign you in.
- To build, save, publish and share invitations, including link previews and downloadable cards.
- To collect replies and show them to the host, and to match replies to the host’s guest list by mobile number.
- To show your Invitations list, notifications and reminders you ask for.
- To fill in your details on RSVP forms, and to suggest relevant ideas, templates and festival dates.
- To prevent spam, abuse and fraud, keep the Service secure, and fix problems.
- To comply with law, court orders and lawful requests from government authorities.
We do not use personal data for advertising, sell it, or use it to make decisions that have legal or similarly significant effects on you.
5. Guest data added by hosts
When a host adds people to a guest list (by typing, pasting, importing a file or picking from phone contacts), or writes names into an invitation, the host decides whose data is added and why. A host who uses Gathr for a personal or domestic event, like a family function or a party with friends, uses it for their own personal purposes. Hosts organising events for a business or organisation are responsible for complying with the DPDP Act for their guests’ data. Gathr processes this data only to provide the Service to the host.
Hosts must only add people they genuinely intend to invite and who would reasonably expect to hear from them. Hosts must not use guest data for marketing, sale or any unrelated purpose. If you are on someone’s guest list and want to be removed, ask the host, or contact our Grievance Officer and we will help.
Invites and reminders are sent by the host from their own WhatsApp or other apps. Gathr only prepares the message; we do not send bulk messages on a host’s behalf.
6. Who can see what
- Invite pages are public to anyone with the link: the card, event name, date, time, venue and map, host name, schedule, RSVP questions and the event’s photo album. Share links only with people you want to invite. A host can turn a link off at any time.
- Replies and guest lists are visible only to the host of that event. Guests cannot see who else was invited or how others replied.
- Photos in an album can be seen by anyone with the invite link. They can be added by the host and by signed-in guests who replied “yes”, and removed by the host or the person who added them.
- Your profile is private. Hosts see only what you enter in a reply.
7. Sharing and service providers
We share personal data only as follows:
- Service providers (data processors) who run the Service for us under contract and only on our instructions:
- Supabase: database, authentication and file storage.
- Vercel: website hosting and link previews.
- Google: Google Sign-In, and Google Maps Places for venue search.
- OpenStreetMap / Photon: alternative venue search.
- Google Fonts, cdnjs and jsDelivr: fonts and code libraries delivered to your browser.
- Other users, as described in section 6.
- Apps you choose: when you share an invite to WhatsApp, Instagram, email or another app, you send it through that app under its own terms and privacy policy.
- Legal reasons: where required by law, court order, or a lawful request from a government agency or law-enforcement authority, including under section 69 of the IT Act and the Intermediary Rules; or to protect the rights, safety or property of our users, the public or Gathr.
- Business transfer: if Gathr is merged, acquired or restructured, data may transfer to the successor. The successor will be bound by this policy or must give you notice.
8. Transfers outside India
Our database and file storage are hosted in Tokyo, Japan. Our website is served from a global network. Our service providers may process data in other countries. We transfer personal data outside India as permitted under section 16 of the DPDP Act, and will stop or restrict transfers to any country the Central Government restricts by notification. Our providers are bound to protect the data to a standard at least equal to this policy.
9. How long we keep data
| Data | Kept until |
|---|---|
| Account and profile | You delete your account |
| Events, guest lists, replies, photos | The host deletes them, deletes the event, or deletes their account |
| Replies you sent to someone else’s event | That host deletes them or the event (your account link is removed if you delete your account) |
| IP addresses for anti-spam limits | 24 hours |
| Hosting provider logs | As kept by the provider, typically up to 30 days |
Where a law requires us to keep information longer, we keep only what is required, for as long as required. Examples: preserving information for 180 days for an investigation under the Intermediary Rules, or keeping logs under CERT-In directions.
10. Security and breaches
We follow reasonable security practices under the SPDI Rules, including:
- Encryption in transit (HTTPS).
- Hashed passwords.
- Database access rules that limit each record to the people entitled to see it.
- Least-privilege access for administrators.
- Limits against automated abuse.
No system is completely secure. If a personal data breach affects you, we will inform you and the Data Protection Board of India as required by the DPDP Act, and report cyber incidents to CERT-In within the time it requires.
11. Your rights
Under the DPDP Act, you have the right to:
- Access information about the personal data we process, and who we have shared it with. Use Settings → Privacy and security → Download my data, or write to us.
- Correct, complete or update your data: edit your profile, or open an invite link again to change your reply.
- Erase your data: Settings → Privacy and security → Delete account. This removes your profile, events and their guest lists, replies and photos.
- Withdraw consent at any time, as easily as you gave it. We will stop processing within a reasonable time, though some features may no longer work.
- Nominate another person to exercise your rights if you die or become incapable. Write to the Grievance Officer to do this.
- Grievance redressal (section 15). If you are not satisfied with our response, you may complain to the Data Protection Board of India.
We may need to verify your identity before acting on a request. We respond within the timelines in section 15.
12. Children
Accounts are only for people aged 18 or over. We do not knowingly allow anyone under 18 to create an account.
A parent or lawful guardian may create an event about their child, such as a birthday party, and in doing so gives consent on the child’s behalf for the child’s details in that invitation. Only include what the invite needs.
We do not track, behaviourally monitor or target advertising at children. If you believe a child has created an account, contact us and we will delete it.
13. Cookies and browser storage
We do not use advertising or cross-site tracking cookies. We store a few items in your browser:
- Your sign-in session.
- Your “remember me” choice.
- A random device ID that lets you change your own reply later.
If you block or clear browser storage, you may need to sign in again, or reply again using the same mobile number.
14. Changes to this policy
We may update this policy as the Service or the law changes. We will change the date at the top. For material changes, we will notify you in the app, by email, or both, before they take effect. Where the law requires fresh consent, we will ask for it.
15. Grievance Officer and contact
Grievance Officer: Hritvik Rajoria
Address: Gurugram, Haryana, India
Email: contact email will be published here shortly
Write to us about privacy questions, requests to exercise your rights, removal from a guest list, or complaints about content. We will acknowledge your complaint within 24 hours and resolve it within 15 days of receipt. Requests to remove content that exposes a person’s private area, shows them in full or partial nudity or in a sexual act, or impersonates them, are acted on within 24 hours (Intermediary Rules, rule 3(2)).
This policy is governed by the laws of India. Disputes are subject to the jurisdiction of the courts at Gurugram, Haryana, as set out in our Terms of Service.