What DocuMerge collects
For every submission, the plugin stores:
- The values of every form field
- The submitter’s email (if collected by a form field)
- The submitter’s IP address
- The browser’s user-agent string
- The referring URL (which page the form was embedded on)
- The timestamp of submission
All of this is stored in a database table (wp_wprdm_submissions or prefix variant) on your own WordPress installation.
Where files are stored
Generated documents are stored at /wp-content/uploads/wprobo-documerge-lite/documents/. The directory is protected by .htaccess rules that block direct HTTP access. Files are served through authenticated download handlers.
Nothing leaves your server
DocuMerge Lite never sends submission data or generated documents to third-party services. No Google fonts, no external analytics, no API calls to WPRobo. Everything stays on the WordPress site where the plugin is installed.
(Pro adds optional Stripe payment integration, which does send payment data to Stripe’s API โ this is clearly marked in the Pro documentation.)
GDPR compliance
For EU/UK businesses:
- Lawful basis: Typically “contract” (you’re producing a document the user requested) or “legitimate interest”. Document your choice in your privacy policy.
- Privacy policy: Add a note that form submissions are stored on your own server and used only to generate the requested document.
- Data retention: Use Settings โ Advanced โ Auto-delete documents after to enforce a retention policy (e.g. 90 days).
- Subject access request: Search submissions by email address at DocuMerge โ Submissions to find and export all data for one person.
- Right to erasure: Delete the submission from the Submissions screen โ this removes both the database record and the generated document.
Exporting data
Use the Export CSV bulk action on the Submissions screen to export one or many submissions for subject-access requests.
Logs
If debug logging is enabled, plugin logs may contain form data. Logs live at /wp-content/uploads/wprobo-documerge-lite/logs/ and are auto-purged after 30 days by default. Disable debug logging in production unless actively troubleshooting.
