Skip to content

Privacy

The catalog lives on your phone and is the same for everyone. Your searches and update checks never leave it, so nothing identifies you.

What stays on your phone

Your list of installed apps, your searches in the Android app, and the version comparisons that find updates. None of these are uploaded. The catalog is the same for everyone, so what it holds says nothing about you.

Your phone

  • Installed apps
  • Search terms
  • Update checks

Never uploaded

Zapstore catalog

Apps, releases and their certificates

Release source

The developer’s own, or the catalog

Search runs on the phone, with a model that ships inside the app, so it works offline.

What leaves your phone

  • Catalog updates. Zapstore asks the catalog relay for what changed since your last update. The request says how far your copy goes and which Zapstore version you run. It does not say which apps you have.
  • App downloads. Files come from the developer’s release source, such as GitHub, or from Zapstore’s CDN. Whoever serves the file sees your IP address unless you use Tor or a VPN.
  • What you choose to share. Comments, zaps, stacks and reports are public. Tapping Refresh with your web of trust on the install sheet sends one request, signed with your pubkey, to a service that ranks the people you follow.
  • Bug reports, if you opt in. The app sends no telemetry. During setup, Zapstore asks whether to send anonymous bug reports. They stay off unless you say yes.

Bug reports

When bug reports are on, a crash or logged error is sent as an encrypted message from a one-time key to the Zapstore team. It holds the Zapstore version, the Android version and the error with its stack trace, and no account, device ID or app list. The relay that carries it sees neither who sent it nor what it says. Turn bug reports on or off at any time in Settings.

Using Tor

In Settings, Network is Direct (the default) or Tor. With Tor, every connection Zapstore makes goes through it: catalog updates, relays, downloads and images. If Tor cannot start, Zapstore does not fall back to Direct. Anything tied to your pubkey uses a separate Tor circuit.

Settings with the Tor or Direct network choice

What our servers and this website record

Search on this website runs on our servers, because a web page cannot hold the whole catalog. Searches are not logged, and each IP address may only make so many per minute. Search in the Android app runs on your phone.

The website counts page views with Simple Analytics, through our own server, so your IP address is not sent to them. A page view records the path, the referrer, the browser, the language, the time zone and the screen size.

What an app page says about the app

An app page shows Shares data when the app includes a library that can send analytics, an identifier or a crash report, and Ads when it includes an ad library. The catalog relay reads this from the APK itself, so it does not depend on what the developer says.

Accounts and Social

You need no account to browse, install, or update. To comment, zap, or share stacks, you sign in with your pubkey through a Nostr signer app or a browser extension. Turning Social off in Settings signs you out and removes social features from the app. See Social.

Get Zapstore for Android

  1. Tap Download APK below.Scan the code with your Android phone’s camera.
  2. If Android asks, allow your browser to install unknown apps.
  3. Open Zapstore and finish the onboarding.
Download APK

v2.0.4 · 71.2 MB · Android 10+

Verify the download

On a computer, run shasum -a 256 <the file you downloaded>. It should print: b13e01319fecf0b3ba1fd60132758bd0fa08a235836c52d44fddb412cf1b7137

If you have zsp, Zapstore’s publishing tool, zsp utils extract-apk <the file you downloaded> works too. Its hash should be the same SHA-256: b13e01319fecf0b3ba1fd60132758bd0fa08a235836c52d44fddb412cf1b7137

On the phone, AppVerifier should show this signing certificate: 99e33b0c2d07e75fcd9df7e40e886646ff667e3aa6648e1a1160b036cf2b9320

Source code All releases and notes

Get zsp

  1. Download the file for your computer.
  2. Make it executable and put it on your PATH.
  3. In your project folder, run zsp.

Have Go? This does the same:

go install github.com/zapstore/zsp/v2/cmd/zsp@latest
macOS, Apple silicon Linux, x86-64 Linux, arm64

v2.0.1 · macOS and Linux

Verify the download

On your computer, run shasum -a 256 <the file you downloaded>. It should print the SHA-256 for the one you chose.

macOS, Apple silicon · 18.6 MB 99018fb9744e5ace2b44557550dc333496239912c0e9b1137266d4922c803346

Linux, x86-64 · 23.8 MB 1ef5373f8ecd9ba63d2c3fab98abb0d31b2244a2aac31b3749fb205c7d5f5b38

Linux, arm64 · 22.1 MB e421005ee47cba58293dce4277bb784e4cfe706dbbcb8617d671629d0238be18

Source code All releases and notes