Understand
How encryption and search work
Follow a saved link from device to encrypted sync and understand why search runs locally.
Your device opens your account key with your password or recovery code. It encrypts each link, list, tag, and setting before upload; another signed-in device downloads and opens those encrypted files. Our servers store the files but cannot read the link addresses, titles, notes, or tags inside them.
Why search stays on the device
Searching needs readable words to compare. The app builds and searches against its local copy after decryption. That is why search works offline and why a new device must sync before it can find links saved elsewhere. There is no server index of your saved links. Basic search covers titles and addresses; Plus advanced search can also search notes and narrow by lists and tags. See search for the controls.
What is visible outside that boundary
Our API — the service behind sign-in, sync, and billing — holds the information needed to run them, including your username, public key, sessions, encrypted-file metadata, and a subscription record if you pay. Optional server previews receive a plaintext URL and your IP address while fetching a page. This is a separate service with no account key. You can leave it off and use the browser extension or mobile device for previews. See security, privacy, and link previews for the full boundaries.
There is no email reset path if both your password and recovery code are gone. Keep the recovery code separately from your password.