# SigmaShake Desktop | IT, Security & Compliance Review Packet

> Pre-filled responses to the standard vendor-review questions your IT,
> Security, and Compliance teams will ask before approving SigmaShake Desktop
> for installation on a corporate workstation.
>
> **Download URL:** https://sigmashake.com/desktop/it-review.md
> **Product version covered:** SigmaShake Desktop v1.0.22
> **Document generated:** 2026-10-12
> **Vendor contact for follow-up questions:** security@sigmashake.com
> **Trust portal (auditor artifacts, NDA-gated):** https://trust.sigmashake.com
> **Machine-readable compliance manifest:** https://trust.sigmashake.com/.well-known/compliance.json

If a question your team needs answered isn't covered below, email
security@sigmashake.com. We publish answers back into this packet so the
next reviewer doesn't have to ask.

---

## 1. Vendor identification

| Field | Value |
|---|---|
| Legal entity | SigmaShake |
| Primary website | https://sigmashake.com |
| Trust portal | https://trust.sigmashake.com |
| Security contact | security@sigmashake.com |
| Privacy contact | privacy@sigmashake.com |
| Support contact | support@sigmashake.com |
| Disclosure policy | https://trust.sigmashake.com/vulnerability-report |
| security.txt | https://sigmashake.com/.well-known/security.txt |

## 2. Product identification

| Field | Value |
|---|---|
| Product name | SigmaShake Desktop |
| Version covered | v1.0.22 |
| Distribution surfaces | Direct download (download.sigmashake.com), Homebrew tap, APT repo (apt.sigmashake.com), npm coordinator (`@sigmashake/ssg`), winget, PyPI |
| Licensing | Proprietary. Commercial use requires an active SigmaShake Pro or Enterprise subscription; governed by the SigmaShake EULA. Source-code access is granted only under an Enterprise Source Code Access Addendum. |
| Runs as | Per-user desktop application (no admin / root / UAC required) |
| Underlying CLI | The desktop app is a thin shell around the same `ssg` CLI; both share one rule engine. |
| Underlying GUI runtime | Per OS: Windows: C# / .NET 8 + WebView2 (~96 MB NSIS installer); macOS: Swift / AppKit + WKWebView (~20 MB .dmg); Linux: Go / Wails v2 + system WebKitGTK (~12 MB .tar.gz) |

## 3. What it does and why your team is being asked to install it

SigmaShake Desktop is an **AI agent governance and guardrail tool**. It sits
between an AI coding assistant (Claude Code, Codex, Cursor, Copilot, Antigravity,
Grok, Replit, OpenCode, Aider, Pi, or MCP-compatible assistants) and the local machine, evaluates every tool call the
assistant tries to make (file write, shell command, network fetch, etc.)
against an allow/deny/ask/force/log/shadow ruleset, and blocks, prompts,
substitutes safer paths, logs, or shadow-audits dangerous calls in
under 2 ms.

If your team is being asked to approve this app, it's almost certainly
because:

- An engineer at your company uses Claude Code / Cursor / Copilot / etc. and
  wants on-machine guardrails to prevent the assistant from running
  destructive commands, force-pushing, uninstalling packages without
  approval, etc.
- Your security team has asked for telemetry / audit logs of what the AI
  assistant is doing on developer machines.

## 4. Data handling and privacy

| Question | Answer |
|---|---|
| What data does the app collect? | Rule evaluation data stays on-device and never leaves. The app makes a small set of documented background calls: (1) **license heartbeat:** sends JWT, CLI version, and daily evaluation count to `accounts.sigmashake.com` every 6 hours (licensed installs only); (2) **usage heartbeat:** sends an anonymous device fingerprint, version, and daily evaluation count to `accounts.sigmashake.com` every 6 hours (unlicensed installs only, when evaluation count > 0); (3) **usage counter push:** the same anonymous count pushed every 2 minutes for dashboard freshness; (4) **npm update check:** a plain HTTP GET to `registry.npmjs.org` for the `@sigmashake/ssg-<platform>-<arch>` platform package (falls back to coordinator `@sigmashake/ssg` if unavailable); no install data sent; 3 s timeout; silent on failure; suppressed by `SSG_NO_UPDATE_CHECK=1`) every 24 hours. Anonymous product telemetry (install ID, version, OS platform, CPU arch, decision type, command type; no file paths, no content, no inputs) requires an **explicit opt-in** prompt answered 'y' on first eval; it is off by default. Cloud audit sync (audit log entries) requires explicit configuration and is off by default. No analytics endpoint is called without opt-in. |
| What data leaves the machine? | Only via the documented calls above. Cloud audit sync, if configured, sends audit log entries (rule decisions only, with no file contents or prompts) to the user's chosen SigmaShake account. |
| Is rule evaluation done locally? | Yes. The rule engine runs **entirely on-device**. Tool call evaluation completes in sub-2 ms. No network round-trip per evaluation. |
| Does it read source code? | The app reads the **arguments** of tool calls it evaluates (e.g. the file path being written, the command being run). It does not bulk-scan or index your codebase. |
| Where is data stored at rest? | On the user's machine, under `~/.sigmashake/` (macOS / Linux) or `%LOCALAPPDATA%\SigmaShake\` (Windows). |
| Personal data scope | Email address (if the user signs in for sync), license key, audit log entries (if cloud sync is enabled). No payment data is stored locally. |
| Data retention (cloud opt-in only) | Audit log: 90 days by default, user-configurable. Account data: until account deletion. |
| Sub-processors (cloud opt-in only) | Cloudflare (compute/storage), Stripe (billing), GitHub (auth), Cerebras (LLM rule-drafting only, never your code). Current list: https://compliance.sigmashake.com/api/v1/sub-processors.json |
| GDPR / UK GDPR / Swiss FADP | DPA available on request (security@sigmashake.com). DSR endpoint: `POST https://compliance.sigmashake.com/api/v1/dsr`. |
| CCPA / CPRA | We do not "sell" personal information as defined under CCPA. Right-to-delete handled via the DSR endpoint above. |
| HIPAA / PHI | Not designed for PHI workloads. Do not store PHI in audit logs. |
| Children's data (COPPA) | Not directed at children under 13. |

## 5. Network and firewall requirements

| Outbound destination | Purpose | Required? |
|---|---|---|
| `accounts.sigmashake.com` | License heartbeat (JWT, version, eval count) every 6 h for licensed installs | Background, licensed installs |
| `accounts.sigmashake.com` | Usage heartbeat (anonymous fingerprint, version, eval count) every 6 h for unlicensed installs when eval count > 0 | Background, unlicensed installs |
| `accounts.sigmashake.com` | Eval-count push (anonymous fingerprint, version, eval count) every ~2 min for dashboard freshness on all installs when eval count > 0 | Background, all installs |
| `registry.npmjs.org` | npm update check: plain GET for `@sigmashake/ssg-<platform>-<arch>/latest` (platform package; falls back to coordinator `@sigmashake/ssg` if unavailable) to detect new release versions for this platform; no install data sent; 3 s timeout; silent on failure; suppressed by `SSG_NO_UPDATE_CHECK=1`; every 24 h | Background, all installs |
| `download.sigmashake.com` | Initial download + delta updates | Yes, at install time |
| `accounts.sigmashake.com` | Sign-in / license activation | Only if the user signs in |
| `hub.sigmashake.com` | Pulling community rule packs | Only if the user runs `ssg hub pull` |
| `metering.sigmashake.com` | Usage counter (license-verified installs) | Background, licensed installs |
| Cerebras API endpoints | LLM-assisted rule drafting (user-initiated) | Only if the user uses voice / AI rule-builder features |

There are **no inbound listening sockets exposed to the network** by default.
A local-only HTTP control surface binds to `127.0.0.1` for the daemon and
the optional dashboard (default `127.0.0.1:5599`); it is not reachable from
other hosts.

## 6. Authentication & access control

| Question | Answer |
|---|---|
| Is authentication required to use the app? | No. The app installs and runs without a sign-in. Sign-in is optional and only used for cloud sync / paid features. |
| Authentication mechanism (when signed in) | OAuth via accounts.sigmashake.com (GitHub, Google, Microsoft, Apple, or Twitch). MFA available on the underlying provider. |
| SSO support | Okta (OIDC) SSO today; SAML 2.0 and Entra ID on request, Enterprise tier. |
| Service-account / admin credentials | None embedded in the binary. No default passwords. No telnet/SSH/RDP listeners. |
| Code signing | Windows: signed by Azure Artifact Signing. macOS: Apple Developer ID notarization in rollout. Linux: SHA-256 checksums published; APT repo signed with the SigmaShake APT GPG key (fingerprint A6A1FA60DC38EE17CA443389F562E7E136D128FA). |

## 7. Hosting, residency, and infrastructure

The desktop application itself runs **on the user's machine**. There is no
hosted backend dependency for core functionality.

If the user opts in to cloud sync, the backing services run on Cloudflare's
global edge network (Workers, D1, R2, KV). Data residency: US / EU (configurable
on Enterprise). Cloudflare holds active SOC 2 Type II and ISO 27001
certifications.

## 8. Compliance posture

Authoritative, machine-readable manifest:
https://trust.sigmashake.com/.well-known/compliance.json

Summary as of the date of this document:

| Framework | Status |
|---|---|
| SOC 2 Type II | Readiness: observation window open (2026-05-18 to 2026-11-17); independent CPA audit not yet engaged; earliest realistic Type II report Q1 2027. Evidence collected and available via trust.sigmashake.com. |
| ISO/IEC 27001:2022 | Self-assessed; 93 controls mapped. Not certified (no third-party audit). |
| GDPR / UK GDPR / Swiss FADP | Compliant: DPA available on request, DSR endpoint live |
| CCPA / CPRA | Compliant: no sale of personal information |
| PCI-DSS | N/A: no payment card data is stored on-device; billing handled by Stripe (PCI-DSS Level 1) |
| HIPAA | Not in scope; product is not designed for PHI |
| Cloud Security Alliance CAIQ v4 | Available on request (NDA-gated, via trust.sigmashake.com) |
| Security review report | AI-assisted internal security review (Claude Opus 4.8), not a third-party penetration test. Most recent round: 2026-06-18 (prior round: Claude Opus 4.7, 2026-05-19). No external offensive-security firm and no CPA firm has been engaged. Available on request (NDA-gated, via trust.sigmashake.com). |

To download evidence (controls report, AI-assisted security review report, SOC 2 readiness, SBOM,
or the full bundle), use the email-gated flow at
https://trust.sigmashake.com. An OTP is sent to your work address and the
NDA is recorded on download.

## 9. Vulnerability management & responsible disclosure

| Field | Value |
|---|---|
| Disclosure policy | https://trust.sigmashake.com/vulnerability-report |
| Security contact | security@sigmashake.com |
| security.txt | https://sigmashake.com/.well-known/security.txt |
| Patching cadence | Critical CVEs in dependencies: patched + released within 72 hours. Non-critical: bundled into the next scheduled release. |
| Auto-update | Enabled by default. Delta updates are signed and verified against the SigmaShake release pipeline's public key before being applied. The user can disable auto-update from Settings. |
| Supply-chain integrity | Canary at https://canary.sigmashake.com re-fetches every published artifact every 15 minutes and alerts on hash divergence. Ed25519-signed manifest. |
| SBOM | CycloneDX 1.6 SBOM published at https://trust.sigmashake.com/sbom |
| Release artifacts | https://github.com/sigmashakeinc/desktop/releases. Each release ships a `checksums.sha256` manifest. |

## 10. Software composition and runtime

| Question | Answer |
|---|---|
| Embedded browser? | Windows: uses the system-installed WebView2 runtime (Edge/Blink; pre-installed on Windows 10 1803+ and 11; installed on-demand if absent, with no bundled Chromium). macOS: uses the system WKWebView (no bundled browser). Linux: uses the system WebKitGTK (no bundled browser). |
| Native code / kernel extensions? | No kernel extensions, no drivers, no system services. The agent runs entirely in user space. |
| Background services | A single per-user daemon (`ssg daemon`) for IPC with AI assistants. No `launchd` / `systemd-system` units installed. Linux uses a user-scope systemd unit (`systemctl --user`), Windows uses a per-user scheduled task, macOS uses a per-user LaunchAgent. |
| Outbound network usage | Only as listed in §5. The daemon does not initiate connections unless the user signs in or invokes a network-using subcommand. |
| Programming language(s) | Per OS: Windows: C# / .NET 8 (shell) + Go (ssg daemon); macOS: Swift / AppKit (shell) + Go (ssg daemon); Linux: Go / Wails v2 (shell + daemon). |

## 11. Installation, update, and uninstallation

| Platform | Install | Update | Uninstall |
|---|---|---|---|
| Windows | Per-user NSIS .exe installer; `%LOCALAPPDATA%\SigmaShake\` | Delta patches via R2 (native C#/.NET updater) | Settings → Apps → SigmaShake Desktop → Uninstall |
| macOS | Drag .app to /Applications (no admin) | In-app updates via Sparkle (signed appcast) | Drag .app to Trash; optionally delete the `~/.sigmashake` config directory |
| Linux (.tar.gz / Wails) | `curl -fsSL sigmashake.com/desktop/install.sh \| sh` → `~/.local/share/SigmaShakeDesktop/` | Delta patches via R2 (Go updater) | Delete `~/.local/share/SigmaShakeDesktop/`, the `sigmashake-desktop.desktop` entry under `~/.local/share/applications/`, and the `~/.sigmashake` config directory |
| Linux (APT) | `apt install ssg` (CLI only) | `apt upgrade` | `apt remove ssg` |

Per-user install means:
- No `sudo` / admin elevation prompt.
- No registry hives outside `HKCU`.
- No `/Library/LaunchDaemons/` entries on macOS.
- No `/etc/systemd/system/` units on Linux.

## 12. Logging, audit, and incident response

- **Local audit log:** every rule decision (ALLOW, DENY, ASK, FORCE, LOG, SHADOW) is written to
  `~/.sigmashake/audit.log` (rotated, append-only) with timestamp, rule
  matched, tool-call arguments, and latency. Inspect from the tray menu or
  run `ssg audit tail`.
- **Cloud audit sync (opt-in):** the same entries can be forwarded to a
  centralized audit endpoint (SIEM-compatible; see sigmashake-siem for the
  forwarder).
- **Incident communications:** material incidents are posted to
  https://status.sigmashake.com and notified to affected customers via the
  contact email on file within 72 hours.

## 13. Removal under corporate policy

If your organization later determines SigmaShake Desktop should not run on
employee workstations:

1. The user can uninstall it themselves with no admin privileges (see §11).
2. There is no anti-uninstall mechanism, no protected service, and no
   tamper-resistant component.
3. The `~/.sigmashake/` directory can be deleted to remove all local state
   (audit log, license key, cached rule packs).
4. If you want central enforcement, you can blocklist
   `download.sigmashake.com`, `apt.sigmashake.com`, the Homebrew tap, and
   `@sigmashake/ssg` in your software-allowlist tooling.

## 14. Source-code access for security review

SigmaShake is proprietary, not open-source. We grant **read-only source-code
access** to Enterprise customers under a Source Code Access Addendum (signed
by counsel on both sides) for the purpose of security review and on-prem
build verification. To start that conversation, contact
sales@sigmashake.com or see https://sigmashake.com/enterprise#source-code-access.

## 15. Open follow-up

If, after reviewing this packet, your team still needs:

- For a signed copy of our **Data Processing Agreement (DPA)**, email privacy@sigmashake.com.
- For a signed copy of our **CAIQ v4 / SIG-Lite / VSA** response, email security@sigmashake.com.
- Request an **AI-assisted security review report**, **SOC 2 readiness report**, or **bulk evidence bundle** via https://trust.sigmashake.com (OTP-gated to your work domain, NDA recorded on download). Note: the security review is AI-assisted, not an independent penetration test.
- For **source-code access** under an Enterprise Source Code Access Addendum, email sales@sigmashake.com.
- For a **live security-team Q&A call**, email security@sigmashake.com and we'll book it.

---

*This document is maintained at `sigmashake-web/src/shared/it-review-packet.ts`.
The canonical version is always at https://sigmashake.com/desktop/it-review.md.
If your reviewer is reading a printed or forwarded copy, please re-fetch the
canonical URL to confirm you have the current answers.*