Privacy

Privacy and Data Handling

dbNexia Demo is designed for SQL Server operations teams that need monitoring, forecasting, restore-readiness, database-health checks and incident prevention without losing control of operational data. This page explains what the application stores, what it reads, why it reads it and how access is controlled.

Last updated: 2026-06-29
Data location Kept in your SQL Server environment

Operational telemetry, reports, configuration and user access data stay in the configured customer databases unless your organization exports them.

Purpose Used for operations and governance

The data supports health checks, reporting, capacity forecasts, incident triage, backup readiness, database-health recommendations, licensing and administration.

AI pages Explainable signals from collected telemetry

Forecast, Incidents, Action Center, Data Quality and Database Health use visible SQL Server evidence so DBA teams can review the source behind each recommendation.

Data flowlocal operational evidence
SQL telemetryBackups, jobs, growth, waits, database options, permissions and collector health.
dbNexia Demo storageOperational data remains in configured SQL Server databases.
Web appAuthorized users inspect dashboards, reports and admin pages.
Decision supportForecast and incident scoring stay explainable from visible evidence.

Operational Data Classes

Stored by the appUsers, roles, registered servers, protected connection metadata, license state, alert rules and application configuration.
Read from SQL ServerBackup history, job history, growth, file metadata, waits, runtime events, permissions and health signals when SQL permissions allow it.
Not requiredBusiness-table contents are not required for monitoring. Reports show operational repository data, not arbitrary customer application data.
Controlled actionsDatabase Health and administration actions require authorized roles. Reader/demo access can inspect evidence without executing protected actions.

Recommendation Scope

Recommendation text is generated only for operational signals where a DBA decision is useful: failed jobs, backup exposure, telemetry gaps, capacity risk, unhealthy database settings, security findings, blocking, deadlocks and runtime errors. Routine metrics, successful history rows and ordinary audit records are presented as evidence without unnecessary fix instructions.

What dbNexia Demo Stores

  • User accounts, roles and sign-in metadata needed for authentication and authorization.
  • Registered server metadata, environment labels, server type, connectivity state and collector status.
  • Protected connection metadata required to reach the administration database and monitored SQL Server instances.
  • Configuration rows, alert rules, license state, activation metadata and allowed monitored server count.
  • Operational preferences such as registered server labels, environment classification and host-specific visibility rules.

What dbNexia Demo Reads

  • Backup, SQL Agent job, error, blocking, deadlock, login and connectivity signals.
  • Database file, log, allocation, volume, tempdb and repository growth telemetry.
  • Database options, index/statistics health, constraints, file-growth settings, security configuration and selected metadata when permissions allow it.
  • Collector health and telemetry gaps that affect confidence in dashboards, reports, Action Center and recommendation pages.

How The Data Is Used

  • Dashboard: summarizes current health, backup exposure, jobs, workload and collection coverage.
  • Reports: lets authorized users browse collected operational data per server.
  • Forecast: turns historical growth into file, log and volume capacity planning.
  • Incidents: prioritizes runtime, backup, security, blocking and telemetry problems before they become outages.
  • Database Health: explains configuration, index, statistics, integrity and permission findings, and can run controlled fixes for authorized roles.
  • Backup Readiness: filters backup and restore-chain exposure by server, database, recovery model and risk type.

Decision-support Boundaries

The prediction and recommendation views are decision-support tools. They highlight risk, source evidence and recommended DBA action, but they do not replace operational review.

  • No external AI provider is required for the current Forecast, Incidents, Action Center, Data Quality or Database Health recommendations.
  • Predictions depend on telemetry quality, retention, permissions and collector job health.
  • Missing or stale telemetry is treated as a visible operational risk.
  • Automated remediation actions are only available to authorized Admin/Moderator users and should be reviewed before execution.

Access and Protection

  • Authentication is handled through ASP.NET Core Identity.
  • Administration pages are protected with role-based authorization.
  • Reader and demo-style access can view operational evidence but cannot run protected actions. User and License management remain Admin-only.
  • Connection metadata is protected with ASP.NET Core Data Protection keys stored in the configured database.
  • The application should be published behind HTTPS and managed through the customer's normal access process.

Retention and Removal

  • Retention follows the customer's database configuration, SQL Agent jobs and backup policy.
  • Administrators can remove users, servers and stored connection metadata from management pages.
  • Alert rules, server inventory and action history remain in the administration database until changed by authorized users or normal retention jobs.
  • Operational logs remain in the SQL Server environment unless the customer exports, backs up or transfers them.
  • License information is used only to validate entitlement, expiry and allowed server count.

Plain-language privacy promise

dbNexia Demo is built to help DBAs operate SQL Server estates with clear evidence. The application does not sell customer telemetry, does not require business-table content for its monitoring features, and keeps operational control with the customer deployment and configured SQL Server permissions.