LEGAL / COMPLIANCE

Privacy Policy

Effective Date: August 2026. Your privacy is a fundamental human right.

1. Introduction

This Privacy Policy describes how DropWire ("we", "our", or "us") handles data. Because DropWire is an encrypted peer-to-peer file transfer engine, our core philosophy is Zero Data. We do not collect, store, sell, or monetize your personal information or the contents of your files.

2. The DropWire CLI App

The DropWire desktop and command-line applications operate entirely on your local machine.

  • Telemetry: The app contains no analytics SDKs, telemetry, or crash reporting.
  • File Contents: All files are encrypted client-side using industry-standard cryptography before they leave your device. We cannot read your files.
  • Peer Connections: IP addresses are temporarily used to establish peer-to-peer WebRTC/TCP connections. This data is transient and never logged by us.

3. The Relay Server

If a direct peer-to-peer connection fails (due to strict firewalls or NATs), traffic may route through our public Relay Server (relay.dropwire.tyes.dev).

  • Zero-Knowledge Routing: The relay only forwards encrypted bytes. It has no access to encryption keys and cannot decrypt your data.
  • No Storage: The relay operates entirely in memory. It does not write your files to disk or cloud storage.
  • Logging: The server may generate standard network logs (e.g., connection timestamps and bandwidth usage) for abuse prevention and rate-limiting. These logs do not contain file metadata.

4. DropWire Website

Our website (dropwire.tyes.dev) is hosted on Cloudflare Pages. Cloudflare may collect basic web traffic data (like IP addresses and user agents) for security and DDoS protection. We do not use third-party marketing cookies or tracking pixels.

5. Changes to this Policy

We may update this Privacy Policy as we add new features (such as user accounts or premium relays). Any changes will be posted on this page with an updated effective date.

6. Contact Us

If you have questions regarding this Privacy Policy or our security practices, please open an issue on our GitHub repository.