Security

Built so a stolen password
is not enough.

You are trusting us with the list of businesses you are about to call, which is commercially sensitive whether or not it feels like it. Here is exactly what we do about that, in terms you can check rather than adjectives you cannot.

Two factor is required, not offered

Every account, including ours. A password on its own reaches nothing. Choose an authenticator app, an emailed code, a text, or a passkey using Face ID or a fingerprint.

Your leads are yours alone

Searches, leads and unlocks are isolated per account by the database itself, at the row level, not just by the interface. Another customer cannot read your work even if a bug in a page tried to show it to them.

Credentials are never stored in the clear

Passwords are hashed with scrypt. API keys are stored as hashes, so a leaked table cannot be used to call anything. CRM tokens are encrypted with AES-256-GCM using a key that is not in the database.

Payments never touch our servers

Card details go directly to Stripe. We never see, transmit or store a card number, which is also why we cannot leak one.

Every operator action is logged

If our support team adjusts a balance, suspends an account, or looks something up, it is written to an append only audit record that the panel cannot edit or delete.

Deleting means deleting

Close your account and your searches, leads, credits, keys, integrations and sequences are removed. What survives is a dated row saying an account closed, carrying nothing that identifies you.

What we will not do

Four promises,
plainly stated.

  • We do not sell your search history, and we do not tell anyone which businesses you are working.
  • We do not train anything on your lead data.
  • We do not email your leads on your behalf without you writing the message and pressing start.
  • We do not share data between customer accounts, ever, in any aggregated form that could identify who searched for what.
Reporting a problem

Found something? Tell us.

If you believe you have found a vulnerability, write to us before telling anybody else and we will work with you. We do not threaten researchers who act in good faith, and we will credit you if you want the credit.

Please do not run automated scanners or load tests against the live service. They look identical to an attack from our side, and we will block them. Ask first and we will arrange a window.