Privacy Policy

This page is prepared for review by the TIXVOW owner and qualified legal counsel. It is not attorney-approved, legal advice, or a legal certification. The operating legal entity, service territories, applicable privacy contacts, and jurisdiction-specific notices must be confirmed before publication.

Account information includes a name, email address, authentication and session information, and information submitted to sign up. Buyer profiles can contain phone number, city, saved interests, event preferences, promotional email preference, personalized recommendation setting, Use My City setting, and Encore Alerts setting.

Ticketing records can include event and ticket selections, attendee name and contact details, order amounts and itemized pricing, discounts, fees, taxes, payment and fulfillment status, receipt information, terms version and acceptance time, ticket transfers, check-in or ticket-use status, refund requests and statuses, and event communications. Organizers and venues submit business and event information, contact details, venue addresses, accessibility details, and public-profile information. Venue profile controls include choices about displaying selected public fields.

The app records the version and time of account-level Terms acceptance and separately records the Terms version, time, and source for a ticket checkout. It also stores promotional consent and delivery records used by communication features.

The app makes paid-order and attendee details for an organizer’s own events available through organizer attendee tools. The returned fields include order and attendee names and contact details, ticket selections, order/payment status, and ticket-use or check-in status. Authorized event staff assignments can use scanning flows that return limited event and ticket information needed for check-in. Approved venue members can access event and zone information associated with their venue workspace.

These product access scopes do not establish the parties’ legal privacy roles or a complete permitted-use, retention, deletion, or security schedule. The owner and qualified counsel must confirm those responsibilities and any organizer agreement disclosures before this draft is final.

TIXVOW uses account and order data to provide account access, event discovery, ticket reservations and purchases, payment handoff, receipts, ticket delivery and transfer, event check-in, account recovery, customer-support and refund workflows, event changes, and required transactional communications.

Buyer preferences are used for the selected product features. Saved interests and event preferences, saved events, and events with a verified door check-in can contribute category tokens for personalized event ranking. A ticket purchase by itself is not treated as attendance. When Use My City is enabled, the buyer profile city can move matching same-city events higher in the recommendation order; the reviewed AI prompt does not include that city.

Promotional email preference currently initializes as enabled for new buyer profiles and can be turned off in the buyer profile. Promotional messages are checked against current preference before delivery. Ticket, account, event-change, cancellation, refund, security, and recovery messages use separate transactional workflows. The owner and counsel must review the current promotional default and its notice and consent basis.

For personalized event ranking, the app can send saved category tokens and selected public event facts—such as event identifiers, title, description, date, venue name, category, ticket type, and listed price—to the Polsia AI proxy. The proxy returns a ranking of eligible public events. Saved interests and event preferences, saved events, and events with a verified door check-in can contribute category tokens; a ticket purchase by itself is not treated as attendance. The profile has a control to disable personalized recommendations. The AI request contains category tokens and candidate public event facts, not a raw browsing-history feed.

When an organizer uses the broadcast copilot, the app sends the organizer’s campaign goal, selection hints, and an aggregate event and ticket catalog to the Polsia AI proxy to create an editable draft. The draft is stored in the app and remains subject to organizer review and the separate send workflow.

The current app code does not establish whether Polsia or underlying model providers retain AI inputs, disclose them to further providers, or use them to train or improve AI systems. It also does not establish retention periods or a separate AI-data opt-out for the broadcast copilot. TIXVOW makes no claim that training or improvement use does or does not occur until the owner verifies provider practices and qualified counsel reviews the disclosure. AI output can be incomplete or unsuitable and is not a substitute for human review.

The current “Events Near You” discovery flow can request the browser’s geolocation permission. If permission is granted, the app sends latitude and longitude with the event-discovery request to find nearby events. If permission is denied or unavailable, discovery proceeds without those coordinates. This browser-permission flow is separate from IP-derived location.

The app also stores a city in the buyer profile when supplied. When Use My City is enabled, the app uses that city for local recommendation ranking. The reviewed recommendation prompt does not send the profile city to the AI ranking service.

The current app code does not derive approximate location from IP addresses. If and when IP-derived location is introduced, the planned disclosure is that it estimates city or region only, never precise coordinates, for Events Near You recommendations and regional Promoted Event placements, and is kept separate from an identifiable browsing-history record. The source, actual fields, storage, retention, and user controls must be verified before enabling that feature.

On page loads, the app stores a persistent visitor identifier in browser local storage and sends a beacon containing the TIXVOW app slug and that identifier to Polsia. The app also records daily event counters, such as event views, saves, and shares, without attaching that visitor identifier in the application counter records. The app does not establish beacon retention, platform-side association, or other Polsia analytics processing.

For ticket-lookup abuse prevention, the app reads a request-source IP value from forwarding headers and hashes it into the lookup rate-limit record. If the optional anti-abuse challenge is enabled, the request-source address is also passed to the challenge verifier. The app does not establish a general application-log retention period or all infrastructure-level IP handling.

The app uses Polsia platform services for email delivery, AI requests, and the analytics beacon. Paid checkout hands buyers to a hosted third-party payment flow. Optional anti-abuse verification may be used for ticket lookup. Event, ticket, account, or venue information is processed by the services needed to perform the requested feature.

The checkout does not establish the identity, location, retention, onward disclosures, or independent practices of the underlying email, AI, payment, analytics, hosting, or verification providers. Those provider contracts and roles must be confirmed by the owner. This draft does not describe unverified provider practices or promise that data is never shared, sold, or used by a provider for other purposes.

The app stores account, order, ticket, consent, event, and operational records needed by its current workflows. This repository does not establish a complete retention schedule, account-deletion process, backup lifecycle, or infrastructure-log deletion period. No specific deletion period or completion time is promised here; the owner and counsel must define what applies and update this notice.

Buyers can update profile information and separately change promotional email, recommendation, Use My City, and Encore Alerts settings in the buyer profile. Browser geolocation is controlled by the browser’s permission settings and can be denied. Venue users can control selected public-profile display fields through venue profile settings. Transactional messages for an order, account, or event workflow are separate from promotional email preferences.

This draft does not determine privacy rights, request procedures, response times, or compliance obligations for every service territory. The owner and counsel must add any required notices and request methods for the locations where TIXVOW operates.

Paid Promoted Events are not implemented in the current app code. If introduced, the planned feature would let an organizer pay for a fixed time window of boosted placement in listings, search, and post-checkout “near you” recommendations. Promotion would affect placement only, never the price, availability, or terms of tickets already purchased; placement would return to normal automatically when the paid window ends. The owner must confirm the actual fees, regions, duration, ranking treatment, and data practices before launch.

For general questions, the company contact address supplied for this app is tixvow@polsia.app. The owner must confirm whether this is also the correct address for formal privacy requests and legal notices. Provider retention and onward use, analytics beacon processing, AI training or improvement use, account deletion, operational log retention, service territories, and required privacy rights language remain for owner and qualified counsel review.