PuLoop

DRAFT — OWNER APPROVAL REQUIRED BEFORE PUBLIC ENROLMENT

The campaign uses your stable Telegram account identifier to authenticate Mini App access. Telegram usernames do not determine your reserved PuLoop username. Email is required for verification, reservation ownership, launch recovery and eligibility.

Stored data includes encrypted email and keyed comparison lookup, Telegram ID, reserved username, consent history, first eligible referral, game actions and daily totals, reward entitlements, append-only ledgers and restricted audit information. The browser holds session credentials in memory. Third-party analytics are not integrated. Referral links contain a random public code, not your email or login credential.

Optional product-news consent is separate from participation and can be changed in Rewards. Leaderboards are opt-in. Friends see aggregate referral progress, not other participants' emails or Telegram IDs. The private bot /stop command disables optional reminders. No contact-list access, payment information, crypto wallet or invasive device fingerprint is requested.

Email verification and Telegram bot delivery require service providers chosen by the campaign operator. Their actual identities, hosting locations, lawful bases, retention periods, data-access rights, complaint channels and operator contact must be filled in before public launch.

Self-service export/deletion/recovery is not implemented in this pilot. The owner must complete and test privacy request handling, retention cleanup and fresh ownership proof before public enrolment. Do not treat source-plan retention suggestions as an active deletion policy. Claimed app accounts, once integration exists, follow the main PuLoop policy; campaign deletion must not erase app wallet audit records or an already claimed username.

In development only, email messages are spooled to a private local folder to permit testing. Production must use approved SMTP and must never expose this folder through the web server. Encryption keys and backup access belong in protected secret storage.