Login
privacy policy

Privacy Policy

This page describes how AGDor Pay collects, stores, protects, and processes account data, project settings, payment records, and technical logs in the current early-access stage.

Who we are and our role
  • AGDor Pay is software (SaaS) for orchestrating payment invoices, payment verification signals, and webhook notifications.
  • AGDor Pay is not a bank, payment system, money transfer operator, payment agent, or electronic money institution, and does not accept, hold, transfer, or process any funds.
  • All payments are made directly between the payer and the destination configured by the merchant (the merchant's wallet or the merchant's account on a third-party provider such as DonationAlerts or Binance).
What data we collect
  • Account data: the email address, display name, avatar URL, and stable identity identifier returned by the configured OAuth provider (Google or DonationAlerts).
  • Project data: project names, project codes, webhook URLs, webhook secrets, API key hashes, and wallet labels entered by the account owner.
  • Wallet and credentials data: wallet addresses, network and currency metadata, exchange account identifiers, and encrypted credentials required to read payment destinations (for example exchange API keys in read-only scope or DonationAlerts OAuth tokens).
  • Invoice and payment data: invoice identifiers, external identifiers, customer identifiers, amounts, currencies, statuses, transaction identifiers (TXID), and timestamps.
  • Technical logs: API request metadata, webhook delivery logs, provider request logs, audit records, and error logs used to operate, troubleshoot, and protect the Service.
What data we DO NOT collect or process
  • We never collect, store, or process bank card numbers (PAN), card verification codes (CVV/CVC), or card expiration dates. Card payments, when supported through a third-party provider, are entered directly on the provider's secure page and never pass through AGDor Pay.
  • We never collect, store, or process the personal payment credentials of the payer (for example the payer's wallet seed phrase, exchange login, or banking login).
  • We never have access to the merchant's funds, balances, or payouts at any third-party provider.
  • We never execute, sign, broadcast, or custody blockchain transactions.
Legal basis and purposes of processing
  • We process account data on the basis of contract performance (providing the Service the merchant signed up for) and legitimate interests (security, abuse prevention, service operation).
  • We process wallet and credentials data on the basis of contract performance — these inputs are required for the Service to function.
  • We process technical logs on the basis of legitimate interests — security monitoring, troubleshooting, abuse and fraud prevention, and service stability.
  • We do not sell personal data to third parties and do not use personal data for profiling or automated decision-making with legal effects.
Encryption at rest (data stored in the Service)
  • Sensitive credentials (exchange API keys, DonationAlerts OAuth tokens, webhook secrets, API keys) are encrypted with the AES-256-GCM authenticated encryption algorithm.
  • Each encrypted value uses a unique 12-byte random nonce (cryptographically secure) and a 16-byte GCM authentication tag, which protects both confidentiality and integrity (tamper detection).
  • The encryption key is derived from the master key of the Service through SHA-256 and is never stored alongside the encrypted data.
  • API keys are additionally stored only as a SHA-256 hash; the raw key is shown once at creation and compared on each request using constant-time comparison (hash_equals) to prevent timing attacks.
Encryption in transit (data moving between systems)
  • All traffic between the browser and the Service is encrypted with TLS/HTTPS. HTTPS can be enforced for all requests via the require-https deployment flag.
  • API requests from the merchant's system are authenticated with the X-Project-Code and X-API-Key headers; passing API keys in the URL query string is rejected by default.
  • Outgoing webhooks to the merchant's server are signed with HMAC-SHA256 (X-Payment-Signature header) using the webhook secret configured per project. The receiver is expected to verify the signature with a constant-time comparison.
Authentication and session protection
  • Sign-in is performed exclusively through OAuth 2.0 providers (Google, DonationAlerts). AGDor Pay does not store passwords and does not perform password-based authentication.
  • Session identifiers are 256-bit cryptographically secure random values. Session cookies are marked HttpOnly, Secure (when HTTPS is active), and SameSite=Lax to reduce exposure to cross-site attacks.
  • OAuth state cookies are signed with HMAC-SHA256 to prevent CSRF during the authorization flow.
  • All state-changing actions in the dashboard and admin panel are protected by a CSRF token (256-bit, constant-time validated).
Cookies
  • AGDor Pay uses only strictly necessary cookies: a session cookie (to keep the user signed in) and a CSRF cookie (to protect forms).
  • AGDor Pay does not use third-party advertising or cross-site tracking cookies.
  • A privacy analytics script (Microsoft Clarity) may be present on public pages. It does not process payment data, credentials, or any data from the authenticated area.
Data retention
  • Account and project data is retained for as long as the account is active and is deleted or anonymized within a reasonable period after account deletion.
  • Invoice, transaction, and webhook records are retained for the operational life of the Service and may be kept longer where required by applicable law (for example tax or AML record-keeping obligations).
  • Technical logs are retained for a limited period necessary for troubleshooting and abuse prevention, after which they are automatically purged.
Data sharing and subprocessors
  • AGDor Pay does not sell, rent, or trade personal data.
  • Payment data is exchanged with the third-party providers connected by the merchant (for example DonationAlerts, Binance). These providers are independent controllers of their own data processing, governed by their own privacy policies.
  • AGDor Pay may use infrastructure subprocessors (for example hosting) to operate the Service. Such subprocessors process only the data necessary to run the Service and are bound by confidentiality obligations.
Your rights
  • Depending on your jurisdiction (for example GDPR in the EU/EEA, 152-FZ in Russia), you may have the right to access, correct, delete, or restrict the processing of your personal data, as well as the right to data portability.
  • You may disconnect any third-party provider at any time by removing the wallet or rotating credentials at the provider side; AGDor Pay will no longer be able to read that destination.
  • To exercise your rights, contact the Service using the contact details published on the website.
International transfers
  • AGDor Pay may operate on infrastructure located outside your country of residence. By using the Service you acknowledge that your data may be processed in such jurisdictions.
  • Where required by applicable law (for example GDPR Chapter V), transfers are made under appropriate safeguards.
Children
  • AGDor Pay is not intended for use by persons under the age required to lawfully use payment services in their jurisdiction (typically 16 or 18).
  • AGDor Pay does not knowingly collect personal data from children.
Policy updates
  • This policy may be updated as the product grows, adds more routes, or changes the supported infrastructure.
  • Material changes will be communicated through the Service interface or by email when available.