✦✧✦
Policies

Legal Documents

Every major legal section in one place. Terms, privacy, cookies, buyer protection, and programme-specific policies — all admin-managed and updated regularly.

Privacy Policy

Version 2 · Effective 29 October 2026

Effective date
26/10/26
Last updated
28/10/26

This Privacy Policy explains how CardzLocal collects, uses, stores and shares personal information when you visit or use CardzLocal. It covers the website and account features, Marketplace, seller and buyer tools, orders, CardzSwap, Collections and binders, Price Check powered by OrbitIQ, Communities, CardzConnect, RewardzClub, memberships, Extras, support and related services.

We handle personal information under applicable UK data-protection law, including the UK General Data Protection Regulation (UK GDPR), the Data Protection Act 2018 as amended by the Data (Use and Access) Act 2025, and the Privacy and Electronic Communications Regulations 2003 (PECR), as amended. This Policy is intended to give the information required by those laws. The exact details must reflect CardzLocal’s live systems, providers and settings.

Please read this Policy with the CardzLocal Terms of Service and the Cookie Notice. Short, feature-specific notices may explain additional processing when you use a particular feature, including CardzConnect age verification, Stripe checkout or seller onboarding. If we change how we use your information, we will update this Policy and give you any notice or choice required by law before the new use begins.

The data controller is 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. You can contact us through the Support Hub, the contact form, or by email at support@cardzlocal.co.uk. Use these routes for privacy enquiries, data-protection requests and privacy complaints.

CardzLocal Ltd decides why and how personal information is used to operate CardzLocal. Some suppliers process information for us under written instructions. Other organisations, including Stripe and some Sellers, may also decide how they use information for their own services or legal duties. Their roles and notices are explained below and at the point where you use their service.

This Policy applies to visitors, account holders, Buyers, Sellers, CardzConnect users, Community members, people who contact Support, and people whose information appears in a listing, order, report or other User Content. It also applies when you contact us without an account.

You can browse public Marketplace listings, seller storefronts and other public pages without creating an account. Visiting the CardzLocal domain does not create an account or require you to choose a display name. You choose whether to create an account through the account-creation flow or a valid referral route. We may still process limited technical information needed to deliver the page, protect the service and honour your cookie choices.

This Policy does not replace the privacy information given directly by Stripe, a Seller, a carrier, an identity-check provider or another third party when that organisation processes your information for its own purposes.

We collect only the information needed for the feature and purpose concerned. The information may include:

Account and contact details. Name, username, display name, email address, phone number if supplied, age or date-of-birth information where needed, account preferences, referral code and authentication/security records. Most of this comes from you.

Profile and public information. Avatar, biography, chosen profile settings, badges, follower/favourite relationships, public storefront details, listings, reviews, posts, stories, comments, community membership and content you choose to publish.

Seller and business information. Legal or trading name, date of birth, home or business address, trader/private-seller status, business registration, National Insurance number or other tax identifier, VAT details, bank or payout information where required, seller-programme applications, payout status and documents needed to verify eligibility or meet legal reporting duties. Some payment-onboarding information is collected by Stripe and shared with us as described in its notices.

Orders and payment information. Items, bids and auction results, Sell to Me offers, CardzSwap requests, prices, fees, order status, delivery address, collection arrangements and handover-code status, tracking, refunds, chargebacks and dispute records, payment-provider references and payout status. Stripe handles payment credentials in its payment flow; CardzLocal receives the information needed to confirm and manage the transaction.

Collections and Price Check information. Card or product identifiers, collection and binder records, item photographs, set progress, gallery selections, search terms and Price Check entries or images you submit.

Social and community information. Posts, stories, images, video, comments, reactions, follows, favourites, group roles, messages, blocks, mutes, reports and moderation history. This includes CardzConnect content and Communities content.

Support, safety and account-health information. Support tickets, communications, dispute evidence, safety reports, verification decisions, moderation actions, fraud indicators, internal audit records and account-health measures. Private account-health information is separate from public seller ratings.

Rewards and feature activity. CardzCoins ledger entries, objectives, badges, boosts, referrals, votes, membership entitlements and actions needed to prevent duplicate or fraudulent rewards.

Device, usage and security information. IP address, browser and device details, approximate location inferred from an IP address, location you choose to provide for local search, timestamps, pages or features used, logs, error records, authentication events and cookie or similar-technology choices. If a future feature needs precise device location, we will explain that at the feature and request the permission required by your device.

Information from other sources. Payment and connected-account status from Stripe, delivery events from carriers, information you provide about another user, reports from users, information from business or public registers, and other information a provider shares with us lawfully.

Do not send us passwords, full card security codes or identity documents through public posts, Connect messages or ordinary Support messages. Use only the secure payment or verification flow shown in CardzLocal.

Some information you choose to include in a post, report, message or identity document may reveal sensitive information about you or another person. Do not include sensitive information unless it is necessary for the feature or report. If we need to process special-category or criminal-offence information to address a safety report, prevent harm or establish, exercise or defend a legal claim, we do so only where a UK GDPR and Data Protection Act 2018 condition permits it, with restricted access and appropriate safeguards. We do not use that information for advertising.

We identify a lawful basis before processing personal information and use it only for the purposes described here or a compatible purpose allowed by law. Depending on the activity, the lawful basis will be performance of a contract, steps you request before a contract, compliance with a legal obligation, our legitimate interests, your consent, or another lawful basis where the law permits it.

Create and secure an account; let you sign in and manage settings. Information used: Account details, authentication and device/security data. Lawful basis: Contract or steps requested before contract; legitimate interests in keeping accounts secure and preventing unauthorised access.

Provide Marketplace, Collections, binders, Communities, CardzSwap, RewardzClub, Price Check and other requested features. Information used: Profile, content, collection records, searches, permissions, rewards and feature activity. Lawful basis: Contract or steps requested before contract; legitimate interests in operating and improving a reliable service where processing is necessary and proportionate.

Publish listings and public pages you choose to make public. Information used: Profile, storefront, listing, Gallery and community content. Lawful basis: Contract and your feature settings; consent where a specific optional processing activity requires it.

Complete orders, local collections, shipping, payments, refunds and payouts. Information used: Buyer and Seller details, order and address information, tracking, payment references and dispute evidence. Lawful basis: Contract; legal obligations relating to accounting, payment, consumer, tax or regulatory matters; legitimate interests in preventing fraud and resolving disputes.

Verify Sellers and meet payment, identity, tax or reporting requirements. Information used: Seller identity, business, address, tax and payout details. Lawful basis: Legal obligation where one applies; contract or steps before contract; legitimate interests in verifying eligibility and preventing financial abuse.

Determine whether a Seller must be reported to HMRC and make required reports. Information used: Seller identity and tax details, reportable transaction and fee information. Lawful basis: Legal obligation. If you are reportable, we may send required information to HMRC and give you a copy of the information reported.

Verify CardzConnect eligibility and enforce its 18+ access rule. Information used: Age/identity evidence, verification result, review status and audit information. Lawful basis: Contract and legitimate interests in limiting access to adults and maintaining a safer service; legal obligation where a specific legal duty applies. The verification screen will explain any additional basis before evidence is submitted.

Moderate content, investigate reports and protect users or CardzLocal. Information used: Messages or posts relevant to a report, safety signals, account and order history, moderation notes. Lawful basis: Legitimate interests in providing a safe service and enforcing our rules; contract; legal obligation where applicable. We limit access to what is relevant to the review.

Prevent fraud, abuse, security incidents, duplicate payments and reward manipulation. Information used: Transaction, account, device, system and audit data. Lawful basis: Legitimate interests in protecting users, the Platform and payment flows; legal obligation where applicable; contract.

Provide support and handle complaints. Information used: Contact details, tickets, communications, order details and investigation records. Lawful basis: Contract; legitimate interests in responding and improving support; legal obligation where applicable.

Understand service performance and improve features. Information used: Technical logs, aggregated feature use, search or Price Check activity. Lawful basis: Legitimate interests where a UK GDPR basis is required and the processing is proportionate; consent where required for device storage or access; a PECR exception only where all its conditions are met.

