Pinned Tweet
We are building a decentralized trust layer for the new data economy. Grant or revoke consent to your data, and earn a share of what it generates💰
More info coming soon...
layerd.org
3
2
764
A media buyer we'll call Dana pulled up a campaign report with 212 placements on it. Every URL was checked, and every one was brand safe.
Then someone asked where the audience data came from. The report had no line for that.
Brands spend real effort on where an ad appears. The same care rarely goes to how the person was chosen to see it. Placement is something you can see.
Consent is a claim someone made upstream, and most reports carry it on trust.
That's the blind spot. Brand safety and consent safety are two different checks, and only one of them usually gets run.
A verifiable receipt changes that. When consent is captured through the LayerD SDK, a cryptographic receipt is generated and its proof is anchored to a public blockchain, so the record doesn't depend on whoever happens to be holding it. The buyer can then check consent status for a device identifier instead of taking a seller's word for it.
It doesn't guarantee compliance. It does turn "we have consent" from a promise into something you can check.
If your campaign report can't show where its audience data came from, who signs off on it? That's the person to send this to.
So here's the question a buyer can put to a seller tomorrow:
"Can you show me the consent receipt for this specific device ID?
8
Maya, a product lead at a mid-size app, opened a notice from a data protection authority. It asked for one user's consent decision from last spring.
Her team found a log line. It showed what their own system said it recorded, not what the user actually chose.
That gap is the whole problem. A record you wrote about yourself is a claim. An outsider has to take your word for it, and a regulator has no reason to.
So here's a quick check for your own stack:
Can you pull the opt-in or opt-out for one named user from months ago?
Is it timestamped in a way you can't quietly edit?
Could someone outside your company confirm it without trusting your database?
Any no? You have a log, not proof.
A signed consent receipt anchored to a public blockchain is built for exactly this. The proof lives outside your own system, and the raw personal data stays off-chain. That is the approach behind LayerD's Proof of Consent infrastructure.
We post one plain-English breakdown like this on how consent can be verified, not just declared. Follow along if you want more. More at.
Last question. Could you prove one user's choice from last spring, and would a stranger believe you?
4
A roadmap line read "replace CMP." Estimate: two quarters, one very tired team.
Then someone asked a smaller question. What if the CMP stays?
It can. LayerD connects to an existing CMP, so each opt-in or opt-out becomes a cryptographic receipt. The consent flow your users already see doesn't change.
Receipts are anchored on a public blockchain. Raw personal data and full consent records are not stored on-chain.
Data consumers can then check consent status on their own, instead of taking your word for it.
Proving consent doesn't have to mean rebuilding it. Connecting is a smaller job than replacing.
We post plain-English breakdowns like this on consent and data provenance, so follow along if you'd rather decide with the facts.
7
You tap "Accept" on a dozen screens a week.
Ask yourself: which apps hold your yes today, and what did it cover?
Individuals should be able to see that. It's what we're building toward.
4
Your logs prove what your system recorded.
They can't prove to a partner that nobody changed them later.
Independent verification is a different job from record-keeping.
4
A model team inherits a training set from an aggregator. Three hops back, someone collected it.
Before you train, ask one question: can the provenance be checked, or only trusted?
3
We get asked: "Is the consent data on the blockchain?"
No. Raw personal data and full consent records stay off-chain.
What goes on-chain is a cryptographic proof that a receipt exists and hasn't changed.
2
The product team shipped a new SDK on Friday.
By Monday, a new data flow was live.
But had anyone checked whether the original consent covered it?
A new data flow needs a fresh consent check, not an assumption that old permissions still apply.
4
Your CMP says a user opted out.
Your data partner's system says nothing changed.
Which record do you trust?
Without independently verifiable consent evidence, resolving that disagreement becomes much harder.
2
A buyer reads the last line of a data contract: "All records are consented."
Nobody on the call can say who wrote that line, or how to check it.
A claim you can't verify is still a claim.
1
A user declines consent. Six months later, can you prove it?
LayerD creates verifiable consent receipts, anchors cryptographic proofs on-chain, and lets data partners check consent status.
No personal data on-chain. Just verifiable proof.
#LayerD #DataPrivacy
3
You've tapped "Accept" hundreds of times.
But can you see what you've agreed to?
What data you allowed to be used. Who you gave permission to. Whether that permission is still active.
Which of these would you want to check first?
1
A dataset seller says, "It's all consented."
But can they prove it?
Before using data to train an AI model, check its source and whether consent covers the intended use.
LayerD helps make consent independently verifiable, so buyers don't have to rely on a seller's word.
#LayerD
2
Your internal consent logs say a user agreed.
But can an independent party verify that record hasn't changed?
LayerD anchors cryptographic proofs of consent receipts on a public ledger, making changes detectable.
Personal data stays off-chain.
#LayerD
2
A user declines consent on Monday.
By Friday, can your data partners verify that decision?
LayerD creates verifiable consent receipts, allowing participating partners to check current consent status before using data.
No guesswork. No relying on outdated consent records.
#LayerD
1
A data feed is already in your pipeline.
Then someone asks: “Who collected this data first?”
Nobody knows.
Before activating a dataset, ask four questions:
1. Where did it come from?
2. Can consent be verified?
3. Is that consent still active?
4. Can an independent party confirm it?
3
Your app updates its SDK. A new data flow goes live.
But does the consent you collected actually cover it?
LayerD helps data partners verify whether consent is active and valid for the intended use.
Because yesterday's consent isn't automatically permission for tomorrow's data use.
#LayerD
5
The permission screen had two buttons, and my neighbor tapped "Accept all" in about one second. Then she asked me what she'd just agreed to. Nobody could tell her.
Three questions fix that. Ask them after any sign-up.
1. Who holds my data?
Not "the app" in general. A named company, and the partners it passes your data to. You keep the right to ask.
2. What did I say yes to?
Location, contacts, ads, sharing with others. Each one is a separate choice you made, and you can change it.
3. Could anyone prove it later?
A receipt can. It records your decision and anchors a cryptographic proof on a public blockchain. Your personal data never goes on-chain, only the proof that you chose.
If you can answer all three, you're in control. If you can't, you've found the gap.
Here's a screen that fails question 2: two buttons, "Accept all" and "Manage," where location, contacts, ads and sharing sit behind one yes. That's one tap for four choices, and no receipt for any of them.
Send it to whoever owns your sign-up flow. Ask them which of the three questions their screen can answer.
8
A line in a media plan reads "Auto Intenders, 2.4M devices." Someone asks the buyer where the consent came from.
The answer was a contract clause and a slide.
Curious how this works on your side. When you buy a segment, what shows up as proof that the people in it agreed to be there? A contract line, a dashboard screenshot, or something you can check yourself?
4
