The sqljs-driver (which will be removed in 2.0) runs entirely in-memory so that's why it's wiped every time you reload the page.
To have it save data between page loads you need to run SQLite in a Web Worker and use some SQLite driver that supports some kind of local storage, like absurd-sql (which has some flaws), or sqlite wasm (which is what I would recommend in the future when browser support is better). It's not very well documented yet, but you would use SQLDelight's web-worker-driver instead and I have a sample project that uses it here:
https://github.com/dellisd/sqldelight-sqlite-wasm