GitHub user breautek added a comment to the discussion: Persistent storage

The user can clear **ALL** local storage.

The browser's storage mechanisms (cookies, local storage, indexedDB) are all 
stored in the app's data directory. The file plugin exposes the ability to 
store files directory into the app's data directory, as well as some other 
directories.

When the user uninstalls the app, or clears app storage, the OS will clear the 
app's data directories which includes all that is mentioned above.

Short of controlling the data on a server and having the user to log into an 
account to relate that data to the user, it is impossible to guarantee 
persistent storage. Other options that doesn't involve a server:

1. Is to use a media store plugin to store files on the user's "external" 
filesystem inside the documents container.

Other apps may be able to read these files so it's not suitable if storing 
anything sensitive. The user can still delete the file, but as long as you 
don't use an app-specific external storage, the files should be retained (90% 
sure...).

Apache's file plugin has limited support for external storage since Android's 
SAF framework. It's not suitable for writing documents to external storage. 
Therefore a third-party plugin that interfaces with the native MediaStore APIs 
is required.

2. Use a plugin to integrate with user's cloud storage such as google drive. 
Naturally the user can still delete the data, and other apps may also be able 
to read that data. So it faces similar issues as using the external filesystem 
partition. But I don't believe the data is cleared on app uninstalls or 
explicit clear app storage requests since it's external to the app's data 
directories.

Note that some jurisdictions, by law, you must provide some sort of mechanism 
to allow users to delete their data.

GitHub link: 
https://github.com/apache/cordova/discussions/497#discussioncomment-10753507

----
This is an automatically sent email for issues@cordova.apache.org.
To unsubscribe, please send an email to: issues-unsubscr...@cordova.apache.org


---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org
For additional commands, e-mail: issues-h...@cordova.apache.org

Reply via email to