Supplemental Terms for LLM AI Charts for Excel

Supplemental Terms for "LLM AI Charts for Excel", the Microsoft Excel Add-in

Revised: August 26, 2026

This address is the agreement for the Excel add-in. A single document governs both LLM AI Charts products and is published at an address for each of them, so that the same question can never be answered two different ways depending on which one you asked from. The provisions specific to the Excel add-in are collected in Section 2A, and Section 1(c) explains how to read the remainder for a workbook. The companion address is bizintelligencechampions.com/terms-llmchart.

These supplemental terms ("LLM AI Charts Terms") apply to your use of the "LLM AI Charts" Power BI custom visual ("the Visual") and of "LLM AI Charts for Excel", our Microsoft Excel add-in ("the Add-in") — each of them a "Product", and together "the Products" — made available by CodeX Enterprises LLC ("CodeX", "we", "us", "our") (doing business as "BI-Champ" and "bizintelligencechampions.com" and "Biz Intelligence Champions"). They are IN ADDITION TO and form part of our general Terms of Use & Privacy Policy at https://bizintelligencechampions.com/terms. Where these supplemental terms address a topic differently than the general Terms, these supplemental terms control with respect to the Products.

Your installation, use, or generation of charts through either Product constitutes acceptance of these terms. If you do not agree, you must not use that Product.

1. SCOPE

a. These terms cover the LLM AI Charts Power BI visual and the LLM AI Charts Excel add-in specifically. They cover: how each client behaves inside its host application (Power BI or Microsoft Excel); the server-side request handling, model selection, code generation, and quality-check pipeline — which is the SAME backend for both Products; the freemium tier (Visual only — see Section 2(c)); the example-chart lane (Add-in only — see Section 2A(b)); usage credits and licensing; and persistence of any cached generated code in your saved host document, meaning a Power BI report file (".pbix" / ".pbip") or an Excel workbook (".xlsx" and related workbook formats). Use of the broader bizintelligencechampions.com website, your Account, and any other Service is governed by the general Terms of Use.

b. Calling the engine from your own software is covered elsewhere. Where you reach our backend through our API, our Model Context Protocol (MCP) server, or an SDK — rather than through a Product or another client we publish — the RegiaBI Programmatic Access Terms apply, and several sections of these terms are incorporated into them by reference. Programmatic access requires an active license; there is no freemium tier for it.

c. One document, two hosts — how to read it. These terms are deliberately a single document rather than one per host, so that the same question can never be answered two different ways depending on where you asked it. It is published at one address per Product — /terms-llmchart for the Visual and /terms-llmchart-excel for the Add-in — and those two addresses carry the SAME terms; only the heading and this reading guide are phrased for the Product you arrived from. Except where a provision expressly names one Product, every provision applies to BOTH. Where a provision speaks of your report or of a ".pbix" / ".pbip" file, read it as your workbook when you are using the Add-in; where it speaks of a Power BI visual instance, read it as the chart object anchored in your worksheet. Section 2A collects the provisions that are specific to the Excel add-in, and the sections that follow it flag the Excel position wherever the two hosts genuinely differ. If you use only one of the Products, the provisions naming the other are informational and do not bind you.

2. SERVICE MODES — HOSTED, BYO, FREEMIUM

a. Hosted mode (default). The Product sends each generation request to our backend at bizintelligencechampions.com, which dispatches the request to a third-party large language model (LLM) provider. Routing depends on the model selected for the request: we may route through Microsoft Azure AI Foundry (which itself dispatches to upstream providers such as OpenAI, Anthropic, and DeepSeek), OR we may route directly to a provider's native API (for example, the Anthropic API, the OpenAI API, or a provider-specific Azure OpenAI deployment). Which routing path is used for which model is a backend implementation detail that may change at any time. The list of available models, their pricing, their relative cost, and their default selection may change at any time without notice, and any given model's availability may vary independently — subject to both our decisions and the upstream provider's availability and outages. We do not control or guarantee the availability, accuracy, latency, or behavior of the underlying LLM services and are not liable for interruptions, errors, or third-party policies.

