Search doesn't have a server, so it can't send anything to one that matters. There's no account, no sign-in, and nothing about you or what you browse is collected, logged, or sold — not by us, not by anyone we'd hand it to, because there's nowhere for it to go.
What stays on your Mac
Passwords go into the macOS keychain, the same vault every app on your Mac already trusts, shown back to you with Touch ID.
History and bookmarks are a file in your Application Support folder. Nothing is synced anywhere — not to iCloud, not between your Mac and the iOS app, which is deliberately its own separate browser.
Sites you've hidden things on, or told never to offer a password for are remembered the same way: on disk, locally.
Importing from another browser (Chrome, Dia, Arc, Brave, Edge, Vivaldi) reads that browser's own files on your Mac once, with your permission, and writes the result into Search's local storage and keychain. Nothing is uploaded in that process — it never leaves your disk.
What leaves your Mac
The pages you open — obviously; that's what a browser does. Search doesn't add anything to that traffic beyond what the site needs to load.
A small icon fetch for each site you visit, so its tab can show that site's own favicon instead of a letter.
Searches typed in the address field go to Google, the same as typing them into google.com directly.
Once a day, a request to officecommun.com for a small file that says what the current version is. It carries nothing about you — no account, no identifier, nothing different from a browser loading a web page — and is only how Search knows whether to offer an update.
Ads and trackers
The ad and tracker block list ships inside the app and runs in WebKit's own content-blocking layer, before a page's scripts run. It works from a list built into Search, not one fetched from a server, so nothing about the sites you visit is sent anywhere to make it work.