Elementor can store form uploads in WordPress or send them as email attachments, and those choices create different retention paths. Backups, mailbox archives, malware scanners, ticket systems, and CDN copies can keep a file long after the visible form submission is deleted.
Use this for job applications, intake forms, ID documents, medical or financial files, or any Elementor form where uploaded content deserves a defined access and deletion policy.
Quick answer
Elementor Atomic Forms File Attachment Retention Audit should be handled with a narrow evidence-first workflow: map storage mode, trace synthetic file, limit access, then verify the result before making broader changes.
What to check first
- Identify whether each upload field stores files in wp-admin, sends attachments by email, or does both through custom code.
- Trace one synthetic file through uploads, submissions, mailboxes, backups, scanners, exports, and support systems.
- Record who can access each copy and whether a public or guessable URL exists.
- Set retention by purpose, then test deletion from the primary store and every downstream copy.
- Document the user-facing notice, allowed file types, size limits, and incident response owner.
Diagnostic table
Use this table to keep the work practical. It connects the symptom to evidence and a verification step.
| Action | Evidence to collect | How to verify |
|---|
| Map storage mode | Identify whether each upload field stores files in wp-admin, sends attachments by email, or does both through custom code. | The synthetic file is found in every expected system and nowhere else. |
| Trace synthetic file | Trace one synthetic file through uploads, submissions, mailboxes, backups, scanners, exports, and support systems. | Public requests cannot fetch the file without the intended authorization. |
| Limit access | Record who can access each copy and whether a public or guessable URL exists. | Deleting the test submission follows the documented mailbox and backup schedule. |
| Set retention | Set retention by purpose, then test deletion from the primary store and every downstream copy. | The form notice and internal runbook describe the same storage behavior. |
Why this usually happens
- A form setting controls the primary copy but not mailbox or backup retention.
- Security scanners can quarantine and retain an additional file.
- Support tickets often preserve attachments outside WordPress access controls.
- Deleting a submission row may not remove a file referenced by custom actions.
Useful command or data shape
Adapt paths, IDs, and privacy handling to the site before running commands or storing data on production.
attachment_inventory:
form_id: applicant_upload
primary_store: email_attachment
wp_admin_copy: false
mailbox_retention_days: 30
backup_retention_days: 14
ticket_copy: prohibited
deletion_test: 2026-07-14
Safe fix order
Do the work in a sequence that makes each result easy to prove. Stop if a step produces new evidence that changes the incident scope.
- Map storage mode
- Trace synthetic file
- Limit access
- Set retention
- Prove deletion
What to tell the client or owner
List form ID, field ID, storage mode, file locations, access roles, public URL test, retention days, backup schedule, and deletion evidence.
Production verification checklist
- The synthetic file is found in every expected system and nowhere else.
- Public requests cannot fetch the file without the intended authorization.
- Deleting the test submission follows the documented mailbox and backup schedule.
- The form notice and internal runbook describe the same storage behavior.
Mistakes to avoid
- Do not judge the fix by one browser or the homepage only.
- Do not delete evidence before recording usernames, file paths, timestamps, and response headers.
- Do not add a cache, security, or tracking plugin while the original problem is still unclear.
- Do not leave test users, temporary debug logs, or broad API keys active after verification.
When HandL WP should help
Bring in help when this affects leads, checkout, search visibility, malware risk, paid media reporting, or a client production site. HandL WP can trace the issue through WordPress, hosting, cache, tracking, and Search Console, then verify the workflow after the technical fix.
If this is active on a production site, review an Elementor form workflow.
Related HandL WP guides
Use these related guides when the same issue touches tracking, security, checkout, or crawler visibility.
Helpful references
Test attachment limits before setting retention
Before deciding how long an upload should remain, run the Elementor attachment email size-limit test across the widget, PHP, web server, SMTP provider, and recipient mailbox. It also verifies that failed sends do not leave exposed or orphaned files.