Skip to content

Data Retention

This document explains how Azzamo handles data retention across its services, including Nostr relays, media uploads, and APIs.

The goal is to be clear about what is stored, for how long, and under which conditions data may be removed.

General principles

Azzamo follows a few simple principles regarding data retention:

  • Retain data only as long as it is useful or expected
  • Prefer explicit rules over silent deletion
  • Avoid retroactive changes where possible
  • Be transparent about limits and exceptions

Data retention policies may differ per service.

Nostr relay data

Reading and storage

  • Azzamo relays store Nostr events to support availability and performance
  • Reading from relays is always allowed
  • Storage behavior depends on the relay type (free or premium)

Premium relay retention

  • Events published to the premium relay are intended for long-term retention
  • Notes are not automatically purged due to age
  • Deletion follows standard Nostr deletion semantics

Free relay retention

  • Events on the free relay may be subject to shorter retention periods
  • Older or low-value data may be pruned
  • Retention rules may change to protect service health

Media data (Azzamo Blossom)

Media uploads are handled separately from relay data.

  • Media is stored using content-addressed identifiers
  • Uploaded files are associated with the uploader’s public key
  • Retention depends on storage tier and usage

Storage limits

  • Each user has defined storage limits
  • Exceeding limits may prevent new uploads
  • Upgrading storage extends retention capacity

Deletion and cleanup

Media may be removed if:

  • The user deletes it explicitly
  • Storage limits are exceeded for an extended period
  • A downgrade removes eligibility for storage
  • Legal or security reasons require removal

Deletion is not always immediate.

API data

Azzamo APIs are designed to minimize stored data.

  • Cashu API does not store balances or tokens
  • Temporary data may be kept for processing and auditing
  • Ban API stores moderation-related metadata

API data is retained only as long as required for correct operation.

User-initiated deletion

Where supported:

  • Users may request deletion through standard Nostr mechanisms
  • Media deletion may be available via supported clients
  • Deleted content may persist temporarily in caches or backups

Deletion requests are honored where technically feasible.

Backups and redundancy

To protect against data loss:

  • Backups may be created periodically
  • Backup data may persist after deletion for a limited time
  • Backups are not directly accessible to users

Backups are used strictly for recovery purposes.

Exceptional circumstances

In rare cases, data may be removed or retained outside normal rules due to:

  • Legal obligations
  • Security incidents
  • Abuse or operational emergencies

Such actions are taken conservatively and documented where possible.

Changes to retention policies

Retention policies may evolve as services change.

  • Changes are documented in the changelog
  • Major changes are communicated in advance when feasible

Users are encouraged to stay informed.

Summary

Azzamo aims to balance availability, reliability, and responsible data handling.

Retention rules vary by service and access level, but silent or arbitrary deletion is avoided whenever possible.