Hi, I'm sorry this happened. It's definitely not a bug in our code, though. Something is wiping Firefox's internal storage - it's pretty much impossible for us to accidentally write code that would suddenly just wipe the entire contents of the storage and then delete the entire OneTab database after that.

Some "privacy cleaner" software will wipe Firefox data, or it could have been a crash causing a disk write error that corrupted the storage areas. Firefox's "Refresh" feature also wipes clean the extension storage. Being low on disk space when the browser is trying to write to its databases can also cause corruption.