b. Bring-Your-Own (BYO) mode. You may configure your Account to use your own API key against your own LLM provider account (for example, your own Anthropic, OpenAI, or Azure OpenAI account). In BYO mode, the request payload — including the constructed prompt, your dataset metadata, your sample data (paid only, see Section 4), and any usertext / commentary you have entered — flows from our backend directly to your chosen provider under your contract with that provider, not ours. We do not control or take responsibility for that provider's policies, billing, retention, abuse review, model behavior, or data handling. The LLM token cost in BYO mode is borne entirely by you with your provider. We do NOT charge usage credits for the provider's token cost itself; however, we DO charge a small flat per-request operating fee in usage credits for each BYO generation (configuration-driven and subject to change at any time without notice). Standard Account, service, and platform terms continue to apply.

c. Freemium tier — the Power BI visual only. The Visual includes a freemium tier that allows new and casual users to evaluate it without an Account or purchase. The Excel add-in has NO freemium tier and no equivalent of one: it is licensed-only. The Add-in's way to see the product without an Account is the example-chart lane in Section 2A(b), which serves pre-built charts over OUR sample data and never sends yours. Nothing in this Section 2(c) applies to the Add-in. The freemium tier is a privilege we extend at our discretion, not a contractual entitlement, and the following apply:

• Each Power BI visual instance receives an internally-generated freemium identifier. Usage credits and request counts are tracked against that identifier on our backend.
• Freemium has a per-instance spending cap, expressed in usage credits. We may change the cap, the unit of measurement, the formula for credit consumption, or the underlying model selected for freemium requests at any time without notice. A request that would exceed the remaining freemium budget will be refused; you will see a "freemium capacity exhausted" or similar message in the Visual.
• Freemium model selection is limited to a freemium-eligible subset of our hosted catalog. Bring-Your-Own (BYO) connections are not available in freemium mode, and our most capable / premium models — for example, Opus- and Fable-class Anthropic models — are excluded from freemium. If you do not select a model, we assign a freemium default. The freemium-eligible set, the default we assign, and the prompt configuration we use for freemium may change at any time without notice.
• Some Visual capabilities are reduced or disabled in freemium mode. Examples include but are not limited to: free-text commentary / user prompts ("USERTEXT") are stripped server-side before reaching the LLM and have no effect on generation; sample dataset rows are not transmitted to the LLM; some of the additional quality-assurance processing that paid tiers receive is reduced or disabled in freemium and should not be relied upon; user-history features such as version unlock and clone may be unavailable.
• Single-attempt generation — no automatic retries. On freemium, each generation request gets one shot. The automatic retry / correction that paid tiers receive on a failed generation does not run for freemium. A freemium request that does not pass our quality checks is shipped best-effort or refused rather than retried, so freemium output is more likely to contain an occasional rendering or quality defect than paid output. This is a deliberate quality limitation of the free tier, distinct from the credit cap and throttle above.
• We may disable freemium for any individual instance, IP address, or country at any time, including in response to suspected abuse, automation, or sharing of freemium identifiers across many reports.
• Freemium authoring availability is not guaranteed. Freemium authoring — generating new or revised chart versions through the LLM — may be throttled, paused, or made unavailable entirely at any time and for any duration we deem necessary, at our sole discretion (for capacity, cost, maintenance, abuse mitigation, or any other reason), with or without notice. This does NOT remove access to chart versions that have ALREADY been generated: once a chart version has been produced, it remains accessible and continues to render from its cached code in your saved report, independent of freemium authoring availability (see Section 5(c)).
• Freemium identifiers and any associated usage state may be reset, regenerated, or expired by us at any time. The freemium tier is not transferable.
• Freemium is intended for genuine evaluation and casual personal use. Use of freemium for production reporting, embedded distribution, or any commercial purpose is not permitted. For those uses, an organizational license is required (see the general Terms, Section 3).

d. Licensed (paid) tier. Use of either Product under an organizational license consumes usage credits granted to or purchased by your Account. Cost per generation depends on the chosen model, prompt size, number of retries, and whether multi-pass features (validator, proofread) are engaged. We may change credit consumption rates, model availability, default model selection, prompt content, multi-pass thresholds, and other generation-pipeline behaviors at any time without notice. Credit balances reflect the configuration in effect at the time of each request and are not retroactively adjusted when configuration changes.

e. Feature matrix by service mode — the Power BI visual. The table below summarizes how features vary across the five service modes of the Visual. It does NOT describe the Excel add-in, which has no freemium column at all and differs in several other respects; for the Add-in, read Section 2A. Features that are the same across all modes (cross-filter, tooltips, cached re-rendering of saved reports, the in-browser code execution model, the tamper-detection signature, etc.) are omitted to keep the table readable; those are covered in the relevant sections of these terms and the general Terms of Use. The table is informational — specific behaviors may change as we tune the Visual (see Section 7); the section text above and below is the binding statement of these terms.

