Privacy Policy - PSN Wholesale

Effective Date

This Privacy Policy is effective from 2026-07-31 and applies to psnwholesale.com, its quote-builder workspace, payment status flow, and one-time delivery notes.

Controller / Operator

The website is operated by PSN NETWORK LTD, company number 16191822, registered office 16 Ling Road, Victoria Docks, London, United Kingdom, E16 4AL. Contact: admin@psnwholesale.com.

Data We Collect

Inquiry details: name, email address, requested monthly volume, business type, and page URL.
Technical details: IP address, user agent, timestamps, and basic request logs used for security and troubleshooting.
Geolocation lookup: country, city, ISP, ASN, and timezone derived from IP address when available.
Order and delivery records: order ID, selected SKU and quantity, quote value, payment network, exact invoice amount, transaction reference, payment state, delivery timestamp, and claim records. Delivered code contents are not sent to analytics.
Analytics data: from the start of a standard production visit, Google Analytics may receive a pseudonymous client ID, page URL, referrer, campaign parameters, browser/device data, approximate location, and the order-stage events described below. Local development and automated QA visits are excluded.
Order communications: details you provide by email or another business channel agreed in writing.

Why We Use Data

To respond to quote access requests and business inquiries.
To send the quote-builder workspace and follow up on requested regions or volumes.
To verify B2B order context, prevent abuse, and protect the website.
To troubleshoot form delivery, email delivery, and security logs.
To keep records needed for business correspondence and dispute handling.
To measure which pages and acquisition sources lead to a requested workspace, an invoice, confirmed payment, and delivery-note access.

Data-Flow Matrix

The matrix follows data from its source to the operational record that uses it. A recipient is listed only where that part of the flow applies.

Source	Purpose	Recipient or system	Record class	Explicit boundary
Browser and web request	Serve pages, secure requests, diagnose errors, and measure standard production visits.	Hosting environment; Google Analytics for the limited production measurement described below.	Request/security log and pseudonymous analytics record.	No delivered code contents, inquiry email, wallet address, transaction hash, or delivery-note password is sent to analytics.
Buyer access request	Qualify the B2B inquiry, send workspace access, and follow up on requested volume or regions.	Website form handling, email delivery provider, and order notification tooling.	Inquiry and access-delivery record.	The public form does not request PlayStation credentials, seed phrases, private keys, raw codes, or unnecessary identity documents.
Signed-in quote workspace	Validate SKU selections, quantity, region mix, pricing, and the current order request.	Quote-builder and order runtime.	Quote version and order-state record.	A quote is not a stock guarantee; raw delivered codes are not analytics fields.
Invoice and blockchain transaction	Match the exact amount, network, wallet instruction, transaction reference, and payment state to one order.	Order runtime and blockchain data provider used for matching.	Invoice and payment-reconciliation record.	We do not request a buyer's private key or seed phrase; an analytics event excludes wallet address and transaction hash.
One-time delivery flow	Send the agreed delivery record and document access to it.	Delivery-note runtime and the order email channel.	Delivery timestamp and access-state record.	Delivered code contents are excluded from analytics and general inquiry logs.
Buyer support or claim submission	Trace the order, assess the reported issue, prevent duplicate claims, and record the outcome.	Support and order operations.	Case chronology linked to the order and affected batch reference.	Support does not require access to a customer's PlayStation account, password, or unrelated customer data.

Procurement Data Expectations

B2B buyers should expect us to handle only the information needed to qualify the inquiry, prepare a quote, confirm supply, deliver codes, and support the transaction. We may ask for business context such as company name, reseller channel, expected monthly volume, target regions, and preferred contact method, but we do not ask for retail customer passwords, PlayStation account credentials, seed phrases, or unnecessary personal documents through the website form.

Processors and Recipients

Depending on the action you take, data may be processed by our hosting environment, email delivery provider, order notification tooling, ip-api.com for IP lookup, blockchain data providers used to match an exact payment, and the quote-builder workspace. Google Analytics processes the limited production measurement data listed in this policy. We do not sell inquiry or order data.

Support, Order, and Dispute Records

When an order or support issue is discussed, we may keep records of the quote, order summary, payment reference, delivery timestamp, code batch reference, support messages, and resolution notes. These records help us validate order history, investigate activation or delivery questions, prevent duplicate claims, and maintain a consistent B2B support trail.

Retention

Inquiry and order correspondence is retained for as long as reasonably needed to manage the B2B relationship, meet accounting and recordkeeping duties, handle follow-ups, and resolve disputes. Server logs are rotated according to security and troubleshooting needs. Google Analytics cookies may remain in the browser for up to two years unless you clear browser data or the browser removes them earlier; analytics event retention is controlled separately in the GA4 property.

Security

We use server-side validation, rate limiting, encrypted transport where available, restricted configuration files, and separated operational credentials. No website can guarantee absolute security, but we take reasonable steps to protect inquiry and order records.

Buyer Security Expectations

Buyers should confirm the contact channel before sharing order details, keep payment transaction hashes and delivery archives, and avoid sending sensitive account credentials. If a buyer receives a suspicious message claiming to represent PSN Wholesale, they should verify it through admin@psnwholesale.com or the contact email listed on the Legal Notice.

Your Rights

You may contact us to request access, correction, deletion, restriction, objection, portability where applicable, or clarification about personal data connected to your inquiry. Browser privacy controls can restrict or clear analytics storage. These rights remain subject to identity verification and legal or business record obligations. Send requests to admin@psnwholesale.com.

Analytics and Browser Storage

Google Analytics starts with the initial page load on standard production visits. The on-site analytics panel is an information notice: selecting Got it remembers that the notice was closed, but does not start or stop measurement.

Operational storage: the quote-builder session cookie, security and CSRF state, form success state, one-time delivery view state, and the analytics-notice acknowledgement. These support the requested flow or remember that the notice was dismissed.
Google Analytics: Google may set _ga and _ga_* cookies and receive page views plus events such as access request, magic-link open, workspace authentication, quote calculation, invoice creation/view, confirmed payment, and delivery-note open.
Event boundary: analytics events may contain the order ID, USD quote value, USDT network, card quantity, page path, and acquisition labels. They do not contain the inquiry email, customer name, payment wallet address, blockchain transaction hash, delivery-note password, or delivered code contents.
Server event boundary: confirmed-payment and delivery-note events are sent only when a pseudonymous GA client ID was attached to the production order. Requests marked as local or automated QA are forced into analytics suppression and do not create measurement events.

Google may process analytics data outside the United Kingdom. Its published privacy resources include: