TCG-LB
A practical overview of the data used to run accounts, collections and the marketplace.
We store your account ID, profile details you enter, linked wallet address, and account creation and sign-in timestamps. Email or phone availability depends on how you register. Admin tools can display linked social methods and contact details returned by thirdweb. We do not request your social friends list or posts.
We store the cards, quantities, cost, estimates and notes you add. Profile and item visibility settings control publication. Public information can include your username, city, bio, displayed cards and asking prices. Cost and private notes are excluded from that public view. Card scanning processes the image in your browser; extracted search text is sent to find catalog matches.
Front and back photos are required to put a card up for sale, and are uploaded only when you take or choose one: that is your consent. Location and camera metadata is stripped before a private copy is stored in Supabase. Public access follows item/profile visibility and moderation. Images are saved with offers when sent and their escrow orders, and remain available to participants and named administrators after removal from the current item. Removal hides the image from the current display; deletion of retained files requires an agreement/dispute review. Retained images and reserved upload attempts count toward storage limits.
We store offers, messages, orders, payment and delivery status, and recipient details needed to fulfill an order. Sellers see delivery details for their orders. Messages are available to participants; moderation tools can expose message evidence associated with reports. Account support requests and team responses are private to the account holder and admins. Do not include secrets or identity documents in a request.
We store each case’s subject, category, status and messages, linked to your account and any store ownership application. Only the account holder and authorized named administrators can read the conversation. Internal staff notes and store-verification evidence are restricted to administrators. Decisions record the operator in the audit history. Conversations and their history may remain after account closure; a review determines what can be removed.
We save private account notifications about offer, order and escrow updates, including related record IDs, event times and the time you mark them read. Private messages and delivery addresses are not copied into that history. Notifications appear in the app; email and push notifications are not sent. Admin job monitoring records only timing, status and counts; records older than 30 days are cleaned up on the next job run.
Supabase stores account and marketplace data. thirdweb provides social sign-in, wallets and blockchain services. Render hosts the app. Cookies and sessions support sign-in and language; browser storage supports wallet state and network preference. Card search, images and prices may use external catalog providers. Wallet addresses and transactions recorded on a blockchain are public.
You can edit your profile and visibility, and export your collection from My collection. For a broader copy, another correction or closure, submit a private request from Account security & data. The team reviews ownership, open orders, disputes and wallet funds before acting. There is no automatic deletion or published universal retention period today. Order, counterpart, audit and support records may remain after closure; the team should explain what will be retained and why. We cannot erase blockchain records.