WardenPoint protects alert routing, recipient data and delivery history with concrete controls we can describe in plain English: TLS in transit, scoped API keys, audit-aware retention and per-company isolation. No marketing badges we cannot back.
What we do
What we don't claim
Four pillars
Four buckets cover the security surface for an alerting workflow. Each lists the actual control we have wired in code, not a generic best-practice promise.
01 · Transport
Every byte that leaves your monitoring tool or our dashboard travels over TLS. Public HTTP redirects to HTTPS at the edge.
02 · Identity
Two distinct identity layers — API keys for machine traffic, session auth for humans — and never an integer ID in a public URL.
03 · Retention
Delivery records and audit events are kept long enough for incident review and short enough that nothing lingers unread.
04 · Tenancy
Every request resolves a Company at the middleware layer. There is no shared dataset between tenants — and we test for cross-tenant leakage.
Audit trail
When WardenPoint sends a notification or runs an escalation step, it writes a single audit line. The shape is stable, machine-readable and includes enough to investigate without exposing recipient content.
eventLifecycle marker — dispatched, acknowledged, escalated, failed.company_uuidTenant scope — present on every line for safe filtering.notification_uuidStable lifecycle identifier across all steps of one alert.actorWhich API key or user triggered the event.ipSource IP for machine traffic — captured at the edge.request_idCorrelates audit lines with application logs.Honest boundaries
Claiming a certification or feature we do not actually run would help nobody. These are the boundaries we explicitly leave outside the security posture today.
We hold no ISO 27001, SOC 2 Type II, HIPAA, PCI-DSS or FedRAMP certification. If you need to procure under one of those frameworks, please contact us before assuming coverage.
Messages travel over TLS to each channel provider, but we cannot guarantee end-to-end encryption between sender and recipient — that depends on the channel (Telegram, SMS carrier, mail relay).
We do not store voice-call recordings forever. Retention is bounded and configurable. If you need long-term retention, run your own archive against the audit log.
We do not aggregate or sell traffic data across tenants for marketing or model training. Per-company scope is enforced at the middleware layer.
Your half of the contract
Most alerting incidents come from the customer half of the boundary — leaked keys, stale recipients, unclear consent. A few habits keep the surface small.
Issue a new key whenever someone with access leaves the team. Old keys revoke instantly from the dashboard.
Never commit keys to git. Use environment variables, a secret manager, or the deployment platform's secret store.
WardenPoint dispatches to the contact information you submit. Confirm that each recipient has opted in to voice or SMS contact for the categories you send.
If you wire WardenPoint into a new monitoring tool, run a test alert and read the audit log entry. The actor, channel and status fields catch most setup mistakes.
Security questions
Start on the free plan, create an API key, send a sample alert and read the audit log entry. No credit card. No data shared outside delivery.