Integrity Studio · version 1.1 · October 16, 2026
Your music. Your private workspace.
Make a take, shape it, and keep a record of what you made. Here is what the application protects and what still depends on you, the music model, and the hosting provider.
Accounts and files
- Your tracks, stems, instruments, and project versions are scoped to your account. Their API routes require a valid signed-in session.
- Passwords are salted and hashed with scrypt. Password reset links expire after 30 minutes and work once. Resetting your password revokes existing sessions.
- Private audio and API responses use no-store caching instructions. The installed app caches its public interface, not your private audio or API data.
- The signed-in studio does not load third-party analytics. Public pages may use the analytics described in our privacy policy.
Project recovery
Save a version in the workbench to retain your instrument notes, tempo, and mixer controls. Each project keeps its newest 20 distinct versions. Loading a version does not overwrite the latest save until you choose Save version.
Mixer level, pan, EQ, and mute settings are included when you save a version. Download a WAV to keep a playable copy of your mix. Unsaved changes remain only in the current session.
Integrity receipts
Newly downloaded generated audio and stems receive a SHA-256 fingerprint. Download a track's integrity receipt to keep its title, model identifier, generation time, byte count, and fingerprint where available. Older audio may not have a fingerprint.
Music rights
Use lyrics, recordings, samples, and other inputs you own or have permission to use. Do not assume that generating a song clears rights in your inputs. Review the terms for the model you choose before distributing or selling its output. Our terms explain the service's rules.
What leaves the studio
Song generation sends the lyrics and style you submit to the configured music provider. Stem separation sends the selected audio to the separation provider. These operations cannot be performed without that processing. Local mixing, instrument playback, and WAV rendering run on your device.
Live amp
The live amp at /amp asks your browser for an audio input only after you press Turn on amp. Your guitar signal is processed on your device: it is not recorded, uploaded, or sent to any provider. A cabinet impulse response you load stays in the open tab. Amp settings and your chosen input and output are kept in this browser only. Other pages of the site are not allowed to use the microphone at all.
Traffic protection and service limits
The application limits authentication attempts, request sizes, download sizes, and upstream wait times. These controls reduce some abuse; they do not guarantee uninterrupted service or protection against every attack. Network filtering, encrypted storage, backups, and recovery testing require hosting controls and operational verification.
Get help
Report an account, file, or security concern to [email protected]. Never send a password, API key, or reset link.