Privacy
Updated 16 November 2026. DD Backup is a Windows backup application from Drzewiecki Design. Version 1.8.9 includes application and device-update discovery with separate opt-in installation queues and reviewed native updater workflows. Background checks use measured CPU, disk and memory headroom and do not require keyboard or mouse inactivity. Updates requiring a manual workflow are identified explicitly. This notice covers the features described below in versions that include them.
Your backups and cloud accounts
You choose which files and folders to back up and where to store them. Backup contents and file names are encrypted on your PC before upload. Drzewiecki Design does not receive your source files, file names, folder paths, repository passwords, cloud access tokens or backup reports.
For offline browsing, DD Backup stores a catalog in your Windows user profile. It records file names, folder paths, sizes, backup dates and version identifiers. The catalog stays on your PC when you disconnect a drive or cloud account.
When you connect Google Drive, DD Backup requests permission to manage files created by the application (the drive.file permission). It creates encrypted backup repositories, reads and verifies their contents, restores requested files and removes expired backup objects according to your retention settings. It reads storage quota to show available space. This version uses My Drive. Sign-in happens in Google's browser flow. Backup traffic goes directly between your PC and your chosen provider.
Your storage provider can see account information, the backup folder name, encrypted object sizes and access times. Cloud tokens are stored in an encrypted rclone configuration on your PC, whose key is protected by Windows for your user account. Google account data is not sold, used for advertising or used to train AI models. DD Backup's use of information received from Google APIs adheres to the Google API Services User Data Policy, including its Limited Use requirements.
Control and removal
Disabling a cloud connection stops its use by backup jobs while retaining the saved connection and existing backups. You can revoke access in your provider's account settings. Uninstalling the application does not erase your backup repositories or saved profile. You can remove those separately. Expired Google Drive repository objects are deleted permanently as part of configured retention; DD Backup does not empty your account's entire trash.
Local maintenance
Maintenance stores its policy, queued actions, results and available Windows diagnostics in your local DD Backup profile. Diagnostics can include processor and memory inventory, device identities, firmware versions, exposed storage counters and selected recent hardware/storage events. These reports are not uploaded to Drzewiecki Design. Lightweight local resource counters help optional work yield to foreground activity and heavier CPU, disk or memory use; they do not record the contents of your work. Reports are cached to avoid repeated inspection. Maintenance reuses recorded backup-job verification and does not schedule additional backup-data reads or recovery drills. Existing recovery evidence and private temporary files from interrupted older operations can remain until scoped cleanup completes. Saved reports do not contain recovery passwords or extracted file contents.
System maintenance suggestions
DD Backup periodically reads supported official vendor metadata and Microsoft's public Windows release tables. Vendor requests identify public product families or models. Device serial numbers, backup source paths, backup contents, recovery credentials and diagnostic logs are not submitted to Drzewiecki Design. Vendor infrastructure receives ordinary connection metadata such as IP addresses and requested pages. A supported Kingston check can retrieve one bounded official release-note PDF and verify its checksum; it does not execute the document. BIOS installation and vendor-only firmware procedures remain manual. Suggestions, approvals and detailed journals are stored locally without an in-app journal viewer.
Version 1.8.8 can autonomously prepare the exact supported motherboard's public BIOS ZIP from the official vendor CDN and verify its published checksum. The request exposes the public board/release URL and ordinary connection metadata to that vendor. The archive remains in the local profile; it is not extracted, executed or flashed. Existing archives are retained for reference, and a changed canonical copy is preserved once instead of being trusted or silently overwritten.
Application discovery uses Microsoft's official WinGet catalogue, correlating local installed package names, versions and scope. WinGet may refresh its configured official source and uses its normal Microsoft networking and privacy controls. Device discovery uses Windows Update Agent's online signed device catalogue, which can send device applicability information to Microsoft's configured update service under Windows settings. DD Backup does not request OS update installation. Coverage excludes uncorrelated packages, other user accounts and hardware lacking reliable version evidence; unsupported updates include official resolution links.
Applications, Drivers and Firmware installation preferences start off and require separate explicit opt-in. Discovery runs while installation is stopped. On first normal launch from the installed location, DD Backup automatically prepares its signed protected maintenance component using Windows' standard administrator-consent prompt. This infrastructure setup does not enable updates or change existing backup preferences. A local receipt prevents repeated prompts after cancellation or failure; an explicit retry remains available. Preparation requires the same Windows administrator account, and another account's enrollment cannot be silently replaced. Portable and isolated test launches do not request this setup. The component accepts fixed typed update requests, verifies applicability and publisher signatures, and does not accept arbitrary commands from the profile. Its authenticated readiness probe does not download or install software. Required restarts are reported rather than initiated. Committed installers retain protected local receipts and continue safely if DD Backup exits. The Applications preference also controls DD Backup's signed self-updater. No inventory is uploaded to Drzewiecki Design.
Version 1.8.9 can use reviewed built-in vendor update workflows. GitHub Desktop preparation requests its public production update metadata and an exact release package; these requests identify the public release and platform, without sending account credentials or local backup data. The installed updater receives a protected local offline feed and runs with the enrolled user's limited token. Visual Studio preparation queries its signed local inventory tool and public Microsoft channel metadata. Its installed signed servicing client may download current same-channel product components under Microsoft's normal installation and privacy controls. A bounded local read-only WinGet pin snapshot is required for latest-channel servicing; DD Backup does not remove or alter pins. Native update plans, completion receipts and verification evidence stay local. Preparation does not run a mutating vendor command, and existing application data, workloads, restart choices and separate installation preferences remain respected.
Update checks
The application checks the public release manifest and downloads signed updates when requested or when its separate automatic self-update preference is enabled. It does not generate or send an installation identifier, count installations, or submit usage reports. It removes its old local installation identifier when started.
The former server-side installation counter has been retired and its counting database, key and aggregate report removed. Update requests from older versions remain compatible, but their installation headers are ignored. The hosting provider receives network information such as IP addresses and may retain ordinary security or access logs separately.
Optional Viber notifications
Viber notifications are enabled only when you connect and enable a channel. Requested summaries and issue reports are sent to your channel through Viber. Sending a recovery key is a separate explicit action. The built-in DD webhook accepts and discards incoming callback contents; it does not send messages or store a channel registry. You may choose your own webhook instead.
Contact
For privacy questions, contact Drzewiecki Design through the contact page.