Security & trust

Security isn't a badge. It's the defaults.

You're trusting LeadFuel with your accounts, your inbox and your customers. Here's how it's protected, and what we'll never do with it.

LeadFuel protects your data with encryption in transit and at rest, OAuth-only access (we never store your passwords), and least-privilege scopes that ask only for what a feature needs. It works through official APIs (LinkedIn and Microsoft Graph) and never scrapes. Your data is never sold and never used to train public models. A formal SOC 2 program is on our roadmap; the practices below are in place today.

Encrypted everywhere

Your data is encrypted in transit (TLS) and at rest. Sensitive tokens are encrypted at the application layer, not just stored.

OAuth-only, no stored passwords

You connect accounts through official OAuth flows. We never see or store your passwords, and you can revoke access any time.

Official APIs, never scraping

LeadFuel works through LinkedIn and Microsoft Graph APIs and your own connected data. No scraping means less risk to your accounts and your brand.

Least-privilege scopes

Each feature requests only the permissions it actually needs, and we explain why. You can see and control what's connected.

Your data stays yours

Exportable any time, never sold, and never used to train public models. The customer brain is yours, not a shared pool.

Revoke and delete

Disconnect an integration or delete your data on your terms. Ownership includes the right to walk away with it.

OUR PROMISE

What we'll never do

Sell your data, or share it with data brokers.
Use your data to train public AI models.
Scrape platforms or store your account passwords.
Email people on your behalf without your approval.
Hide what we collect or where it lives. See our data policy.

We follow enterprise-grade security practices today. A formal SOC 2 program is on our roadmap, and we'd rather tell you that plainly than imply a badge we don't yet hold.