Proof & Privacy
Prove the choice. Keep original music data private.
bigcut uses only songs the user explicitly submits. When anchoring is enabled, the selection record can be checked later through non-mainnet/testnet proof, while original user IDs, song IDs, audio, notes, and embeddings are not published on-chain.
Only submitted songs are used
Private library activity, listening sessions, local notes, and unsubmitted songs remain outside the recommendation data path by default.
Non-mainnet/testnet proof does not receive original data
The non-mainnet/testnet chain stores proof material that can verify timing and integrity when anchoring is enabled. Original user IDs, song IDs, audio, notes, and embeddings are not revealed on the non-mainnet/testnet chain.
AI agents verify proof, not private data
An agent can evaluate whether a submitted record matches an anchored proof without needing access to the user's private identifiers or source audio.
How a selection becomes proof
Final Cut submission
Commitment and hash generation
Merkle batch
Non-mainnet/testnet anchor
Proof checked by agent or partner
Not placed on-chain by non-mainnet/testnet proof
- Original user ID
- Original song ID
- Audio files
- Full notes
- Embedding vectors
- Email addresses