Privacy and email data

Updated October 13, 2026

Sell Timing is an independent ticket-record and resale-timing demo. It records public market observations and helps you track tickets you already own. Email sharing is optional: choose an email method or Add tickets manually. Manual profiles use a name and shared access code without any mailbox access.

Information the application uses

• Your chosen site name, saved ticket details, costs, quantities, outcomes, notes and watches.
• Session information and, when you connect Google, your Google account identifier and verified email address.
• For another email provider, your verified mailbox address and IMAP hostname. Automatic collection stores a separately generated app password encrypted on the server; a one-time ownership check does not retain it.
• Selected receipt fields such as provider, event, ticket type, quantity, amounts, notification time and any explicitly stated transaction time. The application keeps bounded, redacted supporting text and hashed identifiers for deduplication.
• Recognized Google Voice venue-announcement fields used in the background to advance public event and tier discovery. They do not enter your receipt-review screen.

Hosting and network services may process connection and security metadata. The application does not ask for your ordinary email password or your DICE or CrowdVolt password. Use only a separate provider-generated app password for non-Gmail IMAP connections.

Optional ways to import email

Connect Gmail: Google grants mailbox-wide read-only permission. The application limits message queries to supported DICE/CrowdVolt senders and, when enabled by the site operator, recognized Google Voice venue notifications used for background discovery. It makes one initial pass over the last 90 days, then checks for new messages without restarting the historical review. It also reads mailbox identity and label information needed for routing. It does not send, edit or delete mail.

Automatic collection with another provider: Supported AOL, iCloud, Fastmail and custom IMAP accounts use verified TLS and a provider-generated app password. That credential may grant broader mailbox permissions at your provider, but this application selects folders read-only and searches only supported ticket senders and enabled venue notifications. Yahoo inbox/app-password connections are disabled. No normal email password is requested.

Non-Google setup: Send one ready-made email to confirm your address; no ticket is required. The server verifies the actual sender signature and private challenge. Google sign-in, inbox permission and passwords are not requested. The next ticket-setup wizard is optional: close it to continue to Insights. Yahoo does not offer ticket-only automatic forwarding, so chosen ticket emails are forwarded manually; whole-inbox forwarding is not recommended. Native Yahoo automation needs provider approval and is not enabled.

Chosen ticket sharing: Copy the To line before opening your ticket email, then Forward, paste into To, and Send. The copied line contains your private recipient and a dedicated routing recipient; the Subject and message stay unchanged. An exact-recipient filter puts these messages in Ticket Imports and out of INBOX. The operator can read copies you send. Original forwarded receipt content remains unverified, private and approval-gated; manually forwarded offers are not automatically shared.

Selective forwarding: You choose which messages your mail provider forwards to your private import address. Those messages are delivered to a receiving Gmail account operated by the site operator. The Ticket Imports label and inbox filters separate that mail from unrelated inbox activity. The operator can access this receiving account.

Google sign-in is used for Google setup only. Non-Google selected-email setup uses the confirmation message, not Google. Providers must authenticate the confirmation with a valid signature; unsigned or forged mail cannot establish ownership. Yahoo does not support ticket-only automatic forwarding. Never forward your whole inbox to this service.

Until confirmation is approved, there is no new account. A browser-bound draft keeps encrypted profile details and a private challenge for up to 20 minutes, not a full raw message. A signed confirmation can finish signup without a ticket; account creation still requires your explicit tap. Ticket-sharing setup can then be closed and resumed later. Any received ticket remains pending until separately approved. Later sign-in does not reconnect disabled imports. Existing rules-based drafts keep their seven-day expiry. Manual signup creates a profile without email.

Source messages remain in your original email account or, for forwarding, in the receiving Gmail account according to those accounts' retention settings. The application downloads selected messages temporarily for parsing and local signature verification; it does not save another full raw-message or attachment copy in its application database. It does not load email tracking images or follow marketing links to determine a ticket price.

Review before changing your tickets

Matched paid purchases, incoming DICE transfers and CrowdVolt completed sales wait for your approval. Transfer emails may omit tier and payment details: you enter those before adding tickets, and receiving a ticket never implies it was free. Owner-entered transfer prices do not become verified purchase calibration. Free purchase receipts, donation/non-resale items, outgoing transfers, listings, payouts, refunds and cancellations do not enter review. Notification time is not exact checkout time, and expected payout is not money already paid.

Recognized receipts that cannot yet be matched retain bounded parsed fields for later automatic matching, not another full email copy. A sale without one unambiguous earlier holding is saved as a private sale amount without changing your held tickets or inventing a purchase cost. Your browser stores account-scoped receipt identifiers and revisions so choosing Later does not repeatedly reopen the same review; the receipts remain available in Insights. New receipts are checked while the page is visible, and no ticket is added without approval.

What stays private and what may be shared

Email-imported ticket records and receipt outcomes are account-scoped and do not enter the name-attributed public sale feed. Raw emails, mailbox addresses, account identifiers, credentials and private order references are not published as shared receipt evidence.

Connected email imports contribute automatically. De-identified confirmed receipt outcomes help evaluate collection coverage and calibrate this application's fee, listing and timing guidance. The calibration inputs do not include raw email text, your name, your email address or your credentials. Parameter changes require independent-event validation and can be rolled back.

Recognized non-personal announcements can contribute structured venue, event/date, drop-time and promotional-code reports. Shared titles use configured venues and public event names, not arbitrary message text. Personal or ambiguous offers stay private. A shared announcement or code is not verified availability or a guaranteed offer.

Public marketplace listings and public seller labels are separate public data. Manually recorded sale reports may appear with the chosen site display name; email-derived records are excluded from that feed.

Google data and service providers

Google provides sign-in and authorized Gmail access. Hosting and backup services support the application. Receipt contents are not sent to the application's public-data AI chat provider. Google user data is not sold, used for advertising or used to train general-purpose AI or machine-learning models.

Sell Timing's use and transfer of information received from Google APIs will adhere to the Google API Services User Data Policy, including its Limited Use requirements.

Security and account access

This is a name-and-access-code demo: unlinked profiles can be accessed by someone who knows their name and code. Linked Google profiles retain Google identity protection. Non-Google linked profiles require their name, invitation code and a fresh signed confirmation from the same email address, without inbox access or a password. Existing IMAP identities remain supported. Disconnecting imports does not remove identity protection, and confirming another email cannot bypass a previously linked Google subject. Credentials and confirmation drafts are encrypted; the receiver grant stays in restricted configuration. Private records remain owner-scoped.

Your choices, retention and deletion

• Disconnect email imports to stop application syncing and revoke the forwarding address. New email data stops contributing after disconnect. You can also remove the app in your Google account connections.
• Disconnecting an IMAP connection deletes its stored encrypted app password. Revoke the app password in your email provider's security settings as well. Previously encrypted credentials can remain in backups until backup rotation removes them.
• Remove your forwarding rule in your mail provider to stop sending new copies to the receiver. Disconnecting the app does not remove that external rule or delete source mail.
• Previously saved receipts and tickets remain until removed. Ask the site operator to access, correct or delete account/import data or forwarded source messages. Backups can retain older copies until the operator's backup rotation removes them.

For privacy or deletion requests, contact the person who supplied your site access code or the support email shown on the Google consent screen. Do not send passwords, access codes or ticket barcodes in a support request.