Draft — not yet in force
This page is a structural placeholder, not a real Terms of Service. Every section below is a TODO(legal) marker, not actual legal text. Nothing on this page is binding, and no self-serve signup should be considered subject to it until an actual attorney-reviewed version replaces this content.
Draft — last structured 2026
TODO(legal): standard acceptance clause — using the service means agreeing to these terms.
TODO(legal): describe the product (SDR ingestion, transcription, AI correlation, Discord relay) and, importantly, disclaim accuracy — AI-generated transcripts and incident summaries are not guaranteed accurate and must not be relied on as the sole source for dispatch or safety decisions.
TODO(legal): this is the section that actually matters. Recording, storing, and rebroadcasting monitored radio traffic (including public-safety frequencies) has different legal treatment by state and by traffic type (encrypted vs. clear, dispatch vs. tactical). Needs jurisdiction-aware legal review before this product can be sold across state lines — do not ship this page live without it.
TODO(legal): who owns the hardware, who's responsible for lawful operation of the field node, prohibited uses.
TODO(legal): who owns the recorded audio/transcripts/incidents, how long they're kept, what happens on cancellation or account deletion. Note: no retention enforcement exists in the product yet either (see DEFERRED.md) — this section can't promise a retention window the system doesn't yet enforce.
TODO(legal): once a billing model and pricing exist (SAAS_PLAN.md section 6, still undecided) — refunds, proration, what happens to data on non-payment.
TODO(legal): whether any uptime/SLA commitment is made (today: none).
TODO(legal): standard limitation-of-liability language, reviewed against the fact that this product touches public-safety-adjacent data.
TODO(legal): how customers are notified of material changes.
TODO(legal): governing jurisdiction, and a real company legal identity and contact address (SAAS_PLAN.md section 6.6 — not yet decided).
Questions in the meantime? Check the FAQ or sign in to reach us directly.