Privacy Policy

Information you provide directly:

• Account details: name, email address, profile photo
• Event information: event names, dates, locations, descriptions, checklists, notes and meeting notes (including the names you list as attending), photos you add (such as the couple’s portraits shown on every guest’s pass), and the crew and vendor names printed on badges, with any photos, logos or artwork you add to those badges (stored in our image storage and shown only on the badges you print)
• Guest information: names, email addresses, phone numbers, RSVP responses, and where a guest is staying if the organizer adds it (hotel, room, check-in and check-out dates, notes)
• Vendor information: business name, contact details, service categories, and the vendor quotes you record or import for an event (vendor, service, amount, status, contact and notes)
• Day-of contacts: the phone numbers and emails you add for your event’s vendors and performers, with their arrival and performance times, used only to send them that event’s reminders and your day-of messages (by email, or text outside 8 PM – 8 AM), and a record of what was sent
• Payment information: processed securely through Stripe — we do not store card numbers
• Tables & booths (show organizers): the room you draw for a show (its layout, colours, table numbers and prices) and any private notes you write on a table. Notes, single-table prices and blocked tables are shown only to you and your show team, never to buyers; buyers see only whether a table is available or taken, never why. If you choose “save this room”, we keep the layout and colours (not prices or notes) as a saved room that is private to you, even when it is linked to a venue listed on EventVidia; other organizers at the same venue cannot see it. You can delete a saved room at any time, and saved rooms are deleted with your account. When a buyer books a table we record which table their order holds, alongside their ticket order. A buyer picking a table without signing in gets a random holding code kept only in that browser tab; it identifies no one and expires with the hold. While any table is on hold we also keep a scrambled, one-way code made from the internet address it was picked from (never the address itself), only so one connection cannot hold a whole room; it is deleted with the hold.
• Payout setup (organizers and vendors): when you set up payouts, your identity details (such as name, date of birth, address and, where required, an ID document or tax number), your business details and your bank account are collected in a Stripe form shown on our page or on Stripe’s site. For payout accounts with no separate Stripe login, EventVidia is the party collecting these details for Stripe; they are typed straight into Stripe’s form and sent to Stripe, which uses them to verify your identity, meet financial regulations and pay you, under Stripe’s privacy policy. We do not store them: we keep only your Stripe account ID, whether payouts are switched on, and your bank’s name and last four digits; Stripe keeps the record of when you accepted its terms in that form. To protect your payouts we may ask you to sign in again before you set up or change your bank, and we keep a record of each bank change on your payout account (the date, the bank’s name and last four digits) and email you about it; that record is kept while your account is open and deleted with it. When Stripe needs more information from you, we tell you on your Payouts page and by email. If you are in India, these details are processed to provide the payouts you asked for, and your rights over them are set out in section 10. If you sell before connecting a bank, we use your email to tell you how much money is waiting for you (one email and one reminder before it is due); these are about your account, not marketing
• An organizer's card on file for show cancellation fees: kept by Stripe; we keep only the card type, last four digits and when they agreed. It stays on file until the organizer removes it, which they can do 90 days after their last ticketed show ends
• Communications: messages, support requests, feedback
• Ask EV conversations: what you ask EV, its replies, the changes it proposed or made and your approvals, the thumbs up or down you give, and any feature request you ask it to send us. If you talk to EV, your browser or device turns your speech into text (for example Google in Chrome, Apple in Safari) under that provider’s privacy terms; we receive the text, not the audio.
• Shop orders and bookings: what you bought, rented or booked, your delivery address and phone number when you choose delivery, the date you need a rental, and appointment details.
• Dietary and food preferences, where an organiser asks for them at registration — including allergies. Always optional, used only to give the organiser catering numbers, and visible to that organiser. Some laws treat allergy information as health data; we treat it that way regardless of where you are.
• Waiver and terms signatures: the name you type as your signature, your email and phone if given, your IP address, your browser, the time you signed, and an exact copy of the wording that was on screen. We keep the wording rather than a link to it, so that an organiser editing their waiver later cannot change what you are recorded as having agreed to.
• Documents a vendor sends an organiser — such as a certificate of insurance or a business licence. These may contain a business address, a policy number, and a signature. They are stored privately and are readable only by that vendor and the organiser they sent them to.
• Questions sent through a "Contact us" form on an event page: your name, email, phone if given, and your message. These are stored and forwarded to the organiser of that event, who replies to you directly.
• In-person (box office) card payments: when you tap a card, Apple Pay or Google Pay at an event's door or a vendor's booth, the card is read and processed by Stripe. EventVidia does not receive or store your card number; we keep the payment reference, the amount, the time, and the tickets or items it bought, so the sale can be admitted, paid out and refunded.
• Check-in records: when a ticket is scanned at a door, we record the time, the station name the door staff entered, and — where the organizer requires sign-in to scan — which member of the organizer's team scanned it. Organizers use this to run their door and resolve disputes.
• Text-message consent statements: before an organizer texts, calls or sends WhatsApp messages to people on their own list, they confirm those people agreed. We record which organizer confirmed it, for which event, the wording, the time, how many people it covered and the organizer's IP address, so it can be shown if a recipient later says they never agreed. We keep it for as long as we keep the event's message records.

