Start here
Private messages, hidden behind an app you already have
1BX installs under a cover you pick. The phone shows Weather. Underneath is a vault with your messages, opened by a code you set.
Pick the cover it installs under. Weather is the one-tap default; the button below follows your choice.
Everyday
Work
Install as Weather — one tap Install as Calculator — one tap Install as Notes — one tap Install as Calendar — one tap Install as Files — one tap Install as Photos — one tap Install as Compass — one tap Install as Settings — one tap Install as Clock — one tap Install as Recorder — one tap Install as Flashlight — one tap Install as Scanner — one tap Install as Units — one tap Install as Steps — one tap Install as Reminders — one tap Install as Recipes — one tap Install as Groceries — one tap Install as Radio — one tap Install as Podcasts — one tap Install as Battery — one tap Install as Wi-Fi — one tap Install as Translate — one tap Install as Dictionary — one tap Install as Books — one tap Install as Journal — one tap Install as Sleep — one tap Install as Timesheet — one tap Install as Inventory — one tap Install as Job Log — one tap Install as Field Ops — one tap Install as Site Survey — one tap Install as Tool Crib — one tap Install as Dispatch — one tap Install as Work Orders — one tap Install as Maintenance — one tap Install as Asset Tags — one tap Install as Route Plan — one tap Install as Stock Count — one tap Install as Purchase Log — one tap Install as Safety Check — one tap
- 1Pick a name
- 2Install it — choose Install, not Create shortcut
- 3Set your code
What is a cover?
The name and icon your phone shows for this app. You pick it before installing.
Hover or tap for detail
A cover is the name and icon 1BX installs under — Weather, Calculator, Timesheet and 37 more.
There are 40. The phone treats each one as its own app, with its own name and its own icon. You choose the cover at install, and not afterwards.
Why
An installed app is a confession
Hiding is the whole point of this product. Three reasons it exists.
A normal messaging app announces itself
Its name and icon tell anyone who picks up the phone what you use.
Hover or tap for detail
Its name and its icon say what it is. Anyone who picks the phone up learns what you use.
An app someone is looking for is a confession
Finding nothing is better than finding the one thing they suspected.
Hover or tap for detail
If they already suspect, the icon confirms it. Finding nothing is better than finding one thing.
This looks like an app you already have
Weather, Calculator, Notes — nothing to explain, nothing in a folder.
Hover or tap for detail
Weather, Calculator, Timesheet. Nothing to explain, nothing to hide in a folder, nothing that reads as a second phone.
A discovered cover is still a worse tell than a boring app, so decide before anything important goes in.
The tour
Five steps, in this order
The whole path, start to finish. Each step opens when you hover it or tap it. No signup, no store listing.
-
Choose the cover
Pick the name and icon it installs as. Weather is the one-tap default.
Hover or tap for detail
Pick the name the app will carry. Weather is the one-tap default.
All 40 covers install from a link, and each one serves its own cover name. The choice is made before install and cannot be changed after.
-
Install from the link
Install from the browser. No store, no account, no card.
Hover or tap for detail
Open the link, then use your browser's own install. Android / Chrome: the ⋮ menu → Install and create shortcut → then choose Install, not Create shortcut — Install puts the cover's own name and icon on your home screen and opens full-screen with no browser bar; Create shortcut is only a bookmark. Safari: Share → Add to Home Screen (Safari offers no separate Install choice). The cover arrives as that app, with that name and that icon.
Nothing to pay and nothing to sign up for. The beta installs from a link rather than a store listing.
-
Set the three codes
Three codes: one opens your messages, one opens a decoy app, one destroys the key.
Hover or tap for detail
Inside the app you set three codes: real, decoy and kill.
The real code opens your messages.
The decoy code opens a working notes app. You can add, edit, search and delete notes, and they persist. It is not a mock screen.
The kill code destroys the key. It is instant, silent, permanent, and irreversible for you as well.
The kill and the decoy look identical on screen: same speed, same wording, no confirmation prompt.
Because there is no confirmation step, the kill code must differ from the real code in at least two digits. That rule is enforced as you type.
There is no recovery path. The code is the only way into the vault, so an app that could help you back in would be a second door.
-
Add one person
Messages go to a person, and their key stays with them.
Hover or tap for detail
Messages go to a person, not to a service. Each person is added on the device, and their key stays theirs.
Start with one. The list is not the point of the app yet.
-
Know the limits before you rely on it
It is a beta. Some checks are tested offline only.
Hover or tap for detail
The covers install from a link. The native checks and the message path are untested on a handset.
The install path has not been measured on a handset.
The screenshot block, the app-switcher blanking, the backup exclusion and the leave button are untested on hardware.
Messaging works: the relay is a function on the app’s own host. What it does not give you is privacy of metadata — the relay can see that a message was sent and when, so who talks to whom is visible to it, even though it cannot read the contents. And the key you send to is a claim, not a verified fact, because there is no built way to confirm it.
There is no store listing and no code recovery. Read this step twice.
Beta testers
The practice run
If you are testing the beta, run the whole loop once — not just the install. It takes a few minutes and it exercises the entire path rather than one screen. The beta build was updated on 2026-10-19 (build 1.0.0+1). If a build is older than the one live, the app shows Update ready at the top — tap Reload.
- 1. Install. Open the cover list, pick a name, and install from your browser. Android: the ⋮ menu → Install and create shortcut → choose Install, not Create shortcut. Safari: Share → Add to Home Screen.
- 2. Create the account and the three codes. Any display name. Choose No email? Set up on this device if asked. Set the real, decoy and kill codes and write them down — there is no reset.
- 3. Pair with one person. Open Your code, screenshot the square, send it to the other person, and have them add it. Then read the fingerprints to each other out loud and check they match. A key you were handed is a claim until you do that.
- 4. Send one message each way. That proves the relay and the sealing path, not just the screen.
- 5. Send feedback from Settings. Settings → Send feedback → one line → Submit. It returns a reference like
FB-20261019-ABCD1234; keep it. If the build has no relay, the same button says Copy report and copies the whole report instead of failing. - 6. Record what happened. Phone and browser, the cover you chose, and whether install / account / pairing / message / feedback each worked. That list is the useful part of a practice run.
The mechanics
It keeps your conversation secret. How?
Your message is sealed before it goes anywhere: the cover app locks it, and the relay in the middle only carries the locked copy. The picture shows the whole path.
The exact path, in technical terms
AES-256-GCM per message, with a fresh key and IV every time. That per-message key is wrapped with RSA-OAEP, and the key pair is generated on the device with the private key never leaving it. The relay is a Cloudflare Pages Function on the app's own host; it holds the sealed copy until the recipient collects it. The key you send to is a claim, not a verified fact: this beta has no built way to confirm that the key handed to you belongs to the person you think it does.
All four steps are live today. A message to someone who is not an app user goes as ordinary email. The message path has not been measured on a handset by us.
Built in
Three things that are true here, not promised
These are structural properties of this build, not marketing. Hover or tap each card for the detail behind it.
No notifications. Ever.
A message never lights up the screen.
Hover or tap for detail
The build carries no push package and declares no notification permission. There is no lock-screen preview, no sender name and no badge to read — because a locked phone is where messages are usually discovered first.
The key never leaves the phone.
Only this app can read your messages.
Hover or tap for detail
The key pair is generated on the device. The private key is stored wrapped with AES-256-GCM under a key derived from your code, and the plaintext copy is deleted at install. No server holds it, and there is no recovery path that could hand it back.
The product name is not in the installed files.
The app is called whatever name you chose.
Hover or tap for detail
Each of the 40 covers is its own app: its own manifest, name and icon. A checker fails the build if the product name appears in any cover, so the home screen, the app title and the installed files carry the name you chose — not the real one.
The covers
40 disguises to install it as
Each cover is a real, separate installable app with its own name and icon, chosen when you install and not afterwards. Two can sit on the same phone and the phone treats them as unrelated.
Everyday
- Weather
- Calculator
- Notes
- Calendar
- Files
- Photos
- Compass
- Settings
- Clock
- Recorder
- Flashlight
- Scanner
- Units
- Steps
- Reminders
- Recipes
- Groceries
- Radio
- Podcasts
- Battery
- Wi-Fi
- Translate
- Dictionary
- Books
- Journal
- Sleep
Work
- Timesheet
- Inventory
- Job Log
- Field Ops
- Site Survey
- Tool Crib
- Dispatch
- Work Orders
- Maintenance
- Route Plan
- Stock Count
- Purchase Log
- Safety Check
The cover closes the inside too
The name the install was given is what the app itself reads and shows — launch screen, title bar and settings all follow the cover, not the product.
Switching covers leaves two icons for a while
The old icon does not vanish on its own. Do it when nobody is watching, and remove the old one yourself.
A discovered cover is a worse tell than a boring app
This is the honest cost of hiding: an app that is found out reads as a deliberate secret. Decide whether to hide at all before anything important goes in.
Status
Where this stands
What is built, what has been tested, and what has not.
- 1BX is in development. The parts of it described on this page are built and covered by tests.
- The beta installs from a link rather than a store listing. There is no signup on this page.
- The native checks and the message path are untested on hardware. The install path has not been measured on a handset. Everything described on this page rests on offline tests, not on a handset.
- There is no revenue model, deliberately. No accounts, no payments, no store listing — for this app, an account and a payment are themselves traces.
The technical version — crypto, the gate, and what has been measured
- What it is
- A web app that installs from a link under one of 40 covers. The cover a visitor picks decides the name and icon the phone shows; the product name appears nowhere in the installed files.
- The gate
- The vault's RSA private key is stored wrapped with AES-256-GCM under a key derived from your code with PBKDF2. There is no stored passcode to compare against, and the plaintext copy of the key is deleted at install.
- Crypto
- AES-256-GCM per message, with a fresh key and IV every time. The per-message key is wrapped with RSA-OAEP; the RSA-2048 key pair is generated on the device and the private key never leaves it.
- Data
- Messages and keys live on the device. The vault is excluded from Android cloud backup through
allowBackup="false"anddataExtractionRules, both read out of the built app rather than assumed. - Notifications
- None by construction. The build carries no push package and declares no notification permission, so there is no lock-screen preview to leak.
- Tested by
- A backend suite reporting 149 tests in this environment (145 passing plus 4 skipped, each printing its reason, where the auth emulator is absent), a Flutter suite at 373 passing, and an emulator gate at PASS 28 FAIL 0.
Install it, or pick a different name
The picker above decides which cover installs. It starts on Weather, so doing nothing still installs Weather; any of the other 39 works the same way.
Pick your cover above See all 40 covers
Something broken, or missing? Open the feedback form.
From the same studio
More from this maker
Other products from the same small studio. Each is its own site with its own terms, and none is needed to use 1BX.
ShiftSwapper Pro
Shift scheduling for hourly workers — the same people this beta is built for.