Legal Documents
Every major legal section in one place. Terms, privacy, cookies, buyer protection, and programme-specific policies — all admin-managed and updated regularly.
Cookie Policy
Version 1 · Effective 29 October 2026
- Last updated
- 28/10/26
This Cookie Policy explains how cookies and similar technologies are used when you visit or use CardzLocal at cardzlocal.co.uk. It explains what these technologies do, the choices available to you and how to change those choices.
It applies to public pages and signed-in features, including the Marketplace, seller storefronts, Galleries, Collections and binders, Trade Hub, OrbitIQ Price Check and Card Scan, CardzConnect, CardzQuest, memberships, cosmetic stores, rewards, referral features and the Support Hub. The technologies relevant to you depend on the pages and features you use.
Read this Policy with the CardzLocal Privacy Policy. The Privacy Policy explains how we handle personal information more broadly, including payments, identity verification, account records, security, retention and your data-protection rights.
1.1 Who operates CardzLocal
CardzLocal is operated by CardzLocal Ltd, company number 17284494, with its registered office at Suite RA01, 195-197 Wood Street, London, United Kingdom, E17 3NU.
Our website is cardzlocal.co.uk. For cookie or privacy enquiries, email support@cardzlocal.co.uk, visit the Support Hub or use our contact form.
2.2 What cookies and similar technologies are
A cookie is a small file stored on your device by a website. It can help a service recognise a browser, maintain a sign-in session or remember a choice. A cookie may contain an identifier rather than your name, but information linked to that identifier can still be personal information.
Similar technologies include browser local storage, session storage, device databases, pixels, tags, scripts and software development kits. Some tools can also access device information to distinguish a browser or device. This Policy covers these technologies when used for the purposes described here.
A first-party technology operates in the context of the website you are visiting. A third-party technology involves another provider, such as an embedded payment service. Both can be subject to the same legal requirements. Calling a tool first-party or server-side does not, by itself, remove the rules that apply when it stores or accesses information on your device.
3.3 Information these technologies may handle
Depending on the feature and your choices, relevant information may include a session or device identifier, sign-in status, security signals, cookie preferences, browser and device details, an IP address, approximate location inferred from an IP address, pages or features used, interaction events, timestamps and technical errors.
Payment-related tools may also handle device and transaction signals needed to authenticate a payment or assess fraud. Referral or advertising tools, where enabled, may associate an identifier with a visit or qualifying action for the disclosed attribution purpose.
The specific information handled by a technology depends on its purpose. We limit it to what is needed for that purpose and explain the relevant provider and use in the cookie information available through Cookie Settings.
4.4 The rules we follow
Our use of these technologies is governed by the Privacy and Electronic Communications Regulations 2003 (PECR), as amended, including changes introduced by the Data (Use and Access) Act 2025. The UK GDPR and Data Protection Act 2018 also apply where personal information is processed.
We obtain consent before storing or accessing information on your device unless a specific legal exception applies. Where consent is required, we do not treat continued browsing, scrolling, silence, account creation, a purchase or acceptance of the Terms of Service as consent.
Where cookie-derived personal information is processed on the basis of consent, we do not switch to legitimate interests simply because you refuse or withdraw that consent. For processing that meets a PECR exception, the appropriate UK GDPR lawful basis depends on the purpose and is explained in the Privacy Policy or relevant feature notice.
5.5 The purposes of the technologies we use
Strictly necessary functions. These support a service or feature you request, such as maintaining a secure sign-in session, protecting an account, transmitting a page, keeping a checkout working or remembering a cookie choice. A technology qualifies for an exception only where its actual purpose and operation meet the legal conditions. A useful business function, general engagement measurement or advertising purpose is not automatically strictly necessary.
Preferences and appearance. These can remember choices about display, accessibility, layout or how a feature works. We request consent unless the particular use meets a legal exception. Where we rely on the narrow appearance exception, we explain the use and provide a simple, free way to object. Using browsing history or inferred interests to select content or advertising is outside that exception.
Statistics and service performance. These can help us understand visits, loading times, errors and use of features so we can improve CardzLocal. We obtain consent unless the particular use meets the statistical-purposes exception. Reliance on that exception requires all its conditions to be met, including the applicable limits on purpose, sharing and handling of information, clear information for you and a simple, free way to object. It does not authorise individual behavioural profiling, cross-service tracking or advertising measurement.
Advertising and attribution. Where used, these technologies can measure an advert or promotion, attribute a visit or conversion, support a referral campaign or help select advertising. Non-exempt advertising, retargeting and cross-site or cross-device tracking require prior consent. A referral identifier used to calculate a commission is not automatically essential just because it has commercial value.
Optional third-party content. A video, social-media embed or other external feature may use its provider’s technologies. Where loading it would activate non-exempt technologies, we request the required consent before doing so. The feature may remain unavailable until you choose to allow it.
Cookie Settings identifies the purposes and providers actually enabled on the relevant part of CardzLocal. Describing a category in this Policy does not mean that every technology within that category is active on every page.
6.6 Base44 and Stripe
CardzLocal uses Base44 as its application hosting and technology provider. Depending on the functions enabled, Base44 and its service providers may support page delivery, application sessions, authentication and security. Information about a technology’s actual purpose determines whether it needs consent. Base44’s involvement does not make every technology exempt. See Base44’s Privacy Policy.
CardzLocal uses Stripe and Stripe Connect for relevant payment and seller-payment services. When you use checkout, seller onboarding or another Stripe payment flow, Stripe may use cookies or similar technologies for payment functionality, authentication, security and fraud prevention. It may receive device and browser information as part of those services. See Stripe’s Cookie Policy and Stripe’s privacy information.
We assess payment and fraud-prevention technologies according to their actual use. Optional analytics or advertising do not become essential merely because a payment provider supplies them. If a provider takes you to its own website, the information and controls shown there apply to that separate service.
Your cookie choice is separate from authorising a payment. Rejecting optional tracking does not remove records needed to complete an order, administer a membership, process a refund, prevent fraud or meet a legal obligation.
7.7 How to make a cookie choice
Use Cookie Settings to review the purposes and providers and make or change your choice. For technologies that require consent, the controls provide options to accept, reject or customise them. Consent-dependent options remain off until you choose to allow them.
Rejecting optional technologies must be as straightforward as accepting them. You can allow one optional purpose without agreeing to every other purpose. If a disclosed appearance or statistical use relies on an exception with a right to object, Cookie Settings also provides a simple, free way to turn that use off.
Rejecting optional technologies does not close your account, cancel a membership or cancel an order. Some optional features may not work without the technologies needed for those features. Essential sign-in, security or checkout functions may also fail if you separately block the technologies they need through your browser.
A choice may apply to a particular browser or device. You may need to make it again when you use another browser or device, clear storage or browse privately. If we apply a choice across an account, we explain that in the relevant controls.
8.8 Changing your mind
You can return to Cookie Settings to withdraw consent or change an objection at any time. We make withdrawal as easy as giving consent. We stop the affected future storage, access and consent-based processing when you withdraw, and take appropriate steps to remove or disable the relevant technologies.
Where a third party received information in reliance on that consent, we communicate the withdrawal and deal with related deletion obligations as required by law. Some third-party cookies may also need to be removed using your browser or that provider’s controls.
Withdrawal does not make earlier lawful processing unlawful. It also does not erase order, accounting, security or other information that is held independently for a separate lawful purpose. The Privacy Policy explains your rights and the circumstances in which records must be retained.
9.9 Information about individual technologies
The detailed cookie information available through Cookie Settings forms part of this Policy. It identifies each technology or clearly described group of related technologies actually used, its name or identifier, the provider and relevant domain, its purpose, who can access the information and how long the information is stored or access continues.
It also explains whether a technology requires consent or is used under a specific exception, and how to change the relevant choice. Where another provider processes the information, its identity and relevant privacy information are supplied.
For technologies that require consent, this information is available before you choose to allow them. Changes to a provider, purpose or duration are reflected in that information. We do not rely on a generic category label to conceal an unrelated use.
10.10 How long technologies and preference records last
Session technologies generally last for a browser session, although some browsers can restore sessions. Persistent technologies remain for a specified period or until removed. Local storage and similar device storage can remain until the service or user deletes it, so they need their own retention limits.
The individual durations are given in Cookie Settings. We use periods appropriate to the purpose and review them when the technology or service changes. The lifetime of a cookie is separate from the retention period for any personal information already lawfully collected through it.
We keep a limited record of your choices, when they were made and the notice or settings version needed to apply and demonstrate them. Remembering a refusal is not permission to activate the refused technologies.
There is no universal legal period after which every cookie choice expires. We review whether a choice remains valid and request fresh consent where a new purpose or other material change requires it. We do not repeatedly prompt you merely to persuade you to reverse a refusal.
11.11 Browser controls and device permissions
Your browser usually provides controls to view, block or delete cookies and other website data. Consult its Help or Privacy settings for instructions. Deleting a browser cookie may not delete local storage, and changing settings on one browser may not affect another.
Browser restrictions are additional to CardzLocal’s own controls. They may prevent some functions from working and may also remove the saved record of your cookie choice. Deleting local website data does not, by itself, delete your CardzLocal account or records held by a payment provider.
Camera, microphone, photo-library, location and notification permissions are separate choices where a feature requests them. Accepting optional cookies is not permission to access those resources. Card Scan and identity-verification uploads remain subject to the explanations and permissions shown for those features.
12.12 Emails and referral activity
Marketing messages may use links or pixels to measure delivery, opens, clicks or a related action. Where that involves non-exempt storage or access on your device, we obtain the required consent before using it. Permission to send a marketing email is not automatically permission for every form of engagement tracking.
You can unsubscribe from optional marketing using the message or preference controls. You can separately change website cookie choices in Cookie Settings. Essential order, account or security messages may continue where necessary for the service.
Account records such as a referral code you enter, a qualifying sale, Gems, XP or a membership entitlement are not automatically cookie tracking. Their processing is explained in the Privacy Policy. If device-based tracking is used to attribute those activities, the cookie rules still apply.
13.13 Children and CardzConnect
CardzConnect is restricted to people aged 18 or over and requires the applicable identity and age verification. A cookie or saved session is not a substitute for that check.
Other CardzLocal features may be accessed by younger users where the Terms and law permit. Where children are likely to access a service, we take their privacy needs into account, provide suitable information and apply the safeguards required for that service. Optional profiling must be off by default where the Children’s Code requires this, unless there is a compelling reason consistent with the child’s best interests.
Where consent is required from a parent or guardian, we obtain the required authorisation. We do not use confusing controls or rewards to pressure a child to weaken privacy choices. A parent or guardian can contact us about a concern using the details below.
14.14 Personal information and your rights
Cookie identifiers and related activity can be personal information even if they do not contain your name. The Privacy Policy explains the purposes, lawful bases, recipients, international transfers, security arrangements, retention and rights that apply to personal information.
Some providers may process information outside the United Kingdom. The relevant providers and their roles are explained in the Privacy Policy, Cookie Settings and any applicable feature notice, together with information about the safeguards required for restricted transfers.
You can contact us to exercise an applicable data-protection right. Refusing cookies and requesting deletion of account information are separate actions; use the privacy contact route if you also want us to consider a data-rights request.
15.15 Changes and contact details
We may update this Policy when CardzLocal’s technologies, providers, purposes or legal requirements change. The latest version shows its update date. A policy update does not itself give consent for a new use; we ask for a new choice where the law requires it.
For questions, a cookie-control problem or a privacy complaint, contact CardzLocal Ltd at support@cardzlocal.co.uk, through the Support Hub or using our contact form. You may also write to Suite RA01, 195-197 Wood Street, London, United Kingdom, E17 3NU.
