✓ 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 identity from context
A verification task does not normally need notes about a customer, order history or other unrelated fields. Determine the actual required schema from the selected service and remove unnecessary columns. Where an internal row identifier is useful, ensure it does not reveal additional private information.
Keep a private mapping
The internal mapping between the batch identifier and source record belongs in a controlled location, not on a public worksheet or shared review screenshot. Do not paste live lists into this site. Our planning tools accept only aggregate counts and do not verify individual addresses.
Before-upload review
Open the exact prepared file, inspect headers and a few appropriately handled rows, and check that unrelated columns are absent. Verify the destination and the organisation’s authority to share the file. The fact that a vendor offers an upload button is not permission to disclose every field in your export.
Put it into practice
Imagine a source export containing an address, customer notes, purchase totals, a phone number and an internal ID. The verification requirement does not automatically justify sending all five columns. Review the selected service's documented input needs, create a minimal working copy, and keep the original in its controlled location. If the internal ID is transmitted, consider whether it embeds information that the recipient does not need. The reviewer should inspect the exact file intended for upload, not a screenshot of a different working sheet. A common process failure is removing columns in one copy and uploading an older export from the downloads folder. Distinct filenames and a final header/count check help prevent that error. Do not use this website as an upload destination: it has no address-processing service. The local worksheet requires only counts and cannot determine whether the underlying disclosure is authorised.
Where the safety evidence stops
This guide draws on Bouncer data processing agreement, 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 privacy policy — Merchant documentation · usebouncer.com · Merchant-controlled · checked 2026-09-27