Privacy

Last updated: August 2026

ClaudeVBA is operated by LIMONTHE AS, Norwegian organization number 938 182 957, Mokollveien 38B, 3226 Sandefjord, Norway. This notice explains what ClaudeVBA processes. For the technical data path and retention boundaries, see Data handling.

Workbook and VBA content

ClaudeVBA does not persist your workbook files or VBA source in the ClaudeVBA cloud service. When you ask Claude to inspect or change VBA, the requested content passes through the ClaudeVBA relay and Anthropic for processing. Anthropic handles that content under the terms and data controls for your Claude plan.

Local files

Companion reads the Active workbook on your computer. Staging copies, backups, settings, and local audit records remain on that computer unless you move or share them.

Purchase and service records

Payments and subscriptions are processed by Stripe. We receive customer, subscription, trial, invoice, payment-status, refund, and dispute metadata needed to provide access and support. ClaudeVBA does not receive or store full card details. The cloud service stores entitlement, activation, device, OAuth, billing-status, and limited service data needed to authenticate the connector, operate the relay, prevent repeated trial abuse, and provide support.

Infrastructure providers

Stripe processes payments; Anthropic processes Claude conversations and connector tool results; hosting and relay providers process data in transit and operational metadata. Their own terms and privacy notices also apply.

Google Ads, cookies, and click identifiers

ClaudeVBA uses Google Ads conversion measurement only if you allow advertising privacy storage. Until then, Google advertising tags are not downloaded and advertising, analytics, user-data, and personalization consent remain denied. If you opt in, Google may set or read cookies and process the page you visit, conversion events, and advertising click identifiers such as gclid, gbraid, or wbraid.

A permitted click identifier may be retained in this browser, passed to our checkout API, and stored with Stripe and the related entitlement so a later paid invoice can be attributed. Private access tokens and Stripe Checkout Session IDs are removed from the address bar before advertising code can run and are never used as Google transaction identifiers.

You can decline without affecting essential service, change your choice, or clear retained advertising identifiers at any time using advertising privacy choices.

Contact

For privacy or deletion requests, email daniel@claudevba.com.