✓ Existing permissioned contact lists
✓ Small teams reviewing verification files
✓ Cross-vendor result and return decisions
— Cold outreach or purchased-list validation
— Guaranteed inbox placement
— Legal permission certification
— An email campaign builder
Separate audit facts from contact files
You may be able to retain a batch identifier, counts, mapping version and decision record without retaining every uploaded address indefinitely. Determine the organisation’s actual requirements rather than applying a universal deletion period.
Check both locations
Review local working copies and the vendor’s current retention/deletion behaviour. Bouncer publishes a data-processing agreement and a retention description; read their applicable scope before relying on them. Automatic vendor deletion does not remove your own exported copies.
A closeout checklist
Record where the original and results are held, who can access them, the applicable review date and any authorised deletion confirmation. Do not delete records needed to preserve exclusions or resolve an active incident merely to tidy a folder. This is an operational checklist, not legal advice.
Put it into practice
Create a simple location register for the input snapshot, prepared upload, returned result, working join and final receipt. For each location, record the responsible owner and the applicable retention decision. A vendor's automatic deletion policy affects its own copy, not the copies in a local downloads folder, email attachment or shared drive. Conversely, deleting every local file may remove evidence needed for an unresolved incident or suppression history. Resolve the actual requirement rather than applying a universal cleanup rule. Where deletion is authorised, use the system's documented method and record the observed outcome without exposing the deleted content. Where retention is necessary, restrict access and avoid duplicate copies. This guide does not determine legal retention obligations or certify a processor. It helps a team identify where the data remains and which decision is still required before calling the batch closed. Check shared copies separately: removing your local download does not revoke a colleague’s access or establish deletion at the processor.
Where the safety evidence stops
This guide draws on Bouncer data processing agreement, Bouncer data handling overview, Bouncer privacy policy. Merchant-controlled records describe the provider’s own capabilities, terms or standards; they do not independently validate those claims. These records do not establish independent confirmation of the product claims.
Verify any current price, plan limit, label direction, compatibility rule, or commercial term that would materially change the decision. The dated source ledger shows the underlying records so this conclusion can be checked and updated.
Sources used for this page
These records support the facts and comparisons above. Merchant-controlled records are labelled so you can separate product claims from independent evidence.
- Bouncer data processing agreement — Merchant documentation · usebouncer.com · Merchant-controlled · checked 2026-09-27
- Bouncer data handling overview — Merchant documentation · usebouncer.com · Merchant-controlled · checked 2026-09-27
- Bouncer privacy policy — Merchant documentation · usebouncer.com · Merchant-controlled · checked 2026-09-27