2A. THE EXCEL ADD-IN ("LLM AI Charts for Excel")

This section states the provisions specific to the Add-in. Sections 2(a) and 2(b) — hosted routing and Bring-Your-Own — apply to the Add-in exactly as they apply to the Visual, because both Products call the same backend. Section 2(c) does not apply to the Add-in at all.

a. What the Add-in is. The Add-in is a Microsoft Office content add-in: a chart object anchored in a worksheet and bound to a range of cells. It measures the shape of that range, asks our backend for chart code written for that shape, and draws the chart inside the workbook. It runs in the Office add-in sandbox that Excel provides. Excel, Microsoft 365, AppSource, and the Office add-in platform are Microsoft's, not ours — we do not control them, we cannot guarantee that any Excel version, platform, or channel will run the Add-in, and nothing in these terms alters your agreement with Microsoft.

b. Licensed only — and the example-chart lane. The Add-in is licensed-only. Generating a chart from YOUR data requires an active license, reached by linking the workbook to your Account; a trial license is added automatically when an Account is created. There is no freemium tier here and no anonymous identifier is minted. Separately, and without any Account, the Add-in can serve example charts: pre-built chart code that we have written and vetted, drawn over a sample table that we supply. An example chart involves no LLM call, consumes no credits, and is not generated from your data. Examples cannot be modified through the Add-in, and we may change, rotate, withdraw, or disable the example catalog at any time without notice. We record that an example was served, for usage measurement (Section 4).

c. How you accept these terms in Excel. You are asked in two places, and the first of them comes before any Account exists. In the Add-in itself, you must accept these terms before the Add-in sends anything measured from your worksheet to us — that means before the free chart-type list ("what fits?") as well as before a generation, because both transmit the measured shape of your columns and this page is where we tell you so. That acceptance is held for as long as the task pane is open and is not written to your machine or into your workbook. And on our sign-in page, you are asked again every time you link a workbook to your Account. A link is time-limited, so that acceptance recurs on its own schedule, and the version of these terms in force at the moment you link is the version you accept — which is how a revision under Section 11 reaches Excel users. Because linking is the only way to license the Add-in, a linked workbook has necessarily accepted the version current at the moment it was linked, and the Add-in does not ask a second time in the same session. Generation is blocked until you accept. Your acceptance is deliberately NOT written into the workbook: a workbook travels to other people, and one person's acknowledgement must never be carried to the next person who opens the file.

d. Linking, and what the workbook then holds. A workbook holds a time-limited account-link token bound to that workbook, and nothing else — not your license key and not your Account secret. Linking through our sign-in page is the only way to obtain one. The Add-in has no field in which to type a license key, so a key and an Account secret cannot enter a workbook at all. A workbook written by an older version of the Add-in may still contain encrypted license credentials; the current version clears them the next time that workbook is linked. Our server resolves your Account from the token; the token expires, and you can sign out from the Add-in at any time to remove it. While that token is live, a workbook you distribute may let whoever receives it generate charts against your Account and consume your usage credits. Signing out, or waiting for the link to expire, before you share a workbook is your responsibility. This is the Excel counterpart of the duty stated for reports in Section 5(c), and the disclaimers in Section 10 apply to it in the same way.

e. What leaves your worksheet. For a generation request, the Add-in transmits the MEASURED SHAPE of the bound range as described in Section 3 — column headers as they appear in your sheet, inferred types, and aggregate statistics — together with the chart's size in pixels, your chosen settings, locale, theme colors, and any text you typed into the "what would you like to see?" box. It does not transmit the raw cell values of your worksheet, and it does not transmit sample rows: the privacy-level sample-row option described in Section 3 is a Visual feature, and the Add-in does not populate it. The deterministic chart-type list ("what fits?") also sends the measured shape to our backend so that we can evaluate which chart types the data supports; that request reaches no LLM and consumes no credits, but it does require your acceptance of these terms in the Add-in before it will run — it transmits the measured shape of your columns, and we ask before we send it, not after. The example-chart lane in Section 2A(b) is the one path that needs no acceptance, because it draws pre-built charts over OUR sample data and transmits nothing measured from your sheet; writing that sample table into your workbook transmits nothing at all. Asking the Add-in to GENERATE a chart against that sample table is an ordinary generation and is treated as one. Excel supplies dates and times as serial numbers; the Add-in interprets them on your machine, and a mis-typed column is a shape question, not a data transfer.

