Operator: Dedyx, Private, Poland; address: Georgia. Data requests: https://t.me/dedyx_support; support: https://t.me/dedyx_support. Dedyx/merchant role allocation and processing grounds by purpose: Georgia. Necessary data supports applications/accounts, technical payment observation, event delivery, access protection and support; without it these functions cannot operate.
Manual applications contain the project/use case, minimal integration contact, expected volume, decision and pilot stage. Do not supply documents, customer details or secrets unless needed for a separately justified request. The pilot log stays outside Git; the operator confirms its location, retention and access.
PostgreSQL stores merchant IDs and API/rotation credential hashes, account/beta conditions, quotas/daily usage/activity; payment addresses, amounts, descriptions, IDs/public tokens and deadlines/status; transaction IDs/event indexes, observed transfers/receipts and reconciliation state; webhook URLs, payload/event IDs, attempts/delivery/errors and encrypted signing keys; audited decisions, cursors/leases and provider counters. Public addresses/transfers can be personal data when linked to a person; being on a public blockchain does not automatically make them anonymous.
The service also uses temporary Redis queue/rate-limit records, diagnostic JSON logs and metrics. Public nginx access logs contain IP addresses and technical request parameters; safe formatting excludes full URIs/query strings. Application logs use restricted fields/references rather than raw headers, bodies or credentials. Infrastructure suppliers have their own logging policies. Support contains what the reporter submits; minimize unnecessary information.
Anyone with payment_url can view the address, amount, description, status and deadlines and pay the invoice. Keep names, phone numbers, email addresses, documents and secrets out of descriptions; do not publish payment links. Cancel/expiry does not revoke public-detail visibility. TRON records already exist on a public blockchain; Dedyx cannot erase blockchain history.
Checkout stores the selected EN/RU language in localStorage. Shared UI may store presentation preferences; these are not analytics identities. Session authentication cookies belong to the separate private operator panel rather than buyer tracking; sessions last at most 8 hours, with 30-minute idle expiry or earlier revocation. First-party website navigation counts send fixed Docs/Demo/access categories, not payment URLs or unique user IDs; the separate event record excludes IP/Referer/body. Ordinary access logging and network connections remain distinct processing. Checkout has no third-party advertising tracker.
The owner and restricted runtime/monitor/panel roles access relevant data; there is no public panel of secrets/actions. Signing envelopes and backups are encrypted, but the owner can decrypt them using the master key; this is not end-to-end secrecy from the operator. TronGrid receives address/transaction observation requests, merchant receivers receive necessary signed payloads, hosting/offsite backup provide infrastructure and Telegram processes support-channel messages. Actual suppliers/countries, contractual roles and international-transfer arrangements: Georgia. Exclusive Polish storage cannot be promised without verified infrastructure.
Current defaults with a functioning retention worker: 24-hour idempotency replay; descriptions on PAID/CANCELED/EXPIRED payments are removed after 90 days from expires_at, and delivered-outbox descriptions after 90 days from delivered_at. REVIEW and undelivered/failed outbox are excluded from this rule. Cleanup is batched rather than instantaneous. Financial records/IDs, audit and address reservations are not automatically deleted.
Stale telemetry is removed after 7 days since heartbeat; inactive diagnostic files are bounded by a 7-day age rule and total size, active files by rotation. Docker/nginx logs have size limits, not a universal 7-day retention promise. The prepared backup policy retains 24 hourly/14 daily/8 weekly/6 monthly snapshots; owner-run forget/prune is separate and is not automatically enabled by the backup timer. Copies can retain data removed from the live database.
Owner-approved retention periods/criteria for applications, support, ledger/audit and copies, periodic necessity review and actual deployment overrides: 7days. Deletion requests are considered individually; disabling credentials does not erase all records. Where justified retention is needed, the operator explains the grounds and reviews its duration. Blockchain deletion or immediate removal from every backup is not promised; previously completed data actions must be reapplied after restoration before reopening access.
Contact the privacy address to request access, correction, restriction, deletion or other applicable rights; identity checks must be proportionate. Mandatory deadlines are unaffected by the absence of a general support SLA. Deletion requests normally receive a response within one month; permitted extensions require timely explanation. Lawful exceptions can apply. You may contact the Polish UODO. Source: UODO guidance. Consent-based processing can be withdrawn without invalidating earlier processing. The operator completes purposes/grounds before access delivery; no invented DPO appointment or certification is claimed.