Last substantive review: September 4, 2026.
Information you submit
The public site does not currently offer reader accounts. If you use the contact form, we store the name, email address, subject, and message you provide. The authenticated editorial team uses those details to review and answer the inquiry.
Security and abuse prevention
The form may store a one-way hash derived from the submitting IP address. This helps find repeated abuse without keeping that address in the message record. Hosting and security systems may separately process standard request logs, including IP address, user agent, requested URL, and timestamp.
Cookies and analytics
Essential session and security cookies support sign-in, SEO tools, form checks, and administrative access. The site also stores your choice in the site_cookie_consent cookie for up to 180 days. Google Analytics is not loaded unless you select “Allow analytics.” If permitted, Google may set measurement cookies such as _ga so we can understand which pages and tools are useful. Advertising storage and ad personalization remain disabled.
Retention and sharing
Contact information is retained only while reasonably needed to handle the inquiry, maintain editorial records, prevent abuse, or meet legal obligations. We do not sell contact-form data. It may be processed by hosting or security providers acting on the site's behalf, or disclosed when legally required.
External links
Other websites have their own privacy practices. Following an external or affiliate link transfers you to that provider's service and policy.
Privacy requests
Use the contact form to request access, correction, or deletion of information you previously submitted. Provide enough detail to find the message without sending extra sensitive data.
Why only necessary contact data is requested
The contact form is for editorial communication. So the message should contain only the information needed to understand and answer the request. Passwords, payment details, government identifiers, and other highly sensitive information are not needed for that purpose and should not be submitted.
Operational data
Hosting and security systems can process standard request information separately from the contact-form record. This may include an IP address, user agent, requested URL, and timestamp. Those records support normal delivery, security, and abuse prevention. The form may use a one-way hash derived from the submitting IP address. This can help find repeated abuse without storing the address in the message record.
Changing your cookie choice
After making a choice, use the “Cookie controls” link at the bottom of any page to reopen the notice. Choosing “Essential only” prevents Google Analytics from loading on later page views and removes Google Analytics cookies accessible to this domain. Information already transmitted after earlier consent is handled under Google’s privacy terms.
Retention and access requests
Contact information is kept only while it is reasonably needed for the inquiry, editorial records, abuse prevention, or legal obligations. A privacy request should include enough information to locate the message. But it should not introduce new sensitive data simply to prove that the message exists.
External services
When you follow a link away from SEO Strategy, the destination site applies its own privacy practices. Review that provider's terms and policy before submitting information there.
Privacy basics
- Send only the data needed for your message.
- Do not send passwords or payment details.
- Essential systems may process request logs.
- Contact data is not sold.
- External sites apply their own privacy rules.
For a privacy request
Use the contact form and describe the message you want us to find. Give enough detail to find it. Do not add passwords, payment data, or other sensitive details just to prove the request is yours.
Simple data rules
- Share only what is needed.
- Do not send private account data.
- Check third-party rules before sharing data there.
- Use the contact form for a privacy request.