Dead Cold Cards
Dead Cold Cards
Sign InCreateCreate Account
Dead Cold Cards
Trading card collection platform
contact@deadcoldgames.co.uk
PrivacyCookiesTermsRefundsLegal
Privacy

Privacy Policy

This notice explains how Dead Cold Cards, operated under the Dead Cold Games brand, handles information for collector accounts and public profile features.

Who operates the service

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

Privacy contact: contact@deadcoldgames.co.uk

Information we collect

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, and market preference settings.

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.

Public profile information

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.

Technical and security information

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.

How information is used

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.

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

Where ads are enabled, advertising technology is used to fund the free web experience and to manage ad delivery, measurement, fraud prevention and consent choices where applicable.

Lawful bases

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.

Sharing and providers

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 AdSense may be used to provide advertising on free, ad-supported pages. Google and advertising partners may process technical, usage and advertising-related data, subject to applicable consent requirements and privacy choices.

Advertising consent controls

For UK, EEA and Switzerland visitors, Google requires a Google-certified consent management platform for AdSense traffic. The intended consent control is Google's AdSense Privacy & messaging CMP. Users should use the advertising consent message or privacy choices control, when available, to update consent choices.

Retention

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.

Your rights and requests

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.

Complaints

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.

Changes

This notice may be updated as the service changes.