Official product disclosure

Software, download & safety information

Last updated: August 9, 2026

Developer, publisher, and operator

ClaudeVBA and ClaudeVBA Companion are developed, published, and operated by LIMONTHE AS, Norwegian organization number 938 182 957, Mokollveien 38B, 3226 Sandefjord, Norway.

Claude and Claude for Excel are trademarks of Anthropic. Excel and Microsoft are trademarks of Microsoft. ClaudeVBA is an independent product and is not affiliated with, endorsed by, or sponsored by Anthropic or Microsoft.

Supported software and current version references

• macOS on Apple silicon (arm64) and Intel (x86_64), with desktop Microsoft Excel.
• 64-bit Windows-compatible systems, with desktop Microsoft Excel.
• Current Companion and installer-service version reference: 0.1.31.

This version reference does not mean a signed customer release is available. The private access service remains disabled until the matching Windows x64, macOS arm64, and macOS x86_64 installers all pass release verification.

Download and signing status

Production signing is currently not complete. This page does not present any installer as a verified signed download and intentionally provides no public installer link. When a verified release is ready, entitled customers receive short-lived private download links through the access page; binaries are not distributed by public stable routes. Until Developer ID signing and notarization for macOS and Authenticode signing for Windows are complete and verified, treat any available build as an unsigned pre-production build.

Do not bypass an operating-system warning based only on the ClaudeVBA name or logo. Contact support to confirm the expected filename, version, and signing state before installing.

What installation changes

On macOS, installation copies ClaudeVBA Companion.app to Applications and registers the claudevba: link scheme through the app bundle. Companion stores settings, activation state, staging files, backups, helper files, and local audit data under ~/Library/Application Support/ClaudeVBA Companion. macOS may ask for permission to automate Microsoft Excel.

On Windows, the per-user installer places the app under %LOCALAPPDATA%\Programs\ClaudeVBA Companion, adds a Start menu shortcut, and registers the claudevba: link scheme for the current user. Runtime settings, activation state, staging files, backups, helper files, and local audit data are stored under %APPDATA%\ClaudeVBA Companion. The installer does not add an automatic startup task or system service.

For live VBA editing, Excel must allow programmatic access to the VBA project object model. Review this security-sensitive Excel setting and generated VBA before enabling or running macros.

Workbook open and close behavior

For normal VBA edits, keep the saved local workbook open in desktop Excel. When Excel automation and VBA project access are available, Companion applies the reviewed changes live and saves the workbook without closing it. If live apply fails, Companion reports the error and does not silently close the open workbook.

If Excel automation is unavailable and Excel has locked the file, Companion cannot perform a file-based replacement and may ask you to close the workbook once. A deploy to a closed, writable file uses a staged copy and backup; open the workbook afterward to load the changes. Always test on a copy of important workbooks.

Network and data behavior

• Companion makes outbound HTTPS and secure WebSocket connections to the ClaudeVBA service for activation, entitlement checks, connector authorization, device presence, requests, and results. No tunnel or inbound port forwarding is required.
• Companion reads only the Active workbook you select within an allowlisted folder. Staging copies, backups, settings, and audit records remain local unless you move or share them.
• Workbook files and VBA source are not intentionally persisted in the ClaudeVBA cloud database. Content requested in a tool call passes through the ClaudeVBA relay to Anthropic and is processed under the terms and controls of your Claude plan.
• The service stores limited account, subscription, activation, device, OAuth, connection, and security metadata needed to provide and protect the service. Stripe processes payment details; ClaudeVBA does not receive full card numbers.

See Data handling and Privacy for more detail.

Deactivate the connector and remove the app

1. In Companion, choose Deactivate. This disconnects Companion and removes its local device credential.
2. In Claude settings, disable or remove the ClaudeVBA connector so Claude can no longer request workbook tools through it.
3. On macOS, quit Companion and move ClaudeVBA Companion.app from Applications to Trash.
4. On Windows, quit Companion, open Settings → Apps → Installed apps, and uninstall ClaudeVBA Companion. The uninstaller removes the app, Start menu shortcut, and registered link scheme.

Uninstalling does not guarantee removal of local settings, logs, staging files, or backups. After preserving any backup you need, delete the ClaudeVBA Companion application-data folder listed above to remove those local files. Deactivation and uninstall do not cancel a subscription.

Subscription, trial, cancellation, and seller

ClaudeVBA costs USD $9.99 per month after a 3-day free trial. A payment method is required. Cancel from the Stripe customer portal linked on the private access page before the trial ends to avoid the first charge, or before the next renewal to stop future renewals. Access continues through the applicable trial or paid period, subject to the subscription terms.

Checkout currently uses Stripe Managed Payments. For a transaction processed through that program, the applicable Stripe entity identified in Checkout and on the receipt acts as seller and merchant of record. LIMONTHE AS is the software developer, publisher, operator, and support provider; it does not claim to be merchant of record for those transactions.

Support

Email daniel@claudevba.com or visit Support. Include your operating system, Companion version, and the exact warning or error. Never email workbook content, activation links, or payment-card details.