{"resourceId":"footnote4a-axon-prepared-911-terms-20260729","versions":[{"version":"external-42ea534e13e3023b33bec309df7943594ea2e079f3cfca84510a83c71b075862","resource":{"id":"footnote4a-axon-prepared-911-terms-20260729","title":"Footnote4a: Axon/Prepared 911 terms claim ownership of caller data and unilateral modification rights","organization":"Footnote4a (H.C. van Pelt)","sector":"Independent investigative reporting / public-safety technology contracts","geography":"United States (Axon/Prepared/Flock 911 product terms affecting local PSAPs)","publishedAt":"2026-07-29","publicationDate":"2026-07-29","eventDate":"2026-07-29","sourceName":"Footnote4a","sourceLabel":"Footnote4a analysis of Prepared/Axon 911 terms of service and privacy policy","sourceUrl":"https://footnote4a.org/news/axon-contract","evidenceClass":"independent-reporting","outcomeClass":"cautionary","topics":["data-security","governance-procurement","operating-model"],"finding":"July 29, 2026 Footnote4a investigation argues FlockOS 911 order forms still bind agencies to Prepared/Axon terms hosted on prepared911.com after Axon acquired Prepared. Analyzing terms versions through v8 (authored Jan 2026, published online May 14, 2026 per Webflow asset IDs), the piece highlights Axon's claim that all right, title and interest in Caller Data remain with Axon and its licensors; agencies get a limited license back. Client Data (including telecommunicator–responder audio/transcriptions in later versions) is licensed perpetually for service improvement and other Axon products. Privacy policy (still Invictus-branded/May 2024 text as of the article) states sessions may be used for business needs and retaining personal information for 10 years under a HIPAA framing, contrasting Apple's shorter emergency-data deletion expectations. Terms allow unilateral website changes applying to prior orders.","sledRelevance":"Independent contract/privacy scrutiny of the same Prepared/Axon 911 assistive stack featured in current PSAP QA deployments. Why now: not archived; newly relevant beside St. John's Prepared AQA case study when SLTT buyers expand Axon 911 Intelligence after 2026-09-27.","evidence":"Opened footnote4a.org HTML via curl. Dated Jul 29, 2026; Caller Data ownership quote; perpetual Client Data license; 10-year retention quote; unilateral modification clause; version timeline including May 2026 v8 from page.","architectureImplications":"Assume vendor-cloud processing of live 911 sessions/transcripts unless contracts mandate on-prem or strict residency; design agency logging of what leaves the PSAP.","governanceImplications":"City attorneys must read current prepared911.com terms (not reseller gloss), freeze versioned PDFs, and negotiate ownership/retention/sub-processor limits before AQA/transcription buys.","securityPrivacyImplications":"Caller audio, location, and optional Medical ID/ELS feeds may be swept into broad vendor licenses; align retention with public-safety records law and Apple/Google emergency-data rules.","caveats":"Legal/investigative interpretation of public terms—not a court finding; enforceability and which version binds a given agency may vary; does not measure product accuracy.","streamIds":["emergency-services"],"roles":{"sales":"Use Footnote4a's July 2026 terms analysis to open a procurement-risk conversation whenever Prepared/Axon 911 assistive tools (QA, transcription, live listen) are proposed. Discovery should ask which terms version was signed, who owns Caller Data, retention defaults, and whether medical-ID side channels are authorized. Bounded engagement: contract redline workshop with city attorney before any pilot expansion. Unsupported claims include that reseller order forms already protect callers, or that HIPAA citations equal 10-year necessity.","engineering":"Fit assessment must include data-flow diagrams for audio, transcripts, location, and optional Medical ID/ELS into vendor clouds. Architecture should prefer agency-controlled retention, immutable term snapshots, and export/delete APIs. Prerequisites: current terms PDF, subprocessor list, and mapping to state records laws. Constraints: unilateral web-term changes; ownership clauses favoring vendor. Proof of value for privacy is contractual lock-in and technical enforcement—not marketing privacy slogans.","delivery":"Delivery includes legal review gates, privacy impact assessment, and operational logging of vendor access. Dependencies: city attorney, CIO/privacy office, ECC leadership, and vendor counsel. Ownership: privacy officer for data rights; ECC for operational use. Acceptance: signed DPA with agency ownership/license clarity, retention ≤ legal minimum, and no silent unilateral material changes. Risks: public trust incidents and multi-vendor term conflicts (Flock vs Axon)."},"roleDetails":{"sales":{"customerProblem":"Agencies adopting 911 assistive AI may unknowingly accept vendor ownership/retention of caller data via website terms.","stakeholders":["City attorneys","ECC directors","Privacy officers","Elected oversight"],"discoveryQuestions":["Which terms version is signed?","Who owns Caller Data?","What is retention?","Are Apple/Google emergency feeds authorized?"],"valueHypothesis":"Assistive 911 AI can proceed only if data-rights terms are negotiated to agency-acceptable ownership and retention—not clicked through.","potentialEngagement":"Pre-pilot contract and privacy redline with term-freeze artifacts.","unsupportedClaims":["Order-form gloss equals protection","10-year HIPAA retention is mandatory","Vendor ownership is standard and harmless"]},"engineering":{"fit":"Contract/data-flow control plane for cloud 911 assistive AI (transcription/QA/live).","architectureIntegration":"PSAP audio/session → vendor processing → agency systems; enforce retention, access logs, and deletion.","prerequisites":["Versioned terms PDF","Data-flow diagram","Subprocessor inventory","Records-law mapping"],"constraints":["Unilateral web term changes","Vendor-favorable ownership clauses","Cross-reseller ambiguity"],"security":"Minimize session data sent to vendors; block secondary use for product improvement unless explicitly approved.","proofOfValue":["DPA with locked retention","Demonstrated delete/export","No undocumented subprocessors"]},"delivery":{"work":"Run PIA, negotiate DPA, freeze terms, and monitor vendor policy pages.","dependencies":["City attorney","Privacy/CIO","ECC","Vendor counsel"],"ownership":"Privacy officer owns data-rights; ECC director owns go-live decision.","skillsAdoption":"Train procurement and ECC leads to read assistive-AI terms, not only feature decks.","governanceCheckpoints":["Legal gate before pilot","Quarterly terms diff","Public records retention check"],"acceptanceCriteria":["Agency-acceptable ownership/license","Retention capped","Change-control on terms"],"risks":["Silent term changes","Caller-data secondary use","Public controversy"]}},"retrievedAt":"2026-09-28T22:06:15-05:00","enrichedAt":"2026-09-28T22:06:15-05:00","enrichmentBasis":"retrieved source","accessibilityWorkforceImplications":"Transparency gaps on 911 data use can erode public and telecommunicator trust even when tools are framed as assistive.","procurementImplications":"Treat terms/privacy URLs as living documents; require negotiated DPAs with locked retention, ownership, and no unilateral material change.","operatingModelImplications":"Separate operational enthusiasm for AQA/transcription from data-rights acceptance; escalate unresolved ownership clauses before go-live.","sourceVerification":{"responseId":"curl-footnote4a-axon-20260928T220615","openedUrl":"https://footnote4a.org/news/axon-contract","referenceExcerpt":"Caller Data shall remain with Axon and its licensors","promptVersion":"sled-research-v4.0","model":null,"basis":"agent-reported inspection"}}}]}