Skip to content

Privacy Policy

This document explains how Azzamo handles user data and privacy across its services.

Azzamo is designed to minimize data collection and avoid centralized identity systems wherever possible.

Core principles

Azzamo follows a small set of privacy principles:

  • Collect as little personal data as possible
  • Do not require real-world identity
  • Do not sell or monetize user data
  • Prefer open protocols over proprietary tracking
  • Be transparent about data handling

Privacy is treated as an infrastructure property, not a feature.

Identity and accounts

Azzamo does not use traditional user accounts.

  • Authentication is based on Nostr public keys
  • No usernames, passwords, or emails are required
  • No centralized identity database is maintained

Your Nostr public key is your primary identifier within Azzamo services.

Data collected

Azzamo collects only data required for operation and security.

This may include:

  • Nostr public keys
  • Published Nostr events
  • Uploaded media files
  • API request metadata
  • Payment-related technical data

Azzamo does not collect names, addresses, phone numbers, or government identifiers.

Payment data

Payments are handled using Bitcoin Lightning.

  • Azzamo does not store credit card information
  • No bank account data is collected
  • Payment processors are not used

Lightning invoices and payment metadata may be stored temporarily for accounting and troubleshooting purposes.

Logs and technical metadata

To maintain service reliability and security, Azzamo collects limited technical data.

This may include:

  • IP addresses
  • Request timestamps
  • Error logs
  • Performance metrics

This data is used for abuse prevention, debugging, and capacity planning.

Cookies and tracking

Azzamo does not use advertising trackers.

  • No third-party tracking pixels
  • No behavioral profiling
  • No cross-site tracking

Cookies may be used only for essential functionality where required.

Data sharing

Azzamo does not sell or rent user data.

Data may be shared only when:

  • Required by law
  • Necessary to protect infrastructure
  • Required for security investigations

When possible, users are informed of such disclosures.

Third-party services

Some infrastructure components rely on third-party providers.

This may include:

  • Hosting providers
  • Network providers
  • Content delivery networks

These providers may process limited technical data as part of normal operation.

Data retention

Data retention is governed by the Data Retention Policy.

  • Operational data is retained only as long as necessary
  • Backups may persist temporarily
  • Deleted data may remain in caches or backups for a limited time

Refer to the data retention document for details.

User rights

Where technically feasible, users may:

  • Inspect publicly available data associated with their public key
  • Request deletion of supported content
  • Stop using services without penalty

Because Azzamo uses decentralized identifiers, some data may remain available on other relays or networks.

Security measures

Azzamo applies reasonable technical and organizational measures to protect data.

This includes:

  • Encrypted connections
  • Access controls
  • Infrastructure monitoring
  • Regular updates and patches

No system can guarantee absolute security.

Policy changes

This privacy policy may be updated as services evolve.

  • Significant changes are documented
  • Continued use implies acceptance of updated terms

Users are encouraged to review this policy periodically.

Contact

Questions about privacy may be directed through official Azzamo support channels.

Summary

Azzamo minimizes data collection, avoids centralized identity systems, and does not monetize user information.

Privacy is treated as a foundational design constraint.