As @idonotlikeusernames correctly recalls, it is possible to develop a beta testing system to achieve your aims. In our case it involved a separate website, a database, some clever code in a ‘proper’ programming language, and a not-inconsiderable amount of time & effort… Is it a practical (or even necessary) solution for most Choice Game authors? Probably not.
Most make do with either “soft saves”, which are of course only useful for a single session but can still be a great benefit to play-testers, or make use of the excellent smPlugin.js by @CJW, which is fully supported by dashingdon.com. This uses a browser’s LocalStorage so saves can persist between sessions, provided that no changes are made to game files up to the point of the latest save. If or when such a change is made, it will usually break all existing saves.
It would take a bit of doing, but it’s certainly an intriguing alternative. This topic might provide the functionality you’re looking for?