f. Rendering, persistence, and workbooks you share. Generated chart code is persisted into the workbook, so reopening it costs no call to us and no credits, and the chart draws when our backend is unreachable. Rendering is not gated on a live link: someone who receives your workbook can see the chart without an Account of their own. Where we can confirm that a chart is being shown against the data it was licensed for, we do so from a token stored with the chart together with a one-way fingerprint of your column names and types held on our servers — we do not store your data to do this, and the fingerprint is not reversible into your column values. Where we cannot confirm it — the ordinary cause is a renamed or retyped column — the chart still draws and may carry a notice or watermark saying it could not be verified. A failure to verify is not an accusation and is never, by itself, a refusal to draw.

g. D3 only, permanently. The Add-in generates and executes D3 (JavaScript / SVG) code only. The Python (Pyodide), Plotly, and Vega runtimes available to the Visual are not available in the Office sandbox, and this is a standing property of the host rather than a temporary limitation. Chart types that exist only in those lanes are therefore not offered in Excel, the set of chart types available in Excel is narrower than in Power BI, and that set may change at any time under Section 7(c).

h. Visual features the Add-in does not have. Freemium (Section 2(c)), version history and the unlock / clone / pin charges (Section 6(d)), the freemium-to-licensed conversion adjustment (Section 6(e)), and cross-filtering are features of the Visual. Where a provision of these terms describes one of them, it does not apply to the Add-in, and no charge described there is levied for Add-in use. Nothing in this paragraph is a commitment to add any of these features to the Add-in, or to keep any feature the Add-in has today.

3. DATA SENT TO LLM PROVIDERS

For each generation request, the Product transmits the following to our backend, and our backend (or your BYO provider, in BYO mode) transmits to the chosen LLM:

• Dataset shape metadata. Column names as they appear in your Power BI model or in your Excel worksheet's header row, column data types, whether each column is a measure or dimension, the column's number/date format string, and aggregate statistics (counts, min, max, mean, median, standard deviation, quantiles, top category counts, and similar shape descriptors).
• Category values. Your actual text category values are obfuscated before transmission, apart from limited exceptions required so generated code can reference and order the chart's categories correctly. Where any value is transmitted, we do NOT promise it is protected against a determined reverse-engineering attempt; do not place secrets in category values.
• Sample dataset rows (the Power BI visual only; higher privacy levels, paid licenses only). When you raise the privacy level to include a data sample, a small sample of rows is transmitted with non-numeric values obfuscated; numeric values pass through. We do NOT promise this obfuscation is irreversible; do not rely on it to protect secrets. Sample rows are NOT transmitted on freemium requests, and are not transmitted at all unless you opt in via the privacy setting. The Excel add-in does not transmit sample rows under any setting — it has no such option, and it sends no raw cell values from your worksheet (Section 2A(e)).
• Viewport, settings, and request hints. Chart width and height in pixels; chart preferences (chart type hint, "favor traditional / non-traditional" preference, legend placement preference, derived-measure preference, "use similar / use different from last" preferences, font family choice); locale; the background and foreground colors of the surface the chart is drawn on; and other generation-control hints derived from the Product's settings pane. The Add-in exposes a deliberately smaller set of settings than the Visual.
• Your commentary / user text (paid licenses only). Any free-text commentary, per-field descriptions, or "describe any changes you want to make" text you have entered into the Product's settings panel, including the Add-in's "what would you like to see?" box. This text is stripped server-side on freemium requests and has no effect on freemium generation.
• Diagnostic context for retries. When a request retries (for example after a code-quality rejection or a runtime exception), the previous attempt's error and a sketch of the violating code line may be sent on the retry prompt for the LLM to reason about its prior mistake.

We do NOT transmit the full unaggregated contents of your dataset to the LLM. We do NOT transmit your Account credentials, license key, or payment information to the LLM.

