Legal

Privacy Policy

Last updated 25 August 2026. This policy explains how SecureCoding (we, us) handles personal data on https://www.securecoding.com. It replaces older text on this URL that named White Source Ltd. That company does not operate this Site.

About Contact Terms Privacy Cookies

1. Who is responsible

SecureCoding is the publisher of the Site. Privacy mail: contact@securecoding.com. If the law requires a postal address, ask and we will provide one.

2. What we collect and why

Contact form and email. Name, email, subject, and message so we can answer you. Legal basis: our legitimate interest in running the desk, or your request before a contract. We do not add you to a newsletter unless you ask in the same message.
Server and security logs. IP address, user agent, referrer, path, and time, kept by our host and CDN to operate the Site, stop abuse, and debug outages. Legal basis: legitimate interest in a working, safe host.
Cookies and analytics. Described in the Cookie Policy. Necessary cookies run the form and the CDN. Google Analytics (measurement ID G-HGYG6TREKW) counts visits and page views. We do not sell a marketing list.
Comments or account data. If a WordPress account exists for an editor, we store the usual WordPress profile fields. Public visitors do not need an account to read.

We do not knowingly collect data from children under 16. If you believe we have, write and we will delete it.

3. What we do not do

We do not sell personal data. We do not share it for cross-context advertising. We do not use a contact message to train a public model. We do not ask for passwords, lockfiles with tokens, or production dumps. If you paste a secret, treat it as exposed and rotate it; we will delete the message when we see it.

4. Who processes data for us

We use processors that must handle data only on our instructions:

Kinsta, for WordPress hosting.
Cloudflare, for DNS, TLS, and edge cache (including a bot-management cookie).
WP Rocket / RocketCDN, for caching and static files.
Google Analytics, for visit and page-view counts (gtag G-HGYG6TREKW).
The email path that delivers Contact Form 7 messages to contact@securecoding.com.

Those vendors have their own privacy notices. We do not control a third-party page you open from a link in an article.

5. How long we keep it

Contact messages: up to 24 months after we close the thread, unless a legal claim needs them longer. Server logs: the host’s default, typically 30 to 90 days, unless an abuse investigation is open. Published articles are kept while the Site exists. Backups follow the host’s retention.

6. Your rights

If GDPR, UK GDPR, or a similar law applies to you, you may ask to access, correct, delete, or export your personal data, or to object to or restrict some processing. If CCPA / CPRA applies, you may ask what we collected and to delete it; we do not sell or share personal information as those statutes define those words. Send the request to contact@securecoding.com from the address we should reply to. We may need to confirm it is you. You may complain to your supervisory authority. We will not discriminate against you for exercising a right.

7. International transfers

The Site is served from hosts that may store data in the United States or the European Union. If we transfer data out of the EEA or UK, we rely on the vendor’s lawful mechanism (such as standard contractual clauses) or on a transfer that is necessary to answer your request.

8. Security

We use TLS, access control on WordPress, and a small editor set. No method is perfect. Do not send material you cannot afford to have logged.

9. Changes

We will post a new date on this page when the policy changes. Material changes that affect rights already in play will also be noted in the first paragraph.