The short version
- We collect what the service needs: your account, the ticketing accounts you connect, your reports and their recipients.
- We read ticket counts and event details from Eventbrite and Universe, not your buyers’ names, emails or orders.
- We don’t sell personal information or share it for advertising.
- Google Analytics stays off in Europe (including the EU, EEA, UK and Switzerland) until you accept, and you can turn it off anywhere.
- You can delete your account at any time in Dashboard > Account.
1.Who we are
TicketCounts.io is a product of Elektronic Group Inc. Elektronic Group Inc., based in Jacksonville, Florida (“we”, “us”), decides how the personal information described here is used and is responsible for it. Questions and requests: support@elektronicgroup.com.
2.What we collect
If you have an account
- Account details: your name, email address and password (stored only as a hash by our sign-in system; we cannot see it), your organization name, an optional profile photo, your optional answer to “How did you hear about us?”, and your trial and plan dates.
- Connected ticketing accounts: when you connect Eventbrite or Universe, we receive access tokens for that account, the account’s ID, name and email address, and the organizations and events you can access (such as event names and dates). When a report runs, we read the number of tickets sold per ticket type (with paid and free totals) and the capacity when the platform provides it. We do not read your buyers’ names, email addresses or orders.
- Reports: the event, schedule and time zone, your recipients’ email addresses, your logo, and a history of each send: when it went out, to which address, whether it bounced or was marked as spam, and the counts it showed.
- Billing: Stripe processes payments. We store your Stripe customer ID, your plan, the subscription status and the billing period dates. We never receive or store full card numbers.
- Messages: what you send us when you contact support, and the notifications we show you in the app.
If you receive reports
Account holders add their recipients’ email addresses. We use them to send that account holder’s reports, and we record each send, any bounce or spam complaint, and whether you unsubscribed. Replies to a report go straight to the account holder; we do not receive them.
If you receive a Growth Operations outreach email
We use business contact details that an organization publicly lists, public information from its official website, and evidence about ticketing platforms to decide whether TicketCounts.io may be relevant. For an outreach email, we record delivery metadata including its Message-ID. If you reply to our dedicated outreach address, we authenticate and verify the inbound message, then use its address and headers to match it to that outreach. A verified reply stops future Growth Operations follow-ups to that contact and is forwarded as a text-only notification to our configured internal inbox so a person can respond manually. We do not send automatic replies, and we do not store the original reply body in the reply-correlation record.
If you ask to be told about a ticketing platform
Your email address and the name of the platform you typed.
Everyone who visits the website
- Technical information: IP address, browser and device type, the pages requested and when. It passes through our security and delivery provider and our servers, and short-lived counters use it to stop abuse.
- Analytics, where you allow it (section 5): pages viewed, how you arrived, approximate location, device and browser, and events such as starting a sign-up or buying a plan. If you are signed in and analytics is on (you accepted it, or it is on by default where you are and you have not turned it off), we also keep your browser’s analytics ID with your account, and our server sends Google Analytics a few account events under that ID: a plan bought, renewed or canceled (with the plan and its price) and your first report sent. We never send your name or email address to Google Analytics.
We get this information from you, from your browser, from public official websites, from the ticketing platforms you connect, from Stripe (payment status), and from our email provider (delivery metadata, bounces, spam complaints, and authenticated Growth Operations replies).
3.How we use it
| Purpose | Information | Legal basis (EEA, UK, Switzerland) |
|---|---|---|
| Run the service: your account, platform connections, fetching counts, sending reports on schedule, the dashboard | Account details, connected accounts, reports | Contract |
| Trial, subscriptions, invoices and payment notices | Account details, billing | Contract; legal obligation for tax and accounting records |
| Service emails: confirmations, trial reminders, billing notices, problems with your reports | Account details | Contract |
| Honor unsubscribes and keep email deliverable: suppression, bounce and complaint records | Recipient addresses, bounces and spam complaints | Legitimate interests; legal obligation where anti-spam law applies |
| Run limited, individual Growth Operations outreach and handle verified replies | Public business contact details, public official-website information, delivery Message-ID, and verified reply data | Legitimate interests; legal obligation where anti-spam law applies |
| Security: stopping abuse and fraud, rate limits, logs | Technical information | Legitimate interests |
| Understand which pages help and where sign-ups come from | Analytics (including the account events our server sends while you allow analytics), your "How did you hear about us?" answer | Consent for analytics; legitimate interests for the sign-up answer |
| Tell you if a ticketing platform you asked about becomes available | Platform request | Consent |
| Comply with the law and enforce our terms | As needed | Legal obligation; legitimate interests |
We do not sell personal information or send newsletters. We may send limited, individual Growth Operations outreach to publicly listed business contacts where we reasonably believe TicketCounts.io may be relevant. Each message includes an unsubscribe option.
4.Service providers and sharing
These companies process personal information for us, only to provide their service to us:
| Provider | What they do for us | Information involved |
|---|---|---|
| Supabase (open-source software we run ourselves) | Database, sign-in and file storage, run on a server operated by Elektronic Group Inc.; Supabase, Inc. does not host this data. Hosting provider and location: Hostinger International Ltd., on a server in the United States (Boston, Massachusetts). | Everything listed in section 2 |
| Stripe, Inc. | Payments, subscriptions, invoices and fraud prevention | Name, email, billing address, payment method, subscription |
| Resend | Sends report, account, and Growth Operations emails; provides delivery metadata, bounces, spam complaints, and authenticated inbound replies | Recipient, account, and public business contact email addresses; email content; delivery Message-ID; bounces; spam complaints; and verified inbound reply content |
| Google LLC (Google Analytics) | Website analytics, only where you allow it (section 5) | Pages viewed, device and browser, approximate location, analytics cookie IDs; for signed-in users who allow analytics, account events our server sends (plan bought, renewed or canceled, first report sent) |
| Cloudflare, Inc. | Website delivery, DNS, security and bot protection; forwards email sent to ticketcounts.io addresses to our mailbox | IP address and request information; email sent to those addresses |
Eventbrite and Universe are not our service providers: they are the platforms you choose to connect, and their own privacy policies cover your accounts there. We use your access token only to read what the service needs. You can remove TicketCounts.io from the connected apps in your platform account settings at any time.
Your reports show your organization name, the event and its counts to the recipients you add. Otherwise we disclose personal information only when the law requires it, to protect the rights and safety of people or of the service, or as part of a merger, acquisition or sale of the business, in which case we will tell you.
We don’t sell personal information, and we don’t share it for cross-context behavioral advertising.
6.How long we keep it
We keep information only as long as we need it. The last column says what ends it: a scheduled job that deletes it automatically, something you do, a request to us, or a retention setting we configure with the provider.
| Information | Kept for | How it ends |
|---|---|---|
| Your account, profile, logos, reports and connected accounts | Until you delete your account | When you delete your account |
| Access tokens for a connected account | Until you disconnect it (the tokens are erased; the connection record stays so you can reconnect) or delete your account | When you disconnect or delete your account |
| History of report sends (recipient, time, delivery status, counts) | 13 months; test sends 30 days | Automatic |
| Growth inbound reply-correlation metadata | 90 days after processing or rejection; 30 days while awaiting a delivery record or retry | Automatic |
| Ticket count snapshots | 180 days | Automatic |
| In-app notifications | Once read, 180 days after they were created; ones with an end date, 30 days after it; others until you delete them or your account | Automatic, or when you delete them |
| Unsubscribe, bounce and spam-complaint records for your recipients | As long as the sending account exists, so opted-out people are not emailed again | When the sending account is deleted |
| Platform requests (your email address and the platform you typed) | Until you ask us to remove them | On request |
| Event records from our payment and email providers, and billing email markers | Up to 180 days | Automatic |
| Your Stripe customer ID after account deletion | 180 days, to handle late payment events | Automatic |
| Rate-limit counters (may include IP addresses) | 2 days | Automatic |
| Server logs (email addresses are masked, never full) | Only as long as needed to troubleshoot and secure the service | Our log settings |
| Google Analytics data | Up to 14 months | Our Google Analytics retention setting |
| The analytics ID stored with your account (only while analytics is on) | Until you decline or turn analytics off, or delete your account; unused after 12 months without a visit | When you decline analytics or delete your account |
| Database backups | Up to 90 days | Our backup settings |
When you delete your account in Dashboard > Account, we cancel any subscription immediately, then delete your profile, reports, connected accounts and their tokens, logos and profile photo, notifications and send history. Stripe keeps invoices and payment records as the law requires, and deleted data disappears from our backups when they expire.
7.Security
- All connections to the site use HTTPS.
- Access tokens for your ticketing accounts are encrypted in our database with AES-256-GCM, using a key kept outside the database. Your browser can never read them.
- Database rules let each account read only its own data.
- Passwords are stored only as hashes. Payment details stay with Stripe.
- Our logs mask email addresses and never record tokens or passwords.
No system is perfectly secure. If a breach affects your information, we will tell you as the law requires. More detail is on our security page.
8.Your choices and rights
Whatever the law where you live, you can:
- See or get a copy of your information: email support@elektronicgroup.com and we will send it in a common format.
- Correct it in Dashboard > Account, or by email.
- Delete your account in Dashboard > Account, or ask us by email.
- Disconnect a ticketing account in Dashboard > Integrations. You can also remove TicketCounts.io from the connected apps in your platform account.
- Stop receiving reports with the “Stop these emails” link in any report, your mail app’s unsubscribe button, or by emailing us.
- Turn analytics on or off with Cookie settings (section 5).
- Withdraw a platform request by emailing us.
We answer requests within 30 days (45 days for California requests). To protect your account, we confirm that a request comes from the email address on the account, or ask for information we already hold, before we act on it.
9.California privacy rights
This section applies to California residents and adds to the rest of this policy (California Consumer Privacy Act, as amended).
| Category | Examples | Sources | Disclosed for a business purpose to |
|---|---|---|---|
| Identifiers | Name, email address, IP address, account and platform account IDs | You, your browser, connected platforms | Our hosting, Stripe, Resend, Cloudflare; Google (where analytics is allowed) |
| Customer records | Name, email, billing details | You, Stripe | Stripe |
| Commercial information | Plan, subscription and payment history | You, Stripe | Stripe |
| Internet activity | Pages viewed, analytics events, request logs | Your browser | Cloudflare; Google (where analytics is allowed) |
| Professional information | Organization name | You | The recipients of your reports |
| Sensitive personal information | Account login (email and password); access tokens for your ticketing accounts | You, connected platforms | Our hosting only |
- We do not sell or share personal information, and have not done so in the last 12 months. We do not knowingly sell or share the information of anyone under 16. We honor Global Privacy Control signals (section 5).
- We use sensitive personal information only to provide the service and keep it secure, as the regulations allow, so the right to limit its use does not apply.
- How long we keep each category is in section 6.
You have the right to know what personal information we collect, use and disclose, and to get a copy; to delete it; to correct it; and not to be treated differently for using these rights. To make a request, email support@elektronicgroup.com with the subject “California privacy request”. We confirm receipt within 10 business days and respond within 45 days (we may extend once by 45 days and will tell you why). An authorized agent may ask for you with your signed permission; we may still ask you to confirm your identity with us directly.
10.EEA, UK and Swiss privacy rights
Elektronic Group Inc. is the controller of the information in this policy. When an account holder adds recipients and sets up reports, we process the recipients’ addresses and the report content on the account holder’s behalf; we keep the unsubscribe, bounce and complaint records ourselves so that people who opted out are not emailed again. The legal bases we rely on are in section 3.
You have the right to access, correct, delete, restrict or port your information, and to object to processing based on our legitimate interests. Where we rely on consent (analytics, platform requests), you can withdraw it at any time; that does not affect what happened before. To use these rights, email support@elektronicgroup.com. You can also complain to your data protection authority, the UK Information Commissioner’s Office, or the Swiss Federal Data Protection and Information Commissioner.
11.International transfers
Our service providers process information in the United States and other countries whose data protection laws may differ from yours. Where the law requires it, these transfers rely on safeguards such as the European Commission’s Standard Contractual Clauses (and the UK and Swiss equivalents) or the EU-U.S. Data Privacy Framework where a provider takes part in it.
12.Children
TicketCounts.io is for people aged 18 and older. We do not knowingly collect personal information from anyone under 18. If you think a child has given us information, email support@elektronicgroup.com and we will delete it.
13.Changes to this policy
We will post any change here and update the date at the top. For a material change, we will email account holders or show a notice in the app at least 30 days before it takes effect.
14.Contact
Elektronic Group Inc., Jacksonville, Florida. Email support@elektronicgroup.com. Our Terms of service explain the rules for using TicketCounts.io.