Information collected automatically:

• Log data: IP address, browser type, pages visited, time spent
• Device information: operating system, device type, unique identifiers
• Usage data: features used, clicks, event creation and management activity
• Visit statistics: for each page view on our website or apps, the section of the site, the approximate location (country, state or region, and city, derived from your network connection), the kind of device (phone, tablet or computer), whether it was the website or our app, the site you came from, and whether you were signed in. We do not store your IP address or which account it was; a daily-changing code lets us count visitors without following anyone from one day to the next. Kept for 180 days.
• Search and AI crawlers: we count how often search engines and AI assistants' crawlers (for example Googlebot or OAI-SearchBot) fetch our public pages, by the crawler's name, the day and the section of the site. This is about automated programs, not people, and records no address, page path or device.
• The page you opened Ask EV from (its address, not its content), so EV can help with what is in front of you
• Cookies and similar tracking technologies (see Section 6)

Information from third parties:

• Authentication providers (Google, Apple) when you sign in via those services
• Payment processors (Stripe) for subscription and billing information

The EventVidia app for iOS and Android asks for the permissions below. Each one is requested only at the moment you use the feature that needs it, never at start-up, and you can refuse or withdraw any of them in your device settings without losing access to the rest of the app.

Contacts

• Why: so you can pick people from your address book when adding guests to an event, instead of typing every name, email address and phone number by hand.
• What we receive: only the contacts you actually select — their name, and their first email address and phone number. Contacts you do not select are never sent to us. We do not read your address book in the background, and we do not upload it in bulk.
• What we do with it: the selected details become guests on your event so we can send them your invitation and record their reply. They are treated exactly like guests you typed in yourself, and are covered by the same deletion rights in Section 7.
• What we never do: we do not sell your contacts, use them for advertising, build a social graph from them, or contact anyone you did not add to an event.

Camera and photo library

• Why: to take or choose a photo for an event cover, your profile, a vendor portfolio or inventory item, and to scan QR codes at the door when checking guests in.
• What we receive: only the individual photo you take or choose. We do not browse your photo library. QR scanning happens on your device — the camera image itself is never uploaded, only the code it contains.

Location, NFC and Bluetooth (organizers and vendors using Tap to Pay or a card reader)

• Why: Stripe, which processes in-person card payments, requires the device's location while a payment is taken (for fraud prevention and to meet card-network rules), uses the phone's NFC chip to read a tapped card, and uses Bluetooth to connect to a card reader. These are asked for only when an organizer or vendor takes a card payment in person.
• What we receive: EventVidia does not store your location; it is used by Stripe's software on the device during the payment, under Stripe's privacy policy. Card details read over NFC go to Stripe, not to EventVidia.
• If you decline: Tap to Pay cannot be used on that device; cash, comps and buyers paying on their own phone still work.

Notifications

• Why: to tell you about RSVPs, ticket sales and reminders for events you host or attend. Declining notifications does not limit anything else in the app.

If you withdraw a permission after granting it, information already saved to an event stays until you delete it — see Section 7, Your Rights, or delete your account entirely at eventvidia.com/delete-account.

We use the information we collect to:

