Data handling
What happens to your file.
A plain-language summary of the current preview and paid audit. The linked privacy notice and data processing agreement give the full terms.
Upload and review
The application runs on Fly.io in London. You upload a CSV or TSV export into your own account. The current audit keeps parsed lead information, including permitted extra columns, so you can review it. It does not promise to remove every personal or sensitive detail for you.
Only upload your own past enquiries and customers. Remove passwords, payment-card details and sensitive information first. The audit organises the supplied data; it does not prove permission to contact someone.
The free preview allows up to 100 rows per account each calendar month. Contact details are masked on screen, but the stored information is not anonymous. Unconfirmed previews expire after 48 hours. A confirmed paid list remains until deleted or the account is closed.
Who handles the information?
Hosting and backup providers process the information needed to run the service. If optional assisted column mapping is enabled and ordinary mapping fails, header labels may be sent to the named mapping provider; contact rows are not sent for that purpose. Do not put personal information in column headings.
When you approve sending and all checks pass, your chosen email provider handles the message and recipient details. Working reply capture is a separate setup. Assisted-help requests are saved in the workspace and also emailed to support when the system-mail attempt succeeds.
Operator screens restrict access and log review actions. These application controls do not mean that the service operator has no administrative access to the hosting environment. Access needed for support, security and recovery is governed by the privacy notice and DPA.
Deletion and recovery copies
Use account deletion to close the active account. The result lists local deletion, subscription and provider cleanup separately, including any unfinished stage.
Ordinary backups normally expire within 30 days. If a recovery failure would leave no verified recoverable copy, an isolated encrypted recovery copy may be kept longer until a replacement is verified. It is used only for recovery, and deletion instructions must be reapplied after restoration.
New offsite database backup objects have been encrypted by the application before upload since 4 September 2026. The current privacy notice explains the earlier-object transition and infrastructure snapshots.
Read the privacy notice · Read the data processing agreement · Understand deletion stages