Local File Management
EPM Commander requires very little local storage footprint. All critical configurations, diagnostic caches, and secure credential storage are strictly isolated within your Windows user profile folder.
Primary Storage Location
All local data generated by EPM Commander is stored in the standard Windows local application data directory. This ensures that configuration does not bleed across multiple users sharing the same physical machine or virtual desktop.
Typically resolves to: C:\Users\YourUsername\AppData\Local\CaptainEPM\
File Types and Contents
AppSettings.json
Stores your UI preferences, theme settings, API endpoint URLs, and recent connections history. No passwords are ever saved in plain text within this file.
LocalCache.db / SQLite
A lightweight local SQLite database used to cache EPM metadata (dimension members, alias tables) to drastically speed up Excel performance. This file is routinely purged and rebuilt.
Diagnostic Logs (*.log)
Stored within the /Logs subdirectory. These are local diagnostic log lines (e.g., "Failed to connect to API", "Timeout on job execution") kept on the workstation to assist with IT support and troubleshooting. Nothing in them is transmitted to Captain EPM.
Clean Uninstallation
Because EPM Commander isolates its data to the %LOCALAPPDATA% folder and does not pollute the Windows Registry with complex keys, uninstalling the Add-in natively cleans up the executable footprint. IT Administrators can simply delete the CaptainEPM AppData folder to perform a factory reset.