Privacy & Data
Transparency

❯ public data, public awareness

bigNOSTRals only processes public events from public relays. We do not access encrypted direct messages (kind:4), private channels, or any content protected by encryption. If you post it publicly, it is public by design — on every relay and in every client that subscribes.

This project also serves as a way to raise awareness about the fact that Nostr can be used in either way: extremely private or extremely public. By seeing how the data is used transparently, each person can be deliberate about what they share and what they keep close.

❯ data we collect

• Public Nostr events (kinds 0–40,000+) from public relay subscriptions
• Relay metadata and event metadata (timestamps, kinds, tags — but not private keys)
• BigQuery usage telemetry (for our own cost management — not user tracking)

We do not collect:

• Your IP address
• Your nsec (private key)
• Encrypted or private content
• Cookies or browser tracking
• Any traditional PII (email, phone, address)

❯ deletion requests

We do not store any personal data about you as an individual, and we do not "own" the Nostr data. The data lives on decentralized relays. If you want your data removed, that request should go to the relays that published your events.

We are just the messenger here. In a censorship-resistant medium, centralized deletion is nearly impossible by design. That is not a bug — it is a feature of the protocol. Early awareness is the best defense.

❯ transparency

All our analytics code is open source (see bignostrals). Every metric and transformation is defined in SQL and visible for audit. If you question how something is calculated, you can read the source.

❯ contact

Questions? The data layer is open source — open an issue, or reach out on Nostr.

Or DM via the Nostr network (njump.me).