Conversely, if it is determined that the user does not correspond to the identifier associated with the first user profile, the use of the data storage device is controlled according to the second user profile (step 23), permitting the user to write data in the memory of the data storage device but prohibiting him or her at least from reading data, in the memory of the device, that were not previously written by that user.

In one or more embodiments, the identifier associated with the first user profile is an identifier (for example a predetermined identifier) that can be stored in the memory of the data storage device so as to advantageously allow autonomous operation of the data storage device.

As a variant, the identifier associated with the first user profile is an identifier (for example a predetermined identifier) that can be stored in the memory of one or more data servers, as described above, for example as part of a Cloud service, in which case the data storage device may be configured to query these one or more data servers upon detecting a use of the device.

In this case, the data of the user profile(s) generated, and/or the data associating these profiles with users, can be stored and managed remotely in remote data servers. For example, user identification elements (“credentials”) may be managed remotely and not stored in the storage medium. This embodiment has the advantage of providing better security for the user identification elements, for example in case of loss or theft of the storage device.

Conversely, user identification elements may be managed locally, in other words within the storage device, advantageously in order to allow completely autonomous operation of this device.