Privacy Policy
Powerhouse Apps — File Explorer, WordSmith, WaveSmith, NVDA Remote, and Remote VT. Last updated: November 9, 2026.
The short version, which is also the whole version: these apps have no accounts of their own, no servers, no analytics, and no trackers. Nothing you do in them is collected, sold, or shared, because none of it ever leaves your device in the first place — except where you send it yourself, as described below.
What stays on your device
- Your files, documents, audio, and settings stay on your device, except where you send them: if you sign in to Google Drive in File Explorer and copy or upload a file, that file travels between your device and your own Google account. Nothing passes through any server of ours — we don't have one.
- Google sign-in (File Explorer) happens through Google's own sign-in on your device. Your sign-in token is stored on your device only. File Explorer asks Google for limited Drive access: it can see only the files it put in Drive itself, and files you hand it through the system file picker.
- WaveSmith: your audio never goes anywhere. The app sends nothing anywhere; when you save or export, the file goes only where you put it — Drive included, if that's where you save it.
- WordSmith: documents stay on your device. If you choose to set up the optional AI feature, it uses your own key, stored only on your device, and contacts the AI service only when you invoke it.
- NVDA Remote: the app connects you to your own computer through the NVDA Remote relay. Your channel key is used to make the connection and is never written to any log.
- Remote VT: the app talks only to the StationPlaylist VT Server you point it at — your logs, hours, and saves go between this device and your own server.
Update checks
Once a day each app checks for a newer version of itself. That check sends only the ordinary technical details any web request carries (like your IP address) to the release host.
Permissions
Each app asks only for the permissions its job requires, and each app's page on this site explains every one of them in plain English.
Bug reports and diagnostics
If you use an app's "Report a bug" feature, a diagnostics log is sent along with your report — always. There is no option to report a bug without the log, because a bug report we cannot verify against what actually happened on the device is not one we can act on. Sending a bug report means sending the log.
The log is built to leave sensitive things out: it records the app version, your Android version, your device model, and what the app did and what went wrong — never the contents of your files, never message text, and never passwords, keys, channel keys, or sign-in tokens.
Reports are sent from inside the app to this website (powerhouseapps.net), which delivers them to our support mailbox — no email app is involved, and nothing else receives them. If a send fails, the app holds onto the report and tries again the next time it opens. A report is used only to diagnose the problem you reported.
The report form offers an optional email field. Fill it in only if you want a reply; if you do, that address is used only to reply to your report.
Sending plain feedback that is not a bug report does not include a log.
Questions
Questions about this policy or any of the apps: support@powerhouseapps.net.