Privacy

What Lunma stores, and where

Your workspace lives in your browser's local extension storage, on this device. That covers your Spaces, your pinned tabs, your favourites, and the tabs Lunma has archived for you. It's there after a restart, and it doesn't leave the machine, because there's nowhere for it to go.

Your preferences are the one thing that travels. Settings like Colour intensity and density sit in your browser's synced storage, so when you're signed into your browser they follow your profile to your other machines, the same way your bookmarks do. That's your browser's own sync, not ours, and your Spaces and tabs are never part of it.

If you give a connector an access token, it stays in local storage on this device and never syncs. We keep tokens out of synced storage on purpose, so one can't ride your browser account to another machine. A token is never written to a log and never shown back to you in the options screen.

The permissions Lunma asks for

Each permission is here for a job you can point to.

• Your open tabs, so the sidebar can show them and the launcher can search them.
• Tab groups, because a Space is built on your browser's own tab groups.
• An alarm, so Lunma can tell when a tab has gone idle and archive it.
• Bookmarks and history are optional. The launcher can fold them into a search, and Lunma asks for each the first time you reach for it, not at install. Lunma reads them on your machine and sends them nowhere.
• A small script on the pages you open, so the launcher works wherever you are and a pinned tab stays on its own page. It reads the text you type into the launcher and the link you click. It never reads the page around it.

All of it reads locally. None of it goes to a server of ours, because we don't have one.

Connecting Lunma to a service

A smart folder can pull in your work from a service you already use, like a code host, an issue tracker, or a feed. When you connect one, Lunma talks to that service directly from your browser. It only asks for that access when you connect, and nothing about the connection passes through us.

How it signs in depends on the service. Some take an access token you create and paste in. That token is your authentication for that host: Lunma stores it locally and sends it only to the host it belongs to. Others ride the session you're already signed into, so the request carries your existing browser cookie to that host, the same as if you'd opened the site yourself. Either way the request goes straight to the service and the results come straight back.

A public feed needs none of this. Lunma fetches it directly, with no sign-in.

Backup and export

You can export your workspace to a file and import it back later. That file is yours. It's written wherever you choose on your own disk. Lunma never uploads it, and it's the only copy unless you make another. Keep it somewhere safe if it matters to you.

Keeping it, and deleting it

Lunma holds nothing of yours, so there's nothing for us to keep or delete. Your data lasts exactly as long as it sits in your browser. Clear the extension's storage, or remove Lunma, and it's gone from that browser. Your open tabs stay open either way, since they're ordinary browser tabs. A connector token goes when you disconnect the connector or clear storage.

Children

Lunma collects nothing from anyone, children included. There's no account to create and no age to enter.

Chrome's data policy

Lunma's use of information received from Chrome and Google APIs adheres to the Chrome Web Store User Data Policy, including the Limited Use requirements. In plain terms: Lunma reads what it needs to do the job you asked for, on your own machine. None of it is sold or passed on.

Lunma is not a data controller

Because Lunma gathers no data about you and sends none to itself, it isn't a controller or a processor of your data under laws like the GDPR or CCPA. There's no profile of you to hand over or delete, because none was ever built. Your data stays in your browser the whole time, and it stays yours.

Changes to this policy

If this policy changes, the new version goes up here and the date at the top moves with it. Lunma has no way to email you, so checking back is how you'll see what's new. We won't quietly start collecting your data. Nothing here is built to.

Contact

If something here needs explaining, email [email protected]. The code is public too, so you can read what Lunma does and hold this page to it.