Profiles, Accounts, and Identity Layers Explained
Profile vs account identity: two layers most platforms blur together. Here is the distinction, why it matters, and how separating them protects users.
- An account is your private root; a profile is your public, shareable identity built on top of it.
- Most platforms blur the two, which couples your public presence to your private credentials.
- Separating the layers lets identity be portable and shareable without exposing the account.
- DeadArk keeps the account private and exposes only the portable profile.
Two layers, usually blurred
Most platforms treat "your identity" as a single thing: the account you log into *is* the identity others see. That conflation is convenient and quietly costly. DeadArk separates identity into two deliberate layers — the account and the profile — and the distinction explains a lot about why portable, privacy-respecting identity is even possible.
The account layer
The account is your private root. It is the underlying record that holds your credentials (passkeys), your recovery, and the core of who you are on the system. It is not something meant to be handed to other apps or shown to the public. Think of it as the foundation: essential, sensitive, and private by design.
Key properties of the account layer:
- It anchors authentication and recovery.
- It is private — never exposed to integrating apps or other users.
- It is the thing your security model is built to protect.
The profile layer
The profile is your public, shareable identity, built on top of the account. It is what other people and apps actually see and recognize: your display identity, your public presence, and a stable, portable identifier that represents you consistently across contexts. The profile is meant to be shared; the account is not.
Key properties of the profile layer:
- It is public and shareable by design.
- It carries a portable identifier that apps use to recognize you (see How Portable Profile IDs Work).
- It can be presented, connected, and recognized without touching the account.
Why the separation matters
Blurring the layers means your public presence is welded to your private credentials — to be recognized, you expose the very thing that should stay protected. Separating them removes that bad trade:
- Portability without exposure. Your profile identity can travel across apps while your account stays private.
- A safe integration boundary. Apps work at the profile layer and never receive your account UUID — enough to recognize you, nothing to compromise you.
- Cleaner exit and recovery. Because identity is not trapped in the account of any single app, you keep ownership of who you are.
This is the architectural reason DeadArk can offer portable identity and privacy at the same time: the public thing and the private thing are genuinely different objects.
How DeadArk applies it
At DeadArk, the account stays private and the portable profile is what the world sees and what apps recognize. Sign in with DeadArk exposes the profile identity, never the account UUID — so you get one identity you can carry, without surrendering the private root it is built on.
The short version
Your account is your private root; your profile is your public, portable identity built on top of it. Keeping them separate is what lets identity be shareable and portable without exposing what should stay protected.
Frequently asked questions
What is the difference between a profile and an account?
An account is your private root — credentials, recovery, the core record — never exposed to other apps. A profile is your public, shareable identity built on top of it, carrying a stable, portable identifier that apps recognize.
Why separate identity into layers?
Blurring them welds your public presence to your private credentials. Separating them lets identity be portable and shareable across apps while the account stays private — and gives apps a safe boundary that never exposes the account UUID.
How does DeadArk use these layers?
DeadArk keeps the account private and exposes only the portable profile. Sign in with DeadArk shares the profile identity, never the account UUID, so you carry one identity without surrendering its private root.
More in Definitions
Doxxing is publishing someone's private information to expose or intimidate them. Here is what it is, how it happens, and practical ways to protect your community.
The fediverse is a network of independent social servers that talk to each other, so no single company runs it all. Here is how it works, in plain English, and its trade-offs.
Your social graph is the map of who you're connected to and how. Here is what it is, why platforms guard it so closely, and why it should belong to you.
DeadArk is a local social network for people, communities, businesses, projects, publications, and institutions to connect through shared interests and place. Learn more at deadark.com.