Protection at rest
Device encryption protects stored information, but it does not decide what becomes visible after access is granted.
Situational privacy / In development
Choose what your phone reveals.
Liberty Lock is a privacy app in development for iPhone, with Android to follow. Your real PIN opens the vault. A second PIN opens a separate, ordinary container. It changes what Liberty Lock shows, not the rest of your phone.
Select an access state
Everyday view. The vault stays sealed.Product concept · App in development · Simulated screens
The access problem
A phone can be encrypted and still expose too much.
Ordinary device security assumes the owner decides when and how access is granted. Real situations are not always that clean.
Access under pressure
A privacy control should not depend on navigating settings or explaining why access is being refused.
Deliberate exposure
The useful choice is not simply locked or unlocked. It is deciding which information a given access state reveals.
01 — Access states
One app. Three access states. A boundary you control.
Everyday and Secondary Access are views. The Protected Vault sits behind an access boundary and opens only with your real PIN.
- 01Surface
Everyday Access
What the app shows day to day. The vault stays sealed and nothing protected is on screen.
- 03Surface
Secondary Access
A separate container that a second PIN opens, holding only ordinary content you chose in advance.
- —Design target
Access boundary
Crossing it takes your real PIN. Encryption and platform-protected keys are planned as core constraints.
- 02Behind the boundary
Protected Vault
Credentials, recovery phrases, journals, photos and documents you choose to protect.
Simulated screens · conceptual product model
02 — Quick Lock
Seal the vault in one action. No settings, no network.
A prepared action is intended to close the Protected Vault and return Liberty Lock to its everyday view, without depending on a network request or a sequence of settings.
Conceptual sequence · inside the app
- 01Protected Vault open
- 02Prepared action
- 03Vault sealed
Designed to work without a server round-trip. Seals Liberty Lock only; it does not lock your phone or other apps.
03 — Local-first boundary
Readable here. Cipher there.
The architecture target changes a protected item into a cipher representation on your device before any optional crossing. The service-side model has no path back to readable content.
Inspect the technical modelArchitecture target / guided sequenceLocal control. A changed representation. Limited service scope.
Optional local ruleDEVICE CONTEXT
Access-state controllerPROTECTEDSelected on device
Protected Vault
PRIVATE NOTE
Readable only inside this trust zone8F 2C A1 7D 9B 44
Optional encrypted material
8F 2C A1 7D 9B 44
Stored or processed without a readable representationNo reverse controlThe service-side model contains no key or decrypt action.
Outside intended readable scope
- Vault content
- Key material
- Local context rules
Stage 01 / 07A rule begins on the device.
Optional context is intended to be evaluated locally rather than becoming a service-side activity record.
Conceptual architecture · mobile product in development04 — Product system
Each module controls a different part of exposure.
Each capability exists to support controlled visibility. None is presented as a shipping guarantee while the product remains in development.
Design target
Protected Vault
A separate place for sensitive notes, files, and credentials, with encryption and platform-protected key handling planned as core constraints.
05 — Vision
Starting with one phone. Designed to grow.
The same access-state model could extend from personal privacy to organizations and to computers. This is the direction, not a release plan.
ANow
Consumer app
In developmentLiberty Lock starts as a consumer app for iPhone, with Android to follow. This is the immediate priority.
BDirection
Business & enterprise
Strategic directionLonger term, the same access-state model could help organizations control how sensitive information is exposed, through business configurations and custom work for specialized operational needs. Not a product today.
CHorizon
Desktop & computers
Long-term visionBeyond the phone, the intention is a broader software ecosystem that brings controlled visibility to computers. No operating systems or timing are committed.
Line style encodes status: solid, in development · dashed, strategic direction · dotted, long-term vision. Illustrative progression; the initiatives may not launch in this order.
06 — Security transparency
Current. Planned. Not claimed.
Every product statement is classified by status. Architecture goals remain targets until implementation and review provide evidence.
- 01Current fact
- The website and product model are public; the mobile product remains in development.
- 02Design target
- Protected information and prepared access states are intended to operate locally.
- 03Design target
- Company systems are intended to have a narrow view of protected content.
- 04Not claimed
- No audit, certification, performance benchmark, or cryptographic guarantee is presented as complete.
Questions
Scope, status, and boundaries.
Not yet. Liberty Lock is in active development, iOS first with Android to follow. This site describes the product model and current design goals, not a released security guarantee.
Built-in platform security is essential and remains the foundation. Liberty Lock is exploring an additional control layer for deciding which information is visible through different access states.
The architecture is intended to keep recovery authority with the user and limit company access to protected content. The final recovery model will be documented before release because convenience and confidentiality create real tradeoffs.
The design goal is a narrow backend that handles only what operation requires, such as account or subscription state and encrypted backup material where those features exist. This boundary remains a design target until the product implementation is published or reviewed.
No. Liberty Lock is intended for lawful personal privacy, safety, and control over information on devices a user owns or controls.
No. The planned product does not generate wallets, show balances, or execute transactions. Any supported recovery phrase would be treated as protected user-entered information.
Continue