01 Who we are
MyGuest (“MyGuest”, “we”, “us”, “our”) provides a guest-management and event-hospitality platform that helps hosts and organisers run weddings, celebrations, corporate events, and group trips, and helps their invited guests experience those events. The platform is delivered through the MyGuest mobile application and the website at joinmyguest.com (together, the “Service”).
This policy forms part of, and should be read together with, our Terms of Service. By using the Service you acknowledge the practices described here.
02 Scope & our roles
MyGuest is used by two kinds of people, and our responsibilities differ for each:
Hosts & organisers
Create events, add and invite guests, and coordinate hospitality. Hosts decide what guest information to enter and how to run their event. For that event data, the host is the primary decision-maker and MyGuest largely acts on the host’s behalf.
Guests
Receive an invite code, view their event, and share their own preferences (RSVP, meals, travel, and more). For information a guest submits about themselves, that guest is in control.
Where the law recognises the concepts, MyGuest generally acts as a processor (or “data fiduciary’s processor”) for information a host enters about guests, and as a controller for account, billing, security, and product-analytics data that we determine ourselves.
03 Key terms
- Personal information / personal data — information that identifies, or can reasonably be linked to, an individual.
- Event data — details a host enters to run an event: guest lists, groups, itineraries, seating, budgets, vendors, and announcements.
- Guest-submitted data — information a guest provides about themselves through the Service.
- Processing — any operation performed on data, such as collecting, storing, using, sharing, or deleting it.
04 Information we collect
| Category | Examples | Source |
|---|---|---|
| Guest details entered by a host | Name, phone number, guest group/side, plus-one allowance, event assignments | The host |
| Information you provide as a guest | RSVP status, dietary preference, number of accompanying guests, gender/age group/t-shirt size (for trips), travel & arrival details, emergency contact, self-reported gift contributions | You (the guest) |
| Event information | Event names, dates, venues, itineraries, agendas, seating, budgets, vendors, rituals, announcements, perks | The host / organising team |
| Account information | Name, email, and login credentials for hosts and team members | You, via our authentication provider |
| Media & content | Photos, performance soundtracks, notes, and other content you upload | You |
| Payment information | Purchase records for guest-capacity packs (card/UPI details are handled by our payment provider, not stored by us) | You, via our payment provider |
| Device & usage data | Device and app version, language preference, a push-notification token (if you enable notifications), diagnostic logs, and analytics events | Collected automatically |
We do not ask for government IDs, passwords to third-party accounts, or full payment-card numbers, and you should never send those to us.
05 How we use information
- To run the Service — deliver invites, RSVPs, itineraries, seating, arrivals, announcements, gift registry, and guest perks.
- To coordinate hospitality — help hosts organise travel, stays, meals, activities, and the little touches that make an event work.
- To communicate — send the notifications you enable (announcements, reminders, urgent updates) and respond to your requests.
- To operate accounts & billing — authenticate users, process capacity-pack purchases, and prevent abuse of paid features.
- To keep the Service safe & reliable — detect, prevent, and investigate fraud, security incidents, and misuse; debug and improve performance.
- To improve MyGuest — understand which features help hosts and guests, using aggregated and diagnostic data.
- To meet legal obligations — comply with applicable law and enforceable requests.
06 Our legal bases
Where data-protection law (such as India’s Digital Personal Data Protection Act, 2023, or the EU/UK GDPR) requires a legal basis, we rely on one or more of the following: your consent (which you may withdraw); the performance of a contract or steps taken at your request; our legitimate interests in operating, securing, and improving the Service (balanced against your rights); and compliance with legal obligations. Hosts are responsible for having a valid basis to add and share their guests’ details with their team and service providers.
08 Service providers we rely on
We use a small set of trusted providers strictly to operate the Service:
- Google Firebase — hosting, database, authentication, cloud functions, analytics, and push-notification delivery.
- Cloudinary — storage and delivery of media you upload (such as photos and soundtracks).
- Razorpay — payment processing for guest-capacity packs. Payment-card and UPI details are handled by the provider; we receive only transaction results.
- Expo push service — technical delivery of notifications to your device.
Gift contributions are made directly by guests to a host’s own UPI ID through the guest’s payment app. MyGuest records only what a guest self-reports; we are not a party to, and do not process, those transfers.
09 International data transfers
Our providers may store or process data on servers located in countries other than yours. Where required, we take steps to ensure such transfers have an appropriate legal basis and safeguards. By using the Service you understand that your information may be processed in those locations.
10 Data retention
We keep event data for as long as the event is active and for a limited period afterward to allow for corrections, disputes, and cleanup, after which it is deleted or anonymised. Hosts may remove guests, or delete an event and its associated data, at any time. Account, billing, and security records may be retained for longer where we have a legal obligation or a legitimate need (for example, tax, fraud-prevention, or record-keeping). Backups are cycled out on a rolling basis.
11 Security
Data is transmitted over encrypted connections and protected by access controls, authentication, and scoped permissions so that event data is visible only to the right event’s team and guests. We work to protect information using industry-standard safeguards. However, no method of transmission or storage is perfectly secure, and we cannot guarantee absolute security; you use the Service with that understanding.
12 Your rights & choices
Depending on where you live, you may have some or all of these rights over your personal information:
- Access a summary of the information we hold about you.
- Correct inaccurate or incomplete information.
- Delete your information (subject to legal or legitimate retention needs).
- Withdraw consent where we rely on it, without affecting prior processing.
- Object to or restrict certain processing, and request portability where applicable.
- Nominate another individual to exercise your rights in the event of death or incapacity, where the law provides for it.
You can access or update much of your information directly in the app (for example, your profile and RSVP). You can turn notifications off at any time in your device settings; the push token then stops being usable and is removed on our side. For anything else, contact us using the details below and we will respond in line with applicable law. Because hosts control their guest lists, some requests about event data may be directed to, or coordinated with, the relevant host.
13 Grievance Officer
In accordance with applicable Indian law, you may raise concerns or complaints about the handling of your personal information with our Grievance Officer:
Email: hello@joinmyguest.com
We aim to acknowledge grievances promptly and resolve them within the timeframes required by law.
14 Children’s privacy
MyGuest is intended for adults organising and attending events. It is not directed to children, and we do not knowingly collect personal information from children without the consent required by law. If a host includes a child in an event, the host is responsible for any consents needed. If you believe a child’s information has been provided to us without appropriate consent, contact us and we will take appropriate steps.
16 Changes to this policy
We may update this policy from time to time to reflect changes in the Service, our practices, or the law. When we do, we will revise the “Last updated” date above, and for material changes we will take reasonable steps to notify you. Your continued use of the Service after an update means you accept the revised policy.
17 Contact us
Questions about this policy or your data? Email us at hello@joinmyguest.com. We read every message and aim to respond quickly.