Security and procurement
For the IT, security, compliance and purchasing teams who approve Nevisel. This page covers Nevisel 1.0 on Windows, and you can check every statement on it on your own computers. Last updated October 16, 2026.
At a glance
| Customer data Causalytics receives | None. Snippets, notes and settings stay on each computer, and the shared library stays on your SQL Server. |
|---|---|
| Network connections | None, except to your own SQL Server when you turn on the shared library. Nevisel opens no listening ports. |
| Telemetry and crash reports | None. |
| Accounts | No Nevisel account. The shared library signs in with each person's Windows identity. |
| Licensing | Offline. A key's Ed25519 signature is checked on the computer; there is no license or activation server. |
| Updates | Nevisel never updates itself or checks for updates. You decide when to deploy each release. |
| Subprocessors for the app | None. This website and online checkout use Netlify, Plausible and Paddle, described in the privacy notice. |
| Platform for organizations | Windows 10 and 11, 64-bit. The shared library is Windows only. |
| Buying | Purchase order and invoice, payable within 30 days. See Buying for an organization. |
What touches the network
Nevisel.exe and nevisel-mcp.exe include no HTTP client. The only connection either makes is the one you configure.
| Part | Connects to |
|---|---|
| Expansion, snippets, notes, spelling and grammar, PDF export | Nothing |
| Shared library | Your SQL Server, through ODBC with Windows Integrated Authentication, at each sync |
| License check | Nothing. The key is verified on the computer. |
nevisel-mcp (optional) | Nothing. An AI assistant starts it and talks to it through standard input and output. |
The shared library is cached on each computer, so expansion keeps working when the server is out of reach.
Keystrokes
To expand bindings, Nevisel watches the keys typed in other programs, as every text expander must. Security tools that look for keyboard monitoring will find it. This is all it keeps:
- Only the word being typed, in memory, at most 128 characters, cleared at every space, Tab or Enter.
- Nothing typed is ever logged, stored or sent.
- Anyone can pause expansion from the toolbar, the Expansion menu or the tray.
Where data lives
- The personal library is a SQLite database in the user's profile, in
%LOCALAPPDATA%\. Nevisel does not encrypt it; the computer's disk encryption, such as BitLocker, protects it.Causalytics\ Nevisel\ data - Locked notes are encrypted with a secret phrase (Argon2id and XChaCha20-Poly1305). Causalytics cannot open them or recover a lost phrase; only the person's recovery key can.
- The shared library lives in your SQL Server and is cached on each computer for offline use.
- License and trial dates are kept in
license.jsonin the data folder, and the trial's first day also underHKEY_CURRENT_USER\.Software\ Causalytics\ Nevisel - Identifiers. Nevisel refuses to save snippets, shared phrases, notes and imports that look like a Social Security number, a labelled date of birth or a medical record number. It cannot recognise names, so it is a guard rail, not a data loss prevention control.
Controls in the shared library
- Your server. The shared library is a set of tables in your own Microsoft SQL Server. Causalytics has no access to it.
- Windows identity, no stored passwords. Nevisel connects with Windows Integrated Authentication and stores no SQL credentials.
- Encrypted in transit with ODBC Driver 18 for SQL Server, which encrypts the connection and checks the server's certificate by default. The older drivers encrypt only when you turn it on.
- Editors are a Windows group you name. SQL Server permissions decide who can change shared phrases, and SQL Server checks every write, so removing someone from the group takes effect at once. Everyone else can only read.
- Safe writes. Each change is one transaction of parameterized statements, with a version check so two editors cannot overwrite each other.
- An audit row for every change. Each insert, update and delete made in Nevisel writes the phrase as changed to an audit table. A trigger on SQL Server records who made it and when (UTC), so a client cannot record another name. Changes made outside Nevisel, for example in SQL Server Management Studio, need SQL Server Audit.
AI assistants and approved prompts
- Approved prompts. The shared library can hold the prompts your AI policy approves. Staff type a binding in any AI tool and get the approved prompt, word for word. Nevisel makes the approved prompt the easiest one to use; it cannot stop anyone typing their own.
nevisel-mcpis optional and separate. On Windows it is its own signed program. If you do not deploynevisel-mcp.exe, no assistant can reach Nevisel.- Narrow by design. It listens on no network port, is read-only unless started with
--allow-writes, never shows Clinical, shared or disabled snippets, and never reads the clipboard. - Covered by your assistant's review. What an assistant reads goes to that assistant's provider.
nevisel-mcp's log records which tools ran, never snippet contents.
Signed software and allowlisting
- Authenticode-signed.
Nevisel.exeandnevisel-mcp.exeare signed by Causalytics through Microsoft's Artifact Signing, with SHA-256 and an RFC 3161 timestamp. Each release's signature is verified before it is published. - Rules on the publisher. Artifact Signing issues short-lived certificates, so the certificate changes often while the publisher, Causalytics, stays the same. Base AppLocker rules on the publisher, not on a certificate thumbprint or a file hash, which changes with every release. For App Control for Business, follow Microsoft's guidance for Artifact Signing.
- No installer, no admin rights. Nevisel is one program that runs from the user's profile. If your policy blocks programs in user-writable folders, a publisher rule lets it run, or you can place it in a folder you control.
- Checksums. The download page lists the SHA-256 of every file.
- Mac. The Mac app is not yet signed with an Apple Developer ID or notarized, so for organizations Nevisel is a Windows product for now.
To see a file's signature in PowerShell:
Get-AuthenticodeSignature .\Nevisel.exe | Format-List Status, SignerCertificate, TimeStamperCertificate
How releases are built
- Nevisel is written in Rust. Every release is built, tested and signed from source by an automated release workflow.
- Every third-party component and its license is listed in the open-source notices.
- A CycloneDX software bill of materials for each release is available on request.
Accessibility
Nevisel targets WCAG 2.1 Level AA, as applied to desktop software by the W3C's WCAG2ICT guidance. The accessibility self-assessment goes criterion by criterion and lists the known limitations. It is our own assessment, not a third-party audit.
Reporting a vulnerability
Email info@causalyticsimpact.com with "Security" in the subject, the Nevisel version and the steps to reproduce. Please give us the chance to fix the problem before you publish it. The same contact is in security.txt.
Buying for an organization
- Purchase order and invoice. Send us a purchase order, or ask for a quote first, and we invoice your organization, payable within 30 days.
- $49.99 per user for 12 months, with every feature. Licenses never renew automatically, so nothing is charged without a new order, and a license can be reassigned when someone leaves.
- A pilot needs no purchase. Every feature is free for 45 days, with no account.
- Security questionnaires. Send us yours, such as SIG Lite, CAIQ or HECVAT, and we complete it.
- Vendor. Causalytics, 27221 Red Willow Ct, Valencia, California 91381, United States.
The license terms are in the license agreement, and the pricing page has the details of a license.