$hreflang_block $hreflang_block

Scrcpy Trust,
Security & Ethics

Transparency, integrity, and user privacy are at the core of everything we do. Learn how Scrcpy protects you and how you can verify it for yourself.

Open-Source Transparency

Scrcpy is fully open-source software. The complete source code is publicly available for anyone to read, audit, modify, and contribute to. This level of transparency means there are no hidden features, no secret data collection mechanisms, and no undisclosed behaviors. You can download Scrcpy or read our FAQ for more details.

Publicly Auditable Code

Thousands of developers and security researchers have reviewed the codebase since 2018.

Community Contributions

Bug fixes and features are submitted, reviewed, and merged in the open by volunteers.

No Telemetry

Scrcpy does not collect usage data, crash reports, or any personal information.

No Malware Clarification

Scrcpy contains no malware, no spyware, no adware, and no potentially unwanted programs. The software has been distributed to millions of users worldwide and has maintained a clean security record since its initial release.

Verified Clean

Scrcpy has zero security incidents in its entire history. The code is reviewed by the community before every release.

If your antivirus flags Scrcpy, this is a known false positive caused by the software's legitimate use of ADB to communicate with Android devices. We recommend whitelisting Scrcpy or building from source if you have any concerns.

Legal Usage Policy

Scrcpy is licensed under the Apache License, Version 2.0. This grants broad permissions with clear responsibilities.

Permitted Uses

  • Personal and private use on your own devices
  • Commercial use within your organization
  • Modification and distribution of modified versions
  • Patent use as granted by the Apache 2.0 license

License Requirements

  • Include a copy of the Apache 2.0 license when distributing
  • State significant changes made to the original code
  • Include NOTICE file contents if one exists
  • Do not use original project trademarks without permission

Ethical Usage Statement

Scrcpy is intended for legitimate device management, application development, accessibility support, and personal productivity. Users are expected to employ the software responsibly and in compliance with all applicable laws and regulations.

Appropriate Use Cases

  • • Testing and debugging Android applications
  • • Providing technical support to device owners
  • • Creating tutorials and educational content
  • • Managing your own devices remotely
  • • Accessibility assistance for users with motor impairments

User Responsibility Disclaimer

By using Scrcpy, you acknowledge that you are solely responsible for how you use the software. This project and its maintainers assume no liability for misuse, unauthorized access to devices, or any damages arising from the use of Scrcpy.

Respect Privacy

Only mirror and control devices that you own or have explicit permission to access. Unauthorized access to another person's device may violate privacy laws and computer fraud statutes.

Comply With Local Laws

Users are responsible for understanding and complying with all local, national, and international laws that apply to remote access software and device monitoring in their jurisdiction.

No Warranty

Scrcpy is provided "as is" without warranty of any kind. The software is used at your own risk. Always verify downloads and back up important data before making system changes.

How to Verify Your Download

Ensure the Scrcpy file you downloaded is authentic and has not been tampered with.

SHA-256 Checksum Verification

Every release includes a SHA-256 checksum. After downloading, compute the hash of your file and compare it to the published value.

# Windows (PowerShell)
Get-FileHash scrcpy-win64-v3.3.4.zip -Algorithm SHA256
# macOS / Linux
sha256sum scrcpy-win64-v3.3.4.zip

Build From Source

The most reliable way to verify Scrcpy is to build it yourself from the official source code. Build instructions are available for Windows, macOS, and Linux.

  • • Install required build dependencies
  • • Clone the official repository
  • • Follow the platform-specific build guide
  • • Run your self-built binary with confidence

Published by the Scrcpy Open Source Project. Last updated: .

Source code available on GitHub. Licensed under Apache 2.0.

Share:
Download