Send service and security messages. Information used: Account contact details, order and security events. Lawful basis: Contract, legal obligation or legitimate interests, depending on the notice. These are not marketing messages.

Send optional marketing. Information used: Contact details and marketing preferences. Lawful basis: Consent or another permitted electronic-marketing basis, such as the soft opt-in where its legal conditions are met. You can opt out at any time.

Establish, exercise or defend legal claims and keep required business records. Information used: Relevant account, order, report, payment and communication records. Lawful basis: Legal obligation and legitimate interests in establishing, exercising or defending legal claims.

Our legitimate interests include maintaining a secure and dependable service; protecting users from fraud, scams and abuse; resolving order or safety disputes; preventing duplicate or manipulated transactions or rewards; supporting users; and improving CardzLocal. Where we rely on legitimate interests, we consider whether the processing is necessary and whether it unfairly affects your rights. You can object in the circumstances described in Section 16.

If we need to use information for a new purpose that is not compatible with the reason it was collected, we will explain that use and identify a lawful basis before starting it. We will not use private messages, transaction details or Price Check queries as a general dataset to train third-party AI models by default. If an AI feature needs your input to provide the feature, that use is described in Section 8 and in any feature notice.

For digital-platform tax reporting, reportable Seller information may include legal name, home address, date of birth, tax identifier, payout account details we hold, amounts paid, transaction counts and fees or taxes charged. We assess which Sellers are reportable under the rules. If a report is required, we verify the information, send it to HMRC and provide the Seller with a copy as required. If a Seller does not provide legally required information, we may need to restrict selling features until the issue is resolved.

CardzLocal shows Seller status and the identity or contact information required by law before a Buyer orders. When you buy, the Seller receives the information needed to fulfil the order, such as your name, delivery address, selected fulfilment method and relevant order messages. A carrier may receive your name, address, contact details and tracking information to deliver the item. When you sell, the Buyer receives the information needed to complete the order and the Seller information that must be disclosed by law.

We do not make private collection records, private binder costs, payout identifiers, identity documents or internal account-health records public. A Seller must use Buyer information only to fulfil the order, meet legal obligations and resolve a permitted order issue. Business Sellers are responsible for their own privacy obligations when they use information for their own purposes.

CardzLocal is not the Seller of a Marketplace item unless the listing or checkout clearly says that we are. Sellers may be independent traders or private individuals. Their own privacy practices may apply to information they receive. For a purchase sold directly by CardzLocal, CardzLocal is responsible for the relevant customer and order information.

Storefronts, public profiles, listings and content you choose to publish to a Gallery, Community or CardzConnect audience can be seen by other users. Some public pages may be visible without an account or indexed by search engines. The Platform will identify available audience and privacy settings. Check those settings before publishing. Information you deliberately share publicly can be copied, downloaded, cached or captured by other people; changing a setting or deleting the original may not remove copies already made elsewhere.

Collection and binder records are private unless you publish them, share them or grant another person access. A contribution to a shared binder requires your express permission. We process sharing settings and access records to apply your chosen permissions, prevent unauthorised changes and keep an audit trail.

We may display public username, profile image, selected badges, follower counts, public listings, seller ratings and other details you choose to show. Internal account-health measures, security flags, private addresses and payout details are not public. You can edit or remove public material using the relevant feature, subject to open orders, reports, legal retention and technical backup cycles.

CardzConnect is a separate feature restricted to adults aged 18 or over. You cannot access it until the required age and identity review has been completed and manually approved. We may ask for government-issued photo identification or other suitable evidence through a secure in-product process. At present, the product specification calls for manual review. If an external verification provider or a different verification method is introduced, we will identify it and explain its data use before information is sent to it.

Verification information may include your legal name, date of birth, the image or details on an identity document, the information needed to match the document to you, the outcome and date of the review, a reviewer’s limited notes, and an appeal or re-check record. We restrict this information to authorised verification and safety reviewers. We do not display identity documents or full date of birth on your public profile. We aim to retain the verification outcome and minimum audit information rather than a copy of your identity document. Raw evidence is kept only while needed to complete the review and any appeal, or longer where a documented safety, fraud, legal or dispute reason requires it; it is then securely deleted. The precise retention schedule must be confirmed before launch and will be stated in the Connect Verification Notice.

