Key points
- Choose the input carefully.
- Keep the provider handoff visible.
- Delete stored files when finished.
- Thirty-day retention ceiling.
Detailed explanation
Before processing, your browser can inspect structure and duplicates locally. When you start a verification run, the selected input and job metadata are stored so the workspace can show progress, preserve File IDs, reconcile credits, and provide downloads. Eligible unique addresses are sent to the configured verification provider; surrounding spreadsheet columns are not required for that provider request. Returned statuses are mapped back to the original rows so you can reconcile the result with your source file. For the Google Sheets™ add-on, Refresh List receives only the spreadsheet range you explicitly select for verification. Email addresses are sent to the Refresh List verification service to perform the requested checks, and results are returned in a separate results sheet. Refresh List does not access unrelated spreadsheet tabs, Drive files, images, contacts, or personal content, and does not overwrite the original spreadsheet data. Refresh List does not process images or intimate imagery and does not use Google APIs for AI-generated non-consensual intimate imagery (NCII).
Example
A typical workflow is: upload a CSV, review the free preflight assessment, start verification, monitor progress, download the categorized results, and delete stored files after your team has the exports it needs. Duplicate rows remain connected to their original source rows, while completed valid, invalid, and unknown outcomes remain distinguishable.
How Refresh List handles it
Refresh List retains uploaded inputs and generated results for up to 30 days to support review and download. You can delete stored files earlier after processing stops. Deletion removes app-held list objects and results; it does not automatically control a separate provider’s retention schedule. Account, payment, invoice, security, and support records may need to be retained for operational, accounting, fraud-prevention, or legal reasons.
Limitations
Do not upload data you are not allowed to process. Keep passwords, API keys, card details, and complete lists out of support tickets. Use suppression and consent controls in your own sending workflow. Review the Privacy Policy for the complete legal description and contact support for a privacy or deletion request.
Related topics
Methodology and sources
Product behavior is described from the current Refresh List implementation and provider contract. Protocol context should be checked against the applicable standards and provider documentation. This page does not create a benchmark or certification.