Privacy Policy

TicketDesk is a ticket resale operations management application used to organize events, ticket inventory, purchases, sales, documents, financial records and related operational workflows. TicketDesk is an operations tool and is not a ticket marketplace or an affiliate of third-party ticketing services.

Depending on the features a user chooses to use, TicketDesk processes account information and operational records entered or imported into the workspace. These may include event and inventory details, purchase and sale information, expenses, documents, and team or fan-card operational information.

Some fields and features are optional. TicketDesk processes them only when they are supplied or enabled by an authorized user.

TicketDesk can connect supported third-party services, including Google Gmail and Google Drive, only when a user explicitly starts and authorizes the connection. Those services remain governed by their own terms and privacy practices. Their availability does not imply endorsement of or affiliation with TicketDesk.

When a user connects Gmail, TicketDesk requests the read-only gmail.readonly permission. It reads mailbox profile information and searches for messages likely to contain ticket-related purchase, booking, order or sales information. Relevant message headers and content are retrieved so the Automation Center can identify operational information and create structured, reviewable candidates.

• TicketDesk does not use this permission to send email.
• TicketDesk does not delete email.
• TicketDesk does not modify the connected Gmail mailbox.
• Automation output remains review-oriented and does not independently complete financial actions.

TicketDesk's use and transfer to any other app of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements.

Google user data is not sold, used for advertising or personalized advertising, transferred to data brokers, or used to determine creditworthiness.

Google data is used to connect an authorized mailbox, identify relevant operational messages, parse operational information, create reviewable TicketDesk automation candidates, and associate user-approved information with TicketDesk workflows.

OAuth credentials, message information and parsed operational records serve different purposes and are stored separately. Gmail attachments are not imported by the current mailbox synchronization process.

TicketDesk stores the connected account identifier, granted scope, synchronization position and an encrypted refresh token so authorized synchronization can continue. Refresh tokens are encrypted by the application before storage and are available only to protected server-side processes.

For messages that match conservative ticket-related discovery rules, TicketDesk persists the provider message and thread identifiers, sender, recipients, subject, received date, and the relevant plain-text and HTML message bodies. This means raw content from relevant emails is persisted. A content fingerprint and processing status are also stored. Attachments are excluded.

Google user data is not routinely read by people. Human access is limited to circumstances permitted by applicable Google policy, such as when the user affirmatively requests support involving specific data, when necessary to investigate security or abuse, when required by law, or in another policy-permitted circumstance.

TicketDesk uses infrastructure and service providers needed to authenticate users, store application information, process authorized integrations and operate the service. These providers may process data only as necessary to deliver those functions. This operational processing is distinct from selling data. TicketDesk does not sell Google user data.

TicketDesk backup functionality can store user-requested TicketDesk backup archives in an authorized Google Drive account. It requests the drive.file scope, which allows TicketDesk to create and work with files and folders created or opened through the application rather than requesting general access to all Drive content.

The integration creates or reuses a “TicketDesk Backups” folder and uploads requested backup archives to it.

TicketDesk records are retained as necessary to provide the service and until they are removed through available application controls or otherwise deleted. The current system does not apply a general fixed automatic deletion period.

Google OAuth credentials remain until the integration is disconnected, replaced or otherwise removed. Disconnecting an integration does not automatically delete previously created TicketDesk candidates, parsed information, audit records or other operational records.

Authorized users can disconnect Gmail and Google Drive from TicketDesk. Gmail disconnect attempts to revoke the Google refresh token, removes the stored credential and disables the mailbox connection even if remote revocation is unavailable. Drive disconnect removes the stored TicketDesk Drive credential and folder connection information.

Future TicketDesk API access stops after the stored credential is removed. Users can also revoke third-party access from their Google Account. Previously created TicketDesk records are retained unless separately deleted.

TicketDesk provides record-level deletion controls for supported operational records such as tickets, documents, teams, fan cards, AMKA records, loans and expenses, subject to the user's role and existing application rules. Connected-service credentials can be removed through the relevant disconnect controls.

The current product does not provide a complete self-service account-deletion workflow. Requests beyond the available in-app controls require a verified TicketDesk contact method, which has not yet been published.

TicketDesk uses authenticated access, workspace access controls, server-side credential handling and application-level authenticated encryption for stored Google refresh tokens. Access to credential tables is restricted from browser roles. No system can guarantee absolute security, and TicketDesk reviews its safeguards as the service changes.

TicketDesk is a professional operations application and is not directed to children.

This policy may be updated when TicketDesk functionality or data practices change. Material changes to the use of Google user data will be reflected in the published policy and handled consistently with applicable authorization and consent requirements. Google data will not be silently repurposed for unrelated uses.

For privacy questions, data requests or questions about connected Google services, contact TicketDesk at billpsem@gmail.com.