Your verification information is not used for advertising, public badges beyond the verification status, or general AI model training. A verified status means only that CardzLocal completed the stated age/identity check. It is not a guarantee of your conduct or the authenticity of items you list.

CardzLocal does not impose a universal 18+ rule on all features. General CardzLocal features may be used by under-18s where permitted by the Terms and applicable law. We recognise that collecting communities may be used by children. Where children are likely to access a feature, we will take their needs into account and apply age-appropriate privacy and safety measures, including high privacy settings by default for children, clear information, limiting unnecessary location use and avoiding pressure to disclose more information. Optional public sharing should require a clear choice. We do not use CardzConnect for under-18s, even with parental permission.

If we rely on consent to process a child’s personal information, we will obtain parental authorisation where required by law, including for a child under 13. A parent or guardian who believes a child has provided information improperly can contact us using the privacy contact details above. We may ask for information reasonably needed to confirm authority and protect the child.

CardzLocal may use automated tools, including classifiers, to help detect spam, scams, account abuse, suspicious payment activity and content that appears to breach rules. In CardzConnect, automated checks may analyse messages or other content to identify prohibited sales, promotions, payments, trades or collection arrangements, as well as other safety issues. Relevant content may be flagged, filtered, temporarily limited or sent to an authorised moderator for review. Users may report or appeal a moderation action through the in-product controls or Support Hub.

We may also use usage and listing information to order search results, show relevant features, operate boosts, prevent duplicate rewards, rate-limit rapid Price Check requests or calculate private account-health indicators. Public ranking or seller ratings are distinct from internal account-health measures. Price Check information is used to return a card or product estimate; estimates are not guaranteed valuations.

If a decision about your legal rights or another similarly significant matter is made solely by automated processing, we will only do so where the law allows and with required safeguards. Where the law gives you a right, you can request an explanation, express your view, ask for human intervention and challenge the decision. An automated flag alone does not prove misconduct. Before introducing a new AI use or significant profiling, we will assess its effect on people and update this Policy or provide a just-in-time notice where required.

If an AI or market-data supplier receives information to provide a feature, we will limit the information to what is needed for that feature and identify the provider in the relevant provider or feature notice. CardzLocal does not send private user content or personal information to an unspecified service to build a general AI-training dataset by default.

CardzLocal and its providers may use cookies, local storage, pixels, SDKs, scripts or similar technologies. These technologies can store or access information on your device and may also process personal information such as an online identifier. The separate Cookie Notice will list the actual technologies, providers, purposes, whether they are first- or third-party, how long they remain and how to change your choices.

Essential and security. Sign-in, authentication, fraud and security checks, routing, remembering a basket, saving your cookie choice and providing a feature you requested. These may qualify for a PECR exception where strictly necessary.

Appearance and preferences. Remember display, accessibility or other choices you make. A narrow PECR appearance exception may apply only if its conditions are met and a simple, free way to object is available.

Statistics and service improvement. Measure visits, errors and performance so we can understand and improve CardzLocal. We will obtain consent unless a narrow PECR statistical-purposes exception applies. If we rely on that exception, the technology will be used only for that statistical purpose, we will explain it clearly and provide a simple, free way to object.

Advertising, cross-site or cross-device tracking. If introduced, used only with the consent required by law and described in the Cookie Notice. We do not use an advertising or cross-site tracking technology for a purpose merely because it is convenient or funds the service.

You can use the cookie controls to accept, reject or customise optional technologies, and return later to change your choice. Withdrawing consent does not affect processing that was lawful before withdrawal. Strictly necessary technologies may still operate where the law permits. If an analytics or preference technology is used under a statutory exception rather than consent, you will be given the information and objection method required for that exception.

Where a cookie or similar technology processes personal information, we also identify a UK GDPR lawful basis for that later processing. PECR permission to store or access information on a device is separate from the UK GDPR lawful basis for processing personal information obtained through it.