In hosted mode (Azure AI Foundry routing or our direct routing to a provider's native API), the underlying provider's terms govern how the transmitted content is handled. Such content is NOT used by us or by the underlying provider for model training. Prompts may be temporarily stored and reviewed by the underlying provider if flagged for abuse, in accordance with that provider's published terms.

In BYO mode, all content described above flows to your chosen provider under your contract with that provider, not ours. Data handling, retention, abuse-review policies, and training-eligibility in BYO mode are governed by your provider's terms.

4. DATA WE LOG ON OUR SERVERS

For every request to our backend (hosted mode and BYO mode alike, freemium and paid alike), we log on our own servers:

• Request metadata: timestamp, IP address, license key (if any), freemium identifier (if any), chosen model, request tokens, response tokens, credit cost, and a server-side correlation ID.
• The full constructed prompt as sent to the LLM, and the full response received from the LLM, including any quality-pass output.
• The LLM-generated code and a thumbnail (if available) of the rendered chart, when your Visual or Add-in reports the post-render outcome.
• Excel add-in: when an example chart (Section 2A(b)) is served, we log the request and which example was served, so that we can measure whether the lane is used and which examples work. No LLM call is made and no credits are consumed, and the request carries no license.
• Freemium only (the Power BI visual): a thumbnail of the rendered chart is captured and uploaded on the first generation for a freemium visual, regardless of the "Save thumbnails" setting. Re-renders of that same chart (resizing, re-opening the report, cross-filtering) do not upload again. We do this because a freemium generation is the one case where we have no other way to see whether the chart we produced was actually usable, and it is the main signal we use to improve output quality. These thumbnails are held as internal diagnostic records, are not attached to a chart history, and are not shown to other users. If you would prefer to control this, a licensed visual honours the "Save thumbnails" setting in both directions — turn it off and no thumbnail is captured or uploaded.
• Runtime outcome from your client (success, exception type, stack trace), reported back to us when the Product finishes rendering or fails. Used for diagnosis and quality measurement.
• Internal generation-pipeline telemetry and quality signals used to monitor and improve output quality.
• For BYO mode, we do NOT log the response payload returned from your provider beyond the metadata necessary for billing reconciliation and abuse detection.

We use these logs for diagnosis, billing reconciliation, abuse detection, and service improvement (including improving prompts, code-quality rules, and pipeline heuristics). We do not use these logs for training third-party models, and we do not sell them. We may share aggregated, non-identifying usage statistics in marketing materials or roadmap discussions.

5. CODE GENERATED BY THE VISUAL

a. Output is LLM-generated and may be wrong. Generated code (Python, JavaScript, JSON / Vega specifications, or HTML) and accompanying text are produced by large language models and may be inaccurate, incomplete, biased, off-by-one, hallucinated, or contain code that fails to execute or produces a misleading visualization. We make no representations or warranties as to the correctness, safety, or reliability of LLM-generated output. You agree to independently validate the resulting chart and any supporting analysis before relying on it for any business decision. This continues to apply even though we operate a multi-stage quality-check pipeline (validator pre-pass, code-quality regex checks, deterministic code patches, optional proofread pass, post-render visual stats): these stages reduce but do not eliminate the risk of incorrect or misleading output.

b. Code executes in your browser, not on our servers. The generated code is executed inside your Power BI session in your browser, or inside the Office add-in sandbox that Excel provides, via sandboxed runtimes (e.g., pyodide for Python, an inline Function constructor for JavaScript, or direct DOM rendering for HTML / SVG). In the Add-in the runtime is D3 / JavaScript only (Section 2A(g)). We do not execute LLM-generated code against your dataset on our servers. Risks introduced by the generated code at execution time (memory consumption, slowdowns, side effects within the chart's sandbox) are borne by your local environment.

c. Cached code is persisted in your saved report or workbook. When a generation succeeds, the resulting chart code, plus a small amount of associated metadata, is persisted into the Power BI report file (".pbix" / ".pbip"), or into the Excel workbook, so that the Product can re-render the same chart without making another LLM call. The bullets below describe the Visual; for the Excel add-in, Section 2A(d) and 2A(f) state the equivalents — in particular that Excel rendering is not license-gated, and that a linked workbook you share may carry a live link until it expires or you sign out. On pinning, the two hosts now differ in one direction only: the Add-in cannot pin a chart version — pinning is done on the chart's history page on our site — but where a version HAS been pinned, the Add-in honors that pin. A workbook showing a pinned version renders it, and will neither switch to a different version nor generate a new one until the chart is unpinned (or cloned) on the site. Note that pinning in Excel is a version LOCK only: it carries none of the credential-stripping meaning described for the Visual in this Section, because an Add-in workbook holds no license key to strip. This persistence:

• does not depend on the report being open in Power BI Desktop — the cached code re-renders in any environment that loads the saved report, subject to license-status checks the Visual performs at render time;
• is integrity-checked. If the cached code in a saved report is edited outside the Visual, the Visual will refuse to render the modified code and will direct the user to the bizintelligencechampions.com "Unlock Version" feature to make supported edits. This integrity check is provided on a best-effort basis and should not be relied upon as a security control;
• may, for licenses that have expired or accounts that have changed, be gated by status checks the Visual performs at render time. Cached code from a freemium generation is not license-gated, but freemium and trial rendering still requires our backend to be reachable; cached code from a paid generation may require a valid license or an explicit unlock to continue rendering.
• Air-gapped / offline rendering. When our backend is temporarily unreachable, an explicitly UNLOCKED paid version is treated as self-contained and continues to render from its cached code — "air-gapped" use. All other cases — locked paid versions, trial versions, and freemium — require our backend to be reachable to confirm status before rendering; while it is unreachable, they show a "couldn't reach the licensing service" notice rather than rendering.
• Credential persistence and pinning. Except where a version has been pinned, a saved report may retain the credentials the Visual used to authenticate the generation — which can include your organizational license key and the associated account secret — so that the report can continue to render and generate. Pinning a version strips these credentials from the report file and locks the report to that specific cached version, producing a file that renders from its cached code without carrying your license key or secret. You are responsible for pinning any version before you distribute, share, or publish a report outside your organization; a report that has not been pinned may expose your credentials to anyone who obtains the file.

d. Code ownership. Subject to your compliance with these terms and the general Terms, you may use the generated code within your Power BI report or your Excel workbook for the purposes the Product is designed for. You may not extract the generated code to use independently of the Products, redistribute it as part of a competing product, or use it to train another model. The example charts described in Section 2A(b) are OUR code, licensed to you only for display through the Add-in, and this restriction applies to them in full.

e. Who you share a report or workbook with is your decision, and your responsibility. Nothing in either Product limits who you may distribute, share, publish, or embed a report or workbook to, and we have no visibility into who receives one. The validation duty in Section 5(a) applies before you share a chart, not only before you act on it yourself: a recipient sees a finished chart, ordinarily without knowing which parts of it a language model produced, and is not in a position to perform that validation for themselves. This applies with particular force to a workbook, which is ordinarily emailed and forwarded rather than published to a governed workspace, and which a recipient can open and read without any Account of their own (Section 2A(f)). Accordingly, you are responsible for deciding whether a generated chart is fit to be seen by the audience you send it to, for the statements that chart makes to that audience, and for the composition of that audience — including where the file is made available to people outside your organization or to the public. This provision concerns the CORRECTNESS and suitability of what a chart shows; Sections 5(c) and 2A(d) separately concern the CREDENTIALS a saved file may carry, and pinning and signing out address only the latter.

6. COST AND CREDITS

a. Credit consumption. Each successful generation consumes usage credits (paid) or freemium budget. For HOSTED requests, credit cost is computed from the chosen model's per-token rates and the actual input and output token counts (this token-based pricing replaced an earlier fixed-per-request model), plus any retry or quality-pass token consumption — so cost varies by model and request size. Credit cost is therefore NOT fixed or fully predictable per request: the model's response length, the number of retries, and whether quality passes engage are all determined during generation itself, so two similar — even identical — requests may consume different amounts of credits. Some cost drivers are within your control (which model you choose, how many fields you supply, how much commentary you enter); others are not. Treat published per-model rates as indicative of typical cost, not a fixed per-request price. For BYO requests, your provider bills you for the tokens directly and we instead charge a small FLAT per-request operating fee in credits. We publish current per-model rates on the Buy page and we may change those rates, the BYO per-request fee, or the credit-cost formula itself at any time without notice. Such changes apply to requests issued after the change takes effect; they do not retroactively adjust your credit balance or prior charges.

b. Retries and quality-check loops can consume more credits than expected. Our generation pipeline may issue additional LLM calls during automated quality-assurance and correction steps. Each of those calls consumes credits. We make commercially reasonable effort to cap runaway retry loops but do not guarantee any specific upper bound on credits per request.

c. Refunds. Consistent with the general Terms, we do not offer refunds for usage credits consumed by successful or failed generation requests. The freemium tier allows for evaluation of the Visual and its quality before any paid purchase; for the Add-in, which has no freemium tier, the example-chart lane (Section 2A(b)) and the free chart-type list serve that purpose, and an Account carries a trial license automatically.

d. Version unlock / clone / pin pricing (the Power BI visual). Creating a new editable version from your saved chart history is charged per new version, to your Account credit balance: unlocking a locked original costs 20 credits, while cloning an already-editable version costs 20 credits. Each new editable version is charged independently. Pinning a version for distribution costs 4,000 credits — pinning permanently removes the license requirement from deployed copies of that version (they render without any license, forever), which is why it is priced separately from, and higher than, unlocking. These charges are separate from the per-generation credit cost described in 6(a), and apply only when you create a new editable version (or pin one) through the bizintelligencechampions.com history page. The amounts are configuration-driven and may change at any time without notice. (Re-syncing an edit you make to a version you already unlocked is free.) These charges do not arise from use of the Add-in, which keeps no version history and offers no unlock, clone, or pin (Section 2A(h)).

e. Freemium-to-licensed conversion (the Power BI visual). When a visual that was used in freemium mode is first upgraded to a licensed Account, the free freemium allowance is honored, but any freemium usage beyond that allowance is charged to your Account's credit balance as a one-time adjustment at the time of upgrade. This recovers our cloud cost for freemium generations that exceeded the free base before the visual was licensed. The allowance and the amount charged are configuration-driven and may change at any time without notice.

7. AVAILABILITY, RATE LIMITING, AND CHANGES

a. No service-level agreement. The Products depend on third-party LLM providers, third-party cloud infrastructure, our own backend, and the host application each runs inside — Microsoft Power BI or Microsoft Excel and the Office add-in platform, neither of which we control. We offer no service-level agreement, uptime guarantee, latency guarantee, or response-quality guarantee. Service may be slow, partially degraded, or unavailable at any time without notice, and a change Microsoft makes to a host application may affect or disable a Product without any change on our side.

b. Rate limiting and throttling. We may throttle, queue, delay, or refuse requests at any time, from any IP address, account, or freemium identifier, for any reason (including but not limited to capacity management, abuse mitigation, or cost control). Decisions are at our sole discretion.

c. Configuration changes. We operate a database-driven configuration for many aspects of the Products' behavior, including (but not limited to): which models are available, model pricing, model selection defaults, freemium spending caps, freemium model selection, prompt content and structure, code-quality rules, deterministic code patches, validator behavior, proofread thresholds, viewport-aware directives, chart-catalog membership, runtime-weight biasing, which chart types a given host can render, the contents of the Add-in's example-chart catalog, and whether the example-chart lane is offered at all. We may change any of these at any time without notice, and changes take effect on the next request. Your continued use of a Product after such changes constitutes acceptance.

d. Backward compatibility. A given saved Power BI report's, or Excel workbook's, cached chart will continue to render via its cached code as long as the data shape it expects remains compatible. We do not guarantee that REGENERATING that chart at a later date will produce the same code, the same chart type, the same derived measures, or the same visual appearance.

8. PROHIBITED USES SPECIFIC TO THE PRODUCTS

In addition to the prohibited uses in Section 2 of the general Terms, you may not:

• Use a Product with data subject to the Health Insurance Portability and Accountability Act (HIPAA), Payment Card Industry Data Security Standard (PCI DSS), the GDPR special categories of personal data (Article 9), or any other regulatory framework that prohibits transmission of the relevant data to third-party LLM providers. Note that this turns on what the Product TRANSMITS (Section 3), and that the Add-in transmits the shape of your worksheet — including your column headers — even though it does not transmit your cell values.
• Use a Product with classified, export-controlled, or otherwise legally restricted data.
• Attempt to extract, infer, or reverse engineer the system prompt, validator prompt, proofread prompt, code-quality rules, or model selection logic for the purpose of building a competing service.
• Automate the freemium tier (e.g., scripted instance creation, freemium key cycling) to obtain free LLM access at scale.
• Automate, script, or otherwise call the Add-in's example-chart lane other than through the Add-in in ordinary use, or extract its catalog of example charts.
• Share, transfer, or publish an account-link token held in a workbook, or use one obtained from a workbook that is not yours, in order to generate charts against an Account you do not hold.
• Use a Product to generate code that targets, scrapes, attacks, or otherwise interacts with systems outside the render context the Product provides in its host application.
• Use a Product to produce content that violates applicable law or third-party rights.
• Share, transfer, or expose your BYO API key in a way that allows other users to make LLM calls on your provider account.

9. SUSPENSION AND TERMINATION

We may suspend or terminate your access to either Product at any time, including (without limitation) for breach of these terms, suspected abuse of the freemium tier or of the example-chart lane, automation in violation of Section 8, excessive cost generation, or risk to our service. We may also revoke an account-link token held in a workbook, and we may disable a specific saved report's or workbook's cached code from re-rendering, when we have a reasonable basis to suspect tampering, sharing, or other prohibited use.

10. DISCLAIMERS, LIABILITY, AND INDEMNITY

All disclaimers of warranties, limitations of liability, and indemnity obligations in Sections 6, 7, 8, and 10 of the general Terms apply to your use of the Products without modification. For clarity, and without limiting the general Terms:

• We are not liable for any business decision made in reliance on a chart, statistic, or analytical claim produced by either Product, including an example chart served under Section 2A(b).
• We are not liable for any cost incurred with a BYO provider arising from your use of a Product, including cost from runaway retries, oversized prompts, or unexpected pricing changes by your provider.
• We are not liable for the actions of any third-party LLM provider, including but not limited to outages, billing errors, data-handling decisions, abuse-review decisions, or content-policy enforcement.
• We are not liable for the acts, omissions, availability, or platform decisions of Microsoft in respect of Power BI, Excel, Microsoft 365, AppSource, or the Office add-in platform.
• We are not liable for any data a Product transmits in accordance with Section 3, including data transmitted to a BYO provider, where you have configured the Product to do so.
• We are not liable, to you or to any person who receives a report or workbook from you, for the distribution of a file containing generated content, or for any reliance placed on such a file by a recipient. Whether a generated chart was validated before it left your hands, and who it was sent to, are your decisions alone (Sections 5(a) and 5(e)).
• We are not liable for any credit consumption, generation activity, account access, or other loss arising from your distribution, sharing, or publication of ANY report file, whether pinned or not. Pinning is provided as the mechanism to remove your license key and account secret from a report before it leaves your control; a report that has not been pinned may contain those credentials, and their exposure and any resulting use is your responsibility. Pinning a report limits what it carries — it does not transfer any part of that responsibility to us.
• We are not liable for any credit consumption, generation activity, account access, or other loss arising from your distribution, sharing, or publication of ANY workbook. A workbook may carry a live account-link token until it expires or you sign out; signing out before you share is the mechanism provided, and using it is your responsibility (Section 2A(d)). We do not undertake to detect, warn about, or reverse use made of a workbook you have distributed.

11. REVISIONS TO THESE TERMS

We may revise these LLM AI Charts Terms at any time by posting an updated version at https://bizintelligencechampions.com/terms-llmchart-excel, and at the companion address for the other Product (Section 1(c)); the two are revised together and never diverge. Revisions are effective when posted. Where the change is material, we will use commercially reasonable effort to notify Accounts via the email on file. Your continued use of a Product after revisions take effect constitutes acceptance. In the Add-in, you are additionally asked to accept the then-current version of this page in the task pane before anything measured from your worksheet is sent, and again each time you link a workbook to your Account (Section 2A(c)); because a link is time-limited, that acceptance recurs, and it is the version posted here at the moment of linking that you accept.

12. CONFLICT WITH GENERAL TERMS

To the extent there is a conflict between these LLM AI Charts Terms and the general Terms of Use, these LLM AI Charts Terms control with respect to your use of the Products. All other provisions of the general Terms continue to apply. To the extent there is a conflict between Section 2A and any other section of these terms, Section 2A controls with respect to the Excel add-in, and the other section continues to govern the Power BI visual.

13. OPEN-SOURCE LIBRARY ATTRIBUTION

Open-source library attribution for the Visual (D3.js, Plotly.js, Vega / Vega-Lite, Pyodide and its Python scientific stack, and various browser-side utility libraries) is consolidated with the attribution for our other visuals in Section 14 of the general Terms of Use. The Add-in draws on the D3.js entries of that same list and on browser-side utility libraries; it does not carry Plotly.js, Vega, or Pyodide (Section 2A(g)). Each listed library is distributed under a permissive open-source license (MIT, BSD-2-Clause, BSD-3-Clause, Apache License 2.0, ISC, Mozilla Public License 2.0, or Zlib) that permits commercial use.