Supplemental Terms for RegiaBI Apps, Maps and Charts for Google Sheets

Supplemental Terms for "RegiaBI Apps, Maps and Charts for Google Sheets", the Google Sheets Add-on

Revised: November 19, 2026


These supplemental terms ("RegiaBI Apps, Maps and Charts Terms", formerly the "LLM AI Charts and Maps Terms") apply to your use of "RegiaBI Apps, Maps and Charts for Google Sheets", our Google Workspace add-on for Google Sheets ("the Add-on", or "the Product"), 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 Product. These terms are separate from the "RegiaBI Terms" at https://bizintelligencechampions.com/terms-regiabi, which govern calling the RegiaBI engine from your own software.


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


1. SCOPE


a. These terms cover RegiaBI Apps, Maps and Charts for Google Sheets specifically. They cover: how the Product behaves inside Google Sheets; the server-side request handling, model selection, code generation, and quality-check pipeline; the example-chart lane (Section 2(c)); usage credits and licensing; and persistence of any cached generated code in your saved Google Sheets spreadsheet. 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. Our other products. RegiaBI Apps, Maps and Charts is also offered for Power BI (bizintelligencechampions.com/terms-llmchart) and for Excel (bizintelligencechampions.com/terms-llmchart-excel), each with terms of its own written the same way for it. The provisions these products share say the same thing on every one of those pages, and one Account, one license and its usage credits cover all of them.


2. SERVICE MODES — HOSTED, BYO, LICENSED ONLY


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, 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. Licensed only — and the example-chart lane. The Add-on is licensed-only. Generating a chart from YOUR data requires an active license, reached by linking to your Account; a new Account receives a trial license once its email address is confirmed. There is no freemium tier and no freemium identifier is minted (the Add-on does carry a per-installation identifier, described in Section 4). Separately, and without any Account, the Add-on 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-on, 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).


d. Licensed (paid) tier. Use of the 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. What the Add-on is. The Add-on is a Google Workspace editor add-on for Google Sheets. Its Google Apps Script part adds a menu to the spreadsheet and opens a window over it; the window shows our page, served from bizintelligencechampions.com, which measures the range you select, asks our backend for chart code written for that shape, and draws the chart in that window. It asks Google for two permissions only: to see and change the one spreadsheet it is open in, and to show its window there. Google Sheets, Google Workspace, Google Apps Script and the Google Workspace Marketplace are Google's, not ours — we do not control them, we cannot guarantee that any browser, account type, or Workspace configuration will run the Add-on, and nothing in these terms alters your agreement with Google.


f. How you accept these terms in Google Sheets. You are asked in the Add-on itself, and the question comes before any Account exists. You must accept these terms before the Add-on sends anything measured from your spreadsheet 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 — and before the Add-on will link to your Account. That acceptance is held for as long as the Add-on's window is open and is not written to your machine or into your spreadsheet, so the Add-on's window opened later asks again unless a live link exists. A link is time-limited, so acceptance recurs on its own schedule, and the version of these terms in force at the moment you accept is the version you accept — which is how a revision under Section 11 reaches you. Because linking is the only way to license the Add-on, and the Add-on will not start a link until you have accepted, a live link has necessarily accepted the version current at the moment it was made, and the Add-on does not ask again while that link is live. Generation is blocked until you accept. Your acceptance is deliberately NOT written into the spreadsheet: a spreadsheet travels to other people, and one person's acknowledgement must never be carried to the next person who opens it.


g. Linking, and where the link is kept. A spreadsheet holds no account-link token, and no license key or Account secret. Linking through our sign-in page is the only way to link, and the Add-on has no field in which to type a license key. The token is kept for you by Google, in storage private to your Google account and that spreadsheet; it lasts 30 days, and signing out in the Add-on removes it. Sharing the spreadsheet therefore does NOT let the people you share it with generate charts against your Account. Anyone who can use your Google account in that spreadsheet can use the link while it lasts; keeping your Google account to yourself is your responsibility.


h. What leaves your spreadsheet. For a generation request, the Add-on transmits the MEASURED SHAPE of the range you select 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 spreadsheet, and it does not transmit sample rows: it has no option to. 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 where the range is YOUR data it does require your acceptance of these terms before it will run — it transmits the measured shape of your columns, and we ask before we send it, not after. Two paths need no acceptance, because neither transmits anything measured from your data: the example-chart lane in Section 2(c), whose request carries the size of the pane and the shape of OUR sample table so that we can choose an example that fits, and the chart-type list run over that same sample table, whose column names are ours and already published. Writing the sample table into your spreadsheet transmits nothing at all. Asking the Add-on to GENERATE a chart against that sample table is an ordinary generation and is treated as one. The "See what's sent" control in the Add-on shows the exact request before you send it.


