Superset AI Privacy Policy

Version: 1.7.5 Effective date: October 25, 2026 Publisher: Eric S. Privacy contact: support@superset.easyais.org

1. Purpose and scope

Superset AI is an independent table-report assistant for Apache Superset, with local sorting, color scales, conditional highlights and user-initiated model analysis. This policy covers the extension. Your Superset instance, selected model provider and external sites you open have their own privacy policies.

2. Data we process

On authorized, enabled Superset sites, the extension locally reads rendered rows, cell text and available raw values, headers, dimensions, report/chart titles, available filter information and data scope. It reads the active tab URL to identify sites that can be added. Related report URLs and titles may be saved in rules and analysis history. It does not read Chrome's complete browsing-history database.

The extension processes your questions, model answers, model endpoint, model ID and API key, along with rules, templates, site settings, language preference and analysis budgets. Reports, questions and answers may contain personal or sensitive information you provide. Choose only data you are authorized to process and share with the selected service.

3. Use and transmission

Sorting, color scales, highlighting, table extraction and token-budget calculations run locally. When you start AI analysis, selected row details or statistics, your question and necessary context such as titles, headers, filters, capture time and scope are sent to your configured model endpoint. Chunked analysis may make multiple requests and send intermediate observations or summaries to the same provider. Summary mode omits raw row details but still includes statistics and context.

Connection tests send test text, the model identifier and credentials only. The API key is sent in the Authorization header to your chosen provider. Model requests omit Superset cookies and reject redirects. Remote model endpoints require HTTPS; user-selected localhost or loopback services may use HTTP. A provider may receive network connection information such as your IP address and retain or use requests and responses under its own terms. Check its retention, location and training-use policies. Cancellation cannot recall information already received by a provider.

The current extension has no developer data-collection backend, advertising SDK, telemetry or tracking service. The developer does not automatically receive reports or API keys through the extension. We do not sell user data, use it for advertising profiles or credit/lending decisions, or transfer it for unrelated purposes. We do not allow unauthorized human review of user data. We comply with the Limited Use requirements of the Chrome Web Store User Data Policy.

4. Local storage and retention

Rules, templates, site settings and model configuration, including the API key, are stored in chrome.storage.local without Chrome cloud sync. Access is restricted to trusted extension contexts. This storage is not a dedicated password vault and does not protect against a compromised device or browser.

Analysis history is saved in local IndexedDB. It includes questions, answers, report URLs/titles, selected column paths, filters, model/provider origin, timestamps, status and related metadata. Complete raw table snapshots are not stored, though answers can quote source data. Records do not have a fixed automatic expiry. Under storage pressure, older non-running records may be removed, unpinned records first and pinned records if necessary.

5. Your controls

You can choose sites, charts, columns or summary mode, disable or remove sites, revoke host permissions in Chrome, delete history/rules/templates, and replace model settings. Removing a site does not delete existing rules/history or automatically revoke browser host grants. To remove local extension data completely, clear extension storage or uninstall. Delete exported files separately. Contact your provider about information already retained by its service.

Rule/template JSON exports omit API keys, conversations and tables. History JSON or Markdown exports include questions, answers and report metadata and may contain sensitive content. You control these files; the extension does not upload them automatically. Opening a link from an answer visits the destination under that site's data practices.

6. Contact and updates

For privacy questions, contact support@superset.easyais.org. Changes will be published on this page with an updated effective date. This policy describes the current implementation; disclosures will be updated if data processing changes.