Guide >

Data and file safety

Distinguish local indexes, online AI requests, and source-file operations so you know what each step affects.

01

Where assets and projects live

Sounds records local asset paths, information, and analysis. Projects records project locations, and generated previews are stored locally. A database is not an audio backup; moving or deleting originals affects use.

02

What goes to AI

Online AI features send requests, conversation, and task-required text to your chosen provider. Data handling varies by task and provider. Do not assume every Chat feature is fully offline.

  • •AI UCS hybrid mode sends text only, not audio, and saves its results to the app database.
  • •Audio similarity uses local sound analysis and indexes. Online language interpretation is a separate step.
  • •Never put API Keys in chat messages, feedback, screenshots, or public pages.
03

Operations that can change files or projects

  • •Rename in the sound list changes the original audio filename and may affect other project references.
  • •Saving Metadata with Save in Wave enabled can write to the original WAV.
  • •Chat actions, Spot, and effect-chain Import change the target REAPER project. Check targets and save first.
  • •Playlist removal, visible-column changes, and virtual project grouping are not deletion of disk assets.
04

What to back up

Keep original audio, .rpp projects, and referenced media. Also back up app databases and settings if you want to preserve organization and search work. Test batch changes on copies before using important projects.