YOUR DATA, EXPLAINED
Privacy & data protection.
We use the data needed to run your queue, keep buyers informed, and support your account. We do not sell personal data or use order data for advertising.
Updated October 21, 2026 · General policy version 2026-10-21 · Shopify processing terms remain version 2026-10-07
What QLive uses
QLive is operated by the team behind Rip Goats Card Shop, LLC. We use your account email and authentication information to sign you in and support your account. Supabase provides authentication; Google and Discord process sign-in through their own services if you choose them. We do not receive your Google or Discord password.
We store the profile, logo, social links, stream links, queue settings, buyer handles, optional item descriptions, and timestamps you choose to add. Your published profile, active buyer queue, and OBS link are public to anyone with the link. Queue links are not private passwords. Public queue responses show buyer labels, position, source platform, and status; item descriptions and stream history stay in the seller workspace.
Cloudflare provides hosting and storage. These providers process data to operate QLive and may process technical connection information for security and reliability. QLive uses essential sign-in cookies. We do not use marketplace order data for marketing, profiling, or decisions with legal or similarly significant effects.
Buyer handles, follows, and turn alerts
If you save buyer preferences, we store your chosen platform handles, followed streamers, and alert settings privately with your QLive account. These handles are self-entered preferences, not verified marketplace identities. You can remove saved handles and unfollow streamers in My buyer hub. Your account data download includes these preferences and follows.
Guest queue tracking, per-show alert choices, and duplicate-alert markers are stored in browser session storage for that tab. Stop following a queue to disable its tracking; closing the tab ends this guest session. On-page and optional sound alerts work while the queue is open and receiving updates. Optional go-live alerts are saved separately for each followed streamer and appear as in-app notifications while QLive is open. Alerts begin with future shows after you opt in; they are not phone push notifications. Browser-local markers prevent repeating a show alert across visits in the same browser. We do not collect phone numbers or send SMS, email, or device push notifications for these features.
A short-lived essential cookie remembers a buyer page during sign-in so you can return to it afterward. Your saved handles and following list are not added to the public queue or shared with streamers.
eBay integration
Sellers authorize their own eBay account through eBay. QLive stores encrypted authorization tokens, connection information, import settings, and a keyed seller-account fingerprint. Access remains limited to approved QLive pilot accounts.
Order APIs can return a broad response. QLive retains the limited queue information it needs: order identifiers for duplicate protection, buyer username, matching item titles and quantities, and purchase/import timestamps. Payment, cancellation, purchase-format, and listing information are checked to decide eligibility. Full order responses, shipping addresses, contact details, and financial breakdowns are not saved as queue records.
Imported usernames are public on buyer displays and OBS overlays. Item details, order references, purchase timestamps, and saved stream history stay in the authenticated seller workspace. Sellers must review the display notice before starting imports and avoid showing labels contrary to an applicable buyer privacy choice.
The pilot uses seller-selected title phrases, listing IDs, or all qualifying paid purchases during the show window. It does not verify eBay Live origin. Matching ordinary-store purchases may enter too. No marketplace payment, refund, cancellation, or shipping action is performed by importing or skipping a queue entry.
Retention and removal
Imported eBay queue records remain with saved show history until removed through a verified deletion request or applicable eBay account-deletion processing. Stopping imports preserves records. Disconnecting removes the stored seller authorization and pending authorization state; it does not by itself erase saved eBay queue history. Use a privacy request for that removal.
QLive validates eBay account-deletion notices and removes matching seller connection and imported-order records. When the notice supplies a buyer username, matching eBay queue entries are removed. Minimal keyed account/username fingerprints prevent matching deleted accounts from being re-imported. These markers have no automatic expiry at present; they do not retain the original username or account identifier. Pending notices are encrypted until processed, then deleted. Provider backups follow the recovery handling described below.
Shopify integration
The Shopify integration is in development. Connecting requires merchant authorization and acceptance of this policy and the Shopify data-processing terms below. Shopify approval and live testing are separate steps; this page does not mean Shopify has approved the app.
Only the order details needed for live rips
- Shop domain and order ID/number, to identify the store and avoid duplicate imports.
- Item titles, variant titles, product/variant identifiers and quantities, to identify eligible live-rip items and show the seller what to open. Product catalog titles and identifiers are read when the seller browses products to configure import rules.
- Order creation/update and successful payment timestamps, plus payment/cancellation status, to import eligible paid orders in sequence.
- Order tags and seller-selected title phrases/products/variants, to filter live-rip purchases.
- Encrypted authorization tokens, to access the store on the merchant’s behalf.
Our order queries do not request customer names, emails, phone numbers, shipping or billing addresses, IP addresses, geolocation, or browser/device information. The public buyer label is an order number, such as #1042. Shopify uses broad permission categories for order access; the wording on its authorization screen may describe more than the fields QLive requests.
Shopify’s required privacy notices may include customer contact fields in a webhook payload. QLive discards those fields without storing them and uses only the shop and order identifiers necessary to export or remove the requested records. No full order/customer webhook payloads are saved.
How the data is used
We use it only to collect qualifying live-rip items from paid orders, manage the show queue, display order numbers and estimated waits, maintain limited stream history, and respond to privacy requests. Estimates are approximate. QLive does not use this data to contact buyers, sell data, build advertising audiences, or make consequential automated decisions.
Retention and removal
- Import inbox: up to 90 days from the order’s creation.
- Imported Shopify queue entries: up to 365 days from the order’s creation, including stream history.
- Privacy export files: up to 30 days. Support requests: up to 90 days.
- Minimal hashed order markers used to prevent removed orders from being imported again: up to 365 days, or until the store is disconnected.
Expiry is enforced when QLive serves requests, before queue and order records are returned. Expired records are removed during these requests; an inactive site may retain records in storage until its next request. Encrypted provider backups may retain previous copies for the provider’s normal recovery period. Restored data must be subjected to the same expiry and removal controls before use.
Disconnecting Shopify or receiving a valid uninstall/store-redaction notice removes its authorization tokens, imported inbox records, and Shopify entries from active queues and saved streams. Your manually entered orders and branding remain. A merchant can remove a specific order in Integrations; removal also blocks re-import during the marker’s retention period.
Shopify data-processing terms
The merchant determines which orders to import and is responsible for lawful processing, buyer notices, applicable consent decisions, and whether an order number can be shown publicly. QLive processes these limited records on the merchant’s instructions to provide the service. Do not import an order when a buyer’s applicable privacy choice prevents that processing. Remove an already imported order when needed.
QLive limits access to authorized accounts, uses HTTPS, encrypts database storage through Cloudflare, and additionally encrypts integration tokens and support/export payloads. Cloudflare and Supabase are service providers; data may be processed in the countries where they operate. QLive will assist with verified access, correction, deletion, and withdrawal requests, and notify affected merchants of confirmed security incidents without undue delay. Contact us if you need additional transfer or processing terms before connecting.
We do not disclose Shopify customer records to unrelated merchants. Merchants can download their records in Account settings and retrieve Shopify-requested exports privately. Privacy requests received from Shopify are authenticated; customer/store redaction is applied to matching order records. The required subscriptions must still be configured and tested before public Shopify rollout.
TikTok Shop integration
TikTok Shop authorization is available only to the configured QLive testing account and development shop. Automatic order importing is not enabled. Creating our partner app or listing permissions does not connect a seller’s shop.
Connection data and purpose
When the tester chooses to connect and authorizes QLive through TikTok, QLive exchanges the authorization code for access and refresh tokens, reads the authorized shop’s ID, name, region and seller type, and verifies that it is the configured US local development shop. We store the shop ID, shop name, connection timestamp and encrypted tokens, token expiry times, shop cipher and granted scopes to maintain that test connection. Authorization state is tied to the signed-in account, is single use and expires after ten minutes. Authorization codes are not saved in our connection records.
This authorization step does not retrieve orders, create public queue entries or enable syncing. After connecting, the tester can explicitly read a configured sandbox orders. TikTok’s order-detail API returns a broad response, which may include buyer contact, address and financial information. QLive immediately projects only the order ID, current status, selected product title and payment timestamp for this private test, discards the other fields, and does not log or store the order response. Test results remain in the page’s temporary state until it is refreshed or closed. No public queue entries are created by this read test. Tokens are used only on the server and are additionally encrypted before database storage. Connection records are accessible only through the authorized account’s integration controls. Cloudflare provides hosting and storage as described above.
The tester may separately choose to add a configured sandbox order to their show queue after accepting the import notice. This saves the shop and order identifiers, selected item title, a bounded safe buyer_nickname from the order-detail response when available (otherwise an order-number buyer label), import timestamp and a minimal Auction or Unknown classification from TikTok’s order_type field. The classification is displayed only in the seller workspace. The nickname or order-number fallback is visible on the public buyer queue and OBS overlay, can be searched by viewers, and is retained with that imported entry. A nickname is a display name, not a verified unique handle or proof of QLive account ownership. We do not use opaque TikTok buyer IDs for the public label, automatically link them to QLive accounts, or combine separate purchases by nickname. Missing, malformed, unsafe or overlength nicknames use the order-number fallback; shipping names and contact details are never substituted. Existing entries are not rewritten. A minimal import marker prevents the same order from being added again after completion or removal. These test entries and markers remain until the shop is disconnected or a verified deletion request is fulfilled; disconnecting deletes TikTok entries from active queues and saved streams, queue undo snapshots and the import markers.
The tester can also explicitly check purchase-format information. QLive reads the two configured comparison products through the Product API and inspects only selling-format values in the order, selected items and product. These limited observations are displayed temporarily, are not logged or saved, and do not classify the purchase or change the queue. A product’s current configuration may differ from how an earlier order was purchased.
Retention and disconnection
Connection records remain while the test shop is connected. Disconnect from the TikTok setup page to delete its stored tokens, shop metadata and pending authorization states from QLive. Also remove QLive’s authorization in TikTok Shop Seller Center to revoke access at TikTok. Disconnecting QLive does not itself revoke authorization at TikTok. Provider backups may retain previous encrypted copies for their normal recovery period; removal must be reapplied before restored records are used. Contact us below for verified access, correction or deletion requests.
The read-only purchase-format diagnostic also searches a two-second creation window through Get Order List to locate the selected configured sandbox order. Other returned orders are discarded without logging, displaying or saving them. Only bounded purchase-type observations for the selected order and matching items are displayed. This test does not import orders or change their status.
Planned order testing
We plan to read the limited order information needed to identify qualifying paid live-rip purchases, avoid duplicate imports and keep the seller’s queue consistent with cancellations. The sandbox-order read test is described above. Before enabling broader order reads or imports, we will document the actual fields, retention and removal controls. We will not assume that TikTok provides a buyer’s username or livestream identifier. QLive does not sell marketplace data or use it for advertising. Do not send app secrets, tokens, passwords or payment information through the contact form.
Profile options and serving-time estimates
Featured links, announcements, schedules, and next-show dates are information you choose to publish. A first saved profile handle publishes the profile; Account settings lets you unpublish it. Existing unpublished profiles stay hidden when edited. Unpublishing a profile does not make previously shared buyer or OBS queue links private.
QLive records active serving duration and completion time as you use queue controls. Optional learned estimates use a seller’s own recent completed orders from ended shows, excluding paused time and unusable, skipped, or undone samples. The calculation considers up to 50 eligible completions from the last 90 days and needs at least five. That window limits the calculation; it is not a separate deletion schedule for stream history. Manual averages remain the fallback. This estimates queue waits, not a buyer’s behavior or value.
Billing & rewards currently describes planned features. QLive does not collect payment-card details there, redeem codes, issue referral credits, or charge subscriptions. We will explain additional billing data and service providers before those features launch.
Your choices & privacy requests
Edit or unpublish your profile, stop importing orders, disconnect an integration, or download your workspace data. Manual queue and profile data stay while needed for your account and stream history; you can request their deletion through our contact form. Authentication-account deletion and provider-held records are handled separately after identity verification.
Buyers: contact the streamer first, or send QLive a privacy request with the store/queue link and order number. Do not send a payment card, password, access token, or full shipping address. We verify the request with the merchant before disclosing or removing records. We aim to complete verified privacy requests within 30 days, subject to applicable law.
Support-form information is used only to answer your request. It is encrypted and restricted to QLive support, and removed after 90 days. A short-lived keyed fingerprint helps limit spam; the form does not store your raw IP address.
Send a privacy requestOther integrations & updates
Other marketplace integrations have separate availability and permissions. We will add platform-specific details here as they are implemented; planned integrations do not receive data merely because they appear on the site. Material changes will be communicated in QLive, and changed Shopify processing terms require renewed acceptance before further imports.