Data Collection & Customer Consent

To improve product quality, forecasting accuracy, and customer support, Lakehouse Optimizer (LHO) can share anonymized and aggregated usage and operational data with Blueprint for analytics and statistics.

Because this sharing is optional and may be regulated by privacy requirements, we require customer consent before any data is sent.

What data LHO collects

1) Forecasting data with Weekly and Monthly KPIs

Used to improve forecasting accuracy and trend quality. This may include:

Aggregated cost/usage time series (e.g., daily/weekly totals)
Forecast model inputs/outputs and confidence ranges
Summary settings that affect forecasts (e.g., forecast horizon, aggregation level)

2) User activity (product telemetry)

Used to understand what features are used and where users encounter friction. This may include:

Feature interactions (clicks, API requests), and navigation flows
Basic session metadata (e.g., timestamp, tenant/environment identifiers that are anonymized)
Performance signals (e.g., load time, API response time)

3) Support emails and diagnostics in case of errors

Used to troubleshoot incidents and improve reliability. This may include:

Error messages, stack traces, request/response metadata (redacted where possible)
Relevant support email content created by LHO for troubleshooting (e.g., “send diagnostics”)
Non-sensitive configuration context needed to reproduce the issue

LHO does not need sensitive personal information in support content. Where feasible, LHO redacts or hashes identifiers before sending.

Anonymization & safeguards

Shared data is anonymized and/or aggregated wherever possible.
Access is restricted to authorized personnel for analytics and support.
Data is protected in transit and at rest using standard security controls.

Consent and user choice

Consent is opt-in.
Consent can be withdrawn at any time. Once withdrawn, LHO will stop sending new data.