Proof & Privacy
Prove the choice. Keep original music data private.
bigcut uses only songs the user explicitly submits. The selection record can be checked later, 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.
Blockchain does not receive original data
The chain stores proof material that can verify timing and integrity. Original user IDs, song IDs, audio, notes, and embeddings are not revealed on-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
01
Final Cut submission
02
Commitment and hash generation
03
Merkle batch
04
On-chain anchor
05
Proof checked by agent or partner
Not placed on-chain
- Original user ID
- Original song ID
- Audio files
- Full notes
- Embedding vectors
- Email addresses