Legal

Privacy

How Tactico Technologies handles data across Pathways, Vertral Spatial Engine, Ionic, and Momentum.

Last updated: 21 August 2026

Language

This privacy notice may be offered in more than one language. If there is any conflict between language versions, the English version shall prevail.

如各語言版本有任何歧義，概以英文版本為準。

Who we are

This Privacy Policy describes how Tactico Technologies handles information when you use our websites and products, including:

  • TACTICO Pathways — covered pedestrian routing for Hong Kong (web / PWA / related apps);
  • Vertral Spatial Engine (VSE) — spatial APIs, path tools, and agentic MCP surfaces;
  • Ionic — multi-agent contract tooling (separate stack);
  • Momentum — goal continuity for long-horizon agents through a local stdio MCP and SQLite store;
  • marketing and company pages (home, product pages, manifesto, licenses, terms).

Contact: [email protected].

Scope

Different Products process different data. Pathways is designed so trip pathfinding stays on your device where possible. VSE and Ionic may run in your environment (CLI, local tools) or, if you choose hosted endpoints, on infrastructure you or we operate. Momentum remains local to your machine. Always check the Product you are using.

Pathways (map & routing)

What we process

  • On-device routing inputs: start, end, and mode choices used for pathfinding in the browser or app. These are not uploaded as a retained trip history product feature.
  • Optional device location: only if you enable location features (e.g. “Near me” or “Start GPS”). Start GPS watches position on this device until you tap Stop. Handled by the platform geolocation API. We do not stream the track to a Tactico backend.
  • Local preferences: theme, language, 3D, walk-roads, offline pack status, and EULA acceptance may be stored in localStorage or similar on-device storage.
  • Offline packs: if you download map or graph data, it is stored in browser Cache / device storage you control.
  • Technical delivery: loading pages, scripts, graph tiles, and basemap assets involves standard HTTP requests. Hosts and CDNs may see IP address, user-agent, and similar request metadata as part of normal delivery and security.

What we do not do (Pathways product design)

  • Require an account to plan a walk.
  • Sell personal walk history or build advertising profiles from your routes.
  • Intentionally retain “from → to” trip query logs as a Pathways product feature (trip zero data retention by design).

Network tiles and basemaps still load over the network unless you have cached them; that is infrastructure data, not your itinerary file.

Vertral Spatial Engine

VSE pathfinding used by Pathways runs on-device. A hosted API, Worker, or MCP surface is coming soon and not generally available. If you later call a hosted VSE endpoint we operate, or embed the libraries in your own systems:

  • Path and graph computation may run in your process or on infrastructure you configure;
  • If you use a hosted endpoint we operate, request metadata (IP, timestamps, payload sizes) may appear in standard operational logs used for reliability and abuse prevention—not as a marketed “trip dossier” product;
  • You are the controller for personal data you send through agents or clients you build on VSE.

Ionic

Ionic is local-first tooling for agent contracts. By product design we do not operate a telemetry product that phones home agent documents or contracts. If you run Ionic against your own repos and CI, processing stays under your control unless you connect third-party services.

Momentum

Momentum is local continuity for agents (versioned goals, typed memory, checkpoints, and resume). Its stdio MCP and SQLite store stay on your machine. Tactico does not operate a hosted Momentum endpoint and does not receive the continuity stream you write. You remain responsible for personal data you place in that local store.

Websites and marketing

Visiting marketing pages may involve the same class of technical logs as any website (IP, user-agent, referrer, pages requested). We do not use third-party advertising trackers as a core product feature. Embedded third-party content (if any) is subject to that party’s policy.

Map and open network data

Pedestrian network data is derived from open sources (including Lands Department 3D Pedestrian Network via CSDI and OpenStreetMap ways). Basemap tiles may come from Protomaps-derived PMTiles we host or from other providers. Loading those assets is not the same as storing your personal itinerary. See Pathways licenses.

Children

The Services are not directed at children under 13 (or the minimum age in your jurisdiction). Do not use them if you are under that age.

Retention

On-device preferences and offline packs remain until you clear site data or uninstall. Server-side technical logs, if any, are retained only as needed for security and operations, then deleted or aggregated. Pathways does not offer a cloud trip history feature.

Your choices

  • Decline location permission in the browser / OS.
  • Clear site storage to remove preferences, EULA flag, and offline packs.
  • Contact us to ask questions about this policy: [email protected].

International users

We may process technical data in regions where our hosts and CDNs operate (for example Cloudflare). By using the Services you understand that such transfers may occur for delivery.

Changes

We may update this Privacy Policy as Products evolve. The “Last updated” date will change. Continued use after updates means you accept the revised policy where permitted by law.

Related

Terms of use · Manifesto · Pathways licenses