Ticketing Audit, Retention, and Data Protection
Understand ticketing audit history, setup audit, buyer lookup privacy, secure tokens, data exports, and ticket order retention reviews.
Article guidance
Ticketing contains buyer details, attendee details, answers, order links, QR credentials, refund records, dispute records, check-in history, and finance records. SmartGig therefore records important changes and protects public access with secure tokens and rate limits.
Setup audit
The setup page includes a searchable setup audit panel. It is useful when a ticket type, schedule, promo code, rule, question, policy, visibility setting, or setup value looks different and you need to know what changed.
Event audit
- The event-level Audit page can search and filter setup, order, ticket, gate check-in, refund, transaction, and token-related audit entries.
- Audit entries can be exported as CSV for review.
- Manual order creation, payment links, order notes, refunds, cancellations, ticket lifecycle actions, gate check-ins, overrides, and order access-token rotations are written to central audit history.
Buyer privacy and secure access
- Public order lookup uses a neutral response so it does not reveal whether an email address has an order.
- Lookup attempts, misses, rate limits, and sent links are audited without storing the raw lookup email in audit details.
- Public quote, checkout, payment retry, and payment confirmation paths have additional rate limits.
- Order access links use secure tokens that can be rotated or revoked.
- Ticket downloads and mobile tickets are tied to secure order access.
Retention and exports
- Tenant data exports include ticketing setup, orders, order items, issued tickets, buyer and attendee answers, reservations, refunds, disputes, transactions, check-ins, and order access tokens.
- Account data-retention review can flag old closed ticket orders for owner approval.
- Approval anonymizes buyer, attendee, answer, order-token, notification, communication, and generated ticket-document PII while preserving finance/order history.
- Generated ticketing report CSV files can be flagged for retention review and deleted from file storage while preserving expired export history.