i. Rendering, persistence, and spreadsheets you share. Generated chart code and the settings that produced it are saved in the spreadsheet, in hidden sheets the Add-on creates for the purpose, so reopening the chart costs no call to us and no credits. The Add-on also writes, only when you ask, the sample table, a picture of a chart placed beside your data, and a sheet a table's Export makes. A spreadsheet you share carries the saved code; a person you share it with sees the chart by opening the Add-on themselves, and rendering is never refused: they can see the chart without an Account of their own. Viewing an unwatermarked chart does, however, require an active license. Each time a chart is displayed we ask what license stands behind it, and there are three answers:

  • A pinned version is licensed unconditionally and is never watermarked. Pinning is paid for separately so that the file can stand alone; the state of the Account that made it is not consulted, then or later.
  • Otherwise the license behind the chart is the one that generated it — resolved from the token stored with the chart, or from your own link. If that Account's license is active, no watermark is shown. If it has lapsed, expired, or was never held, the chart still draws and carries a watermark saying so. A spreadsheet carries no credential at all, so unless the chart is pinned or its token still resolves, a recipient sees the watermarked state.
  • Where we cannot tell — the ordinary cause is a renamed or retyped column, or our service being unreachable — the chart draws and carries a softer notice saying the license could not be checked. A failure to verify is not an accusation.

The token we use for this is 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. No watermark state is ever, by itself, a refusal to draw, and none of them consumes credits.


j. D3 only, permanently. The Add-on generates and executes D3 (JavaScript / SVG) code only. The Python (Pyodide), Plotly, and Vega runtimes available to our Power BI visual are not available in the Add-on, 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 Google Sheets, the set of chart types available is narrower than in Power BI, and that set may change at any time under Section 7(c).


k. Features of our Power BI visual that the Add-on does not have. A freemium tier, version history and the unlock / clone / pin charges, the freemium-to-licensed conversion adjustment, and cross-filtering are features of our Power BI visual, governed by its terms. No charge for them is levied for the Add-on use. Nothing in this paragraph is a commitment to add any of these features to the Add-on, or to keep any feature the Add-on has today.


l. Google user data, and what you agree to. The Add-on's use of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements; we do not sell that information, do not use it for advertising, and do not use it to train AI models. By accepting these terms you agree that: (1) our staff may read the request and diagnostic logs described in Section 4 — which contain the column names and summary statistics of the range you used, never its cell values — to diagnose a problem with the Product or with your Account; and (2) while we investigate a problem with your Account, we may capture a picture of each newly generated chart, which may show values the chart shows, and keep it with those logs rather than in your chart history. What is collected and why is set out in the privacy policy at bizintelligencechampions.com/privacy/llmchart-sheets.


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 the header row of the range you select, 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.
  • No sample rows. The Add-on does not transmit sample rows under any setting — it has no such option, and it sends no raw cell values from your spreadsheet (Section 2(h)).
  • 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.
  • Your commentary / user text. Any text you type into the "what would you like to see?" box, or to describe a change you want made.
  • 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), we log on our own servers:

  • Request metadata: timestamp, IP address, the Account the link resolves to (if any), chosen model, request tokens, response tokens, credit cost, and a server-side correlation ID.
  • A client identifier. The Add-on sends a random identifier that it mints once per browser and keeps in the storage the browser gives our page; where that storage is not kept, it derives the identifier instead from general characteristics of the browser (not its name or version). It is not a credential and carries no name. We use it to tell installations apart in usage reporting, to vary chart choices between one installation's generations, and as one half of the key our unpaid rate limits are counted against (Section 7(b)).
  • 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 the Product reports the post-render outcome.
  • Thumbnails. A thumbnail of a new chart is captured and uploaded only when "Save chart thumbnails" is on (in the Add-on or in your Account; off by default), or while we investigate a problem with your Account; a capture made that way is held as a diagnostic record and is not added to your chart history. When "AI reviews each new chart" is on (off by default), a picture of each new chart is sent to the LLM to check how it rendered.
  • When an example chart (Section 2(c)) 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.
  • 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.
  • BYO mode is logged in the same way. The prompt our backend constructs and the response your provider returns pass through our servers and are logged exactly as in hosted mode. What BYO changes is which provider processes them and under whose contract (Section 2(b)), not what we retain.

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. Verbose diagnostic logs are purged after a limited period set by our configuration; other request logs are retained for as long as they serve the purposes above, and we may purge them on a schedule we set. Who may read these logs, and the agreement you give to it, are in Section 2(l).


5. CODE GENERATED BY THE PRODUCT


