[{"data":1,"prerenderedAt":172},["ShallowReactive",2],{"publication:en:P097":3},{"meta":4,"copy":17,"relatedArticles":134,"terms":164,"term":165,"resourceParent":166,"glossaryParent":169},{"id":5,"path":6,"kind":7,"keyword":8,"title":9,"seoTitle":10,"description":11,"incoming":12,"updated":15,"preparedOn":16},"P097","\u002Fblog\u002Fdelete-old-form-data","article","delete old website form submissions","Delete old website form submissions: plan scope before removal","Delete old website form submissions safely","Plan deletion of old form submissions across WordPress, email, CRM and exports. Check authorization, retention decisions and backup limits before removing data.",[13,14],"\u002Fservices\u002Fwordpress-support","\u002Fservices\u002Fwebsite-maintenance","2026-06-20","2026-10-30",{"intro":18,"sections":19,"checklist":92,"faq":100,"links":110,"sources":127,"cta":129},"To delete old website form submissions responsibly, first decide which records are eligible, who authorizes removal and which copies exist outside the website. Then verify a small, controlled scope before any wider action. Clearing a plugin’s entries does not prove that email, CRM, exports, archives or recovery copies have also been addressed.",[20,26,62,72,78,86],{"title":21,"paragraphs":22},"Agree on the retention decision before selecting records",[23,24,25],"Age alone is not a complete deletion rule. Identify the purpose of the submissions, whether an active customer matter depends on them and which business or legal requirements apply. Ask the responsible owner to approve a written scope and exceptions. This guide supplies a technical planning method, not a universal retention period or legal deadline.","Separate routine cleanup from an individual’s verified request and from incident-related evidence. These can require different authorization, identity checks and handling. If there is an unresolved dispute, investigation or preservation requirement, get the appropriate decision before removing potentially relevant material. Do not assume a convenient database filter settles that question.","Record the system, environment, date boundary, record type and exclusions in a way another person can review. Counts and references can often describe the scope without a full export of the messages. Avoid creating an uncontrolled download simply to make deletion feel reversible; that creates a fresh copy needing its own justification and protection.",{"title":27,"paragraphs":28,"table":31},"Build a copy-by-copy plan with an accountable owner",[29,30],"Follow the enquiry route through the form application, notifications, CRM, attachments, staff exports and diagnostic stores. Each destination may have a different administrator and lifecycle. A single checkbox labelled “delete submissions” may cover only one of them.","Use this worksheet to distinguish a proposed action from a verified result. Populate it for the real workflow before removal, including destinations where the outcome is still unknown. Keep recovery and archive decisions explicit rather than silently treating old copies as outside the process.",{"caption":32,"headers":33,"rows":37},"Retention, copy and deletion-verification worksheet",[34,35,36],"Copy or system","Decision before action","Evidence after authorized action",[38,42,46,50,54,58],[39,40,41],"Form entry store","Exact eligible records, exclusions and owner approval","Scoped count and agreed lookup no longer returning the selected records",[43,44,45],"Uploaded attachments","Whether files are shared or independently referenced","Selected file handling and continued operation of unaffected records",[47,48,49],"Email and CRM","Responsible owner and applicable lifecycle rule","Separate confirmation of the approved action or stated exception",[51,52,53],"Staff export","Known locations, users and justified remaining use","Owner confirmation without claiming unknown copies were erased",[55,56,57],"Logs or support records","Diagnostic and preservation requirements","Documented coverage, restrictions and retention behavior",[59,60,61],"Backups or archives","Recovery, preservation and restore-handling decision","Recorded limitation and process to address restored data",{"title":63,"paragraphs":64,"sources":68},"Understand what the WordPress eraser actually covers",[65,66,67],"WordPress documents a personal-data erasure tool that gathers data from WordPress and participating plugins. Its documentation explicitly excludes backups and archive files. A form plugin, remote CRM or other component may therefore need a separate supported procedure; do not assume every entry is included because the website runs WordPress.","The documented erasure process is permanent once carried out. Confirm the actual product version, plugin support, user identification method and owner authorization before using it. This article does not provide a bulk SQL command or instruct you to force requests through the interface. Use the supported process appropriate to the records and request.","Also distinguish removing an erasure-request record from removing the underlying personal data. Interface status alone is not a complete copy inventory. Check the affected component’s behavior and record any information intentionally retained or excluded, with the responsible owner’s decision.",[69],{"label":70,"url":71},"WordPress: personal-data erasure and participating-system limits","https:\u002F\u002Fwordpress.org\u002Fdocumentation\u002Farticle\u002Ftools-erase-personal-data-screen\u002F",{"title":73,"paragraphs":74},"Validate the scope using synthetic data before a wider change",[75,76,77],"Where supported, rehearse the workflow in an isolated, appropriately protected environment using invented submissions and attachments. Check that the filter selects exactly the intended examples and leaves excluded examples alone. A staging environment containing production data still needs protection; the word “staging” does not make disclosure acceptable.","Before a live authorized action, confirm ownership, dependencies, recovery approach and the acceptance record. A backup can help operational recovery without making deletion harmless or automatically compliant. If old data is restored later, the agreed process must address the previous deletion decision again.","After the action, use the agreed lookups, counts and functional checks. Confirm that the form still accepts an authorized synthetic test through the expected route and that unrelated records remain available to the right people. Coordinate notifications so verification does not send unwanted messages or create real business transactions.",{"title":79,"paragraphs":80,"example":83},"Do not confuse a clean dashboard with complete deletion",[81,82],"A form list can be empty while historical notifications remain in a mailbox or a downloaded spreadsheet remains on a laptop. State the boundary of every result: which application, records and date range were checked, by whom, and what was outside that check. Avoid issuing a blanket statement about copies nobody has located or inspected.","If an unexpected destination is discovered, update the data map and refer it to its owner. Do not use the cleanup as a reason to delete evidence of a possible disclosure. Restrict further unnecessary copying while the responsible people establish what exists and what obligations apply.",{"title":84,"text":85},"Illustrative example: the website entry is gone, the notification is not","A fictional business removes an approved set of old form entries through its supported plugin process. The copy map shows full-message notifications in a shared mailbox and a separate CRM record. Those owners must make and verify their own authorized lifecycle decisions. The website action is recorded as complete for its stated scope, while the other destinations remain explicit follow-up items.",{"title":87,"paragraphs":88},"Prevent the same backlog from returning",[89,90,91],"Ask whether every field and copy is necessary. A shorter form, a minimal notification and a clear export process may reduce future cleanup work more effectively than repeated manual purges. Give each destination a retention owner, review trigger and supported method, with exceptions visible to the people responsible.","CyberFixCrew is an Israeli cybersecurity company serving worldwide businesses. Our practical Israeli website and digital-infrastructure knowledge connects WordPress maintenance, integrations, access and recovery planning. Describe the form system, intended scope and known destinations first; do not send the submissions themselves. Any deletion requires the actual owner’s decisions and a specifically agreed operational scope.","A useful handover contains the approved selection, systems covered, evidence of the scoped outcome, exceptions and restore-handling responsibilities. Keep that record appropriately limited and protected. The objective is a maintainable lifecycle with clear boundaries, not a promise that one cleanup button erases every historical trace.",[93,94,95,96,97,98,99],"Identify the purpose, applicable requirements and authorizing owner.","Specify eligible records, environment, exclusions and preservation needs.","Map form, file, email, CRM, export, log and recovery copies.","Check the actual plugin or platform’s supported deletion coverage.","Rehearse selection and exclusions with synthetic records where practical.","Verify the authorized result and unaffected business functions.","Record remaining copies, exceptions and handling after restoration.",[101,104,107],{"question":102,"answer":103},"Does WordPress erase data from every plugin and backup?","No, WordPress documents coverage of core and participating plugins, with backups and archive files excluded. Review each actual component and external destination separately.",{"question":105,"answer":106},"How old should a form submission be before deletion?","There is no duration that fits every business and record. The responsible owner must consider purpose, active matters and applicable obligations before approving a specific rule.",{"question":108,"answer":109},"Should we export all old submissions before deleting them?","Not automatically: an export creates another copy to protect and govern. Agree on the necessary evidence and recovery approach without making an unnecessary customer-data download.",[111,114,117,120,123,125],{"path":112,"label":113},"\u002Fblog\u002Fbusiness-data-map","Locate each enquiry destination before cleanup",{"path":115,"label":116},"\u002Fblog\u002Fcontact-form-data-security","Reduce unnecessary fields and notification copies",{"path":118,"label":119},"\u002Fblog\u002Fwebsite-backup-retention","Distinguish retained recovery history from active data",{"path":121,"label":122},"\u002Fblog\u002Fsaas-sharing-audit","Review access to cloud exports and folders",{"path":13,"label":124},"Discuss supported WordPress maintenance",{"path":14,"label":126},"Plan a controlled website change and handover",[128],{"label":70,"url":71},{"title":130,"description":131,"button":132,"type":133},"Plan a bounded cleanup of old website enquiries","Tell us the form platform, known copies and business-approved objective. CyberFixCrew can discuss the technical scope and verification before any data is removed.","Discuss the cleanup scope","check",[135,143,150,157],{"id":136,"path":112,"title":137,"description":138,"category":139,"artwork":140,"order":141,"publishedOn":142},"P096","Business website data mapping: follow each enquiry and copy","Map website data from forms to email, CRM, logs and backups. Record purpose, access, retention owners and gaps without collecting real customer data.","governance","integrations",60,"2026-07-06",{"id":144,"path":121,"title":145,"description":146,"category":139,"artwork":147,"order":148,"publishedOn":149},"P103","Cloud file sharing access review: verify who can still open a file","Review cloud links, guests, groups and inherited permissions. Verify effective access and separate current restrictions from past downloads and exposure.","access",46,"2026-06-04",{"id":151,"path":115,"title":152,"description":153,"category":139,"artwork":154,"order":155,"publishedOn":156},"P179","Contact form data security: protect the whole enquiry journey","Improve contact form data security across fields, server checks, uploads and storage. Use synthetic acceptance checks and owned retention decisions.","security",41,"2026-05-19",{"id":158,"path":159,"title":160,"description":161,"category":139,"artwork":147,"order":162,"publishedOn":163},"P090","\u002Fblog\u002Fai-agent-permissions","AI agent permissions for business: control tools, data and actions","Review AI agent tools, identities, read access and business actions. Define approval, logs and a shutdown route before connecting customer systems.",68,"2026-07-22",[],null,{"path":167,"label":168},"\u002Fresources","Website security resources and templates",{"path":170,"label":171},"\u002Fglossary","Cybersecurity glossary for small businesses",1794134058361]