• Create and manage your account
• Provide, maintain, and improve our event planning services
• Process payments and manage your subscription
• Send invitations, notifications, and reminders on your behalf
• Connect you with vendors in our marketplace
• Answer your questions and carry out requests through Ask EV, our AI assistant — including looking up your own events, shows, orders and bookings for you
• Deliver shop orders (buying shipping labels and tracking parcels) and remind you of appointments
• Respond to your support requests and inquiries
• Send product updates, tips, and marketing communications, including news and upcoming events to people who bought tickets through EventVidia (you can opt out at checkout, from any of these emails, or by writing to us), and to guests, expo visitors and donors who tick the (always unticked) “Also email me event ideas and news from EventVidia” box when they RSVP, register or donate. A host’s guest or contact list is never added to EventVidia’s own mailing list; we record the words you agreed to and when, and you can unsubscribe from any of these emails
• Detect, prevent, and address fraud, abuse, or security issues
• Comply with legal obligations
• Analyse usage patterns to improve our platform

We will never sell your personal information to third parties for their own marketing purposes.

We share your information only in the following circumstances:

• With vendors you contact: When you enquire about or book a vendor, we share relevant event and contact details with that vendor.
• Vendor websites and web addresses: When a vendor buys a web address through us, the owner details they enter (name, business, email, phone and address) go to our domain partner (Vercel) and the domain registry, which require them to register the name in the vendor’s own name; registries may publish some of them in public domain records where privacy protection is not available. To show a vendor’s name and logo on their checkout and card statements, we send their business name, logo and brand colour to Stripe. To send order emails from a vendor’s own domain, the domain is registered with our email provider (Resend). When a vendor shows their Google reviews, a visitor’s browser asks us and we ask Google for that listing’s rating and reviews at that moment; we keep only the listing’s Google ID, not the reviews, and the reviewers’ names and links are Google’s. A vendor can stop showing them at any time (Settings → Verification), which deletes that ID. A shop order asks for the buyer’s mobile number; the vendor sees it to reach them about that order, and it is never used for marketing. We text an order confirmation only if the buyer ticks “Text me my order confirmation”, and we record that choice with the order. When a customer opens My orders on a vendor’s website, we email or text a one-time code to the email or number they enter, but only if it has ordered from that vendor, and we never say whether it has. The code is not stored; once it is entered, a cookie on that website (lasting 30 days, removed by Sign out) lets them see their own orders with that vendor and nothing else. When a visitor sends an enquiry from a vendor’s website, what they type (name, email, phone, event date and message) is stored for that vendor and emailed to them so they can reply; we use it for nothing else.
• With venues you ask for information or a quote: Only when you tick the consent box on the request form, and only with the venue you chose. Event details (type, date, guest count, budget range and your message) are shared with that venue once it has claimed its EventVidia profile. Your name, email address and phone number are shared only with a venue EventVidia has verified. If a venue is not on EventVidia, we do not send it your details; we may contact the venue to invite it to respond, without including your contact information. We record the consent wording you saw and when you agreed. You can withdraw a request at any time from Venue requests, and deleting your account erases your contact details from every request. Venue names, addresses, photos and ratings shown from Google Maps are provided by Google and are not stored by us.
• With people an organizer shares an event with: an event’s host can share it with a co-planner or with their client (for example a planner sharing a wedding with the couple). A client sees only the sections the planner opens to them — such as the event schedule, the guest list (guests’ names, contact details and RSVPs) or guest rooms — and never the sections the planner keeps hidden, such as vendor costs, quotes, budget, notes and files. The host, the event’s planner or coordinator, and anyone the host gives Full access can invite people and change what a client sees; only the host can remove someone. A wedding’s sharing covers each of its events, which can also have their own choices.
• With guests you invite: Your name and event details are shared with guests you send invitations to.
• Your own website (vendors, artists and organisations): when you publish a site at eventvidia.com/site/…, everything on it is public: the words and photos you add, and what it shows from your EventVidia profile (your business or stage name, area, photos, videos, packages and prices, upcoming shows and events, and verified reviews — a reviewer is shown by first name only), and any social media handles you add, which link to those networks (a WhatsApp number you add there is public). When you first open the editor we fill in the social handles already on your public profile; we never copy your private phone or WhatsApp number. Following one of those links takes the visitor to that network, under its own privacy policy. Drafts are seen only by you and the people allowed to manage your profile. Taking the site offline removes it from public view; deleting your profile deletes the site.
• Sign-up forms: when you sign up on a form (eventvidia.com/f/…) made by a non-profit, a vendor or a person, your name, the contact details and answers you give, and how many are coming go to whoever made the form, who can see, download and edit them. They are used for that sign-up only. We email you a confirmation when you give an email. If they turned on a QR pass, it is in that email, and you can add it to Apple Wallet or Google Wallet (which then holds a copy of the pass: the form’s name, date, your name and the QR code); anyone with the pass link can open it. If the form has a waiver or disclaimer, we keep a record of your agreement: the exact wording you saw, the name you typed as your signature, when, and the internet address and browser you used, and you get a copy by email. The form’s owner can see it. When you arrive, the organiser or a door helper they invited scans the pass; we record when you were checked in and by whom. Door helpers see only your name and party size, never the list. A form’s owner may also type in or upload people themselves, and may text them only if they agreed.
• Photos sent to a wedding website: when you send a photo from a couple’s wedding website, the photo and the name you type (if any) go to the couple. Nobody else sees it unless the couple approves it, after which it appears on their public website with your name if you gave one. The couple can hide or delete it at any time; a deleted photo is removed from our storage. To have a photo taken down, ask the couple or contact us.
• Donation links: EventVidia does not process donations. If an organisation adds its own donation link, pressing Donate takes you to that organisation’s page, and what you enter there is collected by that organisation and its payment provider under their privacy policies, not by us. We keep the link the organisation gave us. Donations made by card through EventVidia before 20 October 2026 stay in our and the organisation’s records as described in this policy.
• Vendor quote requests: when a host or planner asks a vendor for a quote, we store the vendor’s name, email and (if given) mobile number to send that request and its replies. A vendor’s quote and the files they attach are shown to the event’s planning team and anyone they share the event’s quotes with, and kept privately. A vendor can unsubscribe from the email or reply STOP to a text.
• Timeline columns: an event’s Timeline keeps the name, the columns and their order chosen for it, and what is entered in them, including columns you create yourself (for example comments, a song, or who is confirmed). They are seen by the people working on the event, and by a client only if the Timeline is opened to them. “Save as my default” keeps your column choice on your account for your new events. Downloads are made in your browser and are not stored by us.
• Seating on a floor plan: when an organizer seats guests on an event’s floor plan, we store which table each guest is at. It is seen by the host, the event’s planner or coordinator, and a client only if the planner opens the floor plan to them; each guest sees only their own table, on their own pass. Removing a guest removes their seat.
• With the host, when a planner prepares invitations: if you help with someone else’s event and prepare an invitation send, the request — your name, which guests, how it would be sent and the message — is stored and shown to the event’s host so they can approve or decline it. The host decides; nothing is sent to guests before they approve.
• For in-person card payments: when you pay at an event's door or a vendor's booth by tapping a card or phone, the card is processed by Stripe (including Stripe Terminal, and Apple for Tap to Pay on iPhone) under their own privacy policies. The organizer or vendor sees that a card sale was made, the amount and what it bought — never your card number.
• With the vendor you buy from or book: the vendor receives what they need to fulfil it — your name, the items, and your delivery address and phone for a delivered order, or the appointment details for a booking.
• Service providers: We use trusted third-party services including Stripe (payments), Clerk (authentication), Vercel (hosting), Neon (database), Resend (email), Twilio (text messages), and our shipping-label service and the shipping carriers (the delivery address and parcel details needed to buy a label and track a delivery). These providers process data on our behalf and are bound by data processing agreements.
• Security, reliability and maps: Sentry receives error reports when something breaks in your browser or on our servers, with keys, tokens, email addresses and phone numbers removed first; session recording is switched off. Vercel BotID checks technical signals from your browser and device to tell people from automated bots on sign-up, checkout and other forms; it does not record what you type. Vercel Speed Insights measures how fast pages load, without cookies. Pages with a map (hotels, venues, vendors, digital cards) load Google Maps, so Google receives your IP address and browser details under Google’s own privacy policy. We do not use Google Analytics or any advertising trackers, and our fonts are served from our own servers.
• AI providers, for Ask EV and other AI features: to answer a request, your message and the account information needed for it (for example the details of the event or show you asked about) are sent through Vercel’s AI Gateway to a third-party AI model provider — currently OpenAI, and for artwork EV designs OpenAI with Meta as a fallback; the provider used for a feature may change. Artwork EV makes for you, and any logo or reference picture you attach for it, is saved to your account and deleted with it. A reference picture is sent to the image provider to guide the design; a logo is placed by EventVidia and not sent to it. We use their business services to generate the reply only; we do not sell this data or share it for advertising. Please do not include sensitive information EV does not need (card or bank numbers, passwords, government ID numbers, health details).
• AI assistants you connect (Claude, ChatGPT): if you choose to connect your EventVidia account to an outside AI assistant such as Anthropic’s Claude or OpenAI’s ChatGPT, that assistant can, only while connected and only when you ask it to, read your own events, their details and their guest lists (guests’ names, email addresses and phone numbers, RSVP response, number attending, meal choice and check-in status), browse public vendors and shows, and create a DRAFT event or invitation in your account. It cannot send invitations or messages, take payments, or see other people’s events. What it reads is passed to that assistant’s provider and handled under their privacy policy. You approve the connection when you sign in through EventVidia, and can end it at any time from Settings → AI Assistants, which revokes its access immediately.
• Google Maps Platform: when you or EV search for venues or vendors, the search (for example “wedding venue in Boston”) is sent to Google. Place details shown come from Google and are not stored by us. Google’s use is governed by the Google Privacy Policy.
• Our hotel partner: when you search for or book a hotel, the city, dates and number of rooms and guests are sent to our hotel booking partner. A booking you make is completed on the partner’s service under its own privacy policy.
• Legal requirements: We may disclose information if required by law, court order, or to protect the rights and safety of our users or the public.
• Business transfers: In the event of a merger, acquisition, or sale of assets, user information may be transferred as part of that transaction. We will notify you before any such transfer.

