Privacy policy

Last updated 14 August 2026.

TicketHub is a mobile app that finds the event tickets already sitting in your email and collects them in one place. To do that it reads your mailbox, which means this policy needs to be specific rather than reassuring. It covers both the app and the waitlist on this website.

The short version

We read messages from the ticket sellers you nominate, pull out the event details, and store those. We never store the body of your emails. We don't sell anything to anyone, we don't run ad trackers, and you can disconnect a mailbox at any time.

What we access in your mailbox

When you connect a mailbox, the only mail permission you grant is read-only — gmail.readonly for Google, Mail.Read for Microsoft. Neither permits sending, deleting, or modifying anything. We cannot change your mail, and we cannot act as you.

The consent screen asks for two other things alongside it: openid and email. Neither carries any mail access. They return a stable account identifier and the address of the mailbox you are connecting, which is how we tell your mailboxes apart and label them in the app.

We look at the sender and subject of your messages to decide which ones might be tickets. We only open the body of a message when it comes from a ticket seller you have nominated — Ticketmaster, Eventbrite, and so on. Personal correspondence is never opened.

What we store, and what we don't

For every message we consider, we keep a small record: the sender's address, the subject line, when it arrived, and a link back to the message in your own mailbox. This is what stops us processing the same email twice.

When a message is a ticket, we store what the ticket is: seller, event, date, venue and address, seats, quantity, order number, and price. We also keep the seller's own links out of that email — the "View tickets" or "Add to wallet" buttons — stored exactly as the seller issued them, so the app can hand you straight back to them. If the email carries a ticket attachment, we store that file so you can open it without going back to your inbox.

We do not store the body of your emails. Message bodies are fetched when needed and discarded; your mail provider stays the only place your mail lives. This is a deliberate design decision in how the system is built, not a policy we could quietly change our minds about.

Who else sees this data

Reading a ticket confirmation and understanding it well enough to pull out a seat number is done by an AI model. We use Anthropic's Claude API for this, which means the text of a candidate ticket email is sent to Anthropic to be processed. Under their commercial terms, Anthropic does not use data submitted through their API to train their models, and deletes it within 30 days — apart from anything their abuse-detection process flags, which they may hold longer.

Three other providers hold data on our behalf:

• Convex — our database and backend, which stores everything described above.
• Clerk — handles signing in, and holds your account identity.
• Expo — delivers reminder notifications to your phone. A reminder names the event and when it starts, so that much leaves our systems each time one is sent.

That is the complete list. We do not sell your data, rent it, share it with data brokers, or hand it to advertisers. There are no ad trackers or analytics cookies on this website.

How we use Google user data

TicketHub's use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements.

Specifically, data obtained from Gmail is used only to:

• identify emails from ticket sellers you have nominated;
• extract the details of tickets you have bought, and present them back to you in the app.

It is not used for advertising, not sold or transferred to anyone except as described above, not used to train or improve any generalised AI or machine learning model, and not read by a human except where you have explicitly asked us to help with a support problem, or where the law requires it.

Turning it off

Disconnect any mailbox in the app under Account. Access stops immediately, and the tickets we already found stay in your account.

You can also revoke access directly with the provider:

• Google — myaccount.google.com/permissions
• Microsoft — account.live.com/consent/Manage

How long we keep it

Disconnecting a mailbox deletes its access tokens and the message records we kept for it. The tickets already found stay in your account — they are yours, and they stay useful after the mailbox is gone. Ticket records stay until you delete them.

You can delete your account entirely, in the app at Profile → Delete account — this happens immediately — or at tickethub.damondoesapps.com/delete-account if you have uninstalled, which is actioned within 30 days. Deleting removes your account and profile, your tickets, connected mailboxes and the OAuth access granted with them — withdrawn at Google and Microsoft, not merely forgotten here — stored ticket attachments, extracted email records, notification tokens, scheduled reminders, and any launch-list signup under the same address.

Two things survive a deletion, deliberately: day-level totals of automated processing costs, aggregated with no link to any person; and a record that the deletion took place, holding a one-way hash of your address rather than the address itself, so the request can be shown to have been honoured.

What we cannot reach: calendar events already added to your own Google Calendar. Withdrawing our access removes our ability to delete them — remove them directly in Google Calendar.

Waitlist email addresses are kept until the product launches and the waitlist has served its purpose, or until you ask us to remove yours — whichever comes first.

The waitlist on this site

If you sign up on this page, we store the email address you type in and nothing else. We use it to invite you to test TicketHub and to tell you when it launches. No newsletter, no drip campaign. Our hosting provider logs basic technical data such as IP addresses for every request, as almost every website does; we don't connect that to your email or use it for anything but keeping the site up.

Security

Mailbox access tokens are never sent to the app on your phone. They stay in the backend, every mailbox fetch happens server-side, and the app itself has no way to read your mail directly. They are held in our Convex database, which Convex encrypts at rest with 256-bit AES; we do not add a second layer of our own encryption on top of that. All traffic is over HTTPS. Access to production systems is limited to the developer.

Children

TicketHub is not intended for children under 13, and we don't knowingly collect their data.

Changes

If we change what we collect or who we share it with, we'll update this page and the date at the top. Material changes will be surfaced in the app rather than left here to be discovered.

Contact

Questions, deletion requests, or anything else — privacy@damondoesapps.com.