How SNcode works with your instance

SNcode connects over the ServiceNow REST API using HTTP Basic authentication, with the username and password (or a REST-enabled account) you enter for each instance. When an instance rejects Basic auth (for example, SSO/MFA-only accounts), SNcode falls back to driving an authenticated browser session for that instance.

The connection is desktop-to-instance and direct. SNcode builds the authorization header on your machine and talks to your instance from your machine. There is no SNcode server between the app and your ServiceNow instance.

Nothing. SNcode is not a plugin, a scoped application, or a store entry. There is no update set to import and no platform version to upgrade to. It authenticates as an account you already control and uses the REST API and UI that instance already exposes, which is also why it works against older releases and against client instances where you have credentials but no ability to install anything.

Instance URLs and credentials are stored locally in a SQLite database on your own machine, at ~/.sncode/ on macOS and %USERPROFILE%\.sncode\ on Windows, encrypted at rest with SQLCipher. The database key is generated per user and sealed by the operating system's own secure storage (via Electron): the macOS Keychain on Mac, DPAPI on Windows. It lives only in the app's main process at runtime and is never written to disk in the clear.

This is the part worth reading closely. Your ServiceNow credentials, chat history, and attached files are stored only on your machine. When you send a message, the conversation, including any ServiceNow query results or file excerpts it contains, is sent over TLS to the SNcode API. That is true in both of the ways SNcode can run the AI; they differ in what happens next.

SNcode API mode (Free, Core, Scale, Business Team, Business Scale, and the fallback tasks on Local plans): the SNcode API authenticates you, meters token usage, and relays the request to the Anthropic Claude API. Per Anthropic's commercial terms, API inputs and outputs are not used to train their models.

Local Claude mode (Local, Business Local, any paid plan when you choose to run locally, and the Free plan's 60-day trial): the SNcode API assembles the prompt from the team's instructions and your conversation and hands it back to the app. Your locally installed Claude Code then sends it to Anthropic under your own Claude subscription. Token usage counts against your own account; SNcode does not meter it.

In both modes, SNcode processes the conversation in transit only. It is not written to our database or to our logs. The only thing we keep from a request is its token count, in API mode, for quotas and billing.

Either way, remember the implication: data the AI reads from your instance can become part of the prompt sent to the model. Treat the AI request boundary accordingly.

To operate accounts and enforce limits, the minimum:

• Account profile: email and user ID, plus name and avatar when you sign in with Google or Microsoft
• Aggregate token usage counts, for quotas and billing
• Subscription plan, seat count, and billing status (from Paddle, our payment processor)
• Bug reports you choose to send from the app, including any app logs you attach

SNcode does not store your ServiceNow credentials, conversation content, or attached files on its servers.

Not unless you let it. Execution goes through a review gate: when the AI proposes a script, SNcode shows you a plain-English description and the exact code, and nothing runs against your instance until you explicitly approve that action. The gate is on for every chat by default; if you switch on Skip confirmation in a chat's settings, scripts in that chat run without waiting for approval. See The Review Gate.

Deleting an instance in the app removes its stored credentials from the local database. Signing out closes the encrypted database. Your local data lives under ~/.sncode/ on macOS and %USERPROFILE%\.sncode\ on Windows. Removing the app does not automatically erase it; delete that folder to remove local data completely.

Both builds are code-signed, and updates are delivered as signed builds. The macOS app uses hardened runtime and is notarized by Apple; the Windows installer and executables are signed through Azure Trusted Signing, so Windows can verify the publisher. We do not bundle third-party analytics or tracking SDKs. If you agree to log collection when signing in, the app sends operational logs (errors and timings, never conversation content) used to keep the service reliable; they are never sold or used for advertising.

SNcode is in beta. What is true today: local-first architecture, ServiceNow credentials that stay on your machine, an encrypted-at-rest local database, review-gated execution (on by default), a notarized macOS build, and a signed Windows build. What we have not done yet: we do not hold a SOC 2 report or a third-party security audit, and we are not making compliance certifications. We would rather say that plainly than imply otherwise.

Security questions or vulnerability reports: support@sncode.dev. For data handling and your rights, see our Privacy Policy.