Chapter · Settings & remote access
Privacy and your data
See what stays on your PC, what your prompts and attached files send to Muse, and how to limit agent access safely.
Before you start
- Only attach files you are allowed to send to Muse.
- Review your agent provider’s data practices separately; its service is outside the app.
1Know what stays on this PC
Muse4AI keeps jobs, settings, API-key records, downloaded files, and account sign-in sessions in its own local storage. It does not store your Muse password. Roaming data is under %APPDATA%\MuseStudio; media uses your chosen output folder.
2Know what is sent to Muse
Your prompts and attached files are sent to Muse through your own account so it can answer or generate results. Jobs on one account share its Muse memory and history. Avoid sending confidential material without permission.
3Understand the project boundary
The app does not send your jobs, files, keys, or sign-in sessions to Andrew Babo or the Muse4AI website. Connecting an agent or enabling a tunnel introduces the separate providers you choose.
4Limit access and shared material
Use one key per agent, keep sharing off when unnecessary, and revoke unused keys. Review diagnostics and screenshots before sending them. Never include a full API key in a screenshot or URL.
Check it worked
You know which data stays local, which goes to Muse, and who can access the app through your keys.
If it doesn't work
Does no password storage mean no session storage?
No. The app retains sign-in sessions in its own storage so accounts can stay signed in.
Can I isolate research between agents?
Separate API keys control access, but jobs on one Muse account still share that account’s memory. Use separate accounts when separation matters.