Diagram Pipeline

RadioWatermelon Data Pipeline (Simple & Speculative)

This is a conceptual overview only. Not proof — just possible data paths based on the infrastructure they use.

[People in Gaza]
      │
      │  Video call / photo / verification data
      ▼
[Discord]  ←—— biometric data + chat + metadata
      │
      │  (data stored on Discord servers – US jurisdiction)
      │
      ▼
[GoDaddy]  ←—— domain + hosting + possible files/backups
      │
      │  (data on US infrastructure)
      │
      ├─────────────────────┬─────────────────────┐
      │                     │                     │
      ▼                     ▼                     ▼
[RW Internal Access]   [US Legal Process]    [Breach / Mismanagement]
 (admins & team)        (CLOUD Act etc.)      (leak, sale, misuse)
      │                     │                     │
      └─────────────────────┴─────────────────────┘
                          │
                          ▼
              [Any party that gains access]
              (voluntarily, formally, or improperly)

Short Explanation

1. Data source
   People submit video/face/voice/metadata through the verification process (Discord).

2. Storage

   • Discord stores communications and files.
   • GoDaddy handles domain/hosting (and possibly related files).
     Both fall under US jurisdiction.

3. Possible ways data can leave (speculative)

   • Accessed by RadioWatermelon’s own admins/team.
   • Requested through formal US legal channels.
   • Leaked or misused due to poor handling.
   • Shared voluntarily with other parties (if there is cooperation or pressure).

Core Risk

Biometric data that enters Discord + GoDaddy is not only under RadioWatermelon’s control.
Because the infrastructure is in the US, there are formal and informal paths that can allow other parties to access it.

This remains speculative and general. It is not a claim that any specific party has already taken the data.

My Puddin