Privacy-by-Architecture Layer Pack
Coordination without surveillance.
Timeverse provides spatial context using SWT zones + Tiles—a deliberately coarse, privacy-preserving layer that makes fine‑grained tracking impossible by design.
Privacy by architecture (not policy)
Timeverse does not “hide” GPS. It simply does not produce it.
You can’t leak what you never collect.
What it is
Instead of GPS coordinates, Timeverse represents location as:
- SWT zone (1..12)
- Tile ID (1..600)
Tiles are intentionally large to support distributed coordination while being structurally insufficient for individual tracking.
What you get (business outcomes)
- Reduced compliance risk
Data minimization is built in: no fine-grained location field to secure, store, or explain.
- Safer agent and IoT policies
Policies can still be location-aware (coarsely) without enabling trajectory reconstruction.
- Better trust story
You can say, truthfully: “We do not collect GPS in the protocol.”
Best for
- IoT fleets (coordination without tracking)
- Agentic systems (context without surveillance)
- Security workflows (proofs tied to a coarse region, not a person)
- Regulated environments where minimization matters
How it integrates
- Gateway and policies can bind scope to SWT/Tile
- TSAE receipts include SWT/Tile for auditable coarse spatial context
- Optional: anchors into Clockchain for durable proofs
Packaging
- Included in Team
- Enterprise adds configurable policies, exports, and retention