Your contacts should stay yours.

What the browser processes

When you choose a VCF, CSV, Excel workbook, image, or other supported file, the selected bytes are read by code running in your browser. The current processing tools do not upload contact contents, filenames, names, phone numbers, notes, photos, or generated files to our application server.

Ordinary website requests

Loading a public page still makes normal requests for HTML, styles, scripts, fonts, and images. The application loads no third-party analytics or advertising scripts. Optional developer diagnostics are local browser events; they are not sent to an analytics provider. The hosting provider still handles ordinary page requests.

Local browser state

The core editor does not require an account, cookie, or cloud project. The editor retains a draft in tab memory when you navigate away and return. Open another, a full reload, or closing the tab clears it; contact drafts are not saved to browser storage. Future preferences or recovery drafts will require clear opt-in copy, versioned storage, expiration, and a visible clear-data action.

Shared devices and downloads

Downloads, browser history, crash reports, operating-system backups, extensions, and screenshots remain local device concerns. Clear downloaded files and close the tab when working on a shared computer.

Your choices and questions

Use the Cookies page to review optional storage and the Security page to understand the technical boundary. For privacy questions, use the Contact page and provide a synthetic example rather than real contact data.