Your collection.
Clear boundaries.

Accounts and collections

The service stores your name, email address, password hash, sign-in sessions and the collection records you choose to add. Private collection and binder actions require a signed-in account. The server operator administers the database, backups and user accounts.

Testing access and future billing

This release records a testing membership and access grant. It does not request payment-card information, create payment-provider customers, charge subscriptions or automatically expire testing access. Unpublished plan drafts are administration data, not live subscriptions.

Access, support and privacy requests

The request form stores the name, email address, request type and message you submit, together with its consent version and review status. Only platform administrators can view the queue. Submitting it does not create an account or subscribe you to a mailing list. Requests remain until an administrator deletes them; there is no automatic retention schedule for them in this release.

Cookies and technical records

CardShelf uses a first-party sign-in cookie and server-side sessions to keep you logged in. Security rate-limit records, application logs and audit events support service operation. This release does not add advertising trackers, marketing analytics or third-party tracking cookies.

Wallpaper uploads and sharing

Uploaded wallpapers are decoded, optimised and re-encoded before storage. Original filenames and image metadata are not retained by that upload flow. A wallpaper is accessible to its binder owner and, when enabled, through the binder’s read-only sharing link. Anyone holding an enabled share link can view the shared layout and appearance. Revoking the link cannot recall screenshots or copies already made.

Catalogue and price providers

Catalogue and market-price requests use TCGdex. Card artwork currently loads from its image host, which receives the ordinary connection information required to serve an image. Currency reference requests use Frankfurter. Your full collection database, private notes and account passwords are not sent in these provider requests.

Exports and data requests

Signed-in users can export ownership records as JSON or CSV. Those exports do not include all account, binder or database information. For questions or requests about your data, contact the administrator who invited you or use the form below. Do not include a password or payment information.

This describes the implemented beta features. The operator should review its wider hosting, backup, retention and service terms before a paid public launch.