I received the initial response from the vendor in just six days which stated the following: Communication with vendorĪfter discovering this issue I reported it to the vendor, SanDisk, on the 5th of November and waited for a response. Thus a user who uses SecureAccess fairly regularly is much more likely to end up with some plain-text copies of their files sat on their disk. In standard operation this directory is not emptied unless the user explicitly empties it, either by deleting the content manually or using some other utility. This is exacerbated by the way that Windows handles the “%TEMP%” directory.

As SecureAccess creates a plain-text copy of the encrypted file on disk, if the program exits unexpectedly (program crash, power failure, or the user ends the process) the routine to delete the temporary files does not run, so any files you’ve opened during that session remain on disk in plain-text. Contents of the temp dir after closing the appĪ similar issue exists if the application crashes when the user has a file open.

Sandisksecure