Keep drafts right beside the checkout they are about. No account, no bucket, no server in between - just a folder, read and written directly.
Nothing to configure. There is no form for this one - you click Choose folder and pick it, the same picker your operating system already gives you.
| Context | How it reads the folder |
|---|---|
| Chromium browsers | The File System Access API. Chrome, Edge and Arc have it on by default; Brave ships it off, switched on at brave://flags/#file-system-access-api. |
| The desktop app | Its own picker, driven by the operating system rather than the browser engine underneath it - so this one works inside the desktop app even though the app's web view is Safari's engine, which has no File System Access API of its own. |
| Every other browser | Not available. Safari and Firefox have no File System Access API and no substitute - use the desktop app, or one of the other four backends. |
This is the backend for someone who keeps drafts beside the checkout they came from - no server, not even a bucket, sits between the agent writing and you reading. It is also the fastest of the five to set up: there is no token to scope, no CORS to configure, no region to pick.
The trade is reach. A folder on disk is a folder on this disk - reading the same review from a second machine means syncing that folder yourself, with iCloud Drive, Dropbox, or whatever you already use. If reviews need to reach more than one machine on their own, a bucket or a repository is the better fit.