Privacy policy
This is the privacy policy for the finopsway-costs extension, as published in the Chrome Web Store and on Firefox Add-ons. It describes what the released extension does.
The short version
The extension has no backend. The only network requests it makes go to the Databricks workspace you are signed in to. We run no server, receive no data and cannot see what you query.
What the extension handles
A Databricks personal access token, if you choose token mode.
It is stored with chrome.storage.local, keyed by workspace
origin. That store is readable by this extension alone, is never synced to
a browser account, and is cleared when you remove the token from the
options page or uninstall the extension. In session mode nothing is
stored: the extension reuses the workspace session you already have, and
the CSRF token it needs is fetched per request and held in memory for the
duration of that request.
Databricks billing usage records and SKU prices. The
extension runs read-only SQL queries against the
system.billing tables of your own workspace and keeps the
rows in IndexedDB, in the workspace origin's own storage. This is a cache:
it holds the history you configure on the options page
(Days to keep, 30 days by default, at most a year), is
pruned to that retention on every sync, and can be dropped at any time
from the options page. Alongside the rows it keeps only its own
bookkeeping: which day was last fetched, when, and how many rows landed.
It contains only records the signed-in identity is already entitled to
read.
Compute machine hours, if you use the cloud cost view.
To estimate what the machines under your clusters cost, the extension
also reads system.compute.node_timeline - again read-only,
again from your own workspace. It selects only the cluster id, the
machine type, whether the node was a driver, the hour, and counts of
minutes and instances. It does not read that table's
utilisation, network or IP address columns. The result is aggregated to
one row per cluster, machine type and hour before it is stored, and is
replaced wholesale on each refresh rather than accumulated.
Which cloud and region your workspace runs in. The
extension runs SELECT current_metastore(), which returns a
string such as aws:us-east-2:<id>. The cloud and the
region select which machine price list to use; the metastore identifier
in that string is stored alongside them but is not read by any feature,
is never written to the console, and like everything else here never
leaves your browser.
Extension settings. Your warehouse choice, catalog,
retention and display preferences, in chrome.storage.local.
Where data goes
Every network request the extension makes is to the Databricks workspace
host you are visiting, matching *.cloud.databricks.com or
*.azuredatabricks.net. There are no other hosts, and the
extension declares no permission that would allow any. Your token is sent
to that workspace and nowhere else. Credentials are keyed by workspace
origin, so a token for one workspace is not reachable from another.
The cloud cost view contacts no cloud provider. AWS and Azure machine list prices are downloaded by us in advance, from those providers' public price lists, and ship inside the extension package as static files. Estimating what a cluster costs is a lookup in a file already on your disk. Nothing about your clusters, your account or your region is sent to Amazon, Microsoft or anyone else, and the extension has no permission that would let it.
What we do not do
- We do not collect, receive, store or transmit any of your data. There is no server to send it to.
- We do not sell or transfer your data to third parties.
- We do not use your data for anything unrelated to the extension's single purpose, which is displaying your Databricks spend.
- We do not use your data to determine creditworthiness or for lending.
- There is no analytics, telemetry, crash reporting or advertising of any kind.
-
The extension writes nothing to Databricks. Its SQL only reads
system.billingandsystem.compute, and only ever withSELECT. - It does not read the content of your work. No notebook, query text, table, result or file is read at any point. The tables it queries describe cost and compute usage, not your data.
Logging
Released builds do not write diagnostic traces to the page console. Even in a development build with tracing enabled, the access token and the CSRF token are never logged; the trace names the authentication mode only, and automated tests enforce that.
Removing your data
Uninstalling the extension removes the stored token and settings. The cached billing rows, machine hours and the cloud/region record live in the workspace origin's IndexedDB and are removed together by the Clear cached usage action on the options page, or by clearing site data for the workspace in your browser.
A note on token scope
A Databricks personal access token has the same permissions as your
user account. It cannot be limited to system.billing alone.
The extension only uses it for read-only billing queries, but you should
treat it like any other workspace credential: prefer a short-lived
token and revoke it in Databricks when you no longer need it. Session
mode does not store a credential at all.
Trademarks
finopsway-costs is an independent extension built by FinOpsWay. It is not affiliated with, endorsed or sponsored by Databricks, Inc.
Databricks is a trademark of Databricks, Inc. Google Chrome and the Chrome Web Store are trademarks of Google LLC. Firefox and addons.mozilla.org are trademarks of the Mozilla Foundation. Microsoft Edge and Azure are trademarks of Microsoft Corporation. AWS is a trademark of Amazon.com, Inc. or its affiliates. These names are used only to describe what the extension works with. All trademarks remain the property of their respective owners.
Contact
Questions about this policy: mail@finopsway.com.