About ShareDrop.org

ShareDrop.org is an independent web project with a narrow mission: make moving a file between two devices as private and as honest as the browser allows.

Principles

• Truth over slogans. We never claim “files never touch a server” unconditionally — in relay mode, encrypted packets do transit a relay, and the app tells you so in real time.
• Minimum data. No accounts, no file metadata on servers, session state that deletes itself. The best way to protect data is to never hold it.
• Verifiable claims. Every privacy and security statement on this site corresponds to observable behaviour: what the API accepts, what the app displays, what a network capture shows.
• Transfers and ads never mix. The transfer app carries no advertising or third-party analytics, enforced at build time. Advertising appears only on this content site, clearly separated from the transfer flow.

Name and affiliation

ShareDrop.org is not affiliated with the earlier open-source ShareDrop project, with Snapdrop, or with any similarly named product. We share no code, infrastructure or operators with them. This project is an independent implementation built on the public WebRTC standards (W3C WebRTC, RFC 8827/8831/8656).

Contact and governance

ShareDrop.org is built and operated by the ShareDrop.org team, the operator and data controller for this site. General contact: [email protected].

Questions, feedback and problem reports: contact page. Security research: disclosure policy. How our content is produced and reviewed: the editorial policy below.

Editorial policy

The guides on this site exist to explain how browser-based file transfer really works — including its limits. The rules we hold ourselves to:

• Original work only. Articles are written by the people building ShareDrop.org, based on the standards (W3C WebRTC, IETF RFCs) and our own engineering and testing. We do not rewrite other sites' articles or publish unreviewed machine-generated text.
• Tested claims. Where an article makes a behavioural claim, the article header states when it was last verified and against what. Claims we have not verified are labeled as such or not made.
• Failure cases included. Every how-to documents when the approach does not work, not only the happy path.
• Primary sources. Technical statements reference the relevant standard or documented browser behaviour rather than hearsay.
• Corrections. Factual errors are corrected in place and the “last verified” date updated; reports welcome at [email protected].
• Ads never shape content. Advertising on this site does not influence topic selection or conclusions.

Accessibility statement

We aim for the core transfer flow and this website to meet WCAG 2.2 AA for their essential operations. In place today: full keyboard operability with visible focus states; transfer status announced via ARIA live regions without flooding screen readers; success, warning and failure states distinguished by text, not color alone; semantic headings and landmarks; respect for your light/dark preference.

Known limitations: QR codes are inherently visual — every QR flow has a text alternative (link or short code); browser file pickers and save dialogs are operating system UI outside our control. If you hit an accessibility barrier, email [email protected] — such reports are prioritized alongside functional bugs.