Security

We apply a defence-in-depth model: security controls are layered so that no single failure can compromise the system. Network segmentation isolates the API, database, and worker tiers. All internal services communicate over encrypted private Docker networks with no public-facing ports beyond what is strictly necessary. Regular penetration tests and automated vulnerability scans validate the posture before any update reaches production.

All user funds are held in USDT on the Tron blockchain — a public, auditable ledger. Deposits are verified on-chain via TronGrid before they are credited. A hot/cold wallet separation policy ensures that only the minimum operational balance is kept in the hot wallet; the remainder is held offline. Withdrawal destinations are checked against a user-controlled whitelist, and all on-chain transactions carry a unique idempotency key to prevent double-processing.

All communication between your device and our servers is protected by TLS 1.3 with forward secrecy. Data at rest in PostgreSQL is encrypted at the tablespace level using AES-256. Sensitive fields — password hashes, two-factor secrets, and KYC documents — are stored with Bcrypt (cost factor 12) or AES-GCM encryption and are never returned in API responses. Our HTTP headers include HSTS, X-Frame-Options, CSP, and Referrer-Policy to harden the browser environment.

We support two independent 2FA channels: TOTP (RFC 6238 — compatible with Google Authenticator, Authy, and any standards-compliant app) and Telegram 2FA, which delivers a time-limited one-time code to your verified Telegram account. Login attempts that fail 2FA validation are logged with timestamp and IP. You can review and revoke all active sessions from the Security settings page at any time.

To comply with international anti-money-laundering regulations and protect our community from fraudulent actors, YandexyWin implements a tiered KYC programme. Level 0 allows basic platform access; Level 1 requires email verification and unlocks full withdrawal capabilities. KYC data is collected, processed, and stored in compliance with GDPR and the applicable data protection regulations of the user's jurisdiction. Documents are encrypted immediately on receipt and are never shared with unauthorised third parties.

Our automated AML engine evaluates every transaction against a rule set that includes velocity checks, geographic risk scoring, pattern-based anomaly detection, and cross-referencing against known high-risk address lists. Suspicious activity triggers an automated hold and an alert for manual review by our compliance team. We maintain a full audit trail of every AML decision for regulatory inspection.

Withdrawals are the highest-risk operation on any financial platform. We protect them with multiple independent controls: withdrawal addresses must be pre-registered and verified; changes to the registered address carry a mandatory 24-hour cooling-off period; large withdrawals trigger a secondary confirmation step; and all withdrawals pass through a final AML check before broadcasting to the blockchain. No withdrawal is processed without passing every gate.

Our infrastructure runs in isolated Docker containers on hardened Linux hosts. Each service has a minimal attack surface — only the ports it genuinely needs are exposed, and inter-service communication is restricted by network policy. PgBouncer provides connection pooling for PostgreSQL, limiting exposure to direct database access. Redis operates in password-protected, network-isolated mode. All infrastructure components are patched on a rolling schedule with zero-downtime deployments.

Every public API endpoint is protected by adaptive rate limiting, which distinguishes between legitimate high-frequency users and automated attack tools. Authentication endpoints apply exponential back-off after repeated failures. Our CSRF middleware validates the origin of every state-changing request. Bot-detection heuristics analyse request patterns in real time and can issue soft throttles or hard blocks without user intervention.

Deposit confirmations and blockchain events are received via authenticated webhooks. Each webhook payload is signed with an HMAC-SHA256 signature derived from the transaction hash, destination address, and amount. Our server verifies the signature using a constant-time comparison function before processing any event — eliminating timing-attack vectors and preventing forged deposit notifications.

Every credit, debit, and commission event is recorded in a PostgreSQL ledger with append-only semantics enforced at the database level. UPDATE and DELETE triggers on ledger tables raise an exception if any attempt is made to modify a settled entry. Each record carries a unique idempotency key that prevents duplicate postings even in the face of network retries or concurrent requests. The current balance of any wallet is always the verifiable sum of its ledger history.

We believe in working collaboratively with the security research community. If you discover a potential vulnerability in the YandexyWin platform, please report it through our private disclosure channel at [email protected]. We commit to acknowledging every report within 48 hours, providing regular status updates, and crediting researchers whose findings lead to verified improvements. We do not pursue legal action against good-faith security researchers acting within responsible disclosure norms.