Account protection
Use password changes, email verification, multi-factor authentication, and passkeys to protect sign-in.
Review account security
Refresh List is designed to help you clean email data without losing control of your account, files, or payment information. Here is what customers can expect, what they control, and where our claims deliberately stop.
Clear protections · Practical privacy · No exaggerated certificationsYour account, your workspace, your uploaded files, and your billing history. We keep security guidance understandable so your team can make a good decision before uploading a list or inviting a teammate.
We use the information needed to provide the service and keep customer controls visible.
We do not turn a security page into a certification badge or promise protection we cannot evidence.
These are the safeguards most teams want to understand before trusting a data workflow.
Use password changes, email verification, multi-factor authentication, and passkeys to protect sign-in.
Review account securityYour lists, results, credits, invoices, and support history are available only inside the account and workspace that owns them.
Read the privacy policyCard entry happens in the selected payment gateway. Refresh List keeps the purchase reference needed for credits and invoices, not your card number.
Review payment optionsWhen you need help, share a file ID, page, time, and error—not credentials, payment details, or a complete email list.
Open Help & SupportRefresh List uses your chosen file to assess its structure, remove duplicate work, run verification, and return categorized results. You decide what to upload, who can access the workspace, and when stored files should be removed.
Download the result you need, then remove stored files when your workflow is complete. Keep only the data your team still has a reason to retain.
Read data handlingSmall habits make a large difference when a team works with contact data.
Refresh List support should never ask for a password, card number, payment PIN, provider credential, or complete email database. If a message asks for one, stop and contact us through the official Help & Support page.
Get support safelyPayment history, credit changes, invoices, and account notifications help you recognize what happened. If a payment or sign-in looks unfamiliar, pause activity and contact support with the relevant reference.
Card details are entered on the selected gateway page.
Purchases and credit movements remain visible in your account.
Notifications help you spot unusual access or important account events.
Support can investigate a timestamp, page, and reference without needing your secret.
Change your password, revoke any exposed key, preserve the time and page involved, and contact support. We will ask for the smallest amount of context needed to investigate.
We publish what customers can verify, keep the language current, and update this page when the product’s protections change.
Refresh List does not currently claim SOC 2, ISO 27001, an independent penetration test, a security SLA, a universal accuracy benchmark, or guaranteed inbox delivery. Those claims require independent evidence before publication.
Use a strong password and the available multi-factor or passkey options. Refresh List also provides account notifications and protected downloads so you can spot unusual activity and reduce exposure.
Your file is used to assess and verify the list you choose. Refresh List keeps the result tied to your account, lets you remove stored files, and explains retention in the privacy and data-handling policies.
No. Card details are entered in the selected payment gateway checkout. Refresh List receives the payment reference and purchase details needed to provide credits and an invoice.
Support is designed around the minimum information needed to help: page, timestamp, file ID, and error. Never send a password, payment details, provider credential, or a complete list in a support request.
Refresh List does not claim SOC 2, ISO 27001, an independent penetration test, or a security SLA unless that evidence is independently completed and published. This page describes customer-facing protections and their limits.
Change your password, revoke any exposed API or integration key, preserve the time and page involved, and contact support. Do not include secrets or a complete email list.
Understand the protections, use the controls, and keep your data decisions explainable.