Privacy Policy

Information used for competition operation

• Telegram identifiers such as chat IDs and participant IDs used to attribute trade activity and compute comparative metrics.
• Signal content used to interpret entries, targets, stops, and other trade attributes needed for monitoring or auditing.
• Site access and service logs used to maintain uptime, monitor abuse, and troubleshoot reliability issues.

How the information is used

• To compute leaderboard metrics and render performance visualizations.
• To monitor trade lifecycle events such as progress, closure, or expiry.
• To support site security, service continuity, and operational debugging.

Cookies and infrastructure

The first-party conversion measurement described below uses a short-lived, HTTP-only proof cookie to help reject malformed, replayed, or cross-origin event submissions; this public bootstrap mechanism does not authenticate a human visitor. This release uses no third-party analytics or session-recording vendor. Infrastructure providers may retain ordinary security and access logs needed to host and operate the service.

First-party campaign measurement

The homepage and Elite journey use random, pseudonymous first-party visitor, session, funnel, event, and checkout-attempt identifiers to measure aggregate conversion steps. Campaign fields are limited to controlled source and medium categories plus conservative slug-like campaign, content, and term labels. Values resembling contact details, telephone numbers, or URLs are rejected. Raw advertising click identifiers are not retained, landing paths exclude query strings, and raw referrers are not stored. These identifiers are not derived from email, IP address, Telegram username, Stripe customer data, or browser fingerprinting. Browser state is stored locally, sessions rotate after 30 minutes of inactivity, and Stripe receives only opaque checkout linkage rather than campaign labels.

Raw pseudonymous first-party analytics events and their abuse-limiter metadata are scheduled for deletion after approximately 90 days in bounded maintenance batches. Temporary scheduler or database failures may delay deletion. Aggregate reports do not expose row-level identifiers, while operational commerce and entitlement records follow separate retention needs. This technical description is not legal advice; final legal adequacy remains the responsibility of the service owner and company.

Sharing and retention

Personal information is not sold. Data may be processed by infrastructure providers strictly to host or operate the service. Competition data may be retained to preserve historical integrity and interpret prior leaderboard states.

Questions

For privacy-related questions or requests, contact the project owner or administrators through the relevant Telegram admin channels.