We send transactional, security, service and legal messages needed to operate your account or complete a transaction, such as order updates, payment confirmations, verification notices, policy changes and security alerts. These messages are not marketing and cannot always be switched off while you use the relevant feature.

We send optional marketing by email, text or other electronic channel only where permitted by applicable marketing law. You can opt out at any time using the unsubscribe link or preference controls. We keep a minimal suppression record when needed to make sure we respect your opt-out. You can still receive service messages after opting out of marketing.

We share information only where it is needed for the purposes in this Policy, where you ask us to, or where the law permits or requires it. Recipients may include:

Base44, Inc. CardzLocal’s current application hosting and technology provider. Base44 processes end-user data on CardzLocal’s instructions under its Data Processing Addendum, and may use sub-processors to provide hosting, storage, backend, security, analytics or other enabled platform functions. See Base44’s Privacy Policy, Data Processing Addendum, Security information and Trust Center.

Stripe and relevant Stripe entities. Payment processing, connected accounts, seller onboarding, payouts, refunds, fraud prevention, disputes, identity checks and payment-provider compliance. Depending on the activity, Stripe may act as a controller or processor. See Stripe’s privacy information and the terms shown in Stripe’s payment or connected-account flow.

Buyers, Sellers and other users. Limited profile, order, fulfilment, communication, Seller-status or public content information needed to complete an order, respond to a swap or use a feature. We do not provide access to unrelated account data.

Delivery and tracking providers. Buyer and Seller contact or address details, package and tracking data needed to deliver an order or show tracking status.

Identity, age-verification and compliance providers. Only if a provider is used for a verification or compliance feature. The provider’s name and role will be disclosed in the in-product verification flow before information is sent. CardzConnect review is specified as manual at present.

Price, analytics, AI, messaging and support providers. Information needed to return a Price Check result, deliver a user-requested feature, send notifications or email, support the service, or moderate content. The providers actually enabled for CardzLocal will be named in the current provider list or feature notice.

Professional advisers, insurers and auditors. Information needed for legal advice, accounting, audit, insurance, business continuity or claims.

Courts, regulators, law enforcement and public authorities. Information required by law, court order or a lawful request, or reasonably necessary to prevent serious harm, fraud or unlawful activity. Where required, this includes seller reporting to HMRC.

A business successor. Information may transfer as part of a merger, restructuring, financing, sale or transfer of CardzLocal or the relevant service, subject to appropriate safeguards and notice where required.

We do not sell personal information. We do not share it with third parties for their unrelated direct marketing without the permission required by law. A third-party provider may use information under its own privacy notice for its independent legal, security or payment purposes; those purposes are described in that provider’s notice.

Some of our providers may process or store personal information outside the United Kingdom. The CardzLocal application is hosted on Base44. Base44’s published security information says app data is stored in the United States by default; its sub-processors may operate in other countries listed in its current Trust Center. The actual workspace region and sub-processors enabled for CardzLocal must be confirmed before this Policy is published.

Stripe and other providers may also process information in countries outside the UK. Where a transfer is restricted by UK data-protection law, we use a valid transfer mechanism, such as UK adequacy regulations or an appropriate safeguard such as the UK International Data Transfer Agreement or UK Addendum, and carry out any required transfer assessment. You can ask us for information about the safeguard that applies to a particular transfer using the privacy contact above.

We keep personal information only for as long as needed for the purposes for which it was collected, to meet legal or payment-provider requirements, or to establish, exercise or defend legal claims. We review what we hold and erase or anonymise it when it is no longer needed. The current retention schedule must be kept with the privacy contact details and available on request.

Account and profile information. While your account or relevant profile is active. After closure, we delete or anonymise it when it is no longer needed for open orders, disputes, security, legal duties or claims.

Orders, payments, refunds, fees and payouts. For the period required by accounting, tax, payment-provider, chargeback, consumer or legal-claim requirements, then delete or anonymise unless another lawful reason applies.

Seller reporting and due-diligence records. Where CardzLocal is required to report seller information to HMRC, we keep the information collected and verified, due-diligence steps and report copies for five years after the end of the relevant reportable period, as required by the HMRC platform-reporting rules.

