Privacy policy
This policy describes the public SiegeMap v0.1 prototype. It has no account, cloud sync, analytics, advertising, payment, or live AI connection.
Effective 30 August 2026Campaigns, goals, moves, troop assignments, questions, deterministic Demo counsel, mission packets, proof notes, preferences, and the Chronicle are stored in your browser’s local storage. The service worker stores public application files in a local browser cache so the core board can work after a successful online visit.
The v0.1 application does not send your campaign, counsel, mission, or proof text to SiegeMap, MagicAds, OpenAI, Anthropic, xAI, or another model provider. It does not use analytics cookies or an advertising SDK. Normal hosting infrastructure may process technical request data such as IP address, user agent, requested path, time, and security logs to deliver and protect the public site.
You can export a human-readable kingdom file through Export / import. You can delete app data with the confirmed reset control or by clearing this site’s browser storage and cache. Because current goal data is not uploaded to an app database, SiegeMap has no server copy of that goal data to retrieve or delete.
Imports are validated locally before they replace the current local board. Exported files contain the private text you entered. Store them securely and avoid entering passwords, API keys, financial account details, medical records, or other secrets into campaigns or mission packets.
Advisor responses are deterministic local demonstrations labelled Demo counsel. Economic-agent missions are local coordination records. Approval flags do not authorize or perform a payment, destructive action, public send, secret access, provider request, or irreversible change.
Before live model providers, cloud accounts, analytics, payments, or MagicAds are activated, this policy must be updated with the relevant controller, purposes, data fields, recipients, retention, choices, and contact route. The current interface states that ads are inactive.
See the public support page for the current support scope. No branded human-support inbox is claimed until a product domain and mailbox are selected and verified.
Last updated: 30 August 2026