WordPress Contact Form, Privacy Notice and Spam Protection Plan
Plan forms that collect little data and stay safe.
The Open buttons send the prompt text as currently shown below to that site only when you click. Fill in the placeholders first.
[VERIFY] is an editorial flag, not a blank to fill. Wherever the prompt shows [VERIFY], check that item against a reliable source before you use it.
Plan a contact form for WordPress. Purpose and who reads messages: [PURPOSE_AND_READERS]. Information needed: [INFORMATION_NEEDED]. Where messages go and how long they are kept: [HANDLING]. Spam problems: [SPAM_PROBLEMS]. Collect the minimum. Field table with label, type, required, reason and retention; error messages; a privacy notice of about 60 words under the form with a link, with placeholders for the controller's name and contact; consent wording if marketing is involved [VERIFY]; a confirmation message and an auto-reply, each under 50 words; and a response-time promise I can keep. Spam protection in three layers in order of friendliness to users (honeypot, rate limiting, a challenge only if needed) [VERIFY], with the trade-offs for users with disabilities when challenges are used. Form plugins may store submissions in the database and send by email, which affects privacy [VERIFY]. Process for deleting old messages. Test plan with five submissions (normal, empty required field, very long text, spam-like text, a message with an accented name), and a monthly check that the form still delivers and for failed deliveries.
Fill in before use
Optional: type your details and the prompt above updates. Nothing is saved or sent.
Replace each bracketed placeholder with your own details, then paste into Any AI or another assistant.