Privacy Policy

Privacy Policy

Effective date: 17 October 2026. This notice describes the categories of information handled by CoinDirectly as its software is presently designed. Contact details, retention schedules, jurisdiction-specific rights and hosting arrangements should be reviewed by the operator and qualified counsel before treating this as final legal advice.

1. Information processed

We may process merchant business names, email addresses, public TRON receiving wallet addresses, application and approval status, login/session data, password hashes, email-verification code hashes, API key hashes, invoice references and amounts, webhook URLs, subscription status, support requests and administrative activity. Payment verification also uses public blockchain transaction hashes, events, transfer values, wallet addresses, block numbers and timestamps.

2. Why information is used

To establish merchant accounts, verify email ownership, review applications, enable approved subscriptions, issue invoices, match USDT transfers to merchant invoices, detect repeat transactions, provide status APIs and webhooks, secure accounts, troubleshoot payment disputes and support service operation.

3. Public blockchain data

TRON blockchain wallet addresses and transactions are independently public and may be visible to anyone, including explorers and other nodes. Blockchain transactions cannot generally be deleted or reversed by CoinDirectly.

4. Email verification and account protection

Verification codes contain 10 digits and expire after 10 minutes. Passwords are hashed rather than stored in readable form. Session authentication uses cookies; API keys and webhook secrets must be handled as credentials by merchants. No internet-connected service can promise absolute security.

5. Sharing and service providers

Information needed to deliver our service may flow through hosting, email delivery and public blockchain infrastructure. Merchant checkout and webhook data are made available to the applicable merchant and to users with the scoped invoice link. We do not claim that data is never processed by infrastructure providers. Each merchant has separate responsibilities for data it collects from its customers.

6. Cookies, logs and security

The merchant portal uses a session cookie for authentication; normal server/security logs can include IP address, request time and browser details for troubleshooting and abuse prevention. We do not describe optional advertising or analytics cookies here because they have not been verified as implemented. If such services are added, this notice must be updated.

7. Retention and requests

Account and transaction records may need to be retained for security, dispute handling, operational or legal obligations. A fixed deletion period is not asserted here because the platform's verified data-retention policy has not been finalized. For access, correction or deletion requests, contact support with enough information to establish account ownership. Data already recorded on TRON cannot be deleted by us.

8. Security concerns and updates

If you suspect account compromise, rotate API keys and webhook secrets and contact support. We may update this notice as features, infrastructure and legal requirements change. Any material changes should be reflected on this page before they take effect.

Support: Telegram @fbadspro11.