Privacy

Canvas is a verification layer that runs at the moment someone joins a Telegram group. This page describes the data involved and how it is handled. It is a plain-language summary, not a legal contract.

​

What Canvas collects

Canvas does not collect private keys, payment-card data, government identity, or any off-Telegram profile. End users never connect a wallet.

​

What is written on-chain

The escrow contract stores no user data. On-chain records contain only a numeric campaign ID, wallet addresses, and USDC amounts. No Telegram IDs, usernames, transcripts, or scores are ever written to Base. On-chain data is public and permanent by nature of the blockchain.

​

What advertisers receive

The advertiser that sponsored a task receives, per passing completion: the conversation transcript, the Kimi score, the group context, the on-chain settlement transaction hash, and remaining budget. In other words, your response to a sponsored task is shared with the advertiser that funded it. The task itself is the product being sold — this is the core of how Canvas works, and it is why completions are valuable.

​

Subprocessors

Canvas relies on third parties to operate. Response text is processed by the conversational and scoring models.

​

Retention

Verification records are stored in Postgres to run the protocol, prevent abuse, and deliver completions to advertisers.

​

Your choices

• Group members: verification only runs on new joins to registered groups. Existing members are not affected.
• Group owners: removing @CanvasVerificationBot as admin stops all verification and clears queued attempts.
• Data requests: email hello@canvasprotocol.xyz for questions about your data.

See also Security for how funds and keys are protected.