Straight answers.

Some modern Windows apps create a file only after a destination accepts a drop. Many destinations do not complete that optional Windows negotiation. PWADrop bridges the handoff at the source so the original drag can continue as a normal file drop.

No. PWADrop has no remote file-processing service. Files are prepared locally. If you drop a file into a cloud service or website, that destination may upload it under its own privacy terms.

No. PWADrop runs as the signed-in user and refuses elevated or cross-user source processes.

The current build recognizes supported Chromium browsers and PWAs, New Outlook and New Teams through WebView2, plus explicitly recognized Electron apps such as Slack. It can drop into Google Drive, browser upload zones, File Explorer, and desktop apps that accept standard Windows files. Compatibility can still vary by app version and security policy.

The Store edition provides a trusted Microsoft-signed install, automatic updates, simple removal, and a supported release channel. Source access supports transparency, learning, and community contributions.

The repository is available for study, contribution, and uses permitted by its source-available license. Building requires a Windows native and .NET development toolchain. Commercial use requires an appropriate paid license.

PWADrop is source-available under the PolyForm Noncommercial License. Because commercial use is restricted, it is not an OSI-approved open-source license.

The Microsoft Store handles purchases and available Store updates. Check the current listing for pricing and purchase terms.

No custom telemetry is included today. Microsoft may provide RiddleNEXT with aggregate Store acquisition, usage, and reliability reports under Microsoft’s privacy terms.

Review the repository’s enterprise deployment documentation and license before an organizational rollout. Compatibility depends on Windows configuration and security policy.