← Back to Milvia

Safety and OPSEC

Reviewed at beta launch

How Milvia's OPSEC review works, what it can and cannot do, and the safety tools available to every member.

How the review works

Every post runs through a deterministic pattern review before it can publish. It looks for movement, timing, location, unit references, capability and personal identifiers.

Categories only escalate each other when the post also refers to movement or to a unit. A date and a place on their own — “the commissary in Naples is closed Monday” — stay low risk. A departure or return combined with a date or a place is treated as high risk.

High risk blocks publishing and offers a sanitized rewrite, which is re-scanned before you can continue. Medium risk does not block the post, but Publish stays disabled until you explicitly confirm you have reviewed the findings. Low risk still shows the responsibility line.

What it cannot do

Milvia will never tell you a post is safe to post. Automated screening can miss context; you remain responsible for what you post.

Images

Image handling is not live yet. Image attachment is a preview of the intended flow: it shows which details would be removed and prompts you to check for background text, badges and faces. No file is actually processed or stored in this version.

Your own footprint

Footprint Check reviews only your own posts, comments and profile and shows what they suggest when combined. It never runs against another member and the score stays private to you.

Report, block, verification

Reporting, blocking and seeing another member's verification status are free for everyone and always will be. Verification shows identity or status only, with its provenance stated — never unit or assignment.