Inside Closo
How Closo works under the hood — extension, automations, security.
Articles
- What the Closo extension can read (and what it can't) An honest breakdown of every permission Closo asks for, what we use it for, and what we deliberately don't touch.
- Connection health — how Closo keeps logins fresh Closo runs quiet background jobs every 24-180 minutes per marketplace to keep your sessions alive. Here's what that looks like.
- When the extension can't reach a marketplace Seeing 'Could not connect to <marketplace>'? Here's how to debug in 30 seconds.
- Extension vs Closo server — who does what Two pieces of Closo split the work. Here's the line between them and why it matters when something breaks.
- What 'session expired' really means Your marketplace logged you out. Closo's extension caught it. Reconnecting takes 30 seconds.
- Why Closo needs a browser extension Marketplaces don't have a 'list this item via API' button. Here's why our extension solves that gap.
- How we keep your marketplace login secure Closo encrypts your marketplace tokens at rest, never logs them, and uses your browser's own session — not a copy on our servers.
- How the Closo extension works A 2-minute tour of what your Closo extension does in the background — and why crosslisting needs one.