Skip to content

Latest commit

 

History

History
146 lines (97 loc) · 6.73 KB

PRIVACY.md

File metadata and controls

146 lines (97 loc) · 6.73 KB

Privacy Policy

Last Updated: Nov 4 - 2025

AltSendme is designed with privacy and security as core principles. This privacy policy explains how the application handles your data and what information may be visible to third parties.

Core Privacy Principles

  • No Account Required: AltSendme does not require user registration, accounts, or any personal information
  • End-to-End Encryption: All file transfers are encrypted end-to-end using QUIC + TLS 1.3
  • Peer-to-Peer: Files are transferred directly between sender and receiver when possible
  • Analytics: GoatCounter is used to collect anonymous transfer stats only — never IP, personal data or file contents.

How AltSendme Works

AltSendme uses peer-to-peer (P2P) networking technology powered by Iroh to transfer files directly between devices. The application:

  1. Establishes Direct Connections: When possible, files are transferred directly between devices using NAT hole punching
  2. Uses Relay Servers as Fallback: If direct connection isn't possible, the application may use relay servers to facilitate the transfer
  3. Encrypts All Traffic: All file data is encrypted end-to-end, meaning only the sender and receiver can decrypt it

Data Stored Locally

AltSendme stores the following data locally on your device:

  • Secret Keys: Cryptographic keys used for node identification (stored in your system's standard storage location)
  • Temporary Files: During active transfers, temporary files are stored in your system's temp directory
  • Downloaded Files: Files you receive are saved to a location you choose

This data never leaves your device unless you explicitly share it (e.g., by sharing a transfer ticket).

Network Connections and Third-Party Services

Relay Servers

By default, AltSendme may use relay servers operated by the Iroh project (n0) when direct peer-to-peer connections cannot be established.

What Relay Servers May See:

  • Connection metadata (IP addresses, connection timestamps)
  • Connection duration
  • Amount of data transferred (bandwidth usage)

What Relay Servers Cannot See:

  • File contents (all data is encrypted end-to-end)
  • File names or directory structures
  • File metadata beyond transfer size
  • Who you are communicating with (only encrypted connection endpoints)

Your Control:

  • You can disable relay servers entirely (this may limit connectivity in some network configurations)
  • You can configure custom relay servers if you prefer
  • Relay servers are only used when direct connections fail

DNS Discovery

When using Node ID-only tickets, AltSendme may use DNS-based discovery services (Pkarr) to find peer addresses. This service may temporarily store:

  • Node addresses (IP addresses) associated with Node IDs
  • This information is used only for connection establishment

Direct Connections

When a direct peer-to-peer connection is established (the preferred method), no third-party servers are involved in the transfer.

Encryption and Security

  • Encryption Protocol: All traffic uses QUIC protocol with TLS 1.3 encryption
  • Content Verification: Files are verified using Blake3 cryptographic hashing to ensure integrity
  • Node IDs: 256-bit cryptographic node identifiers are used for peer authentication
  • No Plaintext: File contents are never transmitted or stored in unencrypted form

Analytics and Usage Data

This project uses GoatCounter, a privacy‑respecting, open‑source analytics service.

What GoatCounter Records :

  • Anonymous total transfer volume

What Is Never Collected via GoatCounter:

  • IP addresses
  • Personal information or user identities
  • File contents, file names, or per‑transfer details/sizes
  • Cross‑site tracking or profiling
  • No cookies, no device fingerprinting, no unique identifiers

GoatCounter is privacy‑friendly by design and respects “Do Not Track”. Learn more on their privacy page.

What This Project Doesn't Do

  • ❌ No personal information is collected
  • ❌ File contents are not tracked
  • ❌ Files are not stored or accessed in any servers - no server end
  • ❌ Invasive tracking services or cookies are not used
  • ❌ Data is not shared with third parties (beyond aggregate analytics)

Open Source and Transparency

AltSendme is open source software licensed under AGPL-3.0. You can:

  • Review the complete source code on GitHub
  • Verify how the application handles your data
  • Build and run the application yourself if desired
  • Contribute improvements to privacy and security features

Your Rights and Control

You maintain full control over:

  • Which files you send and receive
  • Where files are saved on your device
  • Whether to use relay servers (can be disabled)
  • Whether to use custom relay servers
  • Local data storage (can be cleared by uninstalling the application)

Data Retention

  • Secret Keys: Stored locally until you delete the application or clear application data
  • Temporary Transfer Files: Automatically cleaned up when transfers complete or the application closes
  • Downloaded Files: Remain on your device until you delete them

Third-Party Services

AltSendme uses the following third-party services:

  1. Iroh Network Library: Core P2P networking functionality (Iroh Privacy)
  2. Default Relay Servers: Operated by the Iroh project, used only when direct connections fail
  3. DNS Discovery: Used for peer discovery when necessary
  4. GoatCounter Analytics: Privacy-respecting analytics service for aggregate usage statistics (GoatCounter Privacy)

You may review the privacy policies of these services if you have concerns.

Changes to This Policy

This privacy policy may be updated from time to time. The "Last Updated" date at the top indicates when changes were made. Continued use of AltSendme after changes constitutes acceptance of the updated policy.

Contact

If you have questions about this privacy policy or how AltSendme handles your data, please open an issue on GitHub.

Disclaimer

While AltSendme is designed with privacy and security in mind, no method of transmission over the internet is 100% secure. Users should:

  • Only share transfer tickets with trusted parties
  • Be aware that encrypted transfer metadata may still be visible to relay server operators (connection metadata only)
  • Consider using custom relay servers or disabling relays for maximum privacy
  • Understand that direct peer-to-peer connections may expose your IP address to the other party and also to any relay server facilitating the connection.