a. Output is LLM-generated and may be wrong. Generated code (JavaScript / SVG) 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 the Add-on's window in your browser, as D3 / JavaScript only (Section 2(j)). 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 spreadsheet. When a generation succeeds, the resulting chart code, plus a small amount of associated metadata, is persisted into the spreadsheet, so that the Add-on can re-render the same chart without making another LLM call. Rendering is never REFUSED for want of a license or of a reachable backend: a chart whose license cannot be confirmed draws with a watermark instead (Section 2(i)). The Add-on 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-on honors that pin: a spreadsheet 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. Pinning here is a version LOCK only, because a spreadsheet holds no license key to strip.


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


e. Who you share a spreadsheet with is your decision, and your responsibility. Nothing in the Product limits who you may distribute, share, publish, or embed a spreadsheet 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. 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 spreadsheet is made available to people outside your organization or to the public. This provision concerns the CORRECTNESS and suitability of what a chart shows; Section 2(g) separately concerns your account link, which a spreadsheet does not carry.


6. COST AND CREDITS


a. Credit consumption. Each successful generation consumes usage credits. 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. The indicative credit range for each hosted model is shown in the Product's own usage panel, and the pricing mechanics are described on the credits page; 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. Every generation a request performs is charged, including an attempt you discard by retrying before it finishes. A generation that fails before it delivers a chart is not charged, and where our records show that a chart was charged but could not reach you at all, we may credit the charge back automatically. Beyond that, and consistent with the general Terms, we do not refund usage credits consumed by generation requests. The example-chart lane (Section 2(c)) and the free chart-type list allow for evaluation of the Add-on before any paid purchase, and a new Account receives a trial license once its email address is confirmed.


d. No version charges. Version unlock, clone, and pin charges arise only on the chart's history page on our site, as our Power BI visual's terms describe; the Add-on keeps no version history and offers no unlock, clone, or pin (Section 2(k)).


7. AVAILABILITY, RATE LIMITING, AND CHANGES


a. No service-level agreement. The Product depends on third-party LLM providers, third-party cloud infrastructure, our own backend, and the host application it runs inside — Google Sheets and Google Apps Script, which we do not 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 Google makes to the host application may affect or disable the 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 client identifier, for any reason (including but not limited to capacity management, abuse mitigation, or cost control). Decisions are at our sole discretion. Unpaid traffic — trial generations and the example-chart lane — is additionally counted against shared service breakers: when too many distinct unpaid originators generate within a short window, or unpaid volume as a whole exceeds a ceiling, unpaid requests are refused until the window passes, and the refusal says how long to wait. Paid generations and cached-version fetches never touch those breakers.


c. Configuration changes. We operate a database-driven configuration for many aspects of the Product's behavior, including (but not limited to): which models are available, model pricing, model selection defaults, 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 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 the Product after such changes constitutes acceptance.


d. Backward compatibility. A given saved spreadsheet'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 PRODUCT


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

  • Use the 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-on transmits the shape of your range — including your column headers — even though it does not transmit your cell values.
  • Use the 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, script, or otherwise call the example-chart lane other than through the Add-on in ordinary use, or extract its catalog of example charts.
  • Use the 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 the 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 the Product at any time, including (without limitation) for breach of these terms, suspected abuse 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, and we may disable a specific saved spreadsheet'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 Product 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 the Product, including an example chart served under Section 2(c).
  • We are not liable for any cost incurred with a BYO provider arising from your use of the 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 Google in respect of Google Sheets, Google Workspace, Google Apps Script, or the Google Workspace Marketplace.
  • We are not liable for any data the 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 spreadsheet 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 use of your Google account by anyone else while your account link lasts (Section 2(g)).

11. REVISIONS TO THESE TERMS


We may revise these RegiaBI Apps, Maps and Charts Terms at any time by posting an updated version at https://bizintelligencechampions.com/terms-llmchart-sheets. 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 the Product after revisions take effect constitutes acceptance. You are additionally asked to accept the then-current version of this page in the Add-on before anything measured from your spreadsheet is sent and before it links to your Account (Section 2(f)); because that acceptance lasts only while the Add-on's window is open and a link is time-limited, it recurs, and it is the version posted here at the moment you accept that you accept.


12. CONFLICT WITH GENERAL TERMS


To the extent there is a conflict between these RegiaBI Apps, Maps and Charts Terms and the general Terms of Use, these RegiaBI Apps, Maps and Charts Terms control with respect to your use of the Product. All other provisions of the general Terms continue to apply.


13. OPEN-SOURCE LIBRARY ATTRIBUTION


Open-source library attribution for the Product is consolidated with the attribution for our other products in Section 14 of the general Terms of Use. The Add-on draws on the D3.js entries of that list and on browser-side utility libraries; it does not carry Plotly.js, Vega, or Pyodide (Section 2(j)). 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.




This application may no longer respond until reloaded. Reload 🗙