Think about every link you save. Articles you want to read later. Tools you want to try. Products you're researching. Videos you'll never finish. That list is a detailed map of your interests, your habits, and often your intentions.

Most bookmark managers send that map to a cloud server — which means a company (or their advertising partners) can see it. Tuckii doesn't.

What "local-first" actually means

A local-first app stores your data on your device. It doesn't need a server to work, and it doesn't send your data anywhere unless you explicitly ask it to.

For a bookmark manager, this means:

  • Your list of saved links lives on your phone — not on a company's server.
  • The app works offline, because there's nothing to sync.
  • Uninstalling the app removes your data entirely.
  • There's no account to create, no email to give, and no password to forget.

Contrast that with most bookmark apps: they ask you to sign up, they store your links in their cloud, and when they shut down — as Mozilla did with Pocket in July 2025 — your data disappears with them.

Why "no account required" matters more than it sounds

Every account you create is a potential breach. Services get hacked; credential databases get leaked. If your bookmark manager requires an account and it gets breached, your browsing habits, saved articles, and private links could be exposed.

With a local-first app like Tuckii, there's nothing to breach. The server doesn't hold your data because the server never receives it.

Tuckii's data model at a glance: Your links, collections, notes, and tags are stored in a local SQLite database on your device. Tuckii's backend only receives the URL you're saving — to fetch the title, description, and thumbnail. Your personal library is never transmitted.

The only cloud call Tuckii makes

When you save a new link, Tuckii sends the URL to its metadata service to fetch the page title, description, and thumbnail image. This is the same thing a browser does when you open a link — except Tuckii's service doesn't log your identity, connect the request to your account, or store which URLs you've saved.

There's no user ID attached to the metadata request, because Tuckii has no user IDs. You can also check Tuckii's privacy policy for the full details.

Local-first vs. cloud-based: what you give up

Being honest: local-first isn't free. There are trade-offs.

  • No cross-device sync. Your links on your iPhone won't automatically appear on your Android tablet. You can export and import a backup file to migrate, but it's manual.
  • No web access. You can't log in to a website to see your saved links from a desktop browser.
  • Backups are your responsibility. Tuckii makes it easy to export a JSON backup — but you need to actually do it. iCloud or Google Drive can store the file; Tuckii just creates it.

For many people — especially those with one primary phone — none of these matter. And the privacy gain is worth more than the convenience loss.

Who Tuckii is for

Tuckii is built for people who:

  • Save links while scrolling and want to find them again later
  • Are tired of creating accounts for every new app
  • Care about privacy but don't want to self-host a server (that's for Linkwarden)
  • Want something fast and simple, not a full knowledge-management system
  • Left Pocket after Mozilla shut it down and want a private, lightweight replacement

How to save links to Tuckii

Tuckii installs a share-sheet extension when you install the app. After that, saving a link from any app takes one tap:

  1. Find the link you want to save — in Safari, Chrome, Twitter/X, Instagram, YouTube, a podcast app, anywhere.
  2. Tap the share icon.
  3. Tap Tuckii in the share sheet.
  4. Done. Tuckii fetches the title, description, and thumbnail in the background.

No copy-pasting URLs. No opening another app first. Just one tap from wherever you are.

Try Tuckii — your links, on your device

No account. No cloud. No tracking. Save links from any app and find them again in seconds.

Download free →