ArcPanel
Privacy

Privacy for ArcPanel

ArcPanel is built around page-aware actions, but the default posture is local-first. The core product should be useful without an account and without sending routine tool input to a remote service.

What stays local

  • Core actions stay local: JSON, JWT, regex, URL, Base64, word count, clipboard history, color workflows, screenshot frame, and GIF flows are designed to run in the extension or browser context.
  • Clipboard history: recent copied values are stored locally so ArcPanel can reopen and reuse them.
  • Intent and usage data: local history is used to rank the next best action in the side panel.

Why page access exists

  • ArcPanel reads the current page URL, title, and selected text so it can suggest or prefill the right action.
  • Capture-oriented actions need page context to open beside the page you are already working on.
  • Permissions are kept to the minimum set needed for the shipped core flows.

AI is optional

The extension should remain useful without AI credentials. If you choose to use AI features, those requests may be sent to the configured provider or ArcPanel proxy for that specific action. AI is not required for JSON, JWT, regex, URL, Base64, color, clipboard, screenshot, GIF, or word-count flows.

Support and questions

Privacy questions and data handling concerns can be sent to [email protected]. General support details are on support.