Home · Security

Skupa — Security Posture

Skupa is built to be pointed at production systems. This page documents how, so your security team can verify rather than trust.

Data source access is strictly read-only

Authentication

Secrets at rest

SecretProtection
MSAL token cacheDPAPI (CurrentUser)
Claude API key (optional)DPAPI (CurrentUser) + entropy
License/trial stateDPAPI (CurrentUser) + entropy

No secrets are stored in plaintext, source code, or logs.

No telemetry

Skupa sends nothing home. There is no usage analytics and no update pinging. License activation is fully offline (ECDSA-signed keys verified locally). The only network calls Skupa makes are to your own Azure tenant, and — if you opt in — to your chosen AI provider.

AI integration (optional, off by default)

Nothing is sent to an AI provider unless you configure one (your own Anthropic key or your organization's Azure OpenAI endpoint) and explicitly click an AI action. What is transmitted: object names, types, dependency lists, and the SQL definition of the selected object — never credentials, tokens, or data rows.

Embedded browser

The dependency diagram renders in WebView2 locked to the bundled local page: external navigation, popups, DevTools, context menus, autofill, and host object injection are all disabled.

Reporting a vulnerability

Email sales@skupa.io with subject "SECURITY". Please report suspected vulnerabilities privately.