Local database connections
The Windows client opens the SQL Server connection from the customer device or environment.
A deliberately small cloud boundary.
SQL SafeOps separates commercial account services from the customer database data plane. The Windows app talks directly to SQL Server; our backend never sits in that path.
No SQL credentials in our cloud
SQL passwords use Windows Credential Manager. Connection profiles contain no plaintext password.
No database records uploaded
Records, queries, connection strings, database names and table values are excluded from cloud telemetry.
Secure authentication
Short-lived JWTs, rotated refresh tokens, OAuth Authorization Code + PKCE and verified identity linking.
Parameterized operations
Values become SqlParameters. Identifiers must match validated metadata and are quoted defensively.
Safe by default
No UPDATE without a condition, no zero-row execution and no reliable rollback claim without a primary key.
What our cloud can receive
- Account identity and email
- Plan, license and subscription status
- Application version and release channel
- Anonymous technical telemetry only after explicit opt-in
What our cloud must never receive
- SQL Server credentials or connection strings
- Queries generated or executed in the desktop app
- Record values, result sets or rollback data
- Database, schema or table names in telemetry
Claims we do not make
SQL SafeOps does not currently claim SOC 2, ISO 27001, GDPR certification, penetration-test certification or any other independent assurance that has not actually been obtained. Security documentation will evolve with evidence.
WINDOWS 10/11 · X64
Download for Windows Ready for a safer SQL workflow?
Start locally. Keep your database local.