Audio file privacy

User audio upload is disabled in the current MVP. That means DJ Library does not accept your private WAV, AIFF, MP3, or vinyl rips through the user interface. The library can display shared release previews that already exist in the OroShop catalog or were prepared by the internal media workflow. Those shared previews are used for listening, BPM/key hints, and release context.

Private library fields are separate from the public catalog. Your media condition, storage location, notes, rating, tags, crates, and track overrides belong to your account. The library API checks ownership through the user session, and DTOs must not include supplier cost, prices, raw payload, object keys, or admin fields. The demo library also creates no users and writes no database rows.

If an audio preview is hosted by OroShop, its public URL may be used by the player as a shared asset. This does not mean user files are uploaded or published. If a preview is external, the browser may contact that external host during playback. External sources can have their own logging and availability policies.

Because only shared previews are enabled, deleting a private library item does not delete a shared catalog audio asset. If user audio upload is added later, it will need a separate policy for storage, deletion, limits, and private access. Until then, do not upload private audio through admin or API workarounds without explicit approval. For account data questions, read the privacy page and contact the service owner.