MDPSRPMason–Dixon Public Safety RP
Information / Privacy

PUBLIC SITE. PRIVATE PERSONNEL RECORDS.

A clear explanation of what this website shares, what it does not share, and how roleplay applications are intended to work.

What is publicly visible

We share the experience—not the playbook.

This public website contains a general server story, high-level career descriptions, public rights education, and introductory recruitment information. It is intended to help players decide whether MDPSRP is the right community for them.

We intentionally do not publish detailed internal operating procedures, exam answers, private staff documents, CAD structure, server security practices, tactical procedures, candidate background records, or sensitive case files.

RP applications

Interest forms request fictional character details and an optional contact handle. Do not submit real identifying documents or personal background disclosures.

Any full employment packet, interview record, training record or confidential application must be processed through an authenticated, access-controlled service before production use.

Actual data retention and access policies must be finalized before collecting real user submissions.

Application data: Public forms accept fictional character details and optional Discord username only. Answers to staff examinations, private recruitment reviews, confidential CAD records, and internal procedures must be stored and served from an authenticated backend, not public site files. Netlify form submissions are accessible to site administrators after form detection is configured; no live delivery is guaranteed before testing.
Support requests and privacy

Community ticket intake

The new Help & Tickets form asks for a fictional or community display name, a contact handle, a support category and, when needed, the department. For ordinary help, it also accepts a brief non-sensitive question.

For Internal Affairs and ban appeals, the public form collects only a contact request and broad category. No allegation narratives, investigation evidence, ban history or private logs should be submitted. Netlify Forms does not provide independent access controls for different department reviewers.

Before the first real submission

Site administrators must publish a complete privacy notice identifying the responsible community operator, how to contact them, Netlify as processor, the intended retention period, who is authorized to read submissions, and how to request correction or deletion.

Until these rules, access limits and a real intake test are verified, do not invite users to file confidential reports through this static site.

Support staff access to form submissions is not separated by category in the public static deployment; restricted ticket queues require a secure backend.

Community media submissions

Our Newsroom has a separate optional suggestion form for public roleplay stories. It may collect your public handle, pitch, content type, and an optional public media link. Do not submit confidential reports, real identity documents or private member information. A submission is only a request for editorial review, not consent for us to publish images of other people.

We will only publish community material after permission and appropriate review. Form submissions are not automatically published or connected to a member portal.