Yesware Terms of Service
Updated 20 July 2026.
Purpose
This site documents an agent-installed company research workflow. Copying a command does not complete installation, grant access to a third-party data source, or authorize a contact to receive outreach. The material is an operational reference, not a claim that any connected service has a particular coverage level, compliance outcome, performance rate, or commercial relationship.
Acceptable use
Use company and professional contact data lawfully and only for a defined business purpose. Maintain human review, suppression and opt-out handling, regional communications checks, retention limits, and access controls. Do not use the workflow for deception, harassment, unlawful profiling, credential collection, or attempts to evade platform terms, rate limits, or privacy rights.
Before any message is sent, the operator remains responsible for checking relevance, source context, email status, sender identity, applicable consent requirements, and the communication rules in the relevant jurisdiction. A generated draft is not approval, and an observed public event is not evidence of buying intent. Keep an immediate stop path for uncertain records and requests to opt out.
Third parties and configuration
Connected runtimes, data providers, mail systems, and storage destinations have their own terms, fees, permissions, limits, and retention practices. Review those documents before supplying credentials. Use minimum-scope keys, protect secrets from prompts and shared logs, document output destinations, and revoke access when testing ends or a connection is no longer needed.
No guarantee
Coverage, identity resolution, event freshness, contact verification, deliverability, inbox placement, and replies vary by source, configuration, market, and operating practice. Sample records are illustrative. You should evaluate a known cohort, including exclusions and ambiguous records, before relying on a workflow in production.
Contact
Email [email protected] for site-policy questions.
Operators should retain a dated record of the test purpose, approved sources, exclusions, reviewer, and stop condition. If a connected system changes its permissions, output schema, or retention behavior, pause the workflow and reassess it before using the new behavior with a production audience.