Phoenix, AZHow this worksTerms
SeatResale

Privacy

Last updated 2026-08-24. This describes what seatresale.com actually does today, not what a template says a website might do.

What we collect

No accounts. No sign-up. No personal information requested. There is nothing on this site to fill in.

Our web server keeps ordinary request logs — IP address, timestamp, page requested, browser user-agent — as any web server does. We use them to keep the site running and to investigate faults. We do not use them to build a profile of you.

Cookies and tracking

We set no cookies and run no analytics, advertising or tracking scripts. If that changes we will say so here before it does, and where consent is required we will ask for it.

Third-party content

Event artwork is served from the ticketing provider’s image servers rather than copied onto ours. Loading a page that shows one of those images means your browser makes a request to that provider, and that provider can see that request — including your IP address and the page you were on. That is how images on the web work; we mention it because you should know it is happening.

When you follow a link to a seller or venue, you leave this site. What they collect is governed by their privacy policy, not ours.

What we do not do

Your rights

Depending on where you live you may have the right to ask what personal information an operator holds about you, and to have it deleted. Because we hold no personal information beyond short-lived server logs, in practice there is little to return or erase — but you can ask, and we will answer honestly.

Children

This site is not directed at children under 13 and we knowingly collect no information from them.

Contact

Questions about this page, or a request about your data: support@seatresale.com. We answer data requests within 30 days, and content-removal requests within 24 hours.

Why this page is short. Most privacy policies are long because the site does a lot with your data. This one does almost nothing with it, so a long policy would be padding — and a policy that describes tracking we do not run would be a false statement in the one document where accuracy matters most.