We don't collect
your data.

01What Try Sidekit is

Try Sidekit has two parts:

• A Chrome extension that provides the side panel UI
• A local companion app (@try-sidekit/companion) that runs on your machine

The extension talks to the companion over http://127.0.0.1:47321 — a connection that never leaves your computer.

02What the extension accesses

• Active browser tab — only when an agent has the readActiveTab permission and you explicitly invoke it. The extension reads the URL, title, and visible text of the tab you have focused.
• User input — messages you type into the side panel.
• Local storage — your UI preferences (port, theme).

The extension does not track which websites you visit. It does not collect browsing history. It does not run on pages you haven't explicitly invoked it on.

03What the companion stores locally

The companion stores everything locally on your machine in ~/.sidekit/:

• Your agent configurations (names, permissions, system prompts)
• Your chat history
• Token usage and cost records (so you can track spend)
• Per-agent sandbox files (whatever the agent writes to its own folder)

You own this data. You can inspect it, back it up, move it, or delete it. Running rm -rf ~/.sidekit/ wipes everything.

04Where data leaves your machine

The only outbound network requests Try Sidekit makes are to LLM provider APIs that you have configured. When an agent sends a message, the content goes directly from your companion to the provider you chose:

• OpenAI — if you've added an OpenAI key
• Anthropic — if you've added an Anthropic key
• Google — if you've added a Google AI key
• Ollama — runs locally on your machine. Zero outbound requests.

If you enable the Web Search skill, search queries also go to Brave Search.

We do not intermediate, proxy, or log these requests. They go directly from your companion to the provider. Their privacy policies apply.

05API key storage

Your LLM provider API keys are stored in your operating system's secure credential store:

• macOS — Keychain
• Windows — Credential Vault
• Linux — GNOME Keyring / KWallet via libsecret

Keys are never stored in plaintext files. Keys are never transmitted to Try Sidekit — we literally have no servers to receive them.

06What we do NOT do

• We do not track which websites you visit
• We do not collect analytics or telemetry
• We do not collect crash reports
• We do not sell data — we have no data to sell
• We do not serve ads
• We do not require accounts — there is no login
• We do not have servers — nothing runs on our infrastructure because we have none

07Chrome permissions requested

When the Chrome extension ships, it will request these permissions. Here's why each is needed:

• activeTab — temporary access to the current tab when the user invokes an agent
• tabs — to identify which tab is currently focused across windows
• storage — for extension UI preferences
• sidePanel — to show the Try Sidekit panel
• scripting — to inject the command overlay on pages when invoked
• <all_urls> — required because users may invoke agents on any site. Try Sidekit never touches a page unless the user explicitly invokes an agent on it
• http://127.0.0.1:47321/* — to talk to the local companion

08Children's privacy

Try Sidekit is not directed at children under 13. We do not knowingly collect data from them — or anyone else.

09Changes to this policy

If we update this policy, we'll update the date at the top. Material changes will be announced on trysidekit.com.

10Contact

Questions about privacy? Email privacy@trysidekit.com.

Bug reports? Email hello@trysidekit.com.