Trading Card Data

Privacy notice

Updated September 23, 2026

FA Applications LLC, 411 SE Mizner Blvd Ste 72 MHS 1203, Boca Raton, FL 33432, United States, operates Trading Card Data and is responsible for the personal information described in this notice. Contact support@tradingcarddata.com about privacy questions or requests.

Trading Card Data uses Clerk for account authentication, Stripe for payment processing and, as reseller of memberships, tax calculation, Vercel for website hosting, and Railway for the research service. Supabase supports creator-content search and may process the search query needed to retrieve relevant content. Your chosen AI assistant independently processes your conversation under its own policies.

When your assistant calls a tool, we receive the tool name and arguments it sends, an authorization token, and identifiers needed to verify your account and the requesting application. This can include card names, searches, filters, and saved research settings. We do not need your full conversation to execute a tool. Avoid sending confidential information in research searches.

We maintain account-access status, subscription and customer references, payment-event receipts, usage counts, optional alerts and indexes, and service analytics such as tool name, time, outcome, selected research dimensions, and duration. Stripe handles payment-card information; the research application's billing database stores subscription references and state, not full payment-card details. Clerk handles sign-in data and may provide verified email information for account authorization.

Search-text retention is off by default in our research analytics. You can opt in through the privacy-settings tool. If enabled, selected search text is redacted and shortened before storage, and scheduled for removal after 30 days. Service analytics events are scheduled for deletion after 90 days; feedback after 30 days. Monthly quota counters are retained separately for approximately 13 months. These periods describe the application database, not independent AI-assistant histories or provider security logs and backups.

We process information to provide access, execute research, enforce limits, manage billing, diagnose failures, and respond to support and security issues. Relevant tool results return to your assistant. Hosting, authentication, payment, and data providers receive the information required for their respective functions. Following an external product link may disclose request and referral information to that destination.

Use account_usage to inspect optional search-text retention, privacy_settings to change it, and delete_research_history to delete research analytics history. The current history-deletion action also removes saved custom indexes; it does not cancel your subscription, remove saved alert rules, or erase billing/access records and quota counters. Contact support for an account-level access, correction, export, or deletion request. We may retain records needed for billing, disputes, legal obligations, and security. Identity verification may be required before acting on a request.

Website sign-in uses browser session storage and authentication providers may use their own cookies or browser storage. Hosting providers may process IP addresses and request information. We do not describe the service as anonymous or promise that deleting local history deletes provider records.

Privacy and support contact: support@tradingcarddata.com.