Terms of service
Not yet drafted — do not rely on this page.
Terms are a contract, and a contract is a decision rather than something that can be derived from source code. What follows is the raw material: the commitments the software actually enforces, and the points a drafter has to settle. It must be completed with a qualified adviser before the product is sold.
What the software actually guarantees
Each of these is implemented and covered by automated tests, so it can safely be committed to in writing.
| Commitment | How it is enforced |
|---|---|
| Your data is yours, and is never mixed with another customer's. | Each route that returns your data filters it by your organization in the application code; there is no separate database-level guard, and the main routes have tests that a second organization cannot see it. The one shared store is the cache of provider search results, which holds business listings from our data providers and no customer information. |
| A guessed email address is always labelled as a guess. | Generated addresses are marked in the interface and in every export, and are never described as verified. |
| Your do-not-contact list cannot be overridden. | Entries are removed from searches, saved lists and every export. No setting or parameter re-enables them. |
| We tell you when a list is incomplete. | Truncated exports, suppressed rows and dropped search terms are reported in the response rather than silently omitted. |
| We respect robots.txt when reading a business website. | The crawler parses and honours robots directives, and identifies itself. |
| Demo data is always labelled. | While no live data provider is connected, fabricated leads are marked in the app and carry a Demo Data column in exports. |
What the software does NOT guarantee
- That a contact is correct or current. Business data changes constantly and comes from third-party sources.
- That an email address will deliver. We can prove an address cannot work; we never claim one does.
- That a search returns every matching business. Coverage depends on the data providers.
- Any particular response rate or commercial outcome from using the leads.
Acceptable use — points to settle
- Resale or bulk redistribution of the underlying business data may be restricted by our data providers' terms; the final wording depends on the provider agreements, which are not yet signed.
- Use of contact data for outreach is subject to the recipient's local law (CAN-SPAM, GDPR, PECR and equivalents). That obligation sits with the customer sending the message, and the terms should say so explicitly.
- Attempting to identify individuals outside a business context, or using the product for harassment, must be prohibited.
Still to be decided
- Controller identity: The legal entity, trading address and contact for privacy requests.
- Governing law: Which jurisdiction's law applies, and where disputes are heard.
- Lawful basis: The basis relied on for processing third-party business-contact data, per market.
- Retention periods: How long leads, raw provider payloads, crawl results, cached provider responses and closed CRM records are kept. Nothing is deleted automatically today: a cached provider response stops being used when it expires, but stays stored.
- Generated addresses: Whether to keep inferring email addresses for named individuals, and in which markets. This is the product's differentiator and its most disclosure-sensitive behaviour.
- Sub-processors: The final list, once hosting, email and billing providers are chosen.
- Billing and refunds: Trial length, refund policy, what happens to a customer's leads after cancellation, and notice period for price changes.
See also our privacy page, which documents what data the product holds and where it comes from.