Context-specific personas
Keep several partial identities — social, work, legal — each a bundle of typed fields graded 0–3 by sensitivity.
Selective disclosure for developers
Identity that knows who is asking, and why.
Afixo keeps a person as several context-specific personas. One endpoint returns exactly the identity a caller is permitted to see — for that caller, for that stated reason — and nothing else.
Free while in preview · no credit card · your data stays yours.
$ curl https://api.afixo.io/v1/disclose/alice?purpose=shipping \
-H "Authorization: Bearer $TOKEN"
HTTP/2 200
{
"decision": "allow",
"persona": "legal",
"fields": {
"full_name": "Alice Example",
"postal_address": "1 Example Row, Leeds"
},
"withheld": ["dob", "email"],
"decision_id": "01a02da7-…"
}How it works
- 1
Describe yourself, per context
Create personas and grade each field. Your date of birth is “high”; your job title is “low”.
- 2
Write rules, not code
For a requester and a purpose, pick the persona, a sensitivity ceiling and optionally an allow-list.
- 3
Let callers ask
An integrator calls one endpoint with a purpose and gets exactly the fields your rules permit — or a uniform 403.
Purpose-aware disclosure
Requesters declare a purpose with every call. Grant-only rules keyed on (requester, purpose) decide which persona and which fields come back. Deny by default.
Audited by construction
Every allow and deny is written to a hash-chained log you can read and verify: who asked, why, and exactly which keys were released.
Built for the people on both sides of the request
Subjects manage personas and rules in the dashboard. Integrators get a plain REST API, an MCP server for AI agents, and a decision id they can quote. Same subject, different purpose or requester → a different persona, a different field set, or a uniform 403.