Privacy Policy

Dead Cold Cards is operated under the Dead Cold Games brand.

Privacy contact: contact@deadcoldgames.co.uk

Account information includes the email address and password credentials handled through Supabase Authentication, plus account metadata such as display name where provided during sign-up.

Profile information can include display name, username, biography, avatar URL, public-profile setting, and toggles controlling whether collection, wishlist, and custom-set sections are public.

Collection, wishlist, and custom-set information can include card identifiers, card names, set details, variant details, quantities, condition, language, grading details, purchase price/date, notes, wishlist priority, and custom-set targets. These records exist so users can manage their own collection.

Preference information is stored locally in the browser for card reveal animation, device-motion tilt, market preference settings, and optional analytics and advertising consent choices.

If a visitor allows optional analytics, Google Analytics 4 can receive usage information such as pages visited, page titles, referral/campaign information, browser/device information and configured product-usage events. Dead Cold Cards does not intentionally send passwords, card images, private collection notes or payment card details to GA4.

If a visitor allows optional advertising on an eligible free page, Adsterra banner technology may process technical and advertising-related information needed to deliver, measure and protect advertising, which may include IP address, browser/device information, page interactions and advertising identifiers where applicable.

Paid subscription records may include account identifiers, Stripe customer/subscription references, product/price references, subscription status, billing-period information, cancellation state and timestamps. Full payment card details are handled by Stripe and are not stored by Dead Cold Cards.

Collections are not automatically public. Public collector profile pages are displayed according to the user's profile privacy settings.

Where public collection sharing is enabled, public views use limited card/profile fields. Private acquisition and financial fields such as purchase price, private notes, trade notes, and certification numbers are not intended to appear on public collector profiles.

The application uses Supabase session cookies for authentication. Hosting and application infrastructure may process technical request information such as IP address, user agent, timestamps, route requests, and security logs as part of operating the service.

Optional Google Analytics 4 measurement is activated only after analytics consent through the site control. The integration disables Google Signals and ad-personalisation signals for GA4 measurement.

Optional Adsterra banners are activated only after advertising consent and only on eligible ad-supported pages. Paid or otherwise ad-free accounts do not load the Adsterra banner integration through the Dead Cold Cards ad-slot system.

Information is used to create and maintain accounts, save collection data, display requested collection/wishlist/custom-set views, provide pricing and portfolio features, operate public profile settings, secure the service, and troubleshoot operational issues.

Where optional analytics are allowed, usage data is used to understand which pages and features are used, how visitors move through the service, and where product flows can be improved.

Pricing/value information is used to provide collector-focused estimates and portfolio summaries. It should not be treated as financial or investment advice.

Where optional advertising is allowed, advertising technology is used to fund the free web experience and to support ad delivery, measurement and fraud prevention.

Service-delivery processing is expected to be mainly necessary to provide the requested account and collector functionality. Security, abuse prevention, and basic operational logging may rely on legitimate interests. Optional Google Analytics measurement and optional advertising are activated based on the visitor's consent and can be changed using Privacy settings in the site footer.

The service uses Supabase for authentication/database services and hosting/runtime infrastructure for serving the application. Public card catalogue and pricing data sources are used to display reference information.

Stripe is used for paid subscription checkout, billing management and payment processing. Stripe may process payment, billing, tax, fraud-prevention and customer-support information according to its own terms and privacy practices.

Google Analytics 4 is used for optional site and product-usage analytics after consent. Google may process analytics data according to its own privacy terms. Google Signals and ad-personalisation signals are disabled in this application's GA4 configuration.

Adsterra is used to provide optional banner advertising on free, ad-supported pages after advertising consent. Adsterra and advertising partners may process technical, usage and advertising-related data according to their own privacy terms and applicable privacy choices.

Advertising is off until the visitor allows the optional Advertising choice in the site's privacy control. Users can reopen Privacy settings from the footer to change that choice. Withdrawing advertising consent prevents this integration from loading Adsterra banner scripts on subsequent eligible page views.

Information is kept for as long as needed to provide the account and collection service, meet legal obligations, resolve disputes, secure the service, and maintain operational records. Analytics retention is also subject to the retention settings configured in the Google Analytics property. Advertising-provider retention is subject to the provider's own policies and applicable settings.

Depending on the circumstances, users may have rights to access, correct, delete, restrict or object to processing, receive a portable copy of information, and withdraw consent where processing relies on consent.

Deletion and data requests should be sent to the privacy contact.

Users may contact the operator first about privacy concerns. UK users also have the right to complain to the Information Commissioner's Office if they believe their data protection rights have not been respected.

This notice may be updated as the service changes.