GrafanaSight Data Handling Disclosure
Stored Data
Section titled “Stored Data”GrafanaSight stores space-scoped configuration, Grafana service account token secret references, dashboard catalog snapshots, dashboard detail metadata, active alert summaries, annotation summaries, rendered panel snapshot metadata, sync status, and operational timestamps.
GrafanaSight does not store customer Grafana data on Flowdence-managed remote infrastructure. App data is stored in Atlassian Forge storage. Customer Grafana source data remains in the customer-configured Grafana Cloud tenant.
Secret Storage
Section titled “Secret Storage”Grafana service account tokens are stored with Forge secret storage. Tokens are not returned to the frontend after save and should never be shared in support tickets.
If a token is suspected to be exposed, customers should rotate the affected Grafana service account token and contact Flowdence support with sanitized evidence.
Cached Snapshots
Section titled “Cached Snapshots”GrafanaSight uses cached snapshots to reduce upstream API usage and keep Confluence pages useful when Grafana is temporarily unavailable. Cache entries may include dashboard titles, folder names, panel titles, alert labels, annotation text, and rendered image data.
The GrafanaSight Specialist answers from cached metadata. It does not silently call live Grafana APIs for ordinary chat. Explicit refresh actions may update cached data from Grafana.
Logs may include identifiers, counts, result states, and redacted error metadata. Logs must not include Grafana service account tokens or rendered image payloads.
Flowdence support may ask for screenshots, timestamps, page URLs, or sanitized diagnostics to troubleshoot issues. Do not send Grafana service account tokens or secrets in support tickets.