Privacy and Local Processing in Audio Visualizers
Short answer: Shimga analyses and renders your audio in your browser, and according to its privacy policy your audio is not uploaded to Shimga's servers unless you save a template that includes it. The studio still needs an internet connection to load, Pro exports need a sign-in, and Shimga collects usage analytics, so it is local-first rather than fully offline or anonymous.
Last updated 21 October 2026. This article summarises Shimga's behaviour; the privacy policy is the authoritative document.
Why does privacy matter for unreleased music?
An unreleased single, a label demo or an exclusive beat can lose value the moment it leaks. Most leaks do not come from attackers breaking in; they come from files sitting on third-party services with retention rules nobody read. When you upload audio to a cloud-based visualizer, a copy sits on someone else's servers, possibly in backups, for as long as their policy says.

Photo: Dan Nelson on Pexels
Local-first processing reduces that exposure: if the file is analysed and rendered on your own device, there is no server copy to retain, breach or subpoena. It does not remove every risk, so it helps to know exactly which data goes where.
What are the risks of cloud-based visualizers?
- Retention: "we delete uploads after a set period" may not cover backups or logs.
- Breach exposure: any incident along the upload, process and delete chain can expose files.
- Policy changes: terms can change after an acquisition and may apply to earlier uploads.
- Jurisdiction: data stored in some countries is subject to local legal access.
Cloud tools are not inherently bad, and they can render on hardware you do not own. The point is to understand the trade-off.

Screenshot: shimga.app
How does Shimga process audio locally?
- Loading. You drop a file into Shimga Studio. The browser reads it from your disk with the File API and decodes it using the Web Audio API.
- Analysis. Frequency and amplitude data are computed in the browser to drive the visuals, and an offline audio context analyses the track faster than real time for export.
- Rendering. Frames are drawn to a canvas and encoded to MP4 on your device using WebCodecs.
- Saving the file. The MP4 downloads straight to your computer.
You can verify this yourself: open your browser's network tab (F12, Network) while loading a track and check whether any request carries your audio.
What stays on my device and what is stored?
| Data | Where it goes |
|---|---|
| Your audio file, its analysis and the exported MP4 | Stays in your browser and on your device. Not uploaded unless you save a template that uses the audio. |
| Your in-progress scene | Kept in your browser's local storage while you work. Signed-in users also get an auto-saved draft stored in Firestore; anonymous drafts are deleted after up to 24 hours of inactivity. |
| Saved templates (settings plus any media you add, including audio if the template uses it) | Stored in Firestore and Cloudflare R2 only when you explicitly save, so the template can be reopened or remixed. Choose private to keep it visible to you only. |
| Account details (email, Google profile if you use Google sign-in) | Firebase Authentication, so you can sign back in. |
| Plan status if you buy a paid plan | Plan type and dates are stored by Shimga; card details go to Dodo Payments and are never seen or stored by Shimga. |
| Usage analytics | Session telemetry in Firebase, Google Analytics 4 and Microsoft Clarity session replays. These can be blocked with a standard tracker blocker without breaking the studio. |
Do I need an account, and can I use Shimga offline?
You can open the studio, load audio, choose a preset and preview without an account or payment, and export a standard MP4 without one too. Pro exports need a sign-in. Saving and syncing templates across devices also needs an account.
Shimga is not designed as an offline app. The page and its assets load over the network, and sign-in, template saving and Pro entitlement checks contact our servers. The audio processing itself happens locally once the studio is loaded, which is why your audio file does not need to be uploaded. If you need a fully air-gapped workflow, a desktop tool is a better fit.

Photo: Kampus Production on Pexels
How can I get the most privacy? Step by step
- Keep templates private when saving, and do not save a template at all if it includes unreleased audio you want to keep on your device.
- Use a private window for sensitive sessions so browsing data is cleared when you close it.
- Review extensions. Extensions with page access can see canvases and file inputs; disable them or use a clean profile.
- Clear site data afterwards in your browser settings if you work on a shared computer.
- Trim or convert first. You can prepare audio with the in-browser Audio Trimmer or Audio Converter before loading it.
- Read the policy of any tool you use, looking for wording on uploaded content, training and retention.
Frequently asked questions
Does Shimga send my audio file to its servers?
According to Shimga's privacy policy, your audio is analysed in your browser and is not uploaded to Shimga's servers unless you save a template that uses it. You can check the browser network tab to see what your session sends.
Do I need an account to use Shimga?
Not to start. You can open the studio, build, preview and export a standard video without an account. Pro exports need a sign-in, and saving templates or syncing across devices needs an account.
Can I use Shimga without an internet connection?
Not fully. The studio needs a connection to load, and sign-in, saving templates and Pro checks use our servers. Audio analysis and rendering themselves run on your device.
What does Shimga collect for analytics?
Session telemetry such as session length, browser and device details, plus Google Analytics and Microsoft Clarity. The privacy policy lists what is collected and how long it is kept, and trackers can be blocked without breaking the studio.
Build your video on your own device
Open the studio, drop in your track and preview without uploading your audio.
Open Shimga Studio →Related: performance and rendering, templates and in-browser audio tools.