Privacy Policy

Contact info — name, email, department affiliation, rank/years on the job when you provide it. Assessment responses — your answers on the PR6 Assessment and any in-course quizzes or task submissions. Account data — login credentials, subscription status, payment records (payment card data is handled by our processor; we don't store it). Community content — posts, replies, and direct messages you create inside the Police Speak Community. Certification data — completion records, instructor notes, and, for CReW, department-level participation data.

To deliver what you signed up for — the assessment result, the download, the course, the community access. To verify officer status where required. To send account and course communications. To improve the PR6 tools and training based on aggregated, de-identified data. We don't sell your data. We don't rent it. We don't share it with your department without your written permission — see section 5.

Your PR6 Assessment answers and course submissions are treated as sensitive. Individual responses are visible only to you and to certified Police Speak instructors reviewing your work. We may use aggregated, de-identified data (n=769 style research, no names attached) for published Impact Papers and program development. If you don't want your de-identified data included in aggregate research, email info@policespeak.co and we'll flag your record.

The Police Speak Community is cops-only and verified. Posts you make are visible to other verified members. Direct messages between members are private but not encrypted end-to-end — moderators can access them if there's a credible safety concern or a violation report. We don't monitor DMs otherwise. Family-space posts follow the same rules within that room.

CReW involves department participation data — how many officers completed training, aggregate resilience scores, cultural indicators. Individual officer scores are not shared with department leadership unless the officer authorizes it in writing. Departments receive rolled-up reports, not personal records.

Service providers only, and only what they need to do their job: payment processor (Stripe), email delivery (email service provider), course hosting platform, community hosting platform, and cloud storage. Each is bound by their own privacy terms and a data processing agreement with us. We may disclose data if required by a valid subpoena or court order — if that happens and we're legally allowed to notify you, we will.

We use standard session cookies to keep you logged in, plus basic analytics to see which pages actually get read. No cross-site advertising trackers. No selling of behavioral data.

Certification records: kept indefinitely so we can verify your credential later. Community content: kept while your account is active; deleted (or anonymized) within 90 days of account closure. Assessment responses: kept while your account is active; you can request deletion any time. Payment records: kept as long as required by tax law.

You can request a copy of your data, correct anything wrong, or ask us to delete it. Email info@policespeak.co from the address on your account. We respond within 30 days. If you're in a jurisdiction with specific privacy rights (California, EU, etc.), those rights apply and we honor them.

Encrypted connections. Access limited to staff who need it. No system is bulletproof — if there's a breach affecting your data, we'll notify you as required by law and tell you what happened and what we're doing about it.

If we change anything material, we'll email registered users and post a notice on this page. Minor edits (wording, typos) may happen without notice.

Michael Simpkins, Founder · info@policespeak.co · policespeak.co