A little information. A clear purpose.
This policy explains how the G.G. Marshall website handles information when you subscribe, send a message, comment on a blog post, or use the Like feature. For privacy questions or requests about your information, use the contact page.
Newsletter subscriptions
The newsletter asks for your first name, last name, email address, and consent to receive author updates. FluentCRM manages these records within this website’s WordPress database. Records include your contact details, subscription status, list membership, and related subscription and confirmation information. If your email matches an existing WordPress account, FluentCRM can associate the subscriber record with that account.
Signup information is first placed in a private scheduled processing job in the website database. The job contains your name, email address, consent selection, and processing details. It becomes ineligible for processing after 30 minutes; removal depends on scheduled processing running, so this is not a guaranteed deletion deadline. These jobs are separate from the subscriber records in FluentCRM.
Subscriptions use double opt-in: you must confirm by email before receiving marketing newsletters. FluentCRM records confirmation information, including the IP address used to confirm. Every newsletter includes an unsubscribe option. Unsubscribing changes your subscription status; it does not automatically erase your contact record.
FluentCRM supports recording email opens and tracked-link clicks when those features are enabled. These records can associate activity and technical information with a subscriber and campaign. An email-open record does not necessarily mean a person read the email, because email software can load images automatically.
Contact messages
The contact form asks for your name, email address, reason for writing, and message so G.G. can receive and respond to your inquiry. Sending a message does not subscribe you to the newsletter.
The form sends this information through WordPress’s email function and FluentSMTP to the configured receiving mailbox. Your validated email address is used as the Reply-To address. The custom forms plugin does not keep a separate contact-message archive, but copies and delivery information can remain in email logs, the email delivery service, and the receiving mailbox.
Blog comments
WordPress stores your display name, email address, comment, submission date, and moderation information. It also records technical information such as your IP address and browser user-agent. A comment submitted while signed into WordPress may be linked to your account.
Approved comments show your display name, comment, and date publicly. The custom comment interface does not display your email address or IP address. Please do not include information in a comment that you do not want others to see. Comments are subject to WordPress moderation; comment notifications may also be emailed to site administrators when enabled.
Blog likes
Viewing a blog article can set a cookie called ggm_reader, even if you do not click Like. It contains a signed random browser identifier and is configured to expire after one year. The website uses it to remember likes and help limit repeated actions.
A like is stored with the post identifier and a hashed browser identifier, without asking for your name or email address. Visitors see a total count, not a list of those identifiers. Removing a like from the same browser deletes that vote; deleting a post removes its votes.
Stored likes do not expire automatically. Clearing or expiring the cookie does not delete a stored vote and can prevent the website from recognizing it as yours.
Spam protection and technical information
Cloudflare Turnstile helps protect contact, newsletter, and comment submissions from automated abuse. Verification sends an IP address and a verification token to Cloudflare. Its browser widget also processes browser and connection signals. The widget can load before a form is submitted, including where a newsletter form appears in the footer.
Cloudflare explains its processing, including use of information to improve Turnstile, in its Turnstile Privacy Policy.
The website also limits repeated submissions. Its custom rate-limit records contain keyed hashes, counters, and expiry information rather than raw email addresses or IP addresses. Expired records are removed through scheduled cleanup. This does not prevent IP addresses from appearing in other records, such as comments, confirmation records, or hosting logs.
Cookies and subscriber links
In addition to the Like cookie, FluentCRM confirmation and subscription-management links can set a subscriber-recognition cookie called fc_hash_secure, configured for 90 days. When link tracking and its cookies are enabled, tracked links can also set fc_cid, configured for 28 days. These cookies can associate a browser session with a subscriber or campaign.
You can manage or delete cookies through your browser settings. Doing so may affect features such as remembering a like or recognizing a subscription-management session.
Hosting and email services
The website is hosted by Hostinger. FluentCRM stores subscriber records in the website’s WordPress database; it is not a separate hosted subscriber database for this integration.
FluentSMTP connects WordPress to the configured email delivery provider. That provider processes recipient and sender addresses, message content, and delivery information to send website emails. The receiving mailbox provider also processes and can retain incoming contact messages and replies.
Depending on logging settings, FluentSMTP can store email addresses, subjects, message bodies, headers, delivery results, and other delivery details in WordPress. Failed messages can be logged even when logging of successful messages is disabled. The delivery provider can also retain delivery records according to its service and account settings.
Data retention
Information is stored in different systems, with different removal mechanisms:
- Subscriber records remain in FluentCRM until removed. Unsubscribing alone does not delete them.
- Temporary signup jobs and rate-limit records use expiry rules and scheduled processing or cleanup. A delayed scheduler can delay their removal.
- The custom plugin adds no automatic deletion schedule for WordPress comments or stored likes. Comments remain subject to WordPress moderation and deletion settings; likes can be removed as described above.
- Contact emails, email logs, delivery records, hosting logs, and backups depend on the relevant system’s retention settings and administrative deletion. Removing information from the active website does not necessarily remove existing backup or mailbox copies.
Privacy questions and requests
You can unsubscribe using the link in a newsletter. To ask about accessing, correcting, or deleting information associated with you, including subscriber records or comments, use the contact page. Please identify the information your request concerns without sending passwords or other unnecessary sensitive information.