Connect identity evidence. Until the manual verification decision and any relevant appeal are complete, then securely delete it as soon as possible unless a documented safety, fraud, legal or dispute need requires longer retention. We may keep a minimal verification outcome and audit record while Connect is active and for as long as reasonably needed for legal compliance or claims.

Moderation, safety reports and dispute evidence. While investigating and handling the report or dispute, any appeal, and any related legal, safety or fraud-prevention need. We then delete or anonymise it under the retention schedule.

Security and diagnostic logs. For a limited period needed to maintain security, investigate incidents, prevent abuse and diagnose technical problems. Incident records may be retained longer where needed for a claim or legal duty.

Cookie and preference records. For the lifetime needed to apply your choices, meet the purpose of the technology and, where required, demonstrate consent or objection. The Cookie Notice will give the actual technology lifetimes.

Marketing preferences. Until you withdraw consent or opt out, with a limited suppression record retained as needed to respect that choice.

Backups. Until the normal secure backup rotation removes them, unless an incident or legal hold requires preservation.

Aggregated or anonymised statistics. May be retained for longer if the data can no longer reasonably identify you.

We may retain information for longer where a law, a legal hold, a payment dispute or a substantiated safety or fraud matter requires it. We do not retain identifiable information indefinitely merely in case it might be useful.

We use technical and organisational measures designed to protect personal information against unauthorised access, loss, alteration or disclosure. These may include access controls, role-limited staff access, multi-factor authentication for staff systems, audit logs, secure handling of identity evidence, encryption where appropriate, backups and monitoring. We review these measures against the information and risks involved and require our processors to protect information under their agreements.

No internet service or storage system can be guaranteed completely secure. Keep your credentials private, use strong unique passwords and contact us promptly if you believe your account or information is at risk. We will investigate suspected personal-data incidents, document them and notify the ICO or affected people where the law requires it. A reportable UK GDPR breach must be reported to the ICO without undue delay and, where feasible, within 72 hours of awareness; people are notified without undue delay if the breach is likely to create a high risk to their rights and freedoms.

Depending on the purpose and lawful basis, you may have the right to:

ask for access to your personal information;

ask us to correct inaccurate or incomplete information;

ask us to erase information where the legal conditions are met;

ask us to restrict processing in certain circumstances;

object to processing based on legitimate interests, including profiling based on those interests;

object at any time to the use of your information for direct marketing;

receive certain information in a portable format where the right applies;

withdraw consent where we rely on consent, without affecting processing that took place before withdrawal; and challenge certain decisions made solely by automated processing and request human intervention where the law provides that right.

These rights are not absolute. We may need to retain or use some information to complete an order, meet a legal obligation, protect another person’s rights, prevent fraud or establish, exercise or defend a legal claim. If we cannot comply fully, we will explain why unless the law prevents us from doing so.

To make a privacy request, use our contact form or email support@cardzlocal.co.uk. Tell us what you are asking for and which account or feature is involved. We may ask for proportionate information to confirm your identity or authority before disclosing or changing account data. Do not email identity documents unless we specifically direct you to an approved secure channel.

You may also make a data-protection complaint through our contact form or by emailing support@cardzlocal.co.uk. Please identify your message as a privacy complaint so it can be directed to the appropriate reviewer. We will acknowledge receipt within 30 days, investigate without undue delay, keep you informed and tell you the outcome without undue delay. If you remain unhappy, you can complain to the UK Information Commissioner’s Office (ICO) at ico.org.uk/make-a-complaint. You may also seek a legal remedy where available.

We may update this Policy when CardzLocal changes, laws or regulator guidance change, or we introduce a new data use or provider. We will publish the new version with an updated date. If a change materially affects your rights or the way we use your information, we will provide reasonable notice through the Platform or by email where available. If consent is required for a new purpose or device technology, we will request it before that processing starts.

This content is admin-managed and may be updated at any time. Legal text shown here is controlled by CardzLocal staff through the CMS.
Questions about our policies?

We use cookies to keep you signed in and, with your permission, to understand how CardzLocal is used. See our Cookie Policy.