MyLeadFox

Data use policy

Effective 1 September 2026

This page is part of the terms of service. It says what you may do with the shop records, exports, API responses and enrichment results the service gives you, and what you may not. The short version: use it for your own business, verify what matters, honour every opt-out, and do not resell it.

1. Your responsibility

When you export or enrich a record you, the MyLeadFox user, become responsible for your own processing of it, entirely and alone. We provide data and tools; we do not provide legal advice, consent management, suppression lists for your systems, or clearance for your campaigns. You decide whether and how you may lawfully use, store, combine, share or contact anyone, under the law of every country where your recipients are. MyLeadFox is not responsible for any message you send, any campaign you run or any consequence of either, and any complaint, claim or allegation about your outreach is yours to answer, as section 19 of the terms of service states.

2. What you may do

You may use outputs for your own business: prospecting, market research, lead generation, account research, verification, and keeping your own CRM current. You may share outputs with your employees, contractors and service providers who need them for that work, provided they are bound to the same restrictions as you. Team seats exist for exactly this and cost less than the support burden of shared logins.

3. What you may not do

You may not sell, publish, sublicense, syndicate or otherwise redistribute shop records, exports, API responses, enrichment results or anything derived from them. You may not use them to build, train, benchmark or improve a competing database, lead list, enrichment service or people-search product, and you may not train machine-learning models on them beyond models used solely inside your own organisation that do not recreate the database. You may not warehouse API results to serve later requests without querying the service again. The acceptable use policy covers conduct; this page covers the data.

4. Enrichment results in particular

A contact enrichment checks a shop's contact routes in real time as you request it and returns what it finds. Those results are licensed for your own business use under the same rules as the rest of the data, with two additions: you may not compile enrichment results into a dataset that is sold, shared or published, and you may not use them to build a contact database that substitutes for running the enrichment. An enrichment that has run is spent, whether or not it found what you hoped for.

5. No regulated decisions

Outputs are not consumer reports. You may not use them to decide anyone's eligibility for credit, insurance, employment, housing, lending, tenancy, education, healthcare or a government benefit, or to make any legal or similarly significant decision about an individual.

6. Opt-outs and removals

You must honour opt-out, unsubscribe, suppression and do-not-contact requests in your own systems and campaigns, immediately and permanently. When a business asks us to remove its record, the data sourcing and compliance page explains that we suppress it and, where we know who exported it, we tell them. If you receive that notice you must stop using that record and delete it from your own systems within 14 days.

7. Accuracy and verification

Data reflects what a shop published when it was last checked, and every record carries that timestamp. We do not warrant that any field is correct or current, that a contact route still works, or that a message sent to it will arrive. Fields we have not measured are marked as undefined and are never presented as zero. Verify anything you intend to rely on before contacting a person, importing records into a production system or making a decision on them. Dissatisfaction with a result is not a billing error and does not create a refund right beyond what the refund policy says.

Exports to Google Sheets shorten any single cell longer than Google's limit and mark it; the CSV download always carries the full text.

8. Monitoring and enforcement

We monitor usage for security, billing, abuse prevention and compliance with this policy. If we reasonably believe your use breaks it, the acceptable use policy's enforcement steps apply: a warning, then suspension, then closure, with API keys, exports and running jobs stopped and the licence to data obtained through the breach ended.

9. Contact

Questions about this policy can be sent to hi@myleadfox.com and a person will answer.