Seatbid Privacy Policy
Effective October 31, 2026 · Pre-launch service
Who operates Seatbid
Seatbid is operated by Michael Rofail, trading as Seatbid, based in New York, United States. Website: https://getseatbid.com. Privacy contact: seatbid.support@gmail.com.
This policy covers Seatbid's pre-launch accounts, seller applications, ticket submissions, launch list, support and operational email. Public ticket purchases remain closed. Authorized internal payment tests are separate from public ticket sales.
Information we handle
| Information | What it includes |
|---|---|
| Accounts | The identifier, email address and available display name supplied through ChatGPT sign-in. We do not collect your ChatGPT password. |
| Seller applications | Name, country, seller type, inventory description, acknowledgments and review decisions. |
| Listings | Event, venue, location, date and time zone, seat details, quantity, adjacency, restrictions, price and review status. Approved listing content can be public. |
| Launch interests | Country, interests, signup consent and subscription changes. Campaign links can also supply source, medium and campaign labels. |
| Support and operations | Messages, replies, review notes, privacy requests, security and operational audit records, and email delivery references and status. |
| Authorized payment tests | Buyer/seller references, synthetic ticket details, order amounts and status, transfer references, issue reports and Stripe payment, transfer and refund identifiers. Stripe handles payment and onboarding details on its own screens. |
| Technical information | Infrastructure providers process request information needed to operate and protect their services, which may include IP address, browser information and request/error times. Seatbid maintains account-based rate-limit counters. |
Do not put passwords, full card or bank details, identity documents or usable ticket barcodes in listings, support forms or email. Use designated provider screens and ticket-transfer services instead.
Why we use information
We use information to provide accounts, review applications and listings, maintain requested launch interests, answer support requests, send relevant operational messages, conduct authorized tests, prevent fraud and duplicate transactions, secure the service, maintain recovery records and meet applicable obligations.
Optional launch updates require the subscription choice shown on the form. Essential account, application, privacy and security messages are separate from optional launch updates. Pre-launch seller application review does not establish identity or ticket authenticity.
We do not sell personal information or use Google API information for targeted advertising. The current site does not install advertising pixels or cross-site advertising trackers.
Google and the business email connection
Seatbid connects seatbid.support@gmail.com as its business sender. Customers are not asked to connect a Gmail inbox. The website requests basic sender identity and email-sending permission, verifies the sender email, sends messages through Gmail and receives delivery/message references. It does not request Gmail inbox-reading, searching, deletion or mailbox-management permission.
Sending shares the recipient address, subject and body with Google. A message may contain relevant account, application or support information. Authorization credentials are stored in protected hosting settings; provider message identifiers and outcomes can appear in restricted operational records. Credentials are not published in pages or source code.
We use this access for Seatbid communications, not advertising profiles or general-purpose AI-model training. Authorized business personnel may separately read the business mailbox to answer messages or investigate a particular delivery or security problem. The website's send-only API permission does not provide that inbox access.
Seatbid's handling of information obtained through Google APIs will follow Google's API Services User Data Policy, including its Limited Use requirements. The business account owner can revoke the connection through Google Account settings. Revocation stops future API access; it does not erase messages already sent or other independently retained records.
Sharing and public visibility
Visitors can see approved listing information. Private application notes, account emails and support conversations are not included in the public listing response. Do not include information in listing text that you do not intend to make public.
Authorized Seatbid administrators can access information needed for account support, content review, authorized testing, privacy requests and security. Test sellers can receive the test buyer's display name and email for an authorized test order; those details are for that transaction, not unrelated marketing.
OpenAI Sites and its hosting infrastructure, including Cloudflare, support hosting, storage and sign-in. Stripe supports payment/onboarding tests. Google supports business email. Providers receive the information needed for their functions and may also handle it under their own policies and legal obligations.
We may disclose information where reasonably necessary for a valid legal requirement, security investigation, protection of users, or the establishment or defense of legal claims. A business transfer would require appropriate safeguards and notice; Google-derived information remains subject to Google's applicable restrictions, including any required consent.
Browser storage and campaign labels
Authentication and infrastructure providers may use cookies or similar technology to operate sign-in and security. Seatbid uses browser session storage for a checkout request identifier to reduce duplicate internal test requests; it is not a saved payment card. Campaign labels can be retained with a consenting launch-list signup. Canceling that subscription removes its stored preferences and campaign labels.
Retention
Our pre-launch retention schedule uses the following defaults, subject to an earlier valid deletion request or a specific, documented retention exception:
| Records | Default treatment |
|---|---|
| Active account profiles and approved applications | While actively needed for the account; eligible identifying information is removed through the closure/deletion process below. |
| Declined applications | Up to 12 months after the decision. |
| Unresolved applications | Review after 12 months without an update. We request confirmation; unnecessary application details can be deleted after 30 days without a response to a sent notice. |
| Unsold listing content | Up to 90 days after withdrawal, rejection or the event date, using the later applicable date. Records connected to a payment are reviewed separately. |
| Closed support cases and corresponding business-mail copies | Up to 12 months after closure; business mailbox cleanup is handled by the operator. |
| Routine delivery metadata and setup-test email | Up to 90 days. Mailbox copies require operator cleanup because the website has send-only access. |
| Detailed operational/security audit records | Up to 12 months, unless a specific incident or hold requires relevant records longer. |
| Stale request-rate counters | Up to 7 days after their last use. |
| Minimal privacy-request and deletion-handling records | Up to 24 months after completion, including limited identifiers needed to prevent deleted information returning through recovery. |
| Controlled recovery backups | Rolling maximum of 30 days from creation. The operator is responsible for expiration of downloaded/exported copies as well as controlled server copies. |
| Launch-list preferences and campaign labels | Until unsubscribe or deletion, or up to 12 months without an affirmative recorded interaction. Email-open tracking is not used as consent. |
Scheduled cleanup handles eligible database records and private server backup expiration. The operator reviews holds and outstanding mailbox/export tasks. Specific unresolved claims, security incidents or legal duties can require limited exceptions with restricted access and a review date. Minimal payment/test references needed for reconciliation are reviewed separately; account closure is not permission to destroy required payment records. No public sales financial-retention schedule is represented as active under this pre-launch policy.
These periods concern records Seatbid controls. Providers may retain independent records under their own policies and obligations. We do not promise a particular lifetime for provider-managed infrastructure logs or provider recovery systems that we cannot independently erase.
Access, correction, closure and deletion
Contact seatbid.support@gmail.com for access, correction or deletion requests. You can also request account deletion in My account. An account request receives an immediate acknowledgment and reference there. Email requests are monitored by Michael Rofail; we aim to acknowledge them within 5 business days and complete eligible active-system deletion within 30 calendar days of receipt. These are operating targets; applicable legal requirements take precedence.
We may verify identity proportionately using an existing signed-in account or account email. Do not send government identity documents by ordinary email. You do not need to create a new account just to send a request by email.
Deletion is reviewed before permanent changes. We remove eligible account and related information and notify or involve providers where necessary and supported. If minimal references must remain for a legitimate unresolved matter or required records, we limit their use and explain an applicable exception where required. We can retain a de-identified account placeholder linked to necessary historical records rather than retain its contact information.
Deleted information can remain in restricted recovery copies for up to 30 additional days after active-system deletion. A copy may therefore remain for approximately 60 days from a request when active deletion takes 30 days. Completed deletions are recorded separately and reapplied before an older backup returns to active use. Backups are not used to restore deleted personal information to ordinary operations.
You can update launch interests, unsubscribe and withdraw eligible listings through My account. Unsubscribing does not stop essential messages about a separate active account issue. Depending on your location and which laws apply, additional access, correction, deletion, portability, opt-out or appeal rights may apply. Contact the same email to exercise a right or ask for review of a request decision. We do not discriminate for exercising rights protected by law.
Security, age and location
We use access controls, private backup storage, protected provider credentials and review procedures to reduce unauthorized access. No online service can guarantee complete security.
Seatbid account and application features are intended for adults aged 18 or older. Contact support if you believe a child has submitted information. The operator is based in New York. Providers may process information in the United States or other countries where they operate, subject to applicable requirements; no particular data-residency location is promised.
Changes
We will post changes and an effective date, provide additional notice for material changes where appropriate or required, and obtain any required additional consent before a new use begins. Public sales would require appropriate marketplace terms and updated disclosures before activation.
Privacy contact: seatbid.support@gmail.com.