Dukto
UNDERSTAND THE FLOW

Privacy and security

Dukto transfers files directly between devices without collecting your personal data.

Who operates Dukto

Dukto is developed and maintained by Djalma Júnior. Questions about this policy or Dukto's data practices can be sent to contato@djalmajr.dev.

Data collection

Dukto does not require an account and does not collect, sell, or send personal data, analytics, advertising identifiers, crash reports, or file contents to the developer. The app has no advertising or tracking SDKs.

Direct, encrypted transfer

Content travels directly to the device selected by the sender over QUIC with a Noise session. A transfer can expose the selected files, file names, device name, device identifier, network address, and transfer metadata to the participating devices. Dukto does not route or retain this information through a developer-operated server or cloud storage service.

Device access and permissions

Dukto uses network access and Wi-Fi multicast to discover and connect to nearby devices. It uses notifications to alert you about incoming transfers. Files are accessed only when you select them for sending or choose where received files are saved.

Approval and trust

The graphical app asks you to approve each incoming transfer. The CLI requires explicit --accept for automatic receiving. Dukto does not currently provide persistent pairing or a trusted-device list. Display names and advertised IDs are self-reported labels, not proof of a person's identity.

Storage, retention, and deletion

Settings and received files remain on your devices until you change or delete them. You can delete received files with your operating system, clear local app data, or uninstall Dukto. Because the developer does not receive or store your files or personal data, there is no developer-side account or cloud record to delete.

Children

Dukto is a general-purpose utility and is not directed to children under 13. The app does not knowingly collect personal data from children.

Protocol compatibility

Protocol 0.2 requires a receipt containing the transfer ID, item count, and byte count. Update the sender and receiver together. Older applications using protocol 0.1 are not compatible with this receipt.

Policy updates

This policy is effective September 17, 2026. Material changes will be published on this page with an updated effective date.

Development version documentationSuggest an improvement
KEEP EXPLORINGTroubleshooting