Your data is stored on secure servers hosted by Vercel and Neon (PostgreSQL), located in the United States. We implement industry-standard security measures including:

• Encryption in transit (TLS/HTTPS) and at rest
• Access controls and authentication requirements for all team members
• Regular security reviews and vulnerability assessments
• Automatic backups of your event data

No method of transmission over the internet is 100% secure. While we strive to use commercially acceptable means to protect your data, we cannot guarantee absolute security.

We retain your data for as long as your account is active. If you delete your account, we will delete your personal data within 30 days, except where we are required to retain it for legal or billing purposes. Ask EV conversations, including your ratings, are kept with your account so you can return to them, and are deleted when your account is deleted — even where other records oblige us to keep an anonymized account.

What deletion does not remove. Deleting your account deletes the events you hosted, and with them the waivers people signed for those events and any documents vendors sent you. It does not remove a waiver or set of terms you signed for someone else’s event. That record belongs to the organiser who ran it, not to us: it is their evidence of what you agreed to before attending, and removing it on your request would destroy their record of an event you took part in. The same applies to a question you sent an organiser through a contact form, which is theirs once it arrives.

Records we keep for this reason are kept for that purpose alone. They are not used to build a profile of you, are not used for marketing, and are not sold or shared beyond the organiser they belong to. If you want one removed, ask that organiser, or write to us at privacy@eventvidia.com and we will pass the request on.

