Olocus is a private proof layer for lived experience. The record stays with you.
Build a private record of where you were, what you did, and what you can prove — on your device. Compose scoped proofs only when you need them. No score, no public graph, no broker. Olocus turns lived behaviour into user-held claims, never into a profile someone else owns.
Record
Each moment — a presence, a stay, a continuity — becomes a signed private receipt. The bytes live on the device that recorded them. Olocus infrastructure never holds the plaintext.
Share
A proof answers a single question — were you present?, have you maintained continuity? — and discloses only the parts that support that claim. The verifier reads recipe, claim support, subject binding, view policy, validity, and signature as independent rows.
The private record belongs to you, not to Olocus. The relay holds only encrypted scoped-proof bytes the device chose to upload, and only for as long as the user keeps them active.
The relay's data plane is provisioned with the strongest
available EU data-residency setting. The self-hosted maps
backend at maps.olocus.com runs under the same
posture — EU-pinned storage, the same honest-metadata invariants
— so map tiles, geocoding, and routing never leak to a
third-party CDN. Workers run at the edge nearest each user;
durable state stays inside the EU jurisdiction boundary.
Olocus does not maintain a directory, a feed, a reputation score, or a contact-discovery surface. Witnesses are bounded corroborators — never generic endorsers.
Proofs answer specific questions. The underlying graph never leaves the device. Relationship leakage — what a proof reveals beyond its question — is treated as disclosure, not a footnote.
What Olocus does not do. Olocus is not a tracker, social graph, reputation score, data broker, quantified-self dashboard, or surveillance tool. A true proof can still reveal too much — so relationship leakage, witness disclosure, and verifier overreach are treated as product risks from the start.