User first
User sovereignty
The user is not a data source to be harvested. User control, consent, revocation, and custody are design requirements, not optional settings.
LAKANA exists for a simple reason: safety technology should protect people without quietly turning their lives into a permanent record for someone else to watch, sell, or control.
The mission is safety without surveillance: local-first systems, narrow evidence release, honest uncertainty, and user sovereignty built into the architecture from the start.
Many safety tools ask people to accept constant tracking as the price of protection. LAKANA takes the opposite position. If a system can protect with less collection, less disclosure, and tighter custody, that is the safer design.
LAKANA is being built for people and institutions that need real safety tools but cannot afford to normalize constant observation: students, athletes, workers, drivers, field crews, families, and communities operating under stress, outage, or coercive conditions.
The goal is not to hide risk. The goal is to handle risk with discipline. A LAKANA system should be willing to hold, narrow, or fail closed when the evidence is not strong enough. It should preserve what happened without opening everything about a person’s life. It should make review possible without making surveillance normal.
The user is not a data source to be harvested. User control, consent, revocation, and custody are design requirements, not optional settings.
Safety logic should stay local when it can. Cloud infrastructure matters for compute, storage, audit packaging, and review — not for continuous surveillance.
When signals conflict, age, weaken, or fall outside the evidence boundary, the system should narrow the claim instead of pretending certainty.
Incident records should be sealed, bounded, and reviewable without turning every ordinary moment into a retained behavioral dataset.
A safety tool must not become a stalking tool, retaliation tool, worker-surveillance tool, or forced-disclosure tool.
LAKANA’s public doctrine rejects a business model built on selling, trading, or exploiting user data.
The mission is backed by public research pages, figures, manuscripts, and claim boundaries. The next stage is careful partner review and narrow pilot design, not broad public-safety claims.