holypanda.dev apps

Privacy Policy

01 / Fogata

Developed by holypanda.dev

Fogata has no servers, so holypanda.dev never receives your messages, calls, files or contacts, unless you send a problem report yourself.

  • No account, no sign-in, no phone number or e-mail address.
  • No telemetry, analytics or crash reporting. Settings → Report a problem writes a report that you read first and then send yourself, by e-mail or as a file. Names, folders and addresses are taken out of it.
  • Messages, calls and files go from device to device, encrypted between the devices. Room chats are gone when the last person leaves the room; direct chats are kept on the two devices, encrypted on disk.
  • When two devices cannot reach each other, another member of a group they share may carry their traffic. It stays encrypted end to end: that member can see who talks to whom, when and how much, never what is said.

What leaves your device

  • Traffic with your friends and the members of your groups.
  • Lookups in the public IPFS distributed hash table, used only as a phone book. They see this device's network addresses, as any peer you connect to does.
  • While its list of known peers is empty, DNS questions to your system's DNS server for the addresses of the hash table's public bootstrap peers.
  • On your local network, mDNS questions, so devices on the same network find each other without the internet.
  • A look at Fogata's releases on GitHub at every start and every few hours, for a new version. GitHub sees your device's address and that it runs Fogata. New versions also come from friends who already have them; Fogata installs only versions signed with the holypanda.dev release key.

Fogata has not yet been reviewed by an outside security auditor. Do not rely on it for anything that would put you in danger. The full and always up-to-date details live in the Fogata README and its architecture and threat model.

02 / CrabyTube

Developed by holypanda.dev

CrabyTube does not collect, store, or share any personal data.

  • No account and no login. CrabyTube uses YouTube Music anonymously and stores no credentials or cookies.
  • No telemetry, analytics or crash reporting.
  • Network requests go only to the services needed for the features you use: YouTube Music, YouTube and Google servers (catalog, artwork, audio and the BotGuard challenge), and the lyrics services LRCLIB and Better Lyrics. Discord Rich Presence (off by default) talks only to the Discord client running on your computer.
  • On Windows and macOS, the update check (on by default, Settings → Updates) downloads update.json and its signature from the latest release on GitHub once a day, and the new package when you choose to update. The requests carry the app's version in their user agent and nothing about you. The Flatpak makes no update requests.

Lyrics

  • LRCLIB (lrclib.net) receives the track's title and artist.
  • Better Lyrics (api.betterlyrics.org) receives the title, the artist and the duration when they are known, and the YouTube video ID; its QQ Music and Kugou lookups go through the same service.
  • Lyrics are requested when the Lyrics tab is open, and also during the last 30 seconds of a track for the next track in the queue. Fetched lyrics are cached on your computer for 30 days.

Files on your computer

  • The track that plays and the next one are downloaded to a temporary folder in the cache directory while they play. Files left behind by a crash are removed when CrabyTube starts.
  • The CRABYTUBE_NETWORK_DIAGNOSTICS environment variable, meant for troubleshooting, makes the BotGuard helper send one request to api64.ipify.org each time it runs. It is off unless you set it.

The full and always up-to-date details live in the CrabyTube README.

03 / This website

holypanda.dev

This website uses no cookies, no analytics and no tracking. Its videos are hosted here, not on YouTube.

Questions? Write to contact@holypanda.dev.