ข้ามไปยังเนื้อหาหลัก
BlockVectra

นโยบายความเป็นส่วนตัว

อัปเดตล่าสุด: 2026-10-06

หน้านี้มีให้บริการเฉพาะภาษาอังกฤษเท่านั้น ซึ่งถือเป็นฉบับที่มีผลบังคับใช้ตามกฎหมาย

This Privacy Policy explains how BlockVectra collects, uses, shares and protects your personal information when you use the JSON-RPC API, the Data API, the Console and the related websites and documentation, and what rights you have.

Please read it together with the Terms of Service. Terms such as "Credits", "API key", "Console", "Contact email" and "compute unit (CU)" have the same meaning here as in the Terms of Service.

1. Who we are

Under applicable data protection laws, the controller of the personal information described in this Policy (called the "personal information processor" under China's Personal Information Protection Law) is the operator of the BlockVectra service ("BlockVectra", "we", "us" or "our"), which is your contracting party under the Terms of Service.

For privacy matters, write to the contact email (contact@blockvectra.com).

2. Scope

This Policy applies to the JSON-RPC API, the Data API and the Console that we provide, our website, documentation site and status page, and your communications with us, for example by writing to the contact email.

This Policy does not apply to services provided by third parties, including sign-in services such as GitHub and Google, the wallet and wallet provider you use, and the blockchain networks themselves. They handle information under their own policies.

This Policy replaces any other privacy policy or privacy notice previously published for the Service.

3. Information we collect

The information we collect is described below by source:

  • Sign-in information. If you sign in with a wallet signature (only externally owned accounts, i.e. EOA wallets, are supported; the sign-in page lists the supported wallet types), we store your wallet address; you only sign a sign-in message, the signature is not submitted to any blockchain and costs no fee, and we never ask you to sign a transaction. When you choose mobile wallet QR sign-in, the connection passes through the network of WalletConnect (Reown, Inc.), and Reown processes the wallet address and information required for the connection; the browser stores WalletConnect connection data in local storage. If you sign in with GitHub, we store the numeric ID and username of your GitHub account. If you sign in with Google, we store the unique identifier (subject ID) of your Google account.
  • Account and API key information. Your Account number, the identifier and name of each API key you create, and records of creating, renaming, rotating and revoking keys. The secret of an API key is shown only once, when it is created or rotated.
  • API usage records. When you call the JSON-RPC API or the Data API, we record usage; these records are used for metering, billing and showing your usage in the Console.
  • Console audit records. When you open an Account, sign in, sign out, manage sign-in methods, or create, rename, rotate or revoke an API key in the Console, we record the type of action, the time and your IP address, for security auditing.
  • Server and network logs. All our domains are proxied by Cloudflare, which as the edge network processes client IP addresses, kept under its own policy. Public endpoints that do not require an API key are rate-limited by client IP address.
  • Billing and top-up records. Charge records, top-up records (amount, currency, time and type) and your Credits balance. You can view these records in the Console.
  • Information you provide when you contact us or top up. Top-ups are completed by on-chain transfer (USDT / USDC) to the Account's dedicated address. We process: the Account's top-up address; on-chain transfer records (payment address, transaction hash, amount, network, and time, which are publicly visible on the blockchain by their nature); the email address, email content, and attachments you provide when you contact us (used to handle issues such as transfers to the wrong chain, and for support); materials used to prove Account ownership if you have lost every sign-in method; and, where the law or our compliance requirements call for it, information about your identity and source of funds.

4. Purposes and legal bases

We use your personal information for the purposes below. Where data protection laws of the EU, the UK or similar regions apply, our bases are performance of a contract, compliance with a legal obligation, our legitimate interests and, where the law requires it, your consent; where the Personal Information Protection Law of the People's Republic of China applies, these correspond to what is necessary to conclude or perform a contract, what is necessary to comply with a legal obligation and, where the law requires it, your consent; the legitimate-interests basis listed in this Policy applies only in the EU, the UK and similar regions.

  • Providing and operating the Service. Creating Accounts and signing you in, issuing and managing API keys, routing requests and enforcing limits, metering, billing and settlement, and showing usage and balance. Basis: performance of a contract.
  • Handling top-ups and billing disputes. Checking payments, handling metering disputes, dealing with payments that are reversed or charged back, and verifying who owns an Account when you have lost every sign-in method. Basis: performance of a contract; our legitimate interests.
  • Security, abuse prevention and enforcing the Terms. Security auditing, rate limiting and limits on account opening, detecting and dealing with leaked API keys, preventing abuse of Free Credits (including deactivating surplus Accounts created automatically by the same person), protecting the Service and other users, and enforcing the Terms of Service. Basis: our legitimate interests; performance of a contract.
  • Legal compliance. Verifying identity and source of funds where necessary, keeping accounting and tax records, and responding to lawful requests from courts and authorities. Basis: compliance with a legal obligation; our legitimate interests.
  • Communications and notices. Replying to your emails and sending you service-related notices. Basis: performance of a contract; compliance with a legal obligation; our legitimate interests.
  • Operations and improvement. Troubleshooting, capacity planning and improving the Service. Basis: our legitimate interests.

5. Public nature of on-chain data

Transactions you submit to blockchain networks through the Service are broadcast to public networks, can be viewed by anyone and cannot be changed or deleted, and we cannot delete them for you.

Wallet addresses are publicly visible on the blockchain by their nature.

If more than one sign-in method (for example, a wallet and a GitHub or Google account) is linked to your Account, we will know that these identities belong to the same Account.

6. Local storage and cookies

The Console stores your sign-in session credential and the sign-in method you last used in your browser's local storage to keep you signed in and make your next sign-in easier. A session ends when you sign out. You can clear local storage in your browser at any time.

Our website remembers whether you have dismissed a language prompt in browser local storage; this can be cleared in the browser at any time.

Our website and the Console use a cookie named bv_lang (valid for blockvectra.com and its subdomains, for one year) to remember the language you selected.

On our website (blockvectra.com), documentation site (docs.blockvectra.com) and Console (console.blockvectra.com) we use Cloudflare Web Analytics to count visits in aggregate, such as the pages viewed, the referring site, and the visitor's country, browser and device type. We also use Google Search Console, which reports how our pages appear in Google Search based on Google's own search data.

To measure channel performance, our servers record the referring website's domain, source parameters in the link, the landing page and country, without using cookies, recording IP addresses or using third-party tracking for these statistics.

7. Sharing and recipients

We share information in the following cases, with the following categories of recipients:

  • Infrastructure providers. Providers of hosting, storage and backup, and Cloudflare, which provides network acceleration (CDN) and security protection; they process information for us.
  • Sign-in providers. If you sign in with GitHub or Google, they handle your sign-in process and process the related information under their own policies.
  • Blockchain networks. Transactions you submit through the Service are broadcast to public networks (see Section 5).
  • Authorities, courts and professional advisers. Where the law requires it, or where it is necessary to establish, exercise or defend legal claims, we disclose information to courts, regulators and law enforcement; we disclose to lawyers, auditors and other professional advisers under a duty of confidentiality.
  • Successors to the business. If the Service is transferred or reorganized between us and an affiliate or a successor to the Service, information moves with the business to the successor.

8. International transfers

The Service is delivered over a global network. We and the providers above may process your personal information outside the country or region where you live, where the level of data protection may differ from that where you live.

9. Retention

Closing an Account does not mean all data is deleted immediately (see Section 25 of the Terms of Service).

  • Logs and audit records: kept as needed; information processed by Cloudflare is kept under its own policy.

10. Security

We take reasonable technical and organizational measures to protect your personal information. For example: the secret of an API key is shown only once, when it is created or rotated; sign-in sessions have an expiry and an inactivity timeout.

No system is completely secure. Please also keep your wallet, sign-in credentials and API keys safe (see Section 6 of the Terms of Service).

11. Your rights

Under applicable data protection laws, you may have the rights below. These rights are not absolute in every situation; for example, records we must keep because of legal or financial obligations, the legitimate interests of others, and data that is already public on a blockchain may limit how a right can be exercised.

  • to access your personal information, obtain a copy and learn how we process it;
  • to have inaccurate or incomplete personal information corrected;
  • to ask for your personal information to be deleted;
  • to ask us to restrict processing, or to object to processing that we carry out on the basis of our legitimate interests;
  • to receive the personal information you provided to us in a commonly used, structured and machine-readable format, or have it transferred to another party (data portability);
  • to withdraw your consent (withdrawal does not affect the lawfulness of processing based on consent before it was withdrawn);
  • to lodge a complaint with the data protection authority where you live.

12. How to exercise your rights

Write to the contact email, saying which right you want to exercise and what your request covers. The Service currently has no self-service deletion or export: you can view your own usage, charges and top-up records in the Console, and we handle other requests manually by email.

To protect Accounts, we may ask you for information that shows you control the Account concerned (for example, the identity you sign in with and your top-up receipts) before we act on a request.

Where a request is manifestly unfounded or excessive we may, where the law allows, charge a reasonable fee or decline to act on it.

Records we cannot delete because of legal or financial obligations are mainly billing, charge and top-up records; and we cannot delete data on a blockchain.

13. Children

The Service is for people aged 18 or over and is not directed at anyone under 18 (see Section 3 of the Terms of Service). If you believe we may have collected such information, please tell us at the contact email.

14. Changes to this Policy and notices

We may change this Policy; changes take effect when posted.

This Policy is available in Chinese and English. If the two versions differ, the English version prevails, except where applicable law requires another language version to prevail.

15. Contact us

If you have any questions about this Policy or your personal information, contact us through the Contact Us page or the contact email (contact@blockvectra.com).