Privacy Notice

Information collected & why

• Purchases: the name, email and ePack account supplied at checkout, Discord identity, break and spot selections, amounts, payment status, transaction identifiers and receipt/transfer records. Order details may be stored when checkout starts, even if payment is not completed. These identify orders, confirm payments, allocate cards, provide receipts, fulfil transfers and resolve disputes.
• Discord sign-in: Discord account ID, username and profile information returned by sign-in, plus server membership and relevant roles. These link your account, control member/admin access and verify PackLink+ benefits. Sign-in credentials and tokens are used to verify the session, not displayed publicly.
• Live Me & game progress: account-linked preferences, card and pack inventory, rewards, lineups, cosmetics, game saves and recorded results. These provide your dashboard, progression and cross-device recovery for the same Discord account.
• Collector and community activity: Rainbow goals/checklists, uploaded photos and crop settings, listings, claims and related activity you submit. These support your collection tools and the community features you choose to use.
• Support: your contact details, report or feedback text, relevant account/order identifiers and any attachments you provide. These allow investigation, replies and an audit trail of the issue.
• Usage analytics: persistent visitor and session identifiers, page paths, device category, referrer hostname, time on visible pages, search terms and feature-use labels. These help administrators understand usage and improve the service. Analytics may be linked to an account where identity is supplied; they should not be assumed anonymous.
• Technical and abuse-prevention information: service requests, errors and diagnostic information, plus account identifiers or fingerprints derived from IP address and browser information for media-abuse detection. Hosting and payment services may also process IP addresses, browser/device details and access logs under their own policies.

Who receives information

• Poole and authorised administrators access information needed to operate breaks, deliver cards, support users and investigate problems.
• PayPal processes break payments. Payment credentials are entered with the payment provider; PACKLINK uses payment confirmations and transaction records. Whop processes PackLink+ subscriptions and its linked Discord role arrangements. Each provider also applies its own privacy and dispute policies.
• Discord processes sign-in and server membership/role checks. Break announcements, team assignments and community posts may be sent to Discord channels. In-site reports and feedback may be forwarded to staff Discord channels, including the identifying details needed for investigation.
• Upper Deck ePack handles card trades and associated recipient/account details within its service.
• Railway hosts the live website and bot. Our database and file-storage service stores account records, photos, support attachments and usage analytics. Email providers handle support correspondence. These providers process information to deliver the service and may process information outside your country. Contact us for current provider details and questions about processing locations.
• Information may be disclosed when legally required, to address abuse or fraud, or to establish or defend legal claims.

What other members may see

Break results, community listings, selected display names and published game rankings/results may be visible to other users or Discord members. Optional Rainbow “Show Off” sharing publishes collection details, photos, display name/avatar and reactions to gallery visitors, including visitors without a live member sign-in. Private Rainbow goals are not a general public collection showcase.

Published content is not anonymous: profile-image URLs and photo links can contain account-related identifiers. Review photos and screenshots before uploading or sharing: they may contain names, account details or other personal information. Public or Discord content can be copied by others, and removing the original does not remove their copies.

Cookies & browser storage

Sign-in uses session cookies to keep access connected to your account. Browser storage also remembers settings, keeps local game recovery data and stores analytics visitor/session identifiers. Analytics storage is separate from essential sign-in storage. Live account saves are linked to your Discord identity; demo progress stays separate and local to the browser.

Clearing storage can remove local settings and demo progress and reset browser analytics identifiers; it does not delete records already stored by the service. Signing out is important on shared devices. These storage functions do not make a shared computer private.

Retention & protection

Order, payment and dispute records may need to be kept for accounting, legal obligations and resolving claims. Account progress, submitted content and support records are retained to provide the relevant services. A fixed retention schedule has not yet been published; contact us to ask what is retained for your account and why.

Access controls and account verification are used to restrict private records. No online service can guarantee absolute security. Avoid including sensitive information in community posts or support attachments unless necessary.

Your choices & privacy requests

Email e-packers@email.com to request access, correction or deletion of information, ask about service providers or raise a privacy complaint. State what you need and the account or order concerned; never send passwords or authentication codes.

We may need to verify that the request concerns your account before disclosing or changing private information. Deletion may be limited where records must be retained for legal obligations or disputes; applicable rights depend on your jurisdiction. You can also use Discord, PayPal, Whop and ePack controls for information held independently by those services.

If you are dissatisfied, you may contact the relevant privacy authority in your jurisdiction. Discord access is not required to send us a privacy request.