Skip to the content
PubHubs
Menu

Security and privacy

This page is for your privacy officer and your IT team. It explains who is responsible for what, which data lives where and how PubHubs is secured. For your members, there is the privacy policy.

Who is responsible for what

  • The PubHubs login is provided by the Privacy by Design Foundation (Stichting Privacy by Design) in Nijmegen, along with the web app and the apps. The login’s servers are in Nijmegen, and Radboud University manages them on the foundation’s behalf.
  • Your hub belongs to your organization, so you are responsible for what happens in it, such as its messages, files and rooms, and for who is a member.

Which data lives where

  • Centrally, PubHubs doesn’t store a member’s email address and phone number themselves, only an encrypted fingerprint of them. It also stores the number of the member’s PubHubs card and an encrypted pseudonym. The member’s settings are stored too, but they’re encrypted on the member’s own device, so PubHubs can’t read them.
  • Your hub holds each member’s pseudonym for your hub and what they do there, such as their messages and files and the name and picture they choose. It gets no email addresses or phone numbers.
  • No single server knows both who someone is and which hubs they visit.
  • Messages in a hub aren’t end-to-end encrypted, so your hub’s administrators are able to read them.
  • Your hub runs where you choose, on your own servers or with a hoster. That means you decide how its data is stored and managed, and who has access to it.

How PubHubs is secured

  • Connections are always encrypted, and members’ settings are encrypted on their own device before they leave it.
  • Members show only what’s needed with Yivi, such as their age or postcode to enter a secured room. Yivi first shows them what they’re about to share.
  • Post-quantum cryptography is used alongside classic cryptography by the servers behind the PubHubs login. It protects the secrets they share and what they sign for hubs.
  • When PubHubs bans an account, its phone number can’t be used for a new one.
  • PubHubs is open source. The source code is public under the Apache License 2.0, so anyone can check how it works.
  • You choose when to update. Every release of the hub is published under its own version number, along with what changed in it.
  • There’s no tracking on the site, in the web app or in the apps. They use no cookies, and no analytics or advertising from third parties.
  • Security problems can be reported privately through GitHub.

Questions?

Does your organization have questions about privacy or security, for example for its own assessment? Mail us.