Privacy policy for Larksail – Tab Manager & Notes
Larksail – Tab Manager & Notes by Bulat
Privacy policy for Larksail – Tab Manager & Notes
Last updated: October 25, 2026
Larksail is a browser extension for managing tabs: collections, notes, suspending idle tabs, merging windows, archiving and snapshots. This policy explains what data Larksail handles and where it goes.
Larksail is made by Bulat Sabirov, Národní 25, 110 00 Prague, Czechia ("we"), who is responsible for your data under the GDPR (the "controller"). Contact: hello@larksail.com.
The short version: Larksail works fully without an account, and everything it stores stays on your device. No analytics, no ads, no tracking. Data leaves your device only for features you choose to use:
- Sync (optional, needs an account): encrypted on your device before it's sent. By default (Standard) our server keeps a copy of your key so it can let your own devices in and you can't get locked out; turn on end-to-end encryption (free) and only your devices hold the key, so we cannot read your library.
- Published pages (optional): a collection or note you deliberately publish as a web page — by default encrypted with a password (or a key in the link) that our server never sees; plaintext only if you choose Public.
- AI (optional, off by default): sent to the AI provider or server you pick.
- Weather on Home (optional, off by default): the place you pick, as rough coordinates, goes through our server to MET Norway for the forecast.
To do its job, Larksail keeps the following on your computer:
- Your collections and saved tabs: page titles, URLs, and any notes, tags, colors, covers, sticky notes and images you add.
- The archive: titles and URLs of tabs Larksail closed (automatically or at your request), so you can find and restore them.
- Snapshots: the layout of your open windows (tabs, order, pinned state, tab groups, window positions), so a session can be restored after a restart or crash.
- Collection history: earlier versions of your collections, so changes can be reviewed and undone.
- The action log: a record of recent actions (closing, moving, merging tabs) so they can be undone.
- Tab activity: when each open tab was last used, to decide which tabs are idle. This is temporary and cleared when the browser closes.
- Saved copies (on by default, only with site access): a readable copy of the text of pages you save, so you can read and search them later; full-page snapshots of pages you ask for; and your highlights in them.
- Notes, files and images: your notes, sticky notes, and the files and images you add.
- AI chats and summaries (only if you turn on AI): your questions to the Assistant and its answers (unless you turn off "Keep chat history"), and summaries of saved pages.
- Settings: your preferences, such as theme, timers and per-site rules.
All of this lives in your browser's local storage (IndexedDB and
chrome.storage). Unless you turn on sync, it is never sent to us or anyone else, and we cannot see it.Larksail keeps its settings in
chrome.storage.sync. If you are signed in to Chrome with sync turned on, Chrome itself syncs these settings between your devices through your Google account, as it does for every extension. This covers preferences only (including site names you added to rules), not your collections, archive or browsing data. Google's privacy policy applies to Chrome Sync. Larksail has no access to it beyond reading and writing its own settings.- No account needed: every feature except sync and published pages works without one.
- No analytics, telemetry, crash reporting or tracking of any kind in the extension. On larksail.com: no cookies, analytics scripts or trackers either — we only count page visits, anonymously (see The website).
- No ads.
- No network requests except for features you turn on or click: sync, published pages, AI (see below), Send feedback (see Feedback below), and Library → Broken links → Check links, which asks each saved page's own site whether it still exists (the address only, no cookies, only when you click); and a picture or PDF you drag from a web page into a note or Files, which Larksail downloads from that page's own site, once, as your browser would (only when you drop it, with site access). Weather on Home (off unless you turn it on and pick a place): finding a city happens on your device (a list of cities built into Larksail, from GeoNames); "Use my location" asks the browser for your position, which is rounded to about 1 km and kept in your settings. While Home is open, when the forecast is due (about every half hour), the place's coordinates — rounded to about 1 km, nothing else, no account or cookies — go to our server (
api.larksail.com), which asks MET Norway for the forecast and keeps that forecast in a cache under the rounded place, shared by everyone nearby. The server doesn't log or store which address asked for which place; the cache holds only forecasts. Our hosting provider (Cloudflare) processes the request like any other request to our server. Larksail does not load remote code, fonts or images. Page icons come from the browser's own local icon cache. - Larksail doesn't read the pages you browse. It reads a page's content only when you save that page (to keep its saved copy, if Saved copies is on and you granted site access) and, with site access, to check a page for unsent form input before suspending or closing it — that check stays on your device and stores nothing.
- No selling, sharing or transferring of your data.
Sync is off by default. If you create an account in Settings → Sync, our server (the "sync API") stores:
- Your account: your email address, whether it's confirmed, and a salted one-way hash of a key your browser makes from your password (never the password itself — it doesn't leave your device), with that key's salt. Signing in creates a session that records the time, the network address it came from and your browser's user-agent string, and expires after 30 days without use.
- Your devices: the name you give each device, its public key, and when it was added, approved and last seen.
- Your library, encrypted: every synced item (collections, saved tabs, sticky notes, notes, spaces, files, images, highlights and settings) is encrypted on your device (AES-256-GCM) before it is sent over an encrypted connection (TLS). The server stores the encrypted items and what it needs to sync them: an item's type and random id, when it changed, which device changed it, and its size. Who can open them depends on your encryption setting (below).
- Cloud backups, encrypted: while sync is on (unless you turn them off in Settings → Backups), once a day each of your browsers uploads a backup of its whole library — collections, notes, the archive, snapshots and settings — encrypted on the device with the same keys. The server stores the encrypted file, its size, when it was made and which of your devices made it, in Cloudflare R2. Each device keeps about three months of them; older ones are deleted.
- Your open tabs, encrypted (unless you turn it off in Settings → Sync): each of your browsers syncs the web pages open in its normal windows — never private windows — so your other browsers can show them, and tabs you send to one of your browsers. Encrypted on the device like the rest; the server sees only that a record changed.
- Your keys, sealed: your account key is stored only in "sealed boxes" — one for each of your devices, one that opens with a key your browser makes from your password (never sent to us), and, depending on your setting:
- Standard (the default): one more box sealed for our server's own key, which is kept as a secret outside the database. This means we could technically read your synced library. We use this key only to let your own signed-in devices in; nothing on our server reads your library. If we ever add a feature that uses it for anything else (for example AI on our server), it will be listed in this policy before it ships, and it will work only in Standard. Because we hold this copy, you don't need a recovery key, new browsers don't need approving, and a forgotten password can be reset by email without losing anything. Someone who gets hold of the database alone can't read your library.
- End-to-end (off unless you turn it on in Settings → Sync → Encryption, free for every account): Larksail makes new keys that only your devices hold, deletes our server's copy, and encrypts your library again with the new keys. We cannot read your titles, URLs or notes, and nobody who gets hold of the server's data can either. You get a recovery key, shown once; you keep it and we never see it. A new browser needs your password, approval from one of your devices or the recovery key, and a password reset by email doesn't open anything. If you forget your password and lose every device and the recovery key, we cannot recover your synced data — your devices still have their local copies. You can turn it off again, which gives our server a copy of your key once more.
Email. Sign-in, verification and password-reset codes are sent through Plunk, an email delivery service, which receives your email address and the message. We send no marketing email unless you opt in.
Service providers. Two companies run the sync API for us. They act only on our behalf, under their own data-processing terms:
| Provider | What it does for us | What it handles |
|---|---|---|
| Cloudflare | Runs the sync API (Cloudflare Workers). | Your network address, as any web host does, to deliver your requests. |
| Neon | Hosts the sync API's Postgres database. | What our server stores, as listed in this policy — your synced library only in encrypted form. |
Where it is stored. The database is in the EU (Frankfurt, Germany). Cloudflare answers requests from the data center nearest you. Some of these providers are US companies; any transfer of your data outside the EU is covered by the EU–US Data Privacy Framework or the European Commission's standard contractual clauses in their data-processing terms.
Deleting your account. Signing out keeps everything on your device. To delete your account and everything stored with it — the encrypted library, files, images, cloud backups, devices, keys, published pages and shared links — use Settings → Sync → Delete account (you type your email, and your password unless you signed in within the last 10 minutes). It's deleted from our database and storage right away; Your library on your device stays. You can also email hello@larksail.com from the account's address; we delete it within 30 days. Our database provider's restore history keeps a copy only until its retention window ends.
If you share a copy of a space or a collection ("Share a copy…" in its menu), Larksail encrypts the copy in your browser with a new key that exists only in the link it gives you (after the
#, the part browsers never send to a server). Our server stores the encrypted file, its size, when it was made and which account made it — we cannot read it. Anyone you give the whole link to can open the copy in their browser, add it to their own Larksail or download it. You can delete a link at any time in Settings → Sync → Shared links. If a link is reported for abuse we can delete it by its address, without being able to see what's in it.If you are signed in, you can publish a collection as a web page from its menu ("Publish as a web page…"). Publishing is never automatic. It sends a copy of that one collection to our server: its title and its links, and — if you leave "Include notes and tags" on — its note, tags and each link's note and tags. Nothing else (no other collections, no browsing data, no page contents). You choose who can open it:
- Password (the default): the page is encrypted in your browser with a key made from a password you pick (Argon2id, then AES-256-GCM). Our server stores only ciphertext it cannot read — not even the title — and never sees the password; the page decrypts in the reader's browser once they type it.
- Anyone with the link: encrypted the same way with a random key that is part of the link (after the
#, which browsers never send to us). Anyone you give the whole link to can open it; we can't. - Public: a plaintext copy, not encrypted — anyone with its link can see it, and so can we.
Your device keeps the page's key (never the password) so Update now can encrypt the new version the same way. Pages are unlisted (we ask search engines not to index them), and a page only changes when you choose Update now.
Link safety check. When you publish or update a public page, its links may be checked against Google Safe Browsing to keep malware and phishing off larksail.com. Only the page's links are sent to Google (they are about to be public anyway), nothing about you. If any link is flagged, the page isn't published and Larksail tells you which links. Password and link pages can't be checked — we can't read them.
Unpublishing removes the page and deletes its content (and its title) from our server right away; caches drop it within a couple of minutes. Settings → Sync lists all your published pages, including ones whose collection you deleted, so you can unpublish them. Deleting your account deletes all your pages.
Reports. Anyone can report a page. We store the reason, any details they write, and a one-way salted hash of the reporter's network address (to limit abuse) — never the address itself. If we take a page down, its content is deleted; we keep its title, the reason and a record of the action.
"Save to my Larksail" on a published page asks your installed extension to add that collection; the extension downloads the page from our server itself and asks you before adding anything.
Published notes. You can publish a note the same way ("Publish as a web page…" in its menu), with the same three choices: a copy of its text, quotes and links — not its images, embedded collections, boards or drawings, nor links to your other notes — at an unlisted address on larksail.com, until you unpublish it.
larksail.com sets no cookies and loads no analytics scripts or third-party code — except the checkout page (
larksail.com/checkout), which loads Paddle's checkout from Paddle when you choose to buy Pro (see Payments). To see which pages people read and where they came from, our server counts each page visit as a total: the page, the website that linked to it (the site's name only), the campaign tags in the link (utm_source, utm_medium, utm_campaign, ref), the country (from Cloudflare), phone or computer, and the browser family. On the page you see after uninstalling Larksail, the version number and the reason you picked are counted too. Your IP address, the full browser string and anything that could tell two visits by the same person apart are never stored. The counts are kept by Cloudflare for 90 days.When you click Send feedback in Larksail (or Report this after an error), our server stores what you wrote, the kind you picked (bug, idea, question), your email address if you gave one (only to reply), and — unless you turn it off in the dialog, where you can see exactly what's included — diagnostics: Larksail's version, your browser and its version, operating system, language, which optional features are on, and the error message if you're reporting one. Never your tabs, addresses, titles, collections or notes. A hash of your network address is kept for the rate limit. Mail you send to hello@larksail.com is stored the same way (the sender, subject and text).
We read every message. To sort them and draft answers faster, the text and diagnostics are also processed by Anthropic (Claude) on our behalf, which doesn't use them to train its models; replies are always sent by a person. Feedback is deleted two years after it was last handled, or sooner if you ask.
Larksail Pro is sold by our reseller Paddle (Paddle.com Market Ltd), the merchant of record. When you buy, you pay Paddle directly: your card or payment details, billing address and the tax information the law requires go to Paddle, who processes them under its own privacy policy — we never see your card. Buying starts from Larksail while you're signed in: our server asks Paddle for a checkout for your account (your email address and account id go to Paddle with it), and the checkout opens on larksail.com/checkout, where Paddle's own script runs it. Paddle tells us what we need to give you Pro and answer billing questions: your email address, country, the plan, the price paid and the subscription's status. We keep these as long as you have an account, and invoices as long as tax law requires.
Larksail asks for only what its features need. Some permissions are optional: Larksail asks for them only when you turn on the feature that uses them, and you can withdraw them at any time in your browser's extension settings.
| Permission | Why |
|---|---|
| Tabs, tab groups, windows | Save, restore, suspend, merge, deduplicate and archive tabs. |
| Navigation events | Notice when you open a page that's already open in another tab ("Already open", off by default). |
| Idle state | Avoid counting time away from the computer as tab idleness, so tabs aren't archived while you're gone. |
| Storage | Keep your data on your device. |
| Notifications, context menus, side panel, alarms | Undo notifications, right-click items, the side panel, and scheduled background tasks. |
| Optional: access to all sites | Show the undo notification inside the page, keep saved copies of pages you save, check for unsent form input, check saved links (only when you click). |
| Optional: page capture | Keep full-page snapshots of pages you ask for. |
| Optional: bookmarks and history | Include your bookmarks and history in Larksail's search, and make collections from bookmark folders you pick. Never sent anywhere. |
| Optional: downloads | Write automatic backup files to your Downloads folder. |
| Optional: access to your AI provider's address | Send AI requests to the provider or local server you chose (only when AI is on). |
| Optional: communicate with cooperating native applications | MCP for AI apps (off by default): talk to the
larksail-mcp helper on your computer, so AI apps you connect can use Larksail. |AI is off by default. When you turn it on in Settings → AI, you choose where it runs:
- On this device: Chrome's built-in model runs on your computer. Nothing is sent anywhere.
- Your own API key with Anthropic, OpenAI, Google (Gemini) or OpenRouter: when you use an AI feature, what that feature needs (for example tab titles, links or the text of a saved page) is sent directly from your browser to the provider you picked, under your own account and that provider's privacy policy. We have no server in between and keep no copy. Your API key is stored on your device only and is never synced. Note that Google may use content sent with a free Gemini API key to improve its products.
- A local model (for example Ollama or LM Studio): requests go to the server address you enter, usually your own computer.
Larksail asks for access to the provider's address only when you pick it, and asks your permission in the app before the first request to each provider or server, saying what may be sent. It sends nothing until you use a feature, nothing in the background, and never to any party you didn't choose. You can revoke that permission in Settings → AI. AI results — answers, chats and summaries — are kept on your device like the rest of your data, and are included in your backups.
Off by default. If you turn it on and install the
larksail-mcp helper, AI apps on your computer that you connect to it (for example Claude, ChatGPT or Cursor) can search your saved tabs, notes, saved pages, highlights, closed tabs and open tabs, and — only if you turn on Allow changes — open, save and close tabs and create notes. The helper runs on your computer and passes messages only between Larksail and those apps, through a local connection only your user account can open; nothing goes to us. What an AI app reads through it, it may send to its own model under that app's privacy policy — as with anything you paste into it.If you turn on automatic backups, Larksail writes backup files to a folder in your Downloads. Export and import work with files you choose. Those files are yours, and Larksail doesn't send them anywhere.
The launcher (⌥⇧K) opens over the page you're on, in a frame that shows a Larksail page. For the browser to allow that, the frame's page has to be reachable by websites. As a side effect, a website could check whether Larksail is installed in your browser. It cannot see any of your data.
Published pages on larksail.com (and only those) can ask the extension whether it is installed, so they can show "Save to my Larksail" instead of "Get Larksail". They cannot read any of your data; they can only ask the extension to add or open the published page you are looking at, and adding always asks you first.
Everything Larksail keeps on your device stays under your control and isn't processed by us. For what reaches our server, the GDPR's legal bases are:
- To provide the service you asked for (performance of a contract, Art. 6(1)(b)): your account, sign-in and its emails, sync, published pages and Pro purchases.
- Our legitimate interests (Art. 6(1)(f)) in keeping the service secure and free of abuse: sign-in sessions' network address and browser, rate limits, the hashed address of whoever reports a page, the link safety check before publishing, records of pages taken down, handling the feedback you send us, and counting visits to larksail.com.
- Your consent (Art. 6(1)(a)): marketing email, only if you opt in. You can withdraw it at any time.
- Legal obligations (Art. 6(1)(c)): when the law requires us to keep or hand over data.
Remove any item in Larksail, or clear the archive in Settings. Uninstalling Larksail deletes all of its data from your browser. Backup files you exported or that were written to your Downloads folder stay there until you delete them.
For data on our server (account, encrypted library, published pages, feedback you sent), you can ask us to see, correct, export or delete it by emailing hello@larksail.com. You also have the right to lodge a complaint with your local data-protection authority.
Larksail is a general-purpose productivity tool and isn't directed at children. Accounts are for people aged 16 or older. If we learn that an account belongs to someone younger, we delete it.
If this policy changes, the new version will be published at this address with an updated date; for changes that affect account holders, we'll also email them. Larksail's core promise won't change: your data stays on your device unless you choose to send it somewhere — and what you sync stays encrypted.
Questions? Email hello@larksail.com.