Can DuckDuckGo be configured to sync searches across devices and does that store data?
This fact-check may be outdated. Consider refreshing it to get the most current information.
Executive summary
DuckDuckGo’s browser now includes a Sync & Backup feature that lets users privately sync bookmarks, passwords and Email Protection settings across devices with end-to-end encryption so DuckDuckGo cannot read the synced contents [1] [2] [3]. The available reporting and the company’s help pages do not show a built‑in, cross‑device sync of search queries or search history; the documented sync targets are bookmarks, passwords and certain settings, and an older “cloud save” system for settings was stored unencrypted on Amazon S3 [1] [2] [4].
1. What DuckDuckGo says it syncs and how it does it
DuckDuckGo’s official documentation and press coverage describe “Sync & Backup” as syncing bookmarks, passwords and Email Protection settings between DuckDuckGo browsers on iOS, Android, macOS and Windows without requiring an account, using end‑to‑end encryption so DuckDuckGo “never has access” to the data or the decryption key [1] [5] [2] [3]. The company advertises device pairing via QR codes or text codes and provides a recovery PDF with codes to restore data if devices are lost, with a copy of the encryption key stored on any other synced device and inside the recovery code [6] [7] [8].
2. Does DuckDuckGo sync searches or search history across devices?
None of the sources present an explicit feature that syncs search queries or search history across devices; reporting and DuckDuckGo’s help pages consistently enumerate bookmarks, passwords and Email Protection settings but do not list searches or search history as a syncable item [1] [5] [3]. Independent coverage framing the new feature focuses on “passwords and bookmarks” and positions the offering as closing a long‑standing gap in DuckDuckGo’s browser functionality, without claiming cross‑device search syncing [9] [3] [7]. Because the available sources do not document search query syncing, it would be inaccurate to assert that DuckDuckGo currently offers that capability based on these materials.
3. What data is stored on DuckDuckGo’s servers and is it readable?
For the Sync & Backup feature, DuckDuckGo says encrypted data is uploaded to its servers so devices can stay in sync; end‑to‑end encryption means the data should remain unreadable to DuckDuckGo or an attacker who only obtains the stored blobs, because decryption requires keys held on users’ devices or in the recovery code [2] [1]. However, a separate older “Cloud Save”/settings mechanism described in DuckDuckGo help pages stored a settings file on Amazon S3 that the company acknowledged was not encrypted and could be inspected, with the passphrase never leaving the browser but the settings file itself saved in plain form on S3 under a generated key name [4]. That distinction matters: the new Sync & Backup is presented as end‑to‑end encrypted, while older settings cloud storage was explicitly not encrypted [2] [4].
4. Caveats, privacy claims and where to look next
DuckDuckGo frames Sync & Backup as a privacy‑first alternative to account‑based syncing offered by other browsers and bolsters the claim with technical details about keys, recovery codes and device pairing to limit server visibility [7] [9] [6]. Still, users should note the company stores encrypted blobs on its servers to enable syncing [2] and that historical or alternate cloud‑settings mechanisms were unencrypted [4], so reading the fine print and understanding what specifically is included in the sync (bookmarks, passwords, Email Protection settings) is essential; the sources provided do not demonstrate any official sync of search queries or full search history, and they warn recovery codes grant unencrypted access if mishandled [8]. Reported coverage is generally favorable and echoes DuckDuckGo’s privacy messaging; readers seeking definitive confirmation about syncing of search history should consult DuckDuckGo’s up‑to‑date help pages or test device behavior, because the available reporting does not document a search‑query sync feature [5] [1].