Privacy & data in Corevum.
Updated 21 September 2026. DawsonyWeb is operated by Adam Dawson trading as DawsonyWeb. Contact info@dawsony.com.
Who this notice covers
This notice explains Corevum 0.7.0 Free and Pro. DawsonyWeb processes account, licensing, download and support information for its customers. A website operator using Corevum is responsible for the visitor and staff information collected on that website. Installing Corevum does not give Dawsony access to that site’s database. For an enquiry about a form submitted on another website, contact that website’s operator.
Corevum Free and external connections
Free does not require a Dawsony account and does not include a Dawsony telemetry or licence-server connection. It does not send form entries, post content or customer orders to Dawsony. This does not mean the whole WordPress site is offline: native WordPress plugin/theme updates, Gravatar avatars, your configured mail provider, other plugins and administrator-added scripts can make their own external requests. Opening a Dawsony link or downloading a release is covered by our general website privacy policy.
Forms and email notifications
Where entry storage is enabled, Corevum stores submitted field values, form identifier, timestamp, status, submitted email where available, source URL and the signed-in user ID where applicable in the site’s WordPress database. Notification emails send submitted values to the recipients chosen by the administrator through WordPress wp_mail() and the configured delivery provider. Storage and notifications are independently configurable and enabled by default. Raw visitor IP addresses are not stored in the form-entry table.
Spam prevention
Corevum reads the request IP address to calculate a salted HMAC for a temporary submission-rate counter. The counter is held in a WordPress transient with a ten-minute expiry refreshed by attempts. This pseudonymous key is used for abuse prevention, not analytics. Forms also use a honeypot and signed time check. The form module does not set a tracking cookie. Hosting, security and email services may keep separate logs.
Workspace preferences and other local data
Corevum stores settings, content definitions and user preferences in WordPress options, metadata and its own tables where appropriate. Browser local storage remembers media preferences and recent command-palette destinations, including labels and URLs. Custom field values can be available through the WordPress REST API under the applicable content permissions; they should not contain secrets. Your theme and chosen output determine what visitors see.
Client help and support reports
Pro client help stores administrator-written instructions and support details locally. Guide and video links open their providers only when clicked. Support reports are generated locally and downloaded only on administrator request; they contain versions, plugin and theme names and diagnostic flags, with no automatic transmission to Dawsony. Review before sharing.
Optional Pro logs
The activity module records selected events with times, user IDs and labels, object identifiers and summaries. Labels can include display names and login names; failed-login summaries can include the submitted username. The default retention is 90 days, cleaned through WordPress cron, and can be changed by a developer. The missing-page log stores normalised paths, hit counts and last-seen times, with periodic size-based trimming around 500 paths. It does not store visitor IP addresses or user agents in that table, but URL paths and titles can themselves identify people. These logs stay on the website unless its operator exports or shares them.
Pro licensing and updates sent to Dawsony
When an administrator activates or deactivates a Pro licence, and during subsequent scheduled validation, Pro sends the licence key, site hostname and product identifier to https://dawsony.com/api/v1/licences/ over HTTPS. Scheduled checks use WordPress cron and are normally daily. Eligible update checks send the key, site hostname and installed Pro version to https://dawsony.com/api/v1/updates/corevum-pro. Authorised package downloads are served by Dawsony using expiring signed links. The service records licence activation and last-seen information to provide subscriptions, enforce site allowances and deliver updates. These requests do not include form entries, page content or WooCommerce order/customer records. Normal network request information may also be present in hosting/security logs.
Accounts, payments and support
Buying Pro creates a Dawsony customer relationship. Stripe processes payments; licence and subscription records connect the purchase to the activated websites. Dawsony’s general privacy policy covers account details, billing identifiers, download logs, support messages, service providers, retention and privacy rights. Full card numbers are not stored by the Dawsony application. Only send support the information needed to resolve the issue, and remove credentials and unrelated visitor/customer information from screenshots and logs.
Retention, export and deletion on your website
Form entry cleanup is disabled by default. Administrators may choose a per-form limit of 30, 90, 180 or 365 days. Daily WordPress cron deletes expired entries, including spam and trash, in bounded batches while Forms is enabled. Email copies, exports and backups have separate retention. The Forms module integrates with WordPress personal-data export and erasure using the stored email address; keep the module enabled when using those tools. Entries without a matching email, email copies, exports, backups and Pro logs need separate review. Disabling a module does not erase data. Deleting the plugin retains data by default; the optional cleanup setting removes Corevum-owned data as described in the documentation. Deactivate Pro licensing before uninstalling to release the remote site activation. Uninstalling does not erase a Dawsony billing account or legally retained transaction records.
Responsibilities and contact
Before collecting information, explain your purposes, recipients, retention period and contact details to visitors and staff. Review the providers used by your own hosting, email, backups and scripts. For information Dawsony processes, contact info@dawsony.com and consult our general privacy policy for your rights and the applicable contact and complaint routes. This product notice supplements that policy; it does not replace the privacy policy of a website using Corevum.