Save Book

Save Book keeps the logins, codes and numbers you need on a specific website one click away, without leaving the page. You choose which sites get a card. On those sites — and nowhere else — a small card appears with the items you saved for them. Click a row and the value is on your clipboard. WHAT IT IS FOR - Test and staging credentials you look up a dozen times a day - Shared QA accounts, support phone numbers, order references - Anything you keep hunting for and pasting into the same site HOW IT WORKS 1. Open the settings page and type a domain, for example staging.example.com. Save Book asks Chrome for access to that domain only. 2. Add the items you want, with a short label — plain text or a masked secret. 3. Open the site: the card is there. Drag it wherever suits you; the position is remembered per site. The card is deliberately minimal: just your items. Click to copy, reveal a masked value with the eye toggle, collapse or hide the card with one click, or toggle it from the toolbar icon. It only appears on domains you added yourself. PRIVACY Save Book has no servers and no accounts. Everything you save stays in Chrome's local extension storage on your own device. The extension makes no network requests at all, contains no analytics and no tracking, and cannot read anything on a page unless that page's host is one you added. Host access is requested one domain at a time, when you add it, and handed back when you remove that site. The extension installs with access to no website at all. OPEN SOURCE Save Book is open source, released under the MIT license. The full source is public at https://github.com/piotroszko/save-book-extension, so you can read exactly what the extension does and verify the privacy claims above instead of taking them on trust. Bug reports and suggestions are welcome in the issue tracker. A NOTE ON SECRETS Items are stored unencrypted in your browser profile, unlike Chrome's own password manager, which encrypts with your system keychain. Anyone with access to your computer and browser profile can read them. Keep that in mind before storing a production credential, and use it for test accounts rather than production ones.