Skip to content

docs: privacy page — what the site collects, what the apps dial - #53

Open
mptfire wants to merge 1 commit into
zig-nostr:mainfrom
mptfire:docs/privacy-and-third-parties
Open

mptfire wants to merge 1 commit into
zig-nostr:mainfrom
mptfire:docs/privacy-and-third-parties

Conversation

@mptfire

@mptfire mptfire commented Nov 15, 2026

Copy link
Copy Markdown

What

A privacy page stating plainly what the site collects (nothing: no analytics, no cookies, only a localStorage theme entry) and — the part only discoverable by reading source today — which third-party destinations the apps talk to on a fresh install, with when/why:

  • Plaza: your relays + NIP-65-derived relays; 2 NIP-50 search relays; NIP-05 domains; Blossom servers (yours, or the 2 built-in fallbacks); GitHub update check (6 h, opt-out); njump.me only on share/open.
  • Notary: configured relays only; loopback approval API; passphrase-gated audited key export.
  • deed: only what you name on the command line; MCP over stdio; publish gated.

Why

No first-party collection deserves saying out loud, and the default third-party list should not require a source dive. Please review the endpoints/wording for accuracy — the built-in Blossom + search relays are taken from the current source.

Related: security headers PR, native FetchOptions.max_redirects/user_agent PR, plaza fetch-hardening PR (same audit).

The site runs no analytics and sets no cookies, and the apps make
no first-party collection — but nothing on the site says so, and
the third-party defaults a fresh install reaches out to (two
Blossom media servers, two NIP-50 search relays, the GitHub update
check) were discoverable only by reading source. List them, with
when and why, per app. Also covers Notary's loopback approval API,
deed's stdio MCP, and the optional media proxy.
@vercel

vercel Bot commented Nov 15, 2026

Copy link
Copy Markdown

Someone is attempting to deploy a commit to the himmelio's projects Team on Vercel.

A member of the Team first needs to authorize it.

@mptfire
mptfire marked this pull request as ready for review November 16, 2026 22:04

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant