IncidentDraft
Privacy Policy

How IncidentDraft Handles Agency, User, and Report Data

IncidentDraft is designed to support law enforcement reporting workflows while helping agencies understand what information is collected, how it is used, and how it is protected.

1. Privacy Overview

IncidentDraft is designed for law enforcement and affiliated public-safety workflows. This Privacy Policy explains how information may be collected, used, protected, retained, and shared when agencies and authorized users use the platform.

2. Scope of This Policy

This policy applies to IncidentDraft websites, platform pages, user accounts, report drafting workflows, administrative tools, and related support interactions. Agency-specific agreements may include additional data handling requirements.

3. Information We Collect

Account Information

  • Name and work email
  • Role or title
  • Login and authentication details
  • Account status and preferences

Agency Information

  • Agency or department name
  • Agency configuration settings
  • User roles and permission settings
  • Administrative contact details

Report and Draft Content

  • Incident details entered by users
  • Draft narratives and report sections
  • Review notes or workflow status
  • Export or handoff activity

Usage and Security Logs

  • Login activity
  • Device/browser metadata
  • Security and audit events
  • Feature usage and system activity

4. Report and Draft Content

Report content entered into IncidentDraft remains associated with the agency and its authorized users. Draft narratives, templates, workflow notes, and export activity are used to support report drafting, review, quality checks, and RMS handoff preparation.

5. How We Use Information

Information is used to provide the platform, authenticate users, manage agency workflows, support supervisor review, improve reliability, protect accounts, and maintain auditability.

Platform Operation

Powering incident reporting and essential workflows.

Security & Fraud

Protecting user accounts and system stability.

Support

Helping troubleshoot reports and administrative settings.

Optimization

Analyzing interface performance to improve reliability.

Compliance & Audit

Enabling agency-specific logs and compliance checks.

6. AI Processing Transparency

IncidentDraft may use AI-assisted processing to help generate, summarize, or improve draft narrative content. AI output is draft assistance only and should be reviewed by authorized users before official use.

Report content should not be treated as final simply because it was generated or suggested by the system.

7. Cookies and Usage Data

IncidentDraft may use cookies or similar technologies for authentication, session management, security monitoring, preference storage, and application performance. We do not run advertising trackers.

8. How Information Is Shared

Information is not shared with unauthorized third parties for unrelated marketing use.

IncidentDraft does not sell agency or report data.

Data is only shared in the following authorized scopes:

Authorized agency users based on roles and permissions
Service providers used to operate and secure the platform
Legal or compliance requests when required
Agency-approved integrations, such as RMS handoff workflows
Security investigations or abuse prevention

9. Data Ownership and Agency Control

Agencies retain ownership of report content, draft narratives, templates, and operational data entered into IncidentDraft. IncidentDraft does not claim ownership of agency report content.

Agency administrators may manage users, roles, templates, and access according to agency policy.

10. Data Retention

Data retention may vary based on agency policy, deployment configuration, legal requirements, and operational needs. Agencies may request retention, export, archival, or deletion workflows according to applicable agreements and system capabilities.

Created
Active Use
Retention Period
Archive / Delete

11. Security Practices

IncidentDraft uses reasonable administrative, technical, and organizational safeguards to help protect information. No system can guarantee absolute security.

Encryption in Transit

Encryption at Rest

Role-Based Access

Audit Logging

Infrastructure Security

12. Agency Controls

Agencies are responsible for provisioning users, assigning roles, removing access when no longer needed, and ensuring users follow agency policy and applicable law.

13. Privacy Requests

Authorized agency representatives may contact IncidentDraft regarding privacy, data access, correction, export, retention, or deletion requests. Individual user requests may need to be routed through the agency administrator.

14. Changes to This Policy

IncidentDraft may update this Privacy Policy as the platform evolves, legal requirements change, or data handling practices are updated. The updated policy will be posted with the revised effective date.

Questions About Privacy?

Contact us for questions about privacy practices, agency deployment, data handling, security, or compliance requirements.privacy@incidentdraft.com