Skip to content

Privacy Policy

What Lorewares collects, how information supports the marketplace, what others can see, and the choices available to you.

Effective September 16, 2026Version 2026-09-16

You are reading an archived version. Read the current privacy policy.

Who handles your information

Lorewares is operated by Andrew Ashenden, a Wisconsin sole proprietor doing business as Lorewares. This notice describes information handled through the Lorewares website, accounts, marketplace, seller tools, trades and support. Contact lorewares@gmail.com for privacy questions or requests.

This notice explains our practices. It does not subscribe you to marketing or ask you to waive privacy rights. Providers such as payment processors may also process information under their own privacy notices when you use their services.

Information we collect and why

We receive information you enter or upload, records generated by your use of the service, and transaction or delivery updates from sellers and service providers. We use it to run requested features, fulfill transactions, provide support, prevent abuse, maintain security and meet applicable recordkeeping obligations.

InformationExamples and purpose
Account and preferencesEmail address, display name, password hash, avatar, privacy and notification preferences, adult eligibility affirmation and policy acceptance records. Used for sign-in, account management, preferences and evidence of the agreement shown.
Collections and activityBinder entries, wanted and for-trade cards, deck or shopping-list data, saved searches, drafts and feature activity. Used to save or sync the features you select and show relevant inventory or trade matches. Some drafts and preferences are stored only in your browser.
Orders, payments and deliveryBuyer and recipient details, addresses, contact numbers where supplied, ordered items, payment references and status, credit entries, tax, shipping, refunds and dispute records. Used to process, fulfill and support transactions and maintain business records.
Seller informationShop and representative details, business information you supply, listing inventory, shipping settings, onboarding status and payout references. Used to operate the marketplace, verify required setup and administer seller obligations. Sensitive identity or bank details entered directly with Stripe are handled through Stripe’s onboarding flow.
Photos, messages and evidenceUploaded card or avatar images, listing notes, inspection findings, transaction messages, support requests and dispute attachments. Used for the feature or transaction you submit them for, and for resolving problems.
Technical and referral informationCookies, browser storage, request details such as IP addresses, service logs, security checks, errors and referral identifiers. Used for sessions, reliability, abuse prevention, saved preferences and attribution of partner promotions.

Card photos and the scanner

The scanner compares an uploaded photo with the catalog image index on Lorewares’ server. The AI fallback has been removed: this scan flow does not send photos to an external generative-AI service to identify cards. An uncertain result requires choosing the printing or searching the catalog manually. Photo matching does not certify authenticity, grade or condition.

Taking or uploading a photo can involve finding the card’s edges and preparing a cropped or resized image. Camera access is controlled by your browser. A photo saved to a private intake draft stays within the draft workflow; if you attach a photo to a published listing, it may be visible to buyers. Inspection and dispute photos may be shared with the participants and staff handling that transaction.

A saved photo may remain as listing, draft, inspection or dispute evidence. Avoid including unrelated people, addresses, identification documents or other sensitive information in card photos. This statement describes the scanner released with this policy and does not claim that no earlier version ever used an external image reader.

Private order evidence may include card-front and back images, packaging, shipping receipts, certification details, uploader references, upload times and whether upload occurred before or after recorded dispatch. Claim reviews retain evidence assessments, return checks, carrier references and written decisions. These records support transaction review and fraud prevention; an upload time does not authenticate capture time. Evidence is shared with the buyer, the responsible seller and authorized Lorewares staff, and relevant records may be provided to carriers, insurers, payment providers or authorities when needed for a claim, dispute or legal obligation. Avoid unrelated people or private information in uploads.

Public information and transaction sharing

Your chosen display name, avatar, public shop, listings, feedback and publicly enabled trading profile can be visible to other people. Collection, wanted and for-trade information is shown through the visibility or sharing features you use. Directory participation and other available privacy controls are managed in account settings. A share link can be forwarded; information already copied by another person may remain outside our control.

Sellers fulfilling an order receive the buyer and delivery information needed for fulfillment and support. Trade participants and case participants see relevant proposal, shipment, inspection and dispute information. They do not receive unrestricted access to your private account. Sellers must use buyer information for the transaction and their applicable legal duties, not unrelated marketing.

Choose public names and notes carefully. Do not put personal contact details in listing text, public profiles or photos unless you intend to share them. Private records and public marketplace pages have different audiences.

Service providers and other disclosures

Stripe processes payments and seller onboarding. We retain payment identifiers, status, amounts and related transaction records; Lorewares does not store full payment-card numbers. Email delivery providers such as Resend receive the addresses and message contents needed to deliver account, transaction or chosen notification emails.

Shipping services such as EasyPost/WeSupply and carriers receive relevant sender, recipient, package, tracking and selected delivery-contact information. Hosting, storage and infrastructure providers process information as needed to run and protect the website. Information is disclosed according to the service being used, rather than sending every provider your complete account.