A cookie is a small file a website stores in your browser. We use as few as we can. We do not use advertising cookies, Google Analytics, a Facebook/Meta pixel or any other cross-site tracker, and we never sell what cookies tell us.

Essential cookies are needed for the site to work and can’t be switched off. Preference cookies are only set when you make that choice yourself. Referral cookies hold only a link’s code or the event it came from — nothing about you. If you visit from the EU, the UK or Switzerland, we ask before setting them, and choosing “Essential only” removes any already set. Anyone can change their choice with “Cookie settings” at the bottom of every page, or delete cookies in their browser settings.

Without cookies. We count page views and measure how fast pages load (Vercel Speed Insights, and Vercel Analytics on invitation pages) without cookies and without identifying you. Pages with a map load Google Maps, which receives your IP address and browser details under Google’s own privacy policy.

Promotional emails. In promotional emails — sent by EventVidia, or by an organiser, vendor or non-profit organisation through EventVidia — we record whether the email was opened and which links were clicked, so the sender can see how it performed and, once, resend it to people who did not open it. We keep only that it was opened (when, and how many times) and which link was clicked (and when): never your location, IP address or device. Opens are measured with a small image in the email, so turning off images in your email app stops them being recorded. Tickets, receipts, passes, invitations and other emails about something you did are never tracked this way. Unsubscribing from a sender stops their promotional emails entirely.

