We can't solve problems which we can't reproduce. Please specify the site URL and the version of Firefox you're using.

Stylus can't "disappear" styles. It's either a bug in the browser or your user profile is damaged. Also make sure you're not using "smart" apps like CCleaner which may delete the style storage.

P.S. If you've switched Firefox into a permanent private mode, Firefox erases the previously used style storage, it's a known bug in Firefox. Might be fixed in Nightly, though.

Stylus doesn't access any data on any site. The new content script for openusercss will simply facilitate installation and updating of usercss styles from that site.

The content script tells the site the name of the extension (Stylus) and whether the style (displayed on the site page) is installed so the site displays the extension name and "Install" or "Update" on its action button.

The fact that Firefox displays this warning is just another example of how buggy WebExtensions implementation is in FF. It's really sad and disgusting. The thing is, Stylus has always had access to all sites via its content script that runs on all URLs - this is a necessary requirement to apply styling - so adding another content script makes no actual difference.

We can't fix what we can't reproduce.
Please post a screenshot and an instruction how to make it happen.
And if you use FF 56 or older, please re-check it in a new browser profile with no other addons installed because in the old Firefox the full (classic) addons can affect WebExtensions.

Styles can only disappear due to a bug in the browser or disk failure. Stylus simply doesn't have the code to mass-delete the styles on a whim.

Always export the styles manually on the styles manager page if you don't have a system-wide periodic backup set up. In the future we'll probably add an internal database backup and external sync.

Mozilla's implementation of Containers API is incompatible with some of the basic approaches we use for speed-up like direct access to the background script. Either the API will be fixed in the future or we'll try to rework our code.

I can't reproduce the problem. If you can do it reliably, please send the exact instruction to our support on discord chat or github (see the addon description here on AMO).