1. Who we are
EventLive Pro, LLP is a limited liability partnership registered in England and Wales (number OC435973). Registered office: 2 Frederick Street, Kings Cross, London WC1X 0ND, United Kingdom.
This policy covers:
- our website, eventlive.pro, including the help center;
- event pages, the video player, ticketing and embeds at evt.live and youthcast.live;
- the EventLive apps for iPhone, iPad, Android and Mac, and the web app at broadcaster.eventlive.pro.
It doesn't cover other websites we link to, or the rest of an organizer's own website when they embed an EventLive player there. Those have their own privacy policies.
Questions or requests: email support@eventlive.pro with “Privacy” in the subject line, or write to us at our registered office.
2. Who decides what happens to your data
We decide (we are the “controller”) for our website, organizer accounts, purchases made from us, support conversations, our marketing, security, and statistics about how EventLive is used.
The organizer decides for the people connected with their event: the guests they invite, people who register or sign the guestbook, ticket buyers' details, viewers, and what is streamed. For that data we work on the organizer's behalf (we are their “processor” or “service provider”) and follow their instructions and our Terms of Service. If you contact us about an event's data, we'll pass your request to the organizer and help them answer it. Organizers who need a signed data processing agreement can email us.
Some payment services act on their own account: Stripe for card payments (for ticket sales, on the organizer's own Stripe account), Apple and Google for in-app purchases and sign-in, and Pledge for donations. Their privacy policies cover what they collect.
3. What we collect, and why
Pick the parts that describe you. Most people fit more than one.
Website visitors (eventlive.pro)
What we collect
- Visit statistics without cookies, from our self-hosted analytics on our servers in Europe: the page, the site that sent you, browser, operating system, device type and country. Your IP address is only used to make an anonymous ID that changes every day; it isn't stored.
- Optional tools, which run only with your OK if you're in the EEA, the UK or Switzerland, and otherwise until you turn them off: Google Ads and Microsoft Advertising measurement tags. With these on we also keep the click ID from the ad you came from (for example “gclid”) for 90 days and pass it to our sign-up and checkout pages. See Cookies.
- Server logs at our hosting provider: IP address, browser and pages requested. It also tells us your country (so we know whether to ask about cookies) and, only for the funeral home search, your rough location.
- Videos in blog posts come from YouTube in privacy-enhanced mode: YouTube sees your IP address when the page loads, and sets cookies only if you play the video.
- App download links go through Branch (eventlive.app.link), the App Store and Google Play, which see the click.
- Wedding officiant script writer: what you enter (names, your story, ceremony wishes and any religious or cultural details you include) is sent to OpenAI to write your script. We don't save it or keep it in our logs. Under OpenAI's terms it doesn't use this data to train its models, and keeps it for at most 30 days to check for abuse.
Why
- To run the site and keep it secure.
- To understand which pages help people, using cookie-free statistics.
- With the optional tools on: to measure which of our ads lead to downloads, sign-ups and purchases.
- To write the ceremony script you ask for in our wedding officiant script writer.
Who else gets it
Our hosting providers, Google Ads, Microsoft Advertising, YouTube, Branch, OpenAI. Contact forms and the support chat are covered below.
Organizers and broadcasters
This includes anyone with an EventLive account: people streaming their own event, videographers, funeral homes, churches, schools, businesses, organizers who sell tickets (pay-per-view) and those who raise donations.
What we collect
- Account: name, email, company and role, time zone, and your password, which is handled by our sign-in service so we never see it. If you sign in with Apple or Google, we get the name and email they share.
- How you found us: the link you arrived from (including campaign tags and partner details, for example from Joy), the ad click IDs from Google or Microsoft ads, and analytics cookie IDs already in your browser (Google Analytics “_ga”, Meta “_fbp” and “_fbc”).
- Events: titles, dates, places, descriptions, images, documents, privacy settings, event passwords, and the guest lists you add.
- Streams and recordings: the video and audio you stream or upload, thumbnails, your stream key, the IP address of the device you stream from, and device details (model, mobile carrier, battery, storage) and app logs that help us fix streaming problems.
- Purchases from us: through Stripe (name, email, billing address, tax ID; your card is entered with Stripe and never stored by us) or through Apple or Google in-app purchases (a receipt). We add your ad click IDs and analytics cookie IDs to Stripe purchases.
- Selling tickets: you connect your own Stripe account through Stripe Connect. Stripe verifies your identity and pays you out. Through Stripe Connect we can see most of your Stripe account's details, such as its business name, email, country, payments and payouts, and we keep your Stripe account ID and the details of each sale.
- Fundraising: the nonprofits you pick and your fundraiser settings.
- How you use the apps: app activity, device model, operating system or browser, app version, language, approximate location from your IP address and an app-specific device ID (Amplitude, in the apps and the web app), crash reports (Sentry), and in the web app, cookie-free statistics from our self-hosted analytics.
Why
- To provide EventLive: streaming, recording, event pages, guest emails, ticketing and fundraising.
- To take payments, issue invoices and handle tax.
- To support you. Our team can open your account and events, including password-protected ones, when needed to help you or keep the service running, and we get a copy of “we’re live” notices to watch for problems.
- To keep EventLive secure and prevent fraud and abuse.
- To understand how the apps are used and improve them.
- To understand and run our business: we analyze account, event, purchase and usage data, including with AI tools such as Anthropic’s Claude, set up so the provider doesn’t train its models on our data.
- To measure which of our ads bring customers.
- To send service emails, and marketing emails (see below).
Who else gets it
Our hosting, storage and content delivery providers, Stripe, Apple, Google Play and Google Sign-In, Amplitude, Sentry, Intercom, Branch, Google Ads, and the others in the full list. Your event pages show what you choose to publish.
Our emails to you. We send service emails about your account, purchases, recordings and storage. New personal accounts also get a short series of tips, and business accounts get our newsletter. Each marketing email has a one-click unsubscribe link, and you can also email us to stop them.
Viewers
You don't need an account to watch an open event. The organizer of the event is in charge of this data; we handle it for them.
What we collect
- An anonymous guest ID saved in your browser, which event you watched and when, and whether you watched live or a replay.
- Device type, browser and rough location (country and region, worked out from your IP address), for playback quality and for the organizer's viewing statistics (Mux Data).
- Your IP address passes through our hosting and video delivery networks. For password-protected events, a cookie keeps you signed in for 7 days. To stop password guessing and other abuse, we briefly keep IP addresses, or scrambled (hashed) versions of them.
- Cookie-free visit statistics from our self-hosted analytics.
Why
- To play the event and show it only to people the organizer allows.
- To give organizers viewer counts and device and location summaries.
- To find and fix playback problems and stop abuse.
Who else gets it
The organizer (summaries, and names of guests who gave them). Our hosting and content delivery providers, Mux Data, Google Fonts and Google Cast (fonts and casting to a TV).
Guests who give their details
This covers registering for an event, asking for reminders, signing the guestbook, and being invited by the organizer, who can add you by typing your details, importing a list or using our API.
What we collect
- Your name and email address, how you were added, and whether you visited or watched.
- Guestbook and chat messages, your name as you wrote it, and any photo you add. These are shown on the event page to everyone who can see the event.
Why
- To let you into the event and show the organizer who registered.
- To email you on the organizer’s behalf: invitations, reminders about 24 hours and 1 hour before, a “we’re live” notice and replay or download notices. They come from support@ses.eventlive.pro with the organizer’s name, and each one has an unsubscribe link for that event.
- To show your guestbook message to the event’s viewers and give the organizer a guestbook PDF.
Who else gets it
The organizer sees your details in the event's guest list. We send the emails through our email provider. We don't send guests our own marketing and we don't sell guest lists. You can delete your own guestbook message; for anything else, ask the organizer or email us.
Ticket buyers
Ticket sales run on the organizer's own Stripe account. The organizer is the seller, sets the refund policy and handles refunds. EventLive charges the organizer a ticketing fee.
What we collect
- Stripe collects your card details, email and name. We never see your full card number.
- We receive your email, what you bought (full event, a day, replay or download), the amount, currency and the Stripe payment reference, and add you to the event's guest list.
- Which device is watching with your ticket, because a ticket works on one device at a time.
Why
- To give you access and email you your link.
- To combine your purchases for the same event, and stop a ticket being shared.
- To help with payment questions and refunds you raise with the organizer.
Who else gets it
Stripe, the organizer, and the companies that run evt.live (see the full list).
Donors
Donations go through Pledge's secure form. Gifts are made to Pledgeling Foundation, a US 501(c)(3) charity, which emails your tax receipt and passes the money to the nonprofit. Pledge's privacy policy covers the details you give there.
What we collect
- If you already gave your name and email on the event page, the donation form may fill them in for you, in your browser.
- From Pledge, we receive the name shown in Pledge's public donor list (or “Anonymous”) and the amount of each completed donation.
Why
- To thank donors in the guestbook and show the amount raised, if the organizer turned this on.
Who else gets it
Pledge's form lets you choose not to share your name and email with the nonprofit and EventLive, and not to show your name publicly.
People who contact us
You can reach us through our support chat (on our website, event pages and in the apps) or by email.
What we collect
- Your messages, files and screenshots you send (we strip location data from images), your email address if you give it, and your country.
- In the apps, when you're signed in, each message includes a screenshot of the screen you're on and which screen it is, and the chat sees a summary of your account and recent events, so it can see the problem.
Why
- To answer you and fix problems.
- To improve our answers and help articles.
Who else gets it
Our support chat uses OpenAI to write answers. Before a message goes to OpenAI we remove email addresses and the parts of links that can carry personal details. Under OpenAI's terms it doesn't use this data to train its models, and keeps it for at most 30 days to check for abuse. Conversations are kept in our support database. People on our team read conversations and can reply. We use Anthropic's Claude to review conversations and draft replies, set up so Anthropic doesn't train its models on our data, and Google's Gemini to test the chat's answers against past conversations. Email goes through our email providers.
People who appear in streams
Events are filmed by organizers, who decide what to stream and are responsible for having the permissions they need, including from parents for children and from families at funerals.
What we collect
- Video and audio of the event.
- Some events, such as funerals and religious services, can reveal sensitive information, like someone's religion or health. We only use it to provide the service to the organizer.
Why
- To stream, record and deliver the event the organizer created.
Who else gets it
Video is processed, stored and delivered by our hosting, storage and content delivery providers (see the list). To have a recording removed, ask the organizer or email us and we'll work with them.
4. Our legal reasons (EU and UK)
If you're in the EEA or the UK, data protection law requires a legal reason for each use of your data. Ours are:
| What we do | Legal reason |
|---|
| Running your account, events, streams and the purchases you ask for | Contract |
| Handling guest, viewer, ticket buyer and event data for organizers | The organizer’s legal reason; we act on their instructions |
| Invoices, tax and accounting records | Legal obligation |
| Security, fraud and abuse prevention, and our team’s access to accounts for support | Legitimate interests: keeping EventLive safe and working |
| Answering support requests, including with AI | Contract, or legitimate interests if you’re not a customer |
| Writing a wedding ceremony script you ask for, with AI | Legitimate interests: giving you the free tool you asked to use; for religious details you include, your consent when you send them |
| Cookie-free statistics, app analytics and crash reports | Legitimate interests: understanding and improving EventLive |
| Optional cookies on eventlive.pro (Google Ads, Microsoft Advertising) | Consent, which you can withdraw at any time |
| Sending ad click IDs from purchases to Google | Consent where required; otherwise legitimate interests: measuring our ads |
| Marketing emails to customers | Legitimate interests, with an unsubscribe link in every email |
| Following up on forms businesses send us | Legitimate interests, or steps before a contract |
Where we rely on legitimate interests, you can object (see Your rights). You can always object to marketing.
5. Companies that handle data for us
These companies help us run EventLive. Most may only use your data to provide their service to us, under contracts that require them to protect it. Those marked “Acts under its own privacy policy” decide for themselves how they use the data they collect. Google and Microsoft's advertising services are explained in Advertising.
For key parts of EventLive, such as video delivery and storage, we use more than one provider, so the service keeps working if one of them has a problem. We review this list at least every three months.
Hosting, storage and video delivery| Provider | What it does for us | Personal data | Where |
|---|
| Hosting, servers, storage and content deliveryAmazon Web Services, Backblaze, bunny.net, Cloudflare, DigitalOcean, Expo, Google Cloud Storage (Firebase), Hetzner, Netlify, Turso, Vercel | Run our websites, apps and servers; store accounts, events, guest lists, messages and recordings; process live video; deliver video and files through content delivery networks (CDNs); deliver app updates | The personal data described in this policy that we store, process or deliver, including IP addresses, account and event details, guest lists, messages, photos, recordings and technical logs | United States, European Union, and servers worldwide for content delivery |
| Google Maps PlatformGoogle LLC | Finds your funeral home's listing when you type its name in our sign-up form | What you type in the search, and your approximate location (from your IP address) so nearby places come first | United States |
| Google Fonts and Google CastGoogle LLC | Fonts on evt.live event pages, and casting to Chromecast TVs | IP address and browser details | United States |
| YouTubeGoogle LLCActs under its own privacy policy | Videos embedded in some blog posts and guides, in privacy-enhanced mode | IP address and browser details when the page loads; YouTube sets cookies only if you play the video | United States |
Payments, app stores and donations| Provider | What it does for us | Personal data | Where |
|---|
| StripeStripe, Inc. and Stripe Payments Europe, Ltd. | Card payments, invoices and tax for organizer purchases; ticket sales and payouts run on the organizer's own Stripe account (Stripe Connect) | Name, email, billing address, tax ID, card details (entered with Stripe, never stored by us), purchase details; for organizer purchases also the ad click IDs and analytics cookie IDs we attach to the purchase. For organizers who sell tickets, we can see most of their connected Stripe account's details through Stripe Connect | United States and Ireland |
| AppleApple Inc.Acts under its own privacy policy | App Store downloads, in-app purchases and Sign in with Apple | Purchase receipts; your name and email (or a private relay email) if you sign in with Apple | United States |
| Google Play and Google Sign-InGoogle LLCActs under its own privacy policy | Google Play downloads, in-app purchases and Sign in with Google | Purchase receipts; your name and email if you sign in with Google | United States |
| PledgePledgeling Technologies, Inc. and Pledgeling FoundationActs under its own privacy policy | Processes donations to nonprofits and sends tax receipts; nonprofit search on our website; adds missing nonprofits when asked | Donor name, email, payment details and gift (collected by Pledge); for nonprofit requests the EIN and the contact's name, email and role | United States |
Email, support and AI| Provider | What it does for us | Personal data | Where |
|---|
| EmailAmazon SES, Google Workspace, Resend | Send event, account and newsletter emails; send website form submissions to our team; receive and answer email | Names, email addresses, event details and the messages themselves | United States and European Union |
| OpenAIOpenAI, L.L.C. | Answers questions in our support chat, finds the right help articles, and writes scripts in our wedding officiant script writer | Your chat messages (we remove email addresses and links first), screenshots you send from the app, a summary of a signed-in organizer's account and recent events, your country; what you enter in the wedding officiant script writer (names, your story, ceremony wishes), which we don't save | United States |
| IntercomIntercom, Inc. | Our previous support chat (we are moving off it): keeps past conversations and receives organizer account updates | Past support conversations, organizer name, email and account details | United States |
| AnthropicAnthropic, PBC | Our team uses Claude to analyze our business and support data, review support conversations, and draft replies and help articles. We've set it up so Anthropic doesn't train its models on our data | Support conversations and email; account, event, purchase and usage data | United States |
| Google Gemini APIGoogle LLC | Checks the quality of our support assistant's answers against past support conversations | Past support conversations and screenshots | United States |
Analytics and diagnostics| Provider | What it does for us | Personal data | Where |
|---|
| AmplitudeAmplitude, Inc. | Shows us how the EventLive apps are used so we can improve them | App activity (including sign-ups and purchases), device model, operating system or browser, app version, language, approximate location from your IP address, an app-specific device ID, and your account profile (name, email, Stripe customer ID) | United States |
| Mux DataMux, Inc. | Measures video playback quality on event pages | Anonymous guest ID, video title, device and browser, approximate location from your IP address | United States |
| SentryFunctional Software, Inc. | Crash and error reports from the EventLive apps | Account ID, device and app version, the screen in use, error details | United States |
| BranchBranch Metrics, Inc. | Links that open or install the EventLive app (eventlive.app.link), including links that sign you in to the app | Link clicks, device type, operating system, IP address; on iPhone, a link copied before install so the app can open it | United States |
Advertising measurement| Provider | What it does for us | Personal data | Where |
|---|
| Google AdsGoogle LLC | Measures which of our Google ads lead to app downloads, sign-ups and purchases | Cookie IDs, IP address, pages visited and buttons clicked on eventlive.pro; when an organizer buys after clicking one of our ads, the Google click ID, purchase amount and time | United States |
| Microsoft AdvertisingMicrosoft Corporation | Measures which of our Microsoft (Bing) ads lead to app downloads, sign-ups and purchases | Cookie IDs, IP address, pages visited and buttons clicked on eventlive.pro, the Microsoft click ID | United States |
Internal work tools| Provider | What it does for us | Personal data | Where |
|---|
| GitHubGitHub, Inc. | Our code and task tracking, including tasks created from crash reports and support issues | Crash diagnostics; occasionally an account or event identifier in a support task | United States |
We may also share data when the law requires it, to protect people's safety or our rights, or as part of a sale or reorganization of our business, in which case this policy would continue to apply to your data.
6. Cookies and similar tools
On eventlive.pro
If you're in the EEA, the UK or Switzerland, the optional tools below stay off until you choose Accept. Elsewhere they're on until you turn them off. If your browser sends a Global Privacy Control signal, they stay off everywhere. You can change your choice at any time:
Cookie settings
| Name | From | What for | How long | Optional? |
|---|
eventliveAdConsentGranted, fbGrantConsentBrowser storage | EventLive | Remembers your choice about optional cookies | Until you change it | No, needed |
eventliveAdClickIdsBrowser storage | EventLive | Keeps the ad click ID (gclid, gbraid, wbraid or msclkid) from the ad you clicked so a later sign-up or purchase can be credited to it | 90 days | Yes |
_gcl_au, _gcl_awCookie | Google Ads | Ad conversion measurement | 90 days | Yes |
_uetsid, _uetvid, MUIDCookie | Microsoft Advertising | Ad conversion measurement | 1 day (_uetsid), 13 months (_uetvid), 1 year (MUID) | Yes |
Our self-hosted visit statistics set no cookies. The support chat window comes from our web app at broadcaster.eventlive.pro and, if you're signed in there, uses that sign-in.
On event pages and in the web app
| Where | Name | What for | How long |
|---|
| evt.live event pages | guestId-<event> | Recognizes you as the same guest on that event (registration, guestbook, ticket) | Until you clear your browser storage |
| evt.live event pages | el_va_<event> | Keeps you signed in to a password-protected event | 7 days |
| evt.live checkout | Stripe cookies (__stripe_mid, __stripe_sid) | Fraud prevention during payment, set by Stripe | 1 year and 30 minutes |
| EventLive web app (broadcaster.eventlive.pro) | Sign-in storage | Keeps you signed in | Until you sign out |
| EventLive web app (broadcaster.eventlive.pro) | eventlive.amplitude.state, eventlive.amplitude.queue | An app-specific device ID and usage events not yet sent, for our app analytics (Amplitude) | Until you clear your browser storage |
The donation form (Pledge), checkout (Stripe) and Mux Data may store their own identifiers. You can block or delete cookies in your browser settings; event pages and the apps keep working without analytics cookies.
7. Advertising, “selling” and “sharing”
We don't show ads, and we don't sell personal information for money. We do advertise EventLive on Google and Microsoft (Bing), and we measure which ads work:
- On eventlive.pro, the Google Ads and Microsoft Advertising tags record cookie IDs, your IP address and the pages and buttons you use, when the optional tools are on.
- When an organizer who came from one of our Google ads buys from us, our server sends Google the click ID, the amount and the time of the purchase.
Google and Microsoft may use this for their own advertising. Under California law, that can count as “sharing” personal information for cross-context behavioral advertising. You can opt out:
8. How long we keep data
| Data | How long |
|---|
| Organizer account and profile | While your account is open. When you ask us to delete your account we erase it within 30 days; backup copies roll off within 90 days |
| Invoices and payment records for purchases from us | 6 years, to meet UK tax and accounting rules |
| Recordings and uploads | For the event's storage period (one month, one year or ten years, depending on what was bought; older events: one year after the event). Then we move recordings to cold storage so the organizer can restore them, and keep them there, along with raw backup copies of live streams, until the organizer asks us to delete them or closes the account |
| Guest lists, guestbook messages and photos, ticket and donation entries on an event | As long as the event is in the organizer's account. Organizers can remove guests; guests can delete their own guestbook messages |
| Records of each viewing connection | 30 days. A per-event summary of who watched stays as long as the event does |
| Support conversations | As long as we need them to help you and handle follow-ups. Ask us and we'll delete them |
| Website form submissions and business leads | As long as we need them to reply and follow up. We review and delete old leads at least once a year |
| Marketing email history | Email send log 2 years, activity records about 1 year. If you unsubscribe we keep your email address on a do-not-email list so we can respect your choice |
| Technical and security logs | Streaming server logs: 7 days on the server. Copies used for troubleshooting and security: as long as we need them for those purposes |
| What you enter in the wedding officiant script writer, and your script | Not kept. We pass it to OpenAI to write your script and don't save it |
| Cookie-free visit statistics (our self-hosted analytics) | Kept only as totals that don't identify you |
Deleting your account in the app removes your sign-in, profile and events. To have your recordings, uploads, guest lists and everything else erased as well, email us; we finish within 30 days. Payment services, app stores and Pledge keep their own records under their own policies.
9. Where your data goes
We're based in the UK. Our main systems are in the United States, live video is processed in the European Union, and video is delivered from servers around the world. The provider list shows where each company handles data.
When personal data leaves the UK or the EEA for a country without an adequacy decision, we rely on the EU–US Data Privacy Framework and its UK Extension where the company is certified, and otherwise on the European Commission's standard contractual clauses and the UK addendum or International Data Transfer Agreement, included in our providers' data processing terms. Email us for more detail.
10. Security, and what is public
Our websites and apps use encrypted connections (HTTPS), and you can stream over an encrypted connection (RTMPS). Our databases and most of our file storage are encrypted at rest. A dedicated sign-in service handles account passwords, payment cards stay with Stripe, Apple and Google, and our team's access is limited to what they need. No system is perfectly secure. If a breach puts your data at risk, we'll tell you and the authorities as the law requires.
Some things are public by design. Please keep them in mind:
- Anyone with the link to an open event can watch it. Use a password, invite-only access or tickets for private events.
- Images, guestbook photos, documents and the guestbook PDF shown on an event page are stored so that anyone with their direct link can open them.
- An event password is shared with everyone the organizer invites, and organizers can view it in their account. Don't use a password you use anywhere else.
Found a security problem? Email support@eventlive.pro with “Security” in the subject line.
11. Your rights and choices
Wherever you live, you can ask us to tell you what we hold about you, give you a copy, correct it, or delete it. Email support@eventlive.pro. We'll check it's you, usually by replying to the email address on your account, and answer within one month (45 days for US state laws). If the data belongs to an organizer's event, we'll pass your request to them and help. Exercising your rights won't affect the price or service you get.
EEA and UK
You can also restrict or object to our use of your data, ask to move it to another service, and withdraw consent at any time. You can complain to the UK Information Commissioner's Office (ico.org.uk) or the data protection authority where you live (list of EU authorities), though we'd appreciate the chance to help first.
Choices you can make yourself
- Optional cookies on eventlive.pro: Cookie settings.
- Marketing email: the unsubscribe link in any email.
- Event emails: the unsubscribe link in that event's email.
- Guestbook: delete your own message on the event page.
- Organizers: edit your profile, delete guests and events, or delete your account in the app.
12. California and other US states
This section is our notice for California residents under the California Consumer Privacy Act (CCPA), as amended by the CPRA.
What we collected in the last 12 months| Category | Examples | Shared for advertising? |
|---|
| Identifiers | Name, email, IP address, account and device IDs, cookie IDs, ad click IDs | Yes: cookie IDs, IP address and ad click IDs, with Google and Microsoft |
| Customer records | Billing address, phone number, tax ID | No |
| Commercial information | Purchases, tickets, donations shown on an event | Yes: amount and time of organizer purchases, with Google |
| Internet or network activity | Pages visited, clicks, app activity, viewing records | Yes: activity on eventlive.pro, with Google and Microsoft |
| Approximate location | Country and region from your IP address | No |
| Audio, video and similar | Streams, recordings, photos, support screenshots | No |
| Professional information | Business name and role, for organizers and businesses | No |
| Sensitive personal information | Account sign-in (email and password) | No |
We get this from you, from organizers (for their guests), from your device, and from partners and payment services. We use it for the purposes in section 3, disclose it to the service providers in section 5, and keep it as described in section 8. We don't sell personal information for money, we don't knowingly sell or share the data of anyone under 16, and we use sensitive personal information only to provide the service, so there is no need to ask us to limit it.
Your California rights: to know and get a copy of what we collect, to delete it, to correct it, to opt out of sharing for advertising, and not to be treated differently for using these rights. Opt out with the Do Not Sell or Share My Personal Information link or Global Privacy Control, which we honor on eventlive.pro; for anything else, email support@eventlive.pro. An authorized agent can ask for you with your signed permission; we may still check your identity with you. We answer within 45 days, or tell you if we need another 45.
Do Not Track: browsers' older “Do Not Track” setting has no agreed meaning, so we don't respond to it. We do honor Global Privacy Control on eventlive.pro.
Shine the Light: we don't give personal information to other companies for their own direct marketing.
Other US states
If you live in a state with its own consumer privacy law, such as Colorado, Connecticut, Oregon, Texas or Virginia, you have similar rights to access, correct, delete and get a copy of your data, and to opt out of targeted advertising. If we turn down your request, you can appeal by replying with “Appeal” in the subject line. We'll answer within 60 days and, if we still say no, tell you how to contact your state attorney general.
13. Children
You must be 18 or older to create an EventLive account. EventLive isn't aimed at children, and we don't knowingly collect personal information from children under 13. Children may appear in events such as school or youth sports streams; organizers are responsible for any permission they need from parents. If you think a child has given us their data, or you want a child's data removed, email us.
14. Changes to this policy
We review this policy at least every 3 months and whenever we add a new service or start collecting something new. We'll post changes here and update the dates at the top. If a change matters, we'll tell organizers by email or in the app before it takes effect.
