Privacy policy

ProjectSend is built around control, and that includes being clear about data. This website, https://www.projectsend.org (the "Site"), is the home of ProjectSend, a free and open source file sharing application. This policy explains what information the Site collects and how it is used. It does not govern the files or personal data stored inside a self-hosted ProjectSend installation — those remain under the control of the organization operating that installation — nor does it cover ProjectSend Cloud, which has its own privacy policy.

What we collect

The Site is a static informational website. You do not need an account to use it, and we do not ask for your name, email address, or any other personal information.

We use Google Analytics to understand how visitors use the Site (pages visited, approximate location, device and browser type). Google Analytics sets cookies and processes data in accordance with Google's privacy policy. This information is aggregated and does not identify you personally.

Our hosting provider may keep standard server logs (IP address, requested page, timestamp) for security and operational purposes.

What we do not do

• We do not sell, rent, or share visitor data with third parties for marketing purposes.
• We do not show advertising on the Site.
• We do not track you across other websites.

Downloads

Software downloads are served through GitHub Releases. When you download ProjectSend, your request is handled by GitHub in accordance with GitHub's privacy statement.

Links to other websites

The Site links to third-party services (GitHub, Discord, Facebook, Patreon, Docker Hub, among others). Each of those services has its own privacy policy, and we are not responsible for their practices.

Children's privacy

The Site is not directed at children under 13 and we do not knowingly collect personal information from them.

Changes to this policy

We may update this policy from time to time. Changes will be posted on this page with an updated revision date.

Contact

Questions about this policy? Reach out through GitHub or our community channels.