HELP CENTER
Klaxon support documentation
Everything you need to run Klaxon yourself — written so you never have to contact support. Klaxon is a local-first incident-response war-room and a deterministic breach-notification deadline engine. Your incident data lives only in your browser; the core console makes zero network calls.
Browse by topic
1 · Getting started
What Klaxon is, the local-first / zero-network promise, opening the app, declaring your first incident, and a worked sample incident end to end.
2 · The incident workflow
Facts intake (including per-state individual-notice dates), roles, the playbook library, tasks, evidence, the comms log, and the append-only timeline.
3 · Obligation clocks
How deadlines are computed per jurisdiction (50 states + DC/PR + HIPAA/GDPR/DFARS/SEC/CIRCIA/PIPEDA/Québec), proposed-vs-final labeling, holiday-aware business-day math, the reminder cascade, and filing-status capture.
4 · Notification letters
Generating jurisdiction-correct letters, prefilling from the incident, the missing-required-field guard, substitute-notice / credit-monitoring clauses, and exporting .txt / PDF.
5 · Timeline integrity
The SHA-256 hash chain, the "timeline verified" vs "TIMELINE TAMPERED" badge, and why auditors and cyber-insurers ask for it.
6 · The what-changed feed
How a law-dataset update flags exactly which of your open incidents need a fresh obligation computation.
7 · Opt-in scheduled push (cloud)
CLOUD Wiring the reminder cascade to email / Slack / Teams / webhook — and the guarantee that it never runs on the local incident path.
8 · Security & privacy
Local-first architecture, the zero-network core, what does and does not leave your machine, and the no-PII-in-cloud-payloads guarantee.
9 · Troubleshooting & FAQ
Deadlines look wrong, business-day vs calendar, AG fallback anchoring, the tampered badge, proposed vs in-force, push unavailable offline, the legal-advice disclaimer, and more.
"How do I…?" recipe index
Jump straight to the steps for a specific task.
| I want to… | Go to |
|---|---|
| Open the app and understand the local-first promise | Getting started → Open the app |
| Declare my first incident | Getting started → Declare an incident |
| Walk through a complete sample incident | Getting started → Sample incident |
| Enter incident facts that drive the deadline engine | Workflow → Facts intake |
| Record the real date I notified a state's residents | Workflow → Per-state notice dates |
| Launch a playbook and auto-create tasks | Workflow → Playbooks |
| Attach evidence with a chain-of-custody hash | Workflow → Evidence |
| Understand how a specific deadline was calculated | Clocks → How deadlines are computed |
| Tell why a clock is red / amber / green | Clocks → The countdown states |
| Read the reminder cascade (T-48/24/4h/overdue) | Clocks → The reminder cascade |
| Mark an obligation as filed | Clocks → Filing-status capture |
| Tell proposed rules from in-force ones | Clocks → Proposed vs final |
| Generate a per-jurisdiction notification letter | Letters → Generate a letter |
| Export the deadline calendar (.ics) | Clocks → Export to calendar |
| Export a PIR or auditor / insurance bundle | Workflow → Exports |
| Verify the timeline hasn't been tampered with | Integrity → The badge |
| See which open incidents a law change affects | What-changed → Reading the feed |
| Send the cascade to Slack / email / Teams / webhook | Scheduled push → Wiring a channel |
| Run a tabletop exercise and generate an AAR | Workflow → Tabletop runner |
| Confirm nothing leaves my machine | Security → What leaves the machine |
| Fix "Failed to load content packs" | Troubleshooting → Content packs |
Klaxon is a static, no-build browser app. Every page in this Help Center is plain HTML served from the same site — no login required to read it.