Depending on your location, you may have the following rights:

• Access: Request a copy of the personal data we hold about you
• Correction: Ask us to correct inaccurate or incomplete data
• Deletion: Request that we delete your personal data ("right to be forgotten")
• Portability: Receive your data in a machine-readable format
• Objection: Object to processing of your data for marketing purposes
• Restriction: Request that we limit how we process your data

To exercise any of these rights, email us at privacy@eventvidia.com. We will respond within 30 days.

You can delete your account at any time from Settings → Account → Delete Account. This will permanently remove all your events, guest lists, and personal data.

EventVidia is not directed at children under the age of 13. We do not knowingly collect personal information from children under 13. If you believe we have inadvertently collected such information, please contact us immediately at privacy@eventvidia.com and we will delete it promptly.

California Consumer Privacy Act (CCPA / CPRA)

If you are a California resident, you have the following additional rights under the CCPA and its amendment, the CPRA:

• Right to Know: Request disclosure of the categories and specific pieces of personal information we have collected about you, the sources, the business purpose, and the third parties with whom we share it.
• Right to Delete: Request deletion of your personal information, subject to certain exceptions (legal obligations, fraud prevention, etc.).
• Right to Correct: Request correction of inaccurate personal information.
• Right to Opt-Out: We do not sell or share personal information for cross-context behavioural advertising. You therefore have no opt-out action required, but you may submit a request to confirm this.
• Right to Limit Use of Sensitive Data: We do not process sensitive personal information beyond what is necessary to provide the Service.
• Right to Non-Discrimination: We will not discriminate against you for exercising your CCPA rights — you will receive the same quality of service regardless.

To submit a CCPA request, email privacy@eventvidia.com with subject line "CCPA Rights Request". We will respond within 45 days. We may ask you to verify your identity before processing the request.

In the past 12 months, we have collected the following categories of personal information:

• Identifiers (name, email, IP address)
• Commercial information (subscription plan, payment history)
• Internet or network activity (pages visited, features used)
• Professional or employment-related information (for corporate accounts)

We have not sold personal information in the past 12 months and have no intention to do so.

CAN-SPAM Act (Email Communications)

All marketing emails we send comply with the CAN-SPAM Act:

• We clearly identify ourselves as the sender in every email
• Subject lines accurately describe the email content — no misleading headers
• Every marketing email includes a clear, functional unsubscribe link
• We honour opt-out requests within 10 business days
• Our physical mailing address is included in all commercial emails
• A non-profit organisation, vendor or show host using EventVidia keeps its own lists of members, supporters or contacts (name, email, phone, categories) with a record of when and how each person agreed to email, text messages and WhatsApp messages from it. Each sees only its own lists; it can remove anyone, and you can ask it to remove you
• You can sign yourself up on an organisation’s, vendor’s or show host’s sign-up page (an EventVidia link they share). You choose email, texts and/or WhatsApp; we record what you ticked and when, add you to that one sender’s list only, and send one confirmation text if you chose texts — no further texts until you reply YES. Reply STOP at any time
• A wedding’s family tree holds the names and photos the couple, their planner or coordinator add of family members; it is seen only by the people working on that wedding, and removed with the event. Add someone’s photo only with their permission
• When you claim a gift card we ask you to confirm your mobile number with a code we text you, as part of claiming; if a claim is left waiting for that step, we send you one reminder email. We keep the number on your account and with the gift card, to allow one gift card per person; the code is stored only in scrambled form and deleted once used. We also record which code you claimed it with; EventVidia staff can see your name, email and where your gift card stands, to run the programme. The creator who shared the code is not shown who claimed it
• When a ticket order comes with an EventVidia credit, we email it to the address the tickets were sent to and keep that address with the credit, so that only the buyer can claim it. We record when it was claimed and by which account. The show’s host does not see who claimed a credit
• A vendor sees its customers (from its orders, bookings and client list) and a show host its ticket buyers, as lists inside its own account; buying something is not treated as agreeing to marketing texts
• An organisation, vendor or host can import people from its own Google Contacts. Google asks it to allow read-only access (the contacts.readonly permission); the contacts are read in its browser, the access is ended straight away, and only the people it ticks are saved to its list — we never store a Google token or the rest of the address book. EventVidia’s use of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements: it is used only to add those people to that organisation’s list, never sold, never used for advertising, and never used to train AI models
• Organisers, vendors and non-profit organisations may only email people who agreed to hear from them: people who tick an (always unticked) “email me about future events” box on their form, or who are on a list the organiser has confirmed agreed to it. We keep when and how each person agreed, and an unsubscribe from one organiser stops all of that organiser’s promotional email to you

