PullX and your information
PullX operates from North Carolina, United States. This notice describes the information handled when you use PullX; the support page provides the current contact route for privacy questions and requests.
Information you provide
Account information includes your email address, display name, sign-in credentials and preferences. Passwords are stored as password hashes rather than readable passwords.
Collection information can include card identities, quantities, condition, finishes, notes, purchase costs and dates, imported files, scan results and photos you submit. Screening, grading and bulk-sale features can retain their own evidence and review history.
If you use selling, buying or trading features, records can include listings, offers, acceptances, inspection findings, addresses, shipping details, transaction references, feedback and dispute information.
Device information, cookies and local drafts
The app uses a sign-in cookie to maintain your session. Security records can include IP addresses, browser or device information, sign-in events and session activity.
Browser storage supports preferences, cached app resources and drafts such as scan queues and prepared imports or bulk requests. Some drafts stay only in the current tab or device. Clearing site data or closing a tab can remove them; browser storage is not a permanent collection backup.
Camera access is used when you choose a capture feature and give your browser permission. You can change that permission in your browser or device settings.
How information is used
The app processes information to provide the features you request, including:
- Signing you in, preserving account preferences and protecting account access.
- Identifying cards, matching imports and maintaining collection and price history.
- Reviewing submitted photos, purchases, shipping, payments and related disputes.
- Applying account limits, displaying verified transaction feedback and investigating misuse.
- Diagnosing errors, responding to requests and maintaining records of important actions.
Photos are handled by the feature you use
Some identification routes process a photo temporarily; other scan, grading or screening workflows save evidence. A scan-image preference is not a promise that every photo in every feature is deleted after identification.
Bulk overview photos are stored privately with the sale request. Screening photos are associated with the screening case. Removing or replacing an image can require a separate storage-cleanup step; a storage failure can delay that cleanup.
Avoid including faces, addresses, payment details or other unrelated private information in card photos. A card image or scan result alone does not prove authenticity or ownership.
Service providers and other users
Hosting, storage and configured analysis services process data needed to operate their part of PullX. Card and pricing sources supply catalog information; loading externally hosted artwork can also send the image host your connection information.
Resend delivers account emails such as verification and password-reset messages. Email delivery involves sharing the recipient address and message content with the delivery provider.
When payment features are enabled, Stripe handles the payment or payout setup presented to you. PullX keeps related account and transaction references. When shipping features are enabled, Shippo and the selected carrier receive the details needed to arrange the shipment.
Marketplace and trade participants receive information relevant to their transaction. Public listings and reputation records can be viewed by other users. Authorized staff can review private records needed to handle a request or investigate an issue.
Advertising and campaign attribution
A landing-page visit can include campaign tags or a Google click identifier. The app can keep these in the current tab and attach them to a submitted selling request.
Staff tools can prepare a file linking supported seller milestones to a click identifier for advertising measurement. Preparing that file does not automatically send it to Google.
Campaign-tag capture is implemented. Its notices, consent handling and retention choices need review; preparing a conversion export does not approve an upload to an advertising provider.
Retention, corrections and requests
Different records have different purposes and lifetimes. Saved collections, transaction evidence, security history and photos do not share a single deletion schedule. Removing an item from a screen does not necessarily remove its history, pending storage cleanup or backup copy.
You can update available profile and privacy preferences in Settings and use the removal controls offered by individual features. For a full-account export or deletion request, use the available account controls or the support contact. A request is separate from confirmation that the process is complete; it does not immediately erase every record.
Full-account export and deletion are not yet complete self-service processes. A pending deletion can disable account access without automatically removing all account records. Do not treat a requested export, a pending status or an estimated deletion date as confirmation of completion; contact support to check the request.
The support page shows the available contact route for questions and requests. Verification may be needed before account information can be disclosed or changed.
The retention schedule, staff handling of privacy requests and disclosures for the approved launch audience remain under review. These operating arrangements must be settled before this notice is approved; incomplete account tools are not completed by publishing the notice.
Questions about this policy?
PullX is operated by PullX.
A verified public contact address is still being configured.
Visit support