Contact Form 7 is a reasonable starting point for GDPR: out of the box it emails each submission and stores nothing. Most of the risk comes from what gets added around it, such as storage plugins that keep everything forever, IP logging and third-party spam checks. Work through this list for each form.
1. Ask only for what you need
GDPR's data-minimisation principle, Article 5(1)(c), says to collect only what's necessary for the purpose. A general enquiry form rarely needs a phone number, a company name and a postal address. Every field you drop is data you never have to protect or delete.
2. Know your lawful basis
Replying to someone who wrote to you doesn't usually need a consent checkbox. Answering an enquiry is normally covered by legitimate interests, or by steps before a contract if they're asking for a quote (Article 6(1)(f) and 6(1)(b)). Consent matters when you want to do something extra, such as adding them to a mailing list. Then use CF7's [acceptance] tag, leave it unticked by default and say exactly what they're agreeing to.
3. Link your privacy policy at the form
Article 13 says to tell people what you'll do with their data when you collect it. A one-line link to your privacy policy beside the submit button does that. The policy should say what you store, for how long and who else receives it.
4. Decide whether to store submissions at all
If the email is enough, don't add a storage plugin. If you do store them, Contact Form 7 lets you opt individual forms out: add do_not_store: true to a form's Additional Settings, or add an [acceptance] checkbox with the consent_for:storage option so visitors choose. Flamingo and The Bonnie Situation honour both. CFDB7 doesn't. Does Contact Form 7 save submissions? →
5. Don't store IP addresses you don't use
An IP address is personal data. Flamingo stores the sender's IP and user agent with every message by default. If you don't use them for anything, don't keep them. The Bonnie Situation stores no IP, user agent or referrer unless you turn them on, and Bonnie Pro can store a masked IP instead of the full address.
6. Set a retention period and enforce it
Article 5(1)(e) says to keep personal data no longer than you need it. Pick a window, write it in your privacy policy, and make deletion automatic so it doesn't depend on someone remembering. How long to keep submissions and how to auto-delete them cover both halves.
7. Be ready for access and erasure requests
People can ask for a copy of what you hold about them, or ask you to delete it. WordPress has tools for both under Tools → Export Personal Data and Erase Personal Data, but they only find submissions if the storage plugin hooks into them. The Bonnie Situation supports both. Flamingo supports erasing but not exporting, and CFDB7 supports neither, so requests have to be handled by hand. See the comparison →
8. List the third parties
Contact Form 7 can send submissions to other services. Its reCAPTCHA integration sends visitor data to Google, its Akismet integration sends the message to Automattic for spam checking, and your SMTP or email provider handles every notification. Name each one in your privacy policy. If a form needs a cookie or script that isn't essential, your cookie consent applies to it too.
9. Protect what you keep
Limit who can see submissions in WordPress, use strong logins, and remember that backups and staging copies contain every stored submission. Bonnie Pro can encrypt names, emails and form fields in the database, with the key kept in wp-config.php, so a leaked database or backup can't be read on its own.
10. Clear out what's already there
Plugins you tried years ago may still hold every submission they ever stored, because neither Flamingo nor CFDB7 removes its data on uninstall. Here's where to look.
This is general information, not legal advice. For your specific obligations, talk to someone qualified where you operate.