A second exemplary implementation relates to a secure storage medium (USB key, SD card, removable disk, etc.) allowing only one “owner” profile for the person who can read, edit, and delete files deposited thereon, and forcing a “guest” or “write-only” mode for everyone else who can only place files therein. The “owner” of the medium must first initialize it during a simple configuration phase, consisting of partitioning the total volume by reserving a drop zone and creating a password to protect it from read accesses thereafter. Each “guest” will only see blank media from their system/file explorer on their personal computer. The only information will be the size available. This capacity may be managed during attempts to deposit files. In addition, after each deposit, the file may or may not be visible to the person who initiated it, depending on the embodiment.

Such simplicity in the experience requires software development to provide drivers for circumventing the usual operation of media inserted into computers. These drivers are of two types, which may be combined: (1) resident application or system extension for computers (for example Kernel extension: KEXT on MacOS), and (2) firmware for the medium itself (for example for a specially formatted key). The embodiment depends on the experience desired and on the constraints: An application allows the use of standard media but requires software installation prior to the first use, and this is true for each guest. Firmware does not require any configuration or prior installation for guests but requires specific media.