Privacy and data
A plain-language overview of the data this product is designed to handle and the safeguards that should govern it.
Pre-launch policy draft: verify the deployed data flows, providers, retention periods and applicable legal requirements before production use.
Depending on features you use, the service may process account details such as your email address; workspace and team membership data; business and prospect information you submit or obtain from permitted public sources; campaign drafts, approvals, suppression choices and delivery records; provider connection metadata; support requests; and technical security and usage logs.
Information is used to provide account and workspace features, organize research and campaigns, create drafts for review, operate approved integrations, enforce access and usage limits, prevent abuse, maintain security, provide support, and improve service reliability. Analytics should distinguish recorded application activity from provider-confirmed delivery or independently verified commercial outcomes.
The product is intended for relevant business research using permitted public sources. Users must not submit or collect private-account data through unauthorized means, bypass access controls, or use the service for unlawful, deceptive, or unwanted contact. Source evidence and observation dates should be retained where available.
Drafts require human review by default. Users are responsible for having an appropriate lawful basis and required permissions for outreach in their jurisdictions and for following email, WhatsApp and provider policies. Opt-outs, suppression requests, negative replies, complaints and provider restrictions must be respected. WhatsApp functionality is limited to eligible use of the official WhatsApp Business Platform.
The service may process data through infrastructure, database, email-delivery, AI/search, analytics and payment providers when those integrations are configured and used. Each integration should receive only the information needed for its purpose. Payment details should be handled by the payment provider; this application is not intended to store raw card numbers or CVV.
Access controls, workspace authorization, secure sessions, rate limits and secret-redaction controls are intended to reduce risk. Provider credentials should be stored in protected server-side secret storage and never placed in source code or application logs. No internet service can guarantee absolute security.
Information should be retained only as long as needed for the disclosed service, security, legal and operational purposes. Backups, audit records and billing records may require separate retention rules. Account export and deletion capabilities must be used where available; any exceptions and retention periods need to be confirmed in the deployed product before launch.
Keep account credentials secure, submit only information you are authorized to use, configure provider connections responsibly, review drafts before sending, and promptly honor contact preferences. Do not rely on robots.txt or other discovery controls to protect confidential information; private data must be protected by access controls.
This page describes intended product practices and must be reviewed against the actual production data flows, providers, retention configuration and launch jurisdictions before the service accepts customers. It is not a substitute for jurisdiction-specific legal advice. Do not treat it as a guarantee that every described control is already deployed.
Use the support channel published by the service operator for privacy questions, data access requests, corrections or deletion requests. A verified support contact must be published before launch.
This page intentionally does not invent a support email address or claim that account export/deletion workflows are already available.