Privacy

Privacy

LakeDB is local by design. It has no telemetry, advertising, analytics SDK, LakeDB account or LakeDB cloud synchronization.

Local application data

Connections, encrypted saved credentials, folders, preferences, recoverable workspace sessions, history, favorites and diagnostics live in the operating system's local application-data directory. Query results are temporary and are not restored with the workspace.

Files are opened, saved, imported or exported only through workflows initiated by the user. Configuration backups exclude passwords unless an unencrypted credential export is explicitly requested and confirmed.

Network activity

LakeDB connects directly to the database and SSH hosts you configure. It also requests public GitHub release metadata when update checks are enabled and downloads update packages from official LakeDB GitHub release assets when requested.

LakeDB does not send connection settings, credentials, SQL or result data to a LakeDB service.

Diagnostics and deletion

Diagnostics and support reports remain local until you copy or share them; LakeDB never submits them automatically. Review hostnames, database names, paths, SQL fragments and server errors before posting anything publicly.

Uninstalling the application package can leave the local profile in place to protect data during updates or reinstalls. Remove the profile directory separately only after keeping any backup you require.

The canonical public policy is PRIVACY.md.