On this page
Company details
CLOUDWAY DIGITAL TRADING LIMITED operates PSN:B2B. PSN:B2B remains the service brand.
- Legal name
- CLOUDWAY DIGITAL TRADING LIMITED
- Jurisdiction
- Hong Kong
- Business registration number (BRN)
- 80722519
- Company registration number (CRN)
- 3814901
- Registered office
- Unit 1501, 15/F, Wing Tuck Commercial Building, 177-183 Wing Lok Street, Sheung Wan, Hong Kong
- [email protected]
Operator effective from: 2026-09-16
These details do not automatically transfer earlier contracts, account balances or claims to a new party. The contracting party and payment arrangement must be identified for the relevant order.
1) Scope
This policy covers visitors to psnb2b.org, registered business customers and people who contact PSN:B2B. The service supplies digital PlayStation Store codes to businesses and resellers; it is not designed for children. Internal website endpoints do not mean that a public ordering API is available.
2) Information we process
For an account, we process your email address, an account identifier and a password hash. We also process business contact details you provide, sign-in and session information, referring pages and traffic-source information.
Orders and balance top-ups create records of products, amounts, currency, invoices, payment status, transaction references and code delivery. A support request contains your email, topic, message and any order details or screenshots you choose to send through the available support channels. Do not send wallet private keys or account passwords.
Technical information includes IP addresses, timestamps, browser and device details, pages visited, cookies and similar identifiers. The analytics and IP-lookup uses are explained separately below.
We also keep the accepted contract text and its checksum, version, language, account, time and acceptance action, and the seller details linked to new transactions. Analytics choices are recorded separately; agreeing to sales terms is not analytics consent.
3) Why we use this information
We use account and transaction records to sign you in, process payments, reconcile balances, deliver purchased codes and investigate order problems. Support communications let us respond to requests. Technical records help protect accounts, limit abuse and diagnose service errors. Analytics helps us understand visits, traffic sources and completed registrations, top-ups and purchases. Records may also be needed to meet legal obligations or handle disputes.
4) Legal grounds and this notice
The applicable legal grounds depend on the purpose of processing and the law that applies to you. They can include performing a contract, complying with legal obligations and legitimate interests such as account security and fraud prevention. Where consent is required by applicable law, that requirement is separate from this notice. Reading this policy, browsing the site or accepting commercial terms does not itself record separate analytics consent.
5) Service providers and recipients
Payment processing
CosmoPAY receives the customer email, invoice amount and currency, order reference and related payment instructions when a crypto invoice is created. Payment status and transaction details are used to reconcile the payment and account balance. We do not ask for your wallet private keys.
Notifications and email
Telegram carries operational notifications about registrations, invoices, payment requests and support messages. Depending on the event, these can include email, message content, order or invoice references, amounts, traffic source, IP address and available country, city, ISP and ASN information. Email correspondence is also processed through the mail services used by the sender and recipient.
IP lookup
For IP geolocation, our server sends only the IP being looked up to IPWHOIS over HTTPS. The response can contain an approximate country and city, internet service provider (ISP) and autonomous system number (ASN). It is not GPS or proof of your location. A failed or rate-limited lookup does not prevent registration, payment processing or a support request.
Analytics and other recipients
Google receives the analytics information described in section 7. Hosting and infrastructure services process data needed to run the website and its records. Information may also be disclosed for lawful requests or disputes where applicable. We do not sell personal information.
6) Retention
Retention depends on the record and its purpose: maintaining an account, reconciling a payment, reviewing a code-delivery dispute, preventing abuse or meeting legal and accounting obligations. A request to close an account does not necessarily remove records that must be kept for those purposes.
Successful IP lookups may be reused from a limited server-memory cache for up to one hour. The lookup helper does not create a separate database or file log of IP queries. This does not remove IP information already included in operational notifications or other service records. Ask us about the records relevant to your request using the contact route below.
The analytics choice expires after 180 days. We keep a browser choice and a necessary preference cookie; signed-in account choices and decision records are stored separately. Contract evidence may need to remain for legal or dispute purposes even when an account closes. A privacy request is reviewed against the relevant retention duty; it is not a promise to erase every record immediately.
7) Cookies and optional analytics
Your choice
Necessary cookies and browser storage support sign-in, session security and your preferences. Optional Google Analytics 4 (GA4) stays off until you separately choose Allow analytics. Reject analytics is available alongside it. Shopping does not depend on that choice. Use Privacy settings at the bottom of the site to change or withdraw it.
When events can be sent
With current consent, browser analytics measures page visits and interactions. The server also checks the account's current consent before sending registration, invoice creation, confirmed top-up and purchase events to Google. Browser-triggered events additionally require that browser's consent cookie. Unknown, refused, withdrawn or expired consent blocks sending. Payment callbacks check current account consent without assuming consent from a payment. Skipped events are not sent later.
What analytics can contain
Permitted events may contain a client or account identifier, event or transaction reference, amount, currency, products and a permitted traffic-source category. These identifiers are pseudonymous, not anonymous. We do not send email addresses, SHA-256 email hashes or Google user-provided data through this integration. Advertising consent is not included. The installed Yandex Metrica component is inactive while no project counter is configured; it is also gated by analytics consent.
Withdrawing consent
Withdrawing stops future optional browser analytics immediately and, when the choice is saved, stops account-based server analytics. If saving fails, analytics in this browser stays off and the settings display an error so you can retry. Previously sent records are not automatically deleted; contact us about erasure. Blocking necessary cookies may prevent sign-in. Operational payment, security and support processing described elsewhere is separate from optional analytics.
8) Security
The website uses HTTPS, account access controls and abuse-prevention measures. The IP lookup and the Google, CosmoPAY and Telegram API connections described here use HTTPS. Access credentials should be kept private. No transmission or storage method can be guaranteed completely secure.
9) Your rights and choices
Depending on applicable law, you may request access, correction, deletion, restriction or portability of your personal data, or object to certain processing. Where processing relies on consent, applicable withdrawal rights remain available. You may also have the right to complain to the relevant data-protection authority.
You can submit a privacy request without creating or signing in to an account. Describe what you want us to check and identify the relevant account or transaction where needed. Before disclosing or changing personal information, we may need to verify that the request concerns your data. Legal retention requirements and the rights of others may limit the outcome.
10) International processing
The services named in this policy operate across countries. Your information may therefore be processed outside your country of residence. Processing locations and provider retention practices depend on the service and the arrangements that apply to it. The provider links below give their own privacy information; they are not a promise that every record stays in one country or receives identical protections everywhere.
11) Third-party websites
A link to a payment provider or another website leads to a service with its own privacy practices. Review that service’s notice before providing additional information. This policy describes PSN:B2B processing, not every use a third party makes of data you give it directly.
12) Policy changes
When this policy changes, the revised text, version and last-updated date will appear here. The original publication date is kept separately. A policy update is a notice of processing; it is not a record of a separate consent choice.
13) Contact and privacy requests
Use the support form linked below and identify your message as a privacy request. Give a reply email, explain the information or action you need and include a relevant account or order reference if available. An account is not required. Avoid passwords, private keys and unrelated third-party data. The form is handled through Telegram as described in section 5; any identity checks and response deadlines depend on the request and applicable law.