Security & Compliance

Zero Data Persistence

No chat history stored. No scripts saved. No output cached. Close the application — everything is gone. Nothing is written to disk unless you explicitly export.

Local Execution Only

Scripts execute in an embedded PS7 runspace. Output, variables, credentials never leave your machine.

Mutual Authentication

Client verifies the proxy. Proxy verifies the client. ECDSA challenge-response prevents MITM attacks.

Authenticated Request Path

Every AI request runs through the authenticated proxy path with device-bound session credentials. Captured traffic alone cannot be replayed against another device or reused outside the active session.

Credential Safety

Get-Credential and Read-Host -AsSecureString handled natively. Passwords encrypted in memory. Never logged, never sent to AI.

SIEM-Ready

Full ScriptBlock Logging compatibility. Windows Event Log integration. Audit every script execution.

Device-Bound

Hardware-based device fingerprints. Activation tied to physical machines. Sessions cannot be cloned or transferred.

Server-Enforced Limits

Budget, rate limits, device count all enforced server-side. Client-side tampering cannot bypass restrictions.

EV Code-Signed

Extended Validation certificate. Immediate SmartScreen trust on all Windows systems. No download warnings.

For Procurement & Security Review

The Detailed Answers, in One Place

The points procurement, audit, and security reviewers usually ask about — stated precisely, without marketing gloss.

Endpoint security stays in effect — no App Control, EDR, or AMSI bypass AMSI scans every PowerShell script block at the engine level, regardless of whether the engine is hosted in powershell.exe, pwsh.exe, or in ShellPilot's embedded runspace. App Control for Business (formerly WDAC) and AppLocker put the embedded runspace into ConstrainedLanguage mode the same way they put any other PowerShell session into it. Behavior-based EDR sees ShellPilot.exe loading the PowerShell runtime and executing scripts, and is free to act on what it observes. Application Guard, Defender ASR rules, and comparable controls do what they were configured to do. ShellPilot does not ship, document, or enable any evasion path against any of those controls — by design.
PowerShell script-block logging — enable it on the host, see everything ShellPilot runs PowerShell's script-block logging is the right channel to monitor every command that the embedded runspace and the external PowerShell execute. It writes to Microsoft-Windows-PowerShell/Operational. ShellPilot does nothing to disable or hide from this logging — but it does not turn it on for you either. If your security operations team needs full PowerShell visibility, enable script-block logging through Group Policy or the equivalent endpoint configuration tool on the systems that run ShellPilot. From that moment on, every script executed through ShellPilot is logged in the same event channel as any other PowerShell on the host. Standard SIEM and EDR pipelines that already consume PowerShell logs pick it up automatically.
Execution policy — Bypass for the session only ShellPilot sets the PowerShell execution policy to Bypass for its own session, both for the embedded runspace and for the external PowerShell launched by the yellow and red buttons. This is per-session and ends with the process; nothing on the machine or in the user profile is changed. Microsoft documents the execution policy as a guardrail against unintentional script execution, not a security boundary — "it's not a security boundary because it can't stop determined users from deliberately running scripts" (Microsoft Learn, about_Execution_Policies). A Group Policy Turn on Script Execution takes precedence for the external PowerShell path.
Credentials never reach the AI Read-Host, Get-Credential, and Read-Host -AsSecureString are intercepted by ShellPilot's custom PSHost. The input never appears as a chat message, never gets logged, and is never serialised into an AI request. SecureString content stays in protected memory and is handed to the runspace as a SecureString. This is a structural barrier, not a system-prompt instruction — the data never technically reaches the model on that path.
Script output stays local Output from your scripts never leaves your machine. It is only sent to the AI if you explicitly attach it as context to your next message.
No telemetry, no server-side chat storage The ShellPilot servers on Azure exist for activation, licensing, and request routing. They do not collect telemetry, do not store your chat content, and do not analyse your scripts.
EU data residency for AI processing Cloud AI requests are processed via Google Vertex AI in the EU region, routed through the ShellPilot proxy on Azure EU. The proxy strips your identity before forwarding — the AI provider sees an anonymous device hash and your prompt, not your email, subscription, or company.
ShellPilot's own events are written to the Windows Event Log ShellPilot's lifecycle events (start, activation, errors) are written to the Application event log under the ShellPilot source. This complements the PowerShell logging above — it lets IT confirm whether the application started cleanly on a given host.
ShellPilot always runs with the permissions of the executing user ShellPilot never grants, escalates, or impersonates privileges — there is no service account, no hidden elevation path, no way for the tool to acquire rights the user doesn't have. Elevated operations work the Windows way: the user explicitly starts an elevated console and authenticates with an account that holds those rights; from that moment on, the rights in play are that account's, never ShellPilot's. Launch ShellPilot standard, and nothing ever exceeds your rights. Launch it elevated, and every execution inherits exactly that context — ShellPilot knows its own elevation state and never changes it.
What ShellPilot does not do No bypassing of PowerShell Constrained Language Mode. No elevated privileges required to run. No registry changes, no system services, no hidden processes. Everything lives in the user profile, encrypted with Windows DPAPI, with log rotation. What you can verify, you can trust.

Engineered for Environments
Where Security Is Non-Negotiable

Zero Data Persistence

Local Execution Only

Mutual Authentication

Authenticated Request Path

Credential Safety

SIEM-Ready

Device-Bound

Server-Enforced Limits

EV Code-Signed

The Detailed Answers, in One Place

Questions From Your Security Team?

Engineered for EnvironmentsWhere Security Is Non-Negotiable

Zero Data Persistence

Local Execution Only

Mutual Authentication

Authenticated Request Path

Credential Safety

SIEM-Ready

Device-Bound

Server-Enforced Limits

EV Code-Signed

The Detailed Answers, in One Place

Questions From Your Security Team?

Engineered for Environments
Where Security Is Non-Negotiable