Privacy policy

All three tools run as client-side JavaScript. When you paste a keyword list, drop in a .csv or .xlsx search-terms report, or tick a formatting option, the parsing, merging, tokenising and formatting all happen on your own device - on a Web Worker when a list is large enough to be worth moving off the main thread.

The result is that your lists never enter a network request. Closing or reloading the tab discards them: nothing is cached, queued, or written anywhere for later.

The outreach tool connects to a mailbox you control and sends messages to contacts you upload. Unlike the three keyword tools, this requires a server: your mailbox credentials, the contacts you import, and the content and delivery status of each message are stored in this application's own database, not processed transiently in your browser.

Mailbox credentials are encrypted at rest and are never included in any API response the browser receives. Contact data and message history are kept only as long as you keep them in the tool, are never sold or shared with anyone else, and are used solely to run the campaigns you create.

Running a cold-outreach campaign is your responsibility, not the tool's: you must have a lawful basis to email the contacts you upload. The tool enforces baseline compliance - a working unsubscribe link and a visible postal address on every message - but it cannot verify where your contact list came from or whether you have the right to email it.

For the three keyword tools: no accounts, sign-ups, or email addresses. The outreach tool is the one exception, by necessity - running it means giving it the contact email addresses you intend to send to, and the mailbox credentials to send from. No cookies anywhere on this site. Nothing written to localStorage or sessionStorage. No advertising or cross-site tracking pixels, and no third-party scripts that would set any of the above on our behalf.

Because no cookies or comparable storage are used, there is no consent banner to click through.

The suite includes an internal event module for measuring which tools get used. It is currently not connected to any analytics provider, so in the published site these events are recorded nowhere.

If a provider is connected later, the events it can send are fixed in advance and consist only of a tool name, a coarse size bucket such as 101-1000, the names of the options you ticked, and an error category. There is no field capable of carrying keyword text, file contents, or file names - that constraint is enforced by the event type definitions themselves rather than by convention, so it holds for any code added later. This page will be updated before any such provider goes live.

These pages are served as static files by a hosting provider. Like any web server, that provider records ordinary request logs - IP address, timestamp, requested URL, browser user-agent - for delivery and abuse prevention. Those logs cover the request for the page itself. They cannot contain your keyword data, because your keyword data is never part of a request.

The footer links to PPC Expert, which is a separate site with its own privacy practices. This policy covers only the tools hosted here.

Any change to how data is handled will be reflected here along with a new date at the top of this page. Material changes - in particular, connecting an analytics provider - will be described rather than folded quietly into the text.

Reach out through PPC Expert, who maintain this suite. The terms of use cover what the tools do and do not promise.