Clear boundaries, written plainly.
This product-facing privacy draft explains the intended data flows. It must be reviewed by qualified legal counsel before commercial launch.
SQL SafeOps Cloud Data
To operate accounts and paid licenses, SQL SafeOps may process account name, email address, authentication provider, verified-email state, plan, subscription and license identifiers, payment-provider customer/order/subscription references, application version, and essential security logs.
Customer Database Data
Database contents, queries, connection credentials, connection strings, table values, rollback snapshots and generated SQL remain on the customer device and target SQL Server environment. They are not designed to pass through SQL SafeOps cloud services.
Payments
Checkout is handled by Lemon Squeezy. The payment provider collects the information needed for checkout and sends signed events used to establish subscription or lifetime entitlements. SQL SafeOps does not store card details.
Desktop telemetry
Technical telemetry is off by default during the MVP. A future opt-in implementation must exclude queries, server aliases, database and table names, record values, credentials and connection strings.
Local operation history
The optional local history stores timestamp, server alias, database, table, operation type, affected-row count and success/failure. It is not synchronized to the cloud and can be disabled.
Retention, rights and contact
Final retention periods, data-subject request procedures, controller identity, lawful bases, international transfer details and privacy contact information must be supplied and legally reviewed before launch.