Privacy · notice
Last updated 2026-05-05 · pre-public-release.
AgniKawach is operated by the project team behind the consequence-modelling platform. This
page describes what data the demo and cloud platform handle, why, and how to remove it.
What we collect
- Scenario inputs you submit through the Scenario Builder, Geometry Viewer, or API — substance, release rate, geometry files, atmospheric class, receptor positions.
- Solver outputs generated from those inputs — concentration / flux / probit fields, reports, casebook PDFs.
- Account metadata for cloud users — email address, organisation, JWT session token. No password is stored in plaintext.
- Operational telemetry — solver wall time, MLMG iteration counts, plotfile size. Used to size capacity; never linked to scenario contents.
What we do not collect
- No analytics or third-party trackers on the demo pages. The static frontend ships with no script tags pointing outside the AgniKawach origin.
- No advertising identifiers. No cookies are set beyond the session-storage member-area gate.
- No telemetry from the local member-gated docs (Tier-1, Tier-2, Coverage, Casebook, Roadmap).
Why we collect it
- To run the consequence simulation you requested and return the result.
- To produce regulator-ready outputs (PNGRB ERDMP, OISD, COMAH, Seveso) — see the compliance guide.
- To diagnose solver failures you report. Crash plotfiles and logs are kept for 30 days, then purged.
Where it lives
- Scenarios + plotfiles for the cloud platform are stored in S3, encrypted at rest, with per-tenant key isolation.
- The local demo (this site, served from your machine or a single VM) keeps everything in process memory and the working directory; nothing leaves the host unless you explicitly export it.
Your rights
- Export every scenario you have submitted as a JSON bundle.
- Delete an account; we purge all linked scenarios and outputs within 7 days.
- Object to specific processing — write to the address below.
Children
AgniKawach is a process-safety engineering tool. It is not directed at children and we do not knowingly collect data from anyone under 16.
Changes to this notice
We will update this page when material changes are made. Substantive changes are also called out in the changelog.