To unsubscribe from marketing emails, click "Unsubscribe" in any email footer, or email privacy@eventvidia.com. Note: transactional emails (account confirmations, event invitations you trigger) cannot be opted out of while your account is active.

COPPA (Children Under 13)

EventVidia does not knowingly collect personal information from children under 13 years of age, in compliance with the Children's Online Privacy Protection Act (COPPA). If we discover we have inadvertently collected such data, we will delete it immediately. Parents or guardians may contact us at privacy@eventvidia.com to request removal of a child's information.

Digital Personal Data Protection (DPDP) Act, 2023

India's DPDP Act governs the processing of digital personal data. EventVidia complies with this legislation as follows:

Lawful Basis for Processing

We process your personal data on the following lawful bases under the DPDP Act:

• Consent: For marketing communications, analytics, and optional features. You may withdraw consent at any time.
• Contractual necessity: To provide the EventVidia service you have signed up for.
• Legitimate use: For fraud prevention, security, and legal compliance.

Your Rights as a Data Principal

Under the DPDP Act, you (as a "Data Principal") have the right to:

• Access information: Know what personal data we hold and how it is processed
• Correction and erasure: Request correction of inaccurate data or erasure of data no longer needed
• Grievance redressal: Raise grievances with us — we will respond within 72 hours and resolve within 30 days
• Nominate a representative: Nominate another individual to exercise your rights on your behalf in the event of death or incapacity

To exercise these rights, email privacy@eventvidia.com with subject line "DPDP Rights Request — India". We will acknowledge within 72 hours.

Consent Management

• Consent is obtained before collecting personal data where required by law
• You may withdraw consent at any time without affecting the legality of prior processing
• We maintain a record of consents provided
• Children (under 18 in India) require verifiable parental consent before we process their data

Cross-Border Data Transfers

EventVidia stores and processes data on servers located in the United States (Vercel, Neon). By using EventVidia from India, you consent to the transfer of your personal data to the United States. We ensure adequate data protection standards are maintained through contractual agreements with our service providers.

We will comply with any notified restrictions on cross-border transfers under the DPDP Act as and when such restrictions are published by the Government of India.

Grievance Officer (India)

In accordance with the Information Technology Act, 2000 and the DPDP Act 2023, we have designated a Grievance Officer for India:

If you are not satisfied with our response, you may escalate your complaint to the Data Protection Board of India once it is constituted under the DPDP Act.

IT Act 2000 Compliance

We comply with the Information Technology (Reasonable Security Practices and Procedures and Sensitive Personal Data or Information) Rules, 2011 under the IT Act 2000:

• We maintain a comprehensive information security policy
• Sensitive personal data (financial info, passwords) is encrypted in transit and at rest
• We conduct periodic security audits
• We will notify affected users of any data breach within 72 hours of becoming aware

We may update this Privacy Policy from time to time. When we make significant changes, we will notify you by email and display a notice in the app at least 14 days before the changes take effect. Your continued use of EventVidia after the effective date constitutes acceptance of the updated policy.

We encourage you to review this page periodically. The "Last updated" date at the top reflects the most recent revision.

If you have questions, concerns, or requests regarding this Privacy Policy, please contact us: