BETA PRIVACY INFORMATION · 10 NOVEMBER 2026
Your cards. Your information.
This page explains how BinderWorth currently handles personal information during its limited testing phase. It describes the product as implemented, not promises about future services.
Who operates BinderWorth?
BinderWorth is currently a privately operated collector-platform project. The formal data-controller identity and privacy contact will be published here before unrestricted public launch. Until then, do not treat this beta notice as a complete statutory privacy statement.
What information do we handle?
- Guest collections: card lists, quantities, finishes, binder positions, set goals, notes, preferences and local diagnostics can stay in the browser's local storage without an account.
- Cloud accounts: the email you provide, salted password hash, session records, synced collection and Chase List, set goals, settings and value history. Previous cloud revisions are stored to provide recovery.
- Account security: one-way hashes of backup recovery codes and expiring password-reset tokens. Codes and reset tokens are never intentionally stored as readable plaintext in the account database.
- Scanning: the normal OCR workflow processes card photographs in your browser. If you explicitly select AI recognition, the cropped image is sent to BinderWorth's private recognition service to identify it. Card photographs are not included in ordinary cloud collection sync.
- Challenge events: joining an event can create participation and unique-scan records. Small review thumbnails may be retained for authorised winner verification.
- Optional scanner feedback: with your permission, matched card details, candidate IDs, confidence/ranking results and scanner diagnostics can be transmitted. Basic feedback does not include photographs, filenames, email or collection valuations.
- Traders and event organisers: applications and authorised stock/event submissions may include business names, contact details, towns and public stock listings.
- Location: if you choose postcode, town or device location features, BinderWorth uses the supplied approximate area to sort local traders or events. An exact home address is not required to use the collection tools.
- Technical and security logs: service requests, IP-related abuse controls and security audit entries are used to protect the site and investigate faults. We do not intend to include passwords or recovery secrets in audit records.
Why we use the information
Account and collection data supports the service you choose to use, including login, sync and recovery. Security and operational logs help prevent misuse, maintain reliable backups and diagnose failures. Optional feedback is used only when enabled to improve card recognition. These purposes and their precise UK GDPR lawful bases require final controller review before public release.
Where data goes
BinderWorth is hosted on Railway with persistent storage and encrypted offsite operational backups. The site also connects to card-artwork and catalogue providers and may load external resources such as Tesseract.js. AI scanning sends selected image data to the dedicated recognition service. Optional event maps and external marketplace or trader links may contact their respective providers when opened. Password-reset emails, when enabled, are sent through Resend. Processor locations and international transfer safeguards must be verified before launch.
Cookies and local storage
Signed-in sessions use an HttpOnly cookie with SameSite=Lax; HTTPS access also uses Secure. The default session lifetime is 14 days, configurable to a maximum of 30 days. Browser storage keeps guest collection data, display preferences, account sync metadata and optional feedback choices. It is not a third-party advertising cookie mechanism.
How long information is kept
Cloud collection data remains while your account exists, with a rolling history of up to 12 older saved revisions. Local operational backups currently retain up to 14 versions by default, but encrypted offsite copies and operational/security records may persist until their respective retention cycles end. Password-reset email links expire after 30 minutes; backup recovery codes remain valid until used, replaced or deleted with the account. Formal periods for offsite backup, feedback and security-log retention must be finalised and documented before public launch.
Your controls and rights
You may use BinderWorth without an account; download collection JSON from Settings; export cloud account data; restore prior cloud collection revisions; disable optional feedback; and request permanent cloud-account deletion from Account (requires your current password). Once deleted, cloud accounts are removed from the active account store; backup retention may mean deletion from historical backups is not immediate.
UK data protection law can provide rights to access, correct, erase, restrict or object to certain processing, and portability in applicable circumstances. You can complain to the Information Commissioner's Office. A verified operator contact address for requests will appear here before full launch.
Important product limits
Card values are estimates, not guarantees. AI and OCR can misidentify cards. The scanner cannot authenticate a card or grade its condition conclusively. Participation in an event challenge may require additional event-specific rules.
Version: Beta 1 · Last updated: 10 November 2026. This notice will be reviewed as account recovery and public onboarding are completed.