← Reach
Privacy Policy
Last updated: 2026-05-29
This policy explains what Reach collects, why, and who it is shared
with. Reach is operated by Emerging Technology Group LLC (etg.ai) as
part of the LeadFuel suite.
What we collect
- Account data. Your email, name, and (when you sign
in via the LeadFuel hub) the same single-sign-on identifier shared
across all LeadFuel apps.
- Campaign content. The sequences, step copy, send
schedules, lead lists, and Campaign Plans you create.
- Send + reply data. Per-message status (sent,
opened, replied, bounced) returned by Resend, our email-sending
partner.
- ICP data from Scope. When you generate a Campaign
Plan, Reach reads your Ideal Customer Profile from Scope
(another LeadFuel app) to shape the plan.
- Usage logs. Anthropic API token counts and cost
figures, used to show your spend in the LeadFuel hub.
How we use it
To run your outbound email campaigns, generate Campaign Plans against
your ICP, track replies and outcomes, and surface the resulting insight
back to you and the other LeadFuel apps you use. We do not sell your
data and do not use it for advertising.
Third parties
- Anthropic. Campaign Plan text, ICP context, and
step drafts are sent to the Claude API to generate copy.
- Resend. Your campaign emails go through Resend's
transactional-email service. Resend stores send + bounce + open
events that we read back.
- Core. Central account, billing, and shared
suite knowledge live there. We read your ICP from Scope and
write campaign-completion events to the shared Knowledge System.
Data retention
Your campaigns, sends, replies, and ICP linkage are kept for as long
as your account is active. When you delete your account (see below), we
remove this data within 30 days unless we are required to keep it for
legal or accounting reasons.
Your rights
You can request a full export of your data or permanent deletion at
any time by emailing privacy@leadfuel.cloud.
We respond within 30 days. EU/UK/CA residents have the additional rights
granted by GDPR / UK GDPR / CCPA respectively.
Security
OAuth tokens and other credentials are encrypted at rest. Email-body
content is stored only as long as needed to send and track the campaign
(drafted message + per-send delivery metadata).
Contact
Questions about this policy: privacy@leadfuel.cloud.
Terms · Cookies ·
Suite-wide privacy