Skip to main content
CryptPays
Product Supported Assets Pricing Developers Security Documentation
Start integrating
CryptPays
Product Supported Assets Pricing Developers Security Documentation
Start integrating

Legal

Privacy Policy

This policy explains how the CryptPays service processes information through its public website, contact form, Merchant API, and payment lifecycle.

Last updated: September 29, 2026

On this page

Scope and operator Information processed How information is used Sharing Cookies and tracking Retention Choices and rights Contact

1. Scope and operator information

This policy applies to the CryptPays public website, contact form, and Merchant API. References to “CryptPays,” “we,” or “the service” refer to the operator of those services. Operator and controller details will be updated when the applicable operating entity is established and before a formal entity launch.

The policy does not control a merchant's own website, wallet, customer relationship, or privacy practices. Merchants are independently responsible for explaining how they process their customers' information.

2. Information we process

Contact inquiries

When you use the contact form, we receive your name, email address, selected subject, and message. The form does not ask for a telephone number, country, wallet secret, or transaction history. Please do not send private keys, seed phrases, passwords, or other credentials.

Website and security information

Web servers, security controls, and infrastructure providers may process an IP address, browser or user-agent information, request time, requested URL, response status, and related diagnostic or security metadata. This information helps deliver the website, protect the service, investigate misuse, and troubleshoot faults.

Merchant API and payment information

To provide a payment lifecycle, CryptPays processes data supplied to or generated by the Merchant API. Depending on the request and network, this can include a callback URL, merchant payout address, generated deposit address, canonical asset ticker, selected priority or callback settings, payment UUID, amounts represented as decimal strings, confirmation or finality state, transaction identifiers, and callback delivery metadata.

Normal Merchant API requests do not require an API key or merchant account. That does not make payment or network information anonymous: callback URLs, internet metadata, wallet addresses, and public-chain activity may be capable of association with a person or business.

Public blockchain information

Supported blockchain networks publish transaction information independently of CryptPays. Addresses, transaction hashes, amounts, token contracts, output indexes, confirmations, and related data may be visible publicly and may remain on distributed ledgers permanently. CryptPays cannot edit or delete a public blockchain record.

Compliance and risk information

CryptPays does not describe identity or business verification as a routine condition of the normal keyless Merchant API. We may, however, request and process identity, business, transaction, source-of-funds, ownership, licensing, or related information where reasonably necessary for applicable law, sanctions or compliance obligations, fraud or abuse review, risk controls, a service-provider requirement, or protection of the service and its users.

3. How we use information

We use information as reasonably necessary to:

  • provide, operate, secure, maintain, and troubleshoot the website and payment service;
  • create payment addresses, detect supported deposits, apply confirmation or finality rules, forward qualifying payments, and deliver callbacks;
  • respond to contact, support, partnership, and press inquiries;
  • prevent, detect, and investigate fraud, abuse, attacks, configuration errors, or prohibited activity;
  • comply with applicable legal, sanctions, compliance, recordkeeping, or service-provider obligations;
  • enforce the Terms of Service and resolve disputes; and
  • understand reliability and improve operation of the service without adding unrelated advertising profiles.

The legal basis for processing depends on the applicable law and context and may include performance of a requested service, legitimate operational or security interests, compliance with legal obligations, and consent where consent is required.

4. When information may be shared

We may disclose information only as reasonably necessary to categories of recipients such as hosting, network, communications, email, blockchain or RPC, security, and other technical service providers; professional advisers; competent authorities where legally required; and a successor involved in a merger, acquisition, financing, reorganization, or transfer of the service.

Public blockchain data is shared through the operation of the relevant network, not through a private CryptPays database alone. A merchant also receives payment and callback information configured for that merchant's endpoint.

CryptPays does not currently sell personal information in the ordinary meaning of selling data for money. Some privacy laws define “sale” or “sharing” more broadly; if practices change in a way that creates additional rights, this policy and available controls should be updated.

5. International processing

The internet, blockchain networks, and service providers may process information in countries other than the country where you are located. Those countries may have different privacy laws. Where applicable law requires a particular transfer mechanism or safeguard, CryptPays will address that requirement as part of the relevant operating arrangement.

6. Cookies and tracking

The public website uses necessary session and request-security mechanisms to operate forms and protect requests, including session and CSRF protections. These mechanisms are not used to build advertising profiles.

CryptPays does not currently load third-party advertising or analytics trackers on the public website. No nonessential tracking has been added to these pages, so the website does not show a consent banner solely for necessary session and security cookies. This policy will be updated if those practices change.

7. Contact submission handling

The contact form validates the submitted fields, applies a honeypot and request throttling, and queues an email to the configured CryptPays recipient. The contact path does not create a dedicated database record for the inquiry. Copies or metadata may nevertheless remain in the application queue, sending and receiving mail systems, security logs, backups, or provider records according to their operational retention.

Submitting an inquiry does not enroll you in marketing communications.

8. Retention

CryptPays retains information for no longer than reasonably necessary for the purpose for which it was processed, including service operation, security, fraud prevention, legal or compliance obligations, accounting or recordkeeping, dispute resolution, and backup integrity. Retention can differ by data type and operational system.

CryptPays does not promise a fixed period where one has not been adopted and validated. Public blockchain information may remain available independently and indefinitely, even after related information under CryptPays’ control is deleted.

9. Security

CryptPays applies technical and organizational safeguards appropriate to the service and the nature of the information processed. No internet service, blockchain network, storage system, or transmission method can be guaranteed completely secure.

10. Choices and privacy rights

Depending on applicable law, you may have rights to request access to, correction of, deletion of, restriction of, or objection to certain processing of personal information. You may also be entitled to lodge a complaint with an applicable supervisory authority.

Requests may be limited where information must be retained for security, fraud prevention, legal claims, compliance, or recordkeeping, or where identity cannot be reasonably verified. CryptPays cannot alter or remove information recorded on a public blockchain.

11. Children and legal capacity

CryptPays is payment infrastructure intended for merchants, developers, and people with legal capacity to enter a binding agreement. It is not directed to children. If you believe a child has submitted personal information through the contact form, use the contact method below.

12. Changes to this policy

CryptPays may update this policy to reflect changes in the service, operating entity, providers, legal requirements, or data practices. The date at the top will identify the current version. Material changes may also be communicated through an appropriate service notice where reasonably practicable.

13. Contact

For a privacy question or request, use the CryptPays contact form and select the most relevant subject. Do not include a wallet private key, seed phrase, password, or other secret.

CryptPays

Developer-focused cryptocurrency payment infrastructure with automatic forwarding and signed callbacks.

Product

Product overview Supported assets Pricing Security

Developers

Developer overview Documentation Merchant API

Company

About Contact

Legal

Privacy Terms Restricted jurisdictions
© 2026 CryptPays. Cryptocurrency payment infrastructure for developers.