Privacy
Last updated: 29 October 2026
AIB SITAC is a tool for tactical situation maps on wildfires: shared rooms, timestamped marks, and a timeline.
In brief
- Incident metadata and event history (marks) are stored in the product PostgreSQL database when you create or open a room.
- The incident list on home (and the list API) is public: for each room you see title, creation date (Europe/Rome), optional creator, and whether it is password-protected; map center and zoom for protected rooms are not exposed in the list. Opening or viewing marks still requires the link and, if set, the password.
- No accounts in v1: access is the incident link and, if set, the password.
- No analytics SDK included by default.
- The display name (profile on home or in the map) stays in the browser’s localStorage; when creating an incident it may be saved as creator (createdBy), and when you add, move, edit, or remove a mark it is copied onto the event as actorLabel.
- Theme preference (system / light / dark) stays in localStorage if you change it from the default (system).
- Map tiles come from HOT OSM / openstreetmap.fr servers, which may see your IP and the coordinates of requested tiles.
- Guide, Privacy, and Terms from the app open on aib.smnl.dev/sitac (no in-app copies).
Data processed
| Data | Where | Why |
|---|---|---|
| Title, creation date, optional creator, “protected” indicator (home list / API) | Database (+ public API response) | Search and open rooms from home |
| Map center and initial zoom | Database (only after unlock) | Open the room at the right center; redacted in the public list if protected |
| Password hash (optional) | Database | Protect read/write access |
| Map events (geometries, symbols, notes, timestamps, actor name) | Database | Collaborative SITAC and timeline |
| Display name (local profile) | Browser localStorage | Creator on new incidents + label on events |
| Theme preference (system / light / dark) | Browser localStorage | Remember UI theme |
| Map tile requests (zoom/x/y) | HOT OSM tile server | Draw the map background |
| Room password (after unlock) | Browser sessionStorage | Reopen the room in the same session |
Access and password
- Open rooms (no password): anyone with the link can view and edit; live updates via Server-Sent Events. If a password is added, open live connections are closed and you must unlock again.
- Protected rooms: the UI only checks whether the room is protected (same flag as the home list), then shows the map shell with a required password dialog and makes no other requests (detail, events, SSE) until you unlock; every read/write sends the password only as the HTTP X-Passphrase header (never in the URL). The API stores a salted scrypt hash and limits failed attempts. Changing or removing the password disconnects live listeners for that room.
- After unlock, the password stays in the browser’s sessionStorage for that room (cleared when the session ends); it is not put in the URL.
- The profile name stays in localStorage; on creation it may become createdBy, on events it appears as actorLabel. Theme preference stays in localStorage (key aib-sitac-theme) if set.
Sharing and export
GeoJSON / PNG export and shared links leave the app under the rules of whatever tools you save or forward them to (chat, email, files).
