Trust
These are the things Belo can't do.
Not won’t. Can’t. These are not promises about how Belo behaves. Most are limits on what Belo can do at all. Where one is a choice rather than a limit, the card says so.
The difference
One of these words is a promise. The other is architecture.
A policy. Written by a company, changed by a company, and you find out in an email you don’t read.
A limit in how the thing is built. It doesn’t depend on us keeping our word, and you can check it.
The five signals
What each one reads. What it never reads.
Timing
When you’re busy, when you’re free, how long you’ve got, roughly where, and how many people are with you.
Never: who those people are. Belo keeps a count, not a guest list.
Geography
The places you stop, and the rhythm of where you go.
Never: a trail of how you got there. Belo keeps where you stopped, not the path between stops.
This one is a choice, not a limit. Belo could keep the route. It doesn’t.
Relationships
Who you actually see, and how often.
Never: anything from their accounts. Belo knows the names you gave it, and that someone keeps showing up.
Taste
What’s worth a photo, read on your phone. The conclusion is what leaves.
Never: the pictures in your camera roll. Those stay on the device.
A photo you send Belo on purpose, like a City Hunt entry, is different. That one you chose to send, and Belo keeps it.
Habit
What you buy and how often, via Plaid.
Never: your balance, and never your login. We can’t see you log in.
Location, only when your phone allows it.
While the app is open, Belo uses your location to find what’s near you. When you allow “Always,” Belo recognizes when you arrive somewhere you go and has your order ready to send in one tap.