Why immersion requires higher trust
You're asking people to overlay their reality. Every decision matters more.
A website can be closed. An immersive layer is harder to escape. That demands a different standard.
The principles
Privacy-first defaults
We don't collect what we don't need.
Security by design
Built in, not bolted on.
Calm technology
Respectful of attention.
Clarity over persuasion
We inform, we don't manipulate.
What we refuse to do
- No dark patterns
- No manipulation loops
- No fake certainty from AI
- No hidden data flows
The tradeoffs we choose
We choose fewer notifications over engagement metrics.
We choose user control over automation.
We choose explicit consent over convenience.
"A recommendation would be 'better' if we stored more context. We don't. We'd rather be slightly less magical than slightly invasive."
What "control" looks like in product
Real control means you can:
- Turn things off completely
- See what's being collected
- Delete your data
- Adjust intensity and frequency
A user turns down "smart suggestions" intensity to minimal—and the product stays fully usable and helpful. That's the test.
How we hold ourselves accountable
- A deep test suite catches regressions
- Security reviews before release
- Clear commitments, publicly stated
- Transparent communication when things go wrong
- "Report an issue" pathway that actually gets read