The app
The belt has no settings. The app has all of them.
The belt vibrates, reads the strap tension and reports a button press. Every decision about what any of that means is a rule on your phone, which means you can change your mind about all of it, at any time, including turning things off completely.
Whether it gets built is up to you, and we mean that literally
Writing the companion apps, keeping them working across phones and supporting them for years is a few months of work and then an ongoing commitment. We are not going to start that for a product nobody is waiting for, and we are not going to pretend it is already underway when it is not.
So the waitlist is not a marketing list. It is the number we are using to decide. If it is there, the apps get written and the belt gets built. If it is not, we would rather tell you that than take your money for something we cannot finish.
Settings
Everything on this page is a switch
A feature you cannot turn off is not a feature, it is an imposition. That is the rule the whole app is built on, and it is why there is nothing to configure on the belt itself.
Who is allowed to reach you
- An allow-list of contacts and apps. Everything else waits.
- A named few who can always break through, each with their own tap pattern.
- Quiet hours, and quiet places by location.
- One switch that silences everything except the people you pick.
What the belt feels like
- Strength of every pulse, per zone.
- Pattern per event type, so you learn them without looking.
- Whether a cue is one tap or a movement travelling around your waist.
- How long the belt waits before repeating itself.
What the button does
- A different action per app: send, capture, advance, answer, run a scene.
- Which actions must have a press and cannot happen on their own.
- Long press behaviour, separate from a single press.
- Off entirely, if you would rather it did nothing.
What the assistant may do
- How long the briefing is, and what it covers.
- Which accounts it can read, all of it read-only.
- Whether anything is allowed to speak without being asked.
- On-device only mode, where nothing leaves the phone.
Identity and sensing
- If research proves them viable: body signalling and gait verification, both opt-in.
- Any validated biometric feature would explain what is stored, where it is stored, and how to delete it.
- Any validated waist or wear measurement would be optional, exportable and erasable.
- A possible future per-device list for explicitly approved authentication targets.
Defaults
The uncomfortable things start off
Recognising you by the way you walk would use biometric data. Putting a signal through your body for authentication would do the same. Both ideas may be useful if proven, but neither has been validated.
Neither capability has been validated. If either is ever developed, it would default to disabled; the app would explain what is stored, whether it leaves the phone, and how to delete it. The same rule would apply to any validated waist measurement or wear history.
There is no always-on microphone anywhere in this. A voice session starts only inside the app on your phone, and never on the belt, which has no put it back.
Tell us it is worth building
The waitlist decides whether the app happens. Reply to the first email with the one setting you care about and it goes to the top.
Thinking about backing it instead? Read the investor page