EQ privacy policy covering account, order, payment, reseller and browser-storage information, recipients, retention and rights.
Version date: 2026-11-09 · Operator details pending
01. Controller and contact
EQ provides the store and guides through equsdt.com. This policy describes information used for accounts, guest orders, payments, delivery, balance, reseller/API access and guides. Browsing public goods and articles usually needs no registration, but necessary access and security logs may be generated.
[To complete: controller legal or individual name, country or region, contact address and privacy request email]. Operator details, providers and hosting locations are not confirmed. This version is awaiting completion.
02. Accounts and authentication
Registration, sign-in, password recovery and profile changes use email, nickname, password-verification information, codes and account status. Security functions may record sign-in time, IP address, browser/device description, sessions and operations for authentication and abnormal-activity detection.
Two-step verification stores binding status and necessary verification material. A compatible TOTP app generates codes on your device; this feature does not itself require Google-account authorisation. Optional Google or Telegram sign-in receives the identifiers and profile information you authorise, as described in the actual sign-in flow.
03. Orders, payments and delivery
Orders contain goods, variants, quantities, amounts, times, status, contact information, lookup verification and required delivery fields. Do not place unrelated identity documents, passwords or sensitive information in order notes.
Payment reconciliation uses channel, transaction identifier, amount, currency, status and refund records. On-chain payments may involve network, address, transaction hash and confirmations. Public blockchain records may be inspected by others and the store cannot delete a broadcast transaction. We do not request private keys or seed phrases.
Codes, licences and manual delivery content are associated with orders for retrieval, fulfilment and support. Member balance records contain top-ups, spending, refunds and adjustments.
04. Resellers, APIs and referrals
Applications use supplied contact details, business website or description and review progress. Approved integrations process credential identifiers, permissions, calls, purchase orders, balance, reconciliation and settlement records for access control, fulfilment and abuse prevention.
When referral attribution is enabled, referral and visitor identifiers, source, time and related orders may be stored for attribution and settlement. Resellers must not supply unrelated downstream information or use access to inspect other users’ data.
05. Browser storage, email and downloads
Local storage supports sign-in state, basic profile cache, cart and language/interface preferences. Guest lookup credentials use session storage, as do some temporary sign-in flows. Enabled referrals may store attribution and visitor identifiers. Clearing storage or signing out may require signing in again, re-verifying an order or restoring a cart.
Configured email services send verification or transactional notices based on settings and events. Guide and download requests may generate time, resource-path, IP and browser logs. External sites have their own policies. Any analytics, advertising or non-essential scripts enabled later require appropriate disclosure and consent/choice mechanisms where required; this policy does not replace them.
06. Purposes and lawful basis
Information supports requested account services, transactions, payment verification, delivery, support, reseller integration, security, complaints and applicable legal obligations. The lawful basis depends on each activity and applicable law. Obtain valid consent where required; reading this policy is not unlimited authorisation for all uses.
Order notes and delivery information are not to be used for unrelated purposes. New purposes, sensitive-information handling or disclosure to another independent controller require the appropriate additional notice and consent or another valid lawful condition.
07. Providers, suppliers and international processing
Services may involve hosting/CDN, email, payment, enabled sign-in or verification providers, and suppliers or manual-fulfilment providers. Share only information needed for that task, such as order identifier, amount, variant or necessary delivery fields. Account passwords, TOTP material and full API secrets must not be sent to suppliers as procurement data.
[To complete: enabled provider names, purposes, data categories, contact details and privacy links; hosting and backup countries/regions; overseas recipient details and rights-request channels]. Update these disclosures when deployment or integrations change. Complete applicable international-transfer and separate-consent requirements before the relevant processing.
08. Retention and security
Keep information for the shortest period needed for fulfilment, support, reconciliation, security and legal duties. Account closure or deletion requests may not immediately remove transaction, dispute or security records that must lawfully be retained. Delete or anonymise information when no longer needed.
[To complete: actual retention periods or clear criteria for orders/accounting, security logs, reseller records and backups, deletion method and backup rotation]. There is currently no promise that every record is automatically erased after a fixed number of days.
The system uses access controls, authentication and related security mechanisms, alongside measures appropriate to the actual hosting, staff access and backup configuration. Address incidents and make legally required notifications; absolute security is not guaranteed.
09. Access, correction, deletion and withdrawal
Use available account, order, balance, session and API controls to view or manage information. Send requests for access, copies, correction, deletion, applicable consent withdrawal or account closure to the published privacy contact. The store does not currently promise one-click automatic closure or immediate erasure of all records.
We will apply necessary and proportionate identity verification and respond as required by applicable law. Withdrawal does not invalidate earlier consent-based processing. Explain lawful retention or technical limits on immediate deletion and restrict further processing appropriately. Refusing unnecessary processing should not prevent unrelated core services.
10. Minors, updates and complaints
Minors should use services under guardian guidance and any required consent. Children’s information requires the special safeguards and guardian-consent mechanisms required by applicable law. Guardians may report inappropriate processing for review.
Updates appear on this page. Material changes to purposes, categories, recipients or rights require further notice or consent where applicable. Questions and complaints may be sent to the published contact; remedies through competent authorities remain available.
易奇 EQ