What Local-First Actually Means: Where a Start Page's Data Lives
IndexedDB vs localStorage vs cookies, the exact data path of a single click, every extension permission explained, and an honest list of what local storage does not protect you from.
"Your data never leaves your device" is often marketing. It is worth unpacking what it promises and what it does not — especially before handing a few hundred bookmarks to a web page.
Three browser storages, three different jobs
| Cookie | localStorage | IndexedDB | |
|---|---|---|---|
| Capacity | ~4KB each | ~5–10MB | Hundreds of MB, disk-bound |
| Sent with every request | Yes | No | No |
| Data shape | String | Key/value strings | Structured objects, indexable |
| Cleared with browsing data | Usually | Yes | Yes |
MyNav keeps bookmarks in IndexedDB, settings (theme, language, ticked engines) in localStorage, and writes no cookies at all. The reason is simple: a cookie's only special property is that it rides along with every HTTP request, and a static site has no server that wants it. Setting one would only add a surface for third-party scripts.
The path of one click
Opening the homepage:
- The browser fetches
index.htmland static assets from Cloudflare's CDN; - Scripts read bookmarks from IndexedDB and render the cards;
- Site icons come from
favicon.imor Google's favicon service — this sends the domain to those services, never your title, note or category; - No other request carries your collection.
Adding a bookmark:
- The record is written to IndexedDB;
- If the extension is installed, an in-page message bridge forwards the change, and the extension writes it to
chrome.storage.local; - There is no network request and no server acknowledgement.
Deleting, pinning and click counting follow the same path.
The extension adds a layer, and a responsibility
The extension needs permissions for context menus, screenshots and reading local bookmarks. Each one, plainly:
contextMenus: adds "search" and "save to MyNav" items; does not read page content;activeTab/scripting: injects into the current page only when you click the icon or use a context menu item;bookmarks: reads local bookmarks for import; never modifies them;storage/unlimitedStorage: holds your data;downloads: saves screenshots and exports to disk;<all_urls>: lets the context menu work on any site — the broadest permission and the one reviewers scrutinise. It does not mean the background reads every page, but it does grant that capability, so only install extensions you trust.
Synchronisation between extension and site happens only on the mynav.site origin: the bridge script is injected there and nowhere else, so pages on other sites cannot read your bookmarks.
What it does not protect you from
Being precise about limits is more useful than repeating "secure":
Other people on the same computer. There is no password in front of the data. Anyone who can open that browser profile can read your bookmarks. Do not keep sensitive items on a shared or work machine.
Clearing browser data. Cleanup utilities, "clear recent data," closing a private window, reinstalling the OS — IndexedDB disappears. That is not a bug; it is the definition of local storage.
Other extensions. A malicious extension with <all_urls> can, in principle, read page data. Installing fewer extensions and auditing them occasionally is more practical than any encryption.
Physical access to the profile folder. Whoever has your disk can read IndexedDB. Genuinely secret material belongs in a password manager or an encrypted container.
What "no account" buys you
Three things:
- No account, no account suspension. No provider can freeze your collection or close your entrance for business reasons.
- No upload, no breach. Your bookmarks are not on a server you can be told about, nor in a database that can be dumped.
- No backend, no shutdown. Domain expires, company folds — your data is still local, in open formats.
The cost is that you do the syncing. That is not a technical limit but a trade: automatic sync necessarily requires a server that knows who you are and holds your data. Choosing local-first means choosing to take that back.
A practical checklist
- Export a JSON backup monthly into a cloud-synced folder;
- Avoid saving account-bearing links (admin panels, internal docs) on shared devices;
- Audit browser extensions periodically and keep only what you use;
- Keep separate file copies of images that matter; a link is not a backup.
FAQ
Can the site operator see locally stored data?
No. A static site has no endpoint to receive it. The only thing an operator sees is anonymous CDN access logs — path and status code — with no bookmark content.
What happens in a private window?
A private window gets its own storage, discarded when the window closes. Fine for a quick test, wrong for daily use.
Can the extension see every page I visit?
Technically, an extension with <all_urls> has that capability. The MyNav extension injects only when you act — click the icon or use a context menu — and does not report browsing history in the background. That is stated in the privacy policy and is what review checks against.
Local-first is not a safer cloud. It is the absence of a cloud. Once that is clear, you know what to back up and what never to store.
Keep reading
Open MyNav
No sign-up. Open it and start.