The protocol for
user-owned data.
DID, encrypted personal data stores, and consent-based rewards. Users own their data; you build on it with a single login SDK.
Users generate the data.
Platforms captured the value.
Three shifts are dismantling that structure.
Public data for AI is running out
Most of the open web has already been trained on. The next edge comes from consented, personal data.
Collection without consent is closing
Third-party cookies are ending; GDPR and privacy rules are tightening. Silent data pipelines are running out of room.
Users were never paid
Users produce the data but held no ownership and got no reward. Perme returns both control and payment to them.
One login. That's the integration.
Add a few lines of SDK. The protocol handles the rest.
Identity and wallet, created
Keep your existing social login. A DID and a personal data store (PDS) are created automatically. No app install.
Encrypted in the user's vault
Behavior, interest, and activity data land in a PDS only the user can open. You never see the raw data.
Used on consent, with rewards
Only permitted data is used by businesses. Users are paid back in PME.
A full stack,
already running.
From login to storage, policy, rewards, and AI access — on one protocol.
Passport · Login SDK
One social login generates a DID. A drop-in login for any web or mobile app — add a few lines of SDK.
PDS · Personal Data Store
Data is encrypted and governed per item by access policy. Only the user opens the raw data, so you carry less privacy risk.
BFS · Off-chain storage
Raw data never goes on-chain. It is encrypted and stored off-chain; only integrity is proven on-chain.
On-chain policy & audit
Consent and access history are recorded on-chain, verifiable by anyone.
PDS dashboard
Users see who requested what, toggle each item on or off, and track the rewards they've earned.
MCP · AI data layer
Consented data is anonymized and structured for AI to use — the connection point for a new data revenue stream.
Every request, in the user's hands.
Users see who asked for what, toggle each data item on or off, and watch rewards add up — all in one view.
Built on Perme.
One protocol, many services — identity, private data, and consent-based rewards, in production.
Reputation & rights management
Most tools stop at telling you what happened. Perme carries it through — detect, file, escalate. Originals and evidence stay in a PDS vault only the creator opens.
Login integration
The world's #5 comment platform, 1M+ MAU, added Perme login.
Discarded data, put to work
Support and CRM logs, taken on consent, cleaned, and connected to AI training.
consent → AI → rewardNo app. From your service.
Bring existing web users into a data store — just add the login SDK.
login → DID · PDS