Event Hub Inc., doing business as EventHub Pro · Last updated September 17, 2026
Event Hub Inc., doing business as EventHub Pro (“Event Hub”, “EventHub Pro”, “we”, “us”), provides an event fundraising platform used by event organizers (“hosts”) and their guests at portal.eventhubpro.com and eventhubpro.com. This policy explains what we collect, how we use it, and the choices you have. This is the only privacy policy that applies to EventHub Pro, including our text messaging program.
What we collect and why. We collect your mobile phone number when you create an organizer account or register for an event and enter it in the mobile number field. We use it to send you a one-time verification code, to confirm your registration, and to send event-related messages (such as bid, raffle, pledge, and receipt notifications) for the event you registered for. We also record the date, time, and source of your consent so we can honor your opt-out.
Consent. Consent to receive text messages is given only when you enter your mobile number and continue. Consent is not a condition of any purchase or donation. Messages may be sent by automated means. Message frequency varies by event; a typical guest receives fewer than 10 messages per event. Message and data rates may apply.
Opting out and help. Reply STOP to any message to opt out at any time; you will receive one final confirmation message and no further texts. Reply HELP for help, text START to re-enable messages, or email support@eventhubpro.com.
We do not share, sell, or provide your mobile phone number or messaging consent data to third parties or affiliates for marketing or promotional purposes. Text messaging originator opt-in data and consent will not be shared with any third parties. The only exception is the messaging service provider that delivers our texts (Twilio), which acts on our behalf, receives only what it needs to deliver the message, and is not permitted to use your number for any other purpose.
Event Hub does not process, store, or transmit card numbers. All payments are processed by Stripe under Stripe’s own terms and privacy policy.
A host’s Stripe account is the host’s, not ours. To accept payments through Event Hub, a host connects its own Stripe account to our platform using Stripe Connect. When it does, Stripe grants Event Hub a programmatic authorization to that account. We use the authorization only to:
What we deliberately do not do. Although the authorization Stripe grants to a connected platform is technically broad, Event Hub does not retrieve, display, store, or analyze transactions, customers, payouts, balances, or other records in a host’s Stripe account that did not originate from Event Hub. Our software requests only the transactions it created, identified by the transaction identifiers we recorded at the time of creation and the Event Hub identifiers we attach to each one. The Event Hub portal is built from our own records of Event Hub transactions, not from a live view of the host’s Stripe account, and where Stripe sends us notifications for a connected account, we discard those that do not relate to a transaction Event Hub created.
How Event Hub transactions are identified in a host’s Stripe account. Every transaction we create is labeled so the host can always tell it came through Event Hub: Event Hub is recorded as the originating application, the description names the event and the module (Ask, Auction, Raffle, or Check-In), and metadata carries the host’s Event Hub organization and event identifiers. Where the card network allows it, we also add a short “EVENTHUB” suffix to the statement descriptor the donor sees on their card statement. Hosts can filter their Stripe Dashboard by any of these at any time.
Disconnecting. A host may disconnect its Stripe account from Event Hub at any time from Settings → Payments in the Service or from the connected-applications settings in its Stripe Dashboard. Disconnecting revokes our authorization immediately. We keep our existing records of Event Hub transactions as described under “Retention & security”, but we can no longer read or act on the host’s Stripe account after disconnection.
Stripe’s role. Stripe acts as an independent payment processor and, for data protection purposes, as an independent controller of the data it collects. Stripe may collect identity and business information directly from a host to meet its own legal obligations; Event Hub does not receive or store that information beyond the connection status Stripe reports to us.
We do not sell your personal information, and we never share your mobile phone number or text messaging consent with third parties or affiliates for their marketing or promotional purposes. We share personal information only with:
We retain account records for as long as your account is active and as needed to operate the service. We retain transaction records (including records of Event Hub transactions on a host’s Stripe account) for seven (7) years from the date of the transaction to meet legal, tax, audit, and dispute requirements, after which they are deleted or anonymized. Passwords and verification codes are stored only as one-way hashes; data is encrypted in transit (TLS).
The service is not directed to children under 13, and we do not knowingly collect their information.
We may update this policy from time to time; the “Last updated” date above reflects the current version. Material changes will be posted on this page.
Event Hub Inc. (EventHub Pro)
Suffolk County, New York
Email support@eventhubpro.com