Can I request earlier deletion of my verification data?

The default 15-day window is the upper bound, not a minimum. If you want a list or a specific verification task gone before the scheduled cleanup job picks it up, Valid Email Checker gives you three paths to early deletion: per-task deletion from the UI, per-row deletion from the results view, or a full-account purge via support. All three remove the data from our database immediately and queue the source files for removal from object storage.

Option 1: delete a specific task from Uploads & Results

Open Uploads & Results in the sidebar, find the verification task you want gone, and click the delete control on that row. The task is removed from the database immediately, and the source file in object storage is queued for cleanup in the next batch (usually within minutes). The credits you spent on the run stay in your Credits History — only the verification data is removed. The aggregate counts (total/safe/invalid) are kept against the task ID for billing reconciliation but no per-address detail remains.

Option 2: delete individual rows from the results view

If you only want a handful of addresses gone — for example, an EU subscriber who asked you to remove their address from your records — open the task, find the row, and use the per-row delete. The single address and its result are removed from the database. The rest of the task stays intact. This is the right tool for one-off GDPR-style erasure requests forwarded by your subscribers.

Option 3: full account purge via support

If you want every verification task and result associated with your account wiped — for example, you are closing the account and want a clean exit — email support@validemailchecker.com from the address on your account. We will confirm your identity, then run a purge that removes all your verification tasks, per-row results, and source files. We can also delete your login history, integration tokens, and API keys at the same time. Credits History and invoices stay (we are required to keep billing records), but they contain no verification content. See how do I file a GDPR data subject request for the formal erasure path.

What happens behind the scenes

Per-task and per-row deletes flip the row state to deleted and unlink the storage path. The actual storage file is removed when the next batch of the cleanup function runs (usually within a few minutes for active accounts). For an account-wide purge, the support tooling skips the 15-day cutoff entirely and acts on the rows immediately. The same audit log that captures the scheduled cleanup runs records on-demand deletions so we can demonstrate compliance later.