Skip to content
MR Clips Global

Security and responsible disclosure.

MR Clips keeps sensitive operations out of the public frontend, publishes installer integrity details and accepts responsible vulnerability reports.

Official installer SHA-256 No server secrets in frontend

Installer trust

Download only MRClips-Setup-v4.6.4.exe from official links and compare SHA-256 when needed. Digital signing remains a commercial trust roadmap item until publisher signature details are shown on the download page.

License and APIs

Client-safe public keys may appear in the frontend, but service role keys, Paddle API secrets and webhook secrets must not. PUBG/KRAFTON keys used by the desktop workflow should stay local or in protected backend paths.

Disclosure

Report suspected vulnerabilities with reproduction steps. Do not exfiltrate data, attack other users or publish details before MR Clips can triage.

Public forms

Public creator forms should use rate limiting and optional Turnstile verification when configured, while private admin routes remain protected by Access and server-side checks.

Public form protection

Creator forms can use rate limiting and optional Turnstile verification when configured. Private admin paths remain protected by Access and server-side checks.