Privacy & cookies
Updated 29 September 2026
Resonant is an online instrument studio operated by AppsOverFlow. This page explains how the studio handles your music and the information used to run the website.
Your music stays on your device
Instrument playback, recording, audio imports, DJ mixing, tune editing, and karaoke run in your browser. Resonant does not upload the audio you import or record to a server. Instrument audio and performance-video recording capture the studio output without microphone access. Karaoke can separately record your voice with a backing track after you enable the microphone. Video combines the instrument illustration and animated note feedback locally. Downloaded exports are saved through your browser.
Device storage
Saved takes, imported audio, and their names are stored in this browser using IndexedDB. The current editable arrangement, including source audio and mix settings, autosaves in a separate IndexedDB database when storage is available. Completed loop layers, their note events, instruments, tempo, and effects settings also autosave locally. Editable loop and tune-editor backups can be downloaded and reopened on another device. DJ decks, source audio, cue points, beat grids and mixer settings save in a separate local database. Karaoke saves the current backing track, pasted lyrics, timing and level settings in its own local database. These sessions reopen with playback stopped; microphone access and monitoring never restore automatically. Playing preferences and practice progress use local storage. Resonant requires an internet connection and does not maintain an offline app cache. Older app caches are removed during migration without deleting saved music or preferences. These storage features do not create a cloud backup.
You can delete individual takes in the Takes panel. Clearing this site's data in your browser removes saved music and preferences; download anything you want to keep first. Wait for the arrangement or loop autosave confirmation before closing. Unfinished recordings, currently recording loop layers, and undownloaded video previews may be lost when the tab closes.
Optional microphone and MIDI access
The tuner requests microphone permission only when you choose Start tuner. It analyses a short live signal on your device to estimate pitch; it does not record, save, or upload microphone audio. Leaving the tuner stops microphone capture. The MIDI tool asks for controller access when you choose Connect. It does not request system-exclusive access, store device identifiers, or send MIDI notes to analytics.
Karaoke requests microphone permission only when you choose Enable microphone. Its recording combines your microphone and backing track locally. Headphone monitoring is off initially and requires a separate choice. Leaving Karaoke or hiding the tab stops microphone capture and playback. Finished performances autosave to Recordings when storage is available; download a copy to keep. The current backing, lyrics and settings save separately on this device. Clear saved session removes that Karaoke session without deleting finished Recordings. Unfinished recordings may be lost when the tab closes. Resonant does not upload your voice, backing tracks, or lyrics.
Hosting
Google Firebase Hosting serves the website and receives information needed to deliver requests, such as your IP address, requested URL, and browser information. Read Firebase privacy information for details.
Optional Google Analytics
Analytics is on by default when no saved preference exists. Saved opt-outs are respected. Resonant uses Google Tag Manager and Google Analytics 4 to measure page visits, instrument and workspace usage, recording starts, exports, DJ playback, preset playback, saved mixes, and loading performance. Google Analytics uses cookies and processes device, browser, approximate location, and referral-origin information. Page URLs exclude campaign labels, other query values and URL fragments.
Analytics does not receive your audio, filenames, take names, or individual played notes from Resonant. The site sends known page titles and instrument names, removes campaign labels, strips other query parameters and URL fragments from its page events, and reduces referrers to their website origin. Google signals and advertising personalization are disabled for this Analytics tag.
You can turn analytics off at any time. Use Analytics preferences in the studio footer at any time to change that choice. Turning it off stops new Analytics events and removes this site's Google Analytics cookies. Events queued while analytics was allowed may finish sending when you leave the page. Your choice stays saved until you change it or clear site data. Unreadable or malformed preferences keep analytics off. This policy page does not load Analytics.
Open analytics preferences. See how Google uses information from partner sites and Google's privacy policy. Advertising consent is a separate choice; the analytics control does not grant consent to personalized advertising.
Google advertising
Resonant includes Google AdSense. Google and its advertising partners may place and read cookies or use web beacons, IP addresses, browser information, and other identifiers to deliver, measure, and protect advertising. Personalized advertising may use information about visits to this and other websites. Availability and personalization depend on consent choices, browser settings, and Google's ad-serving settings.
See how Google uses information from sites that use its services and Google's privacy policy. Google's advertising cookies are separate from the browser storage used to save your music.
Your choices
You can manage cookies and site permissions in your browser and review Google's personalization settings in My Ad Center. You can also learn about participating advertisers' opt-out options at YourAdChoices. Where a consent message is presented, use it to choose how your information may be used. Blocking or clearing storage can affect saved takes, editable arrangements, and preferences.
Other websites and updates
External links are operated by their respective providers and follow their own privacy policies. This page will be updated when the studio's data practices change. The date above identifies the latest revision.
Website owner: AppsOverFlow ↗.