Yesware Privacy Policy

Updated 20 July 2026.

Site data

Hosting systems may receive standard request data such as IP address, user agent, requested page, and timestamp. This site has no lead-capture form and does not ask visitors to submit prospect lists, contact exports, API keys, or account credentials. Do not place those materials in a support request, public issue, prompt, screenshot, or shared log.

Clipboard and installation

The displayed command is copied only after an explicit click. Running it occurs in your own terminal and is subject to the package prompt and runtime you choose. Copying does not transmit a contact record, complete an installation, or connect an external provider. Inspect the requested behavior before running it, then use a test environment and minimum-scope credentials where possible.

Connected sources

Third-party sources may process company and professional contact data under their own policies. Before you connect one, define the lawful purpose, field provenance, access roles, retention period, correction process, suppression rule, deletion path, and the person responsible for revoking access. Provider disagreement and missing fields should remain visible rather than being silently converted into a confident profile.

Outreach boundary

Keep research separate from sending. Review relevance, identity, verification state, claims, opt-out language, sender policy, and applicable regional requirements before a message can leave a mailbox. A returned record does not establish consent, current employment, commercial fit, or a right to contact a person.

Security and questions

Store credentials in a secret manager, rotate exposed keys, limit access, and remove test output according to your retention policy. Email [email protected] for questions about this site policy. For questions about a connected provider, contact that provider directly under its published privacy process.