Each of these is the same architecture wearing a different job. No screenshots yet, on purpose — everything here is in build, and we'd rather show you the real thing than a mockup. What we can show you now is the difference each piece makes.
Private Connections
Your phone rings and a familiar voice needs something. Today, “who is this really?” is a feeling. A VettID connection is a channel between two vaults — both ends proven every time, end-to-end encrypted, with no platform in the middle reading along or selling the metadata.
Today
✗ Caller ID and “sounds like them” are the whole check
✗ Messages ride platforms that read, mine, or leak them
✗ Your contact graph is someone's product
With VettID
✓ Both ends prove who they are — automatically, every time
✓ Calls and messages encrypted vault-to-vault, no middleman
✓ Your own phone-to-vault link is encrypted and proven the same way
✓ Who you know stays yours
Status: in build — design, not yet product
Service Connections
Every business you deal with keeps its own copy of you — and every copy is a future breach letter. A Service Vault connection inverts it: the business asks, you consent, they see what's needed for the moment and store nothing.
Today
✗ Same forms, again, into another database
✗ Every service keeps a copy; every copy can leak
✗ “Delete my data” is a request, not a fact
With VettID
✓ Data accessed on demand, with your explicit consent
✓ Nothing stored means nothing to breach
✓ Revoke access the moment you're done — and it's actually gone
Status: in build — design, not yet product
Identity Credentials
Proving you're over 21 shouldn't require a stranger keeping your address. Verified credentials live in your vault; when a proof is needed, you show exactly that fact — and the checker learns nothing else, keeps nothing at all.
Today
✗ “Verify your age” means uploading the whole license
✗ Copies of your ID scattered across databases
✗ Every proof adds to someone's file
With VettID
✓ Prove the one fact — over 21, licensed, a member
✓ Nothing extra revealed, nothing retained
✓ Your credentials stay in your vault, under your control
Status: in build — design, not yet product
Secure Secrets
Passwords in a notes app, API keys in a text file, the important stuff “somewhere.” Your vault keeps secrets in hardware isolation — usable from your phone, readable by no one else, including us.
Today
✗ Secrets live in apps that sync them somewhere you can't see
✗ A cloud password manager is a promise about someone else's server
✗ One breach exposes everything at once
With VettID
✓ Encrypted in a hardware-isolated vault
✓ Unlocked by you, on your device — no company in the loop
✓ We couldn't read them if we wanted to — by design
Status: in build — design, not yet product
Democratic Voting
Eligible, counted exactly once, ballot secret, tally checkable — the goals sound contradictory only when identity and privacy are opposites. In a vault-based vote they're the same mechanism, which is how this project governs itself too.
Today
✗ Verified voting means showing ID and trusting the count
✗ Anonymous voting means unverifiable results
✗ Communities outsource decisions to whoever holds the ballot box
With VettID
✓ Prove eligibility without revealing identity
✓ One person, one vote — enforced by math
✓ Anyone can check the count; no one can see your ballot
Status: in build — design, not yet product
Encrypted Backup
A backup is a copy of your life — which is exactly why most backups are a privacy problem. Your vault backs up encrypted so only you can unlock it: lose the phone, keep the life, and nobody along the way could peek.
Today
✗ Cloud backups a provider can read, scan, or hand over
✗ Or no backup, and a lost phone is a lost life
✗ Recovery means trusting a support department
With VettID
✓ Backups only you can unlock — provider-blind
✓ Recover everything on a new device, on your own
✓ No recovery department, because none is needed
Status: in build — design, not yet product
AI Agent Access
Agents are useful the moment you hand them credentials — which is the moment things usually go wrong. With VettID, an agent asks, you approve, and it gets scoped access to exactly the secret it needs, revocable the moment you change your mind.
Today
✗ API keys pasted into configs and prompts
✗ Standing access: the agent (and its logs) hold your keys forever
✗ Revoking means hunting down every copy
With VettID
✓ You approve every connection, per agent, per secret
✓ The agent uses the credential without ever holding it
✓ Pull the leash once and access is gone everywhere
Status: in build — design, not yet product
Bitcoin Wallet
“Not your keys, not your coins” — but self-custody usually means seed phrases taped in drawers. Your vault generates and holds wallet keys inside the hardware enclave: spendable by you, exportable by no one.
Today
✗ Exchange custody: your coins, their keys, their risk
✗ Self-custody: a seed phrase one house fire from gone
✗ Sending means addresses copied through chat apps — interceptable, mistypable
With VettID
✓ Keys generated and held in the enclave — they never leave
✓ Share your address privately through your profile — connections get it with no one in between and no mistyping
✓ Backed up the same encrypted, provider-blind way
Status: in build — design, not yet product
Encrypted Agent Messaging
If an agent works for you, its reports shouldn't route through somebody else's chat platform. Agent messages and approval requests arrive in your feed over your own encrypted channel, from an agent whose identity is verified — so “my agent says” actually means your agent said it.
Today
✗ Agent chatter rides third-party platforms
✗ Approval requests arrive as forgeable emails and links
✗ Anything in the pipe can read the traffic
With VettID
✓ Your own end-to-end encrypted channel — no chat app in the loop
✓ Verified agent identity on every message
✓ Approvals in your feed, provably from your agent
Status: in build — design, not yet product
Location on Your Terms
“Share my location” shouldn't be a lifestyle. Share live location with the person meeting you, the family on the trip — and end it the moment it's done, with no ad network riding along in the background.
Today
✗ Location sharing means an app tracking you always
✗ “Only while using” still feeds the ad ecosystem
✗ Turning it off is a settings scavenger hunt
With VettID
✓ Share with exactly the connections — people and services — you choose
✓ Cut access the instant you're done
✓ Nobody else in the loop — no networks, no brokers
Status: in build — design, not yet product
The architecture behind all of this lives on Security, the reasoning on Why VettID, and the code on Open Source as we publish it.