Draft for local review · not an effective legal document
Privacy Policy
Prepared 9 October 2026
This draft explains the data involved in CGBurn’s current product design. The operator, legal bases, retention periods and service-provider arrangements must be confirmed before publication.
1. Account and authentication data
CGBurn uses your email address for one-time sign-in codes and maintains account identifiers, verification and session records to authenticate you and secure account access. Account-related information is also used to support your requests and investigate account problems.
2. Wallets, orders and activity
The service stores token balances, ledger entries, order references, payment statuses and feature usage needed to deliver paid actions and avoid duplicate credits. Collections, likes, downloads, votes, burn requests, boosts and contributions are linked to the account where relevant. Payment providers process payment data under their own notices; their exact entities and data flows require confirmation.
3. Marketplace browsing
CGBurn processes marketplace URLs and listing information to show alternatives and relevant files. Local mode runs the browser engine on your device with a separate network runtime. Remote mode uses a hosted Chrome session. Infrastructure processes connection, session and usage information for routing, quotas, billing and abuse prevention. Third-party sites receive browsing requests and can apply their own cookies and data practices. Confirm the Remote browser’s session-data lifecycle before publication.
4. Files and infrastructure
Uploaded asset files and their metadata are processed to verify contributions, make accepted files available and support downloads. File delivery and service infrastructure include MEGA, Cloudflare and application hosting. A published notice must identify the relevant provider entities, their roles, storage locations and any cross-border safeguards. Do not contribute personal or confidential files without the necessary rights.
5. Analytics and device storage
Where configured, CGBurn uses PostHog for page views and product events, including account-linked identifiers and feature outcomes. The current integration disables session recording and masks captured text and element attributes. Authentication and browser-engine functionality use device storage. Third-party marketplace cookies are separate. Cookie and analytics consent requirements, controls and retention must be reviewed for each applicable jurisdiction.
6. Support conversations
Website chat is provided by Crisp. Messages and any files or contact details you choose to share are processed to answer your support request. Telegram support messages reach the same support inbox through the CGBurn support bot. CGBurn does not automatically send your account email or wallet details to Crisp. Provider arrangements and retention periods must be confirmed before publication.
7. Retention, security and your requests
Retention periods for account, payment, ledger, contribution, browsing and analytics records have not yet been approved for this notice. Deletion may need to preserve records required for accounting, fraud prevention or other legal obligations. To ask about access, correction, deletion or other applicable privacy rights, contact info@cgburn.com. Identity verification and the response procedure need confirmation; this draft does not set legal response deadlines.
8. Publication checklist
The effective policy must state who controls the data, why each category is processed, the applicable legal basis, who receives it, how long it is kept and how to exercise relevant rights or complain. The draft remains incomplete until those operational and jurisdiction-specific details are verified.
Questions about these documents: info@cgburn.com.