We do not sell your personal information or provide it to third parties for their independent advertising. We may disclose information to comply with law or lawful requests, investigate fraud or security incidents, protect rights or safety, handle disputes, or complete a business transfer subject to applicable privacy protections.

Lorewares is based in the United States. Information may be processed in the United States or other countries where our providers operate. Their handling can also be subject to their own legal duties and privacy notices; using a provider does not mean Lorewares controls every record the provider must retain.

Cookies and browser storage

First-party cookies and browser storage support sign-in, carts, saved drafts, preferences and other requested features. Some deck and shopping-list information is saved on this device, while supported account features sync to our server. Clearing browser storage can erase device-only drafts and preferences; deleting an account does not clear every copy stored on your devices.

Visiting a creator’s referral link sets a first-party referral cookie for up to 30 days. The last eligible partner link visited in that browser is used to attribute orders and measure partner promotions. The referral visit record contains a random identifier, the partner and timestamps, without an IP address or browser fingerprint. That limit describes the referral record; ordinary service and security logs can contain request information.

You can clear or block cookies using browser controls. Blocking the referral cookie prevents later attribution through it; blocking session or other essential storage can prevent sign-in or disrupt features. Referral reports count recorded activity, not verified unique people.

Emails and optional delivery texts

We send account, security, order, trade and existing trade-in messages needed to operate the service. Optional discovery alerts, saved searches and restock notifications follow the choices available in your account. Turning off optional alerts does not turn off necessary transaction or security messages. New-account notification choices are separate from acceptance of the Terms of Service.

Delivery texts are optional, order-specific and offered only for supported shipments from participating sellers. Opting in supplies the selected mobile number to EasyPost/WeSupply for automated shipping updates. Providing a phone number only as a carrier contact is not a text-message opt-in. Economy envelopes do not include tracking updates.

Text frequency varies with shipment events; message and data rates may apply. Text consent is not required to buy and does not authorize marketing texts. Follow unsubscribe instructions in a message or contact us for help. Messages can be delayed and do not guarantee delivery; consult your order record for available updates.

Retention and account deletion

Retention depends on the record and why it is needed. We consider whether your account or transaction is active, whether a record is needed for fulfillment, a refund, a dispute, security, accounting or another legal obligation, and whether it can be removed or anonymized. There is not one deletion deadline for every record.

RecordRetention approach
Account and collector dataMaintained to provide an active account and its saved features. Account deletion removes the account and associated collector data handled by that process, subject to retained transaction and legal records.
Orders, payments, shipping and policy acceptanceMay be retained for transaction history, refunds, disputes, security and applicable financial or legal obligations. Closing an account does not erase every transaction record; direct account identifiers may be removed where appropriate.
Photos and correspondenceRetention follows the related listing, draft, inspection, support request or dispute and the need to preserve evidence. Contact us about removal of a specific photo or message, including one associated with a closed account.
Technical records and backupsMay remain for operational recovery, reliability, security or legal needs. Deleting an account does not instantly remove copies from backups or independent provider records. Contact us for information about retained copies.
Device-only data and referral cookiesDevice-only data remains until removed through the feature or browser storage controls. The referral cookie expires after up to 30 days, but related order attribution and business records may remain under the criteria above.

Your choices and privacy requests

Use account settings to manage your profile, privacy, available notification choices and account-deletion options. Open transactions, cases or unresolved seller balances can block self-service account deletion while they are resolved. You may still contact us about a privacy request while a transaction is open.

Email lorewares@gmail.com to request access, correction or deletion, ask about retained records, or request other rights available under applicable law. Depending on your circumstances and the law that applies, these may include receiving a copy of your information, restricting or objecting to certain processing, withdrawing an optional consent, or appealing a decision. We will explain any verification needed, applicable exception or available next step. Do not send passwords, full payment-card details or identity documents unless we arrange an appropriate verification method.

We may need to verify that a request relates to your information or that an authorized representative can act for you. We will not treat a privacy request as permission to delete someone else’s information. Available rights and response requirements depend on applicable law; contact us if you disagree with our response or need help exercising a right.

Children and security

New Lorewares accounts must be held and managed by adults aged 18 or older. A parent or guardian may use their own account for a younger collector without creating a child’s account or supplying the child’s personal details. The account service is not intended for children under 13. If you believe a child has provided personal information, contact us so we can review and address it. An adult-eligibility checkbox is not a claim that every visitor’s age has been independently verified.

We use safeguards such as hashed passwords, account-access controls and restricted transaction workflows. No online service can guarantee absolute security. Keep your sign-in details private and report suspected unauthorized access promptly.

Changes to this notice

The version and effective date identify this notice; earlier versions are available in the policy history. We will bring material changes to affected users’ attention through the service or an appropriate account notice. We will not treat a quiet policy edit as consent to a new use of previously collected information that requires notice or consent. Where required, we will obtain the appropriate choice or consent before applying such a change.

Privacy Policy · 2026-09-16 · Lorewares