Privacy
Privacy policy
A practical account of what the ASKWHYWEB website collects, where an enquiry goes, which services are involved and how to request changes to information you have submitted.
What this policy covers
This policy covers information handled through the ASKWHYWEB website, especially the contact form. It also explains the limited technical processing needed to deliver and protect the site. It does not attempt to describe information handling under a future advisory engagement; any engagement-specific confidentiality, access or record-handling requirements should be agreed as part of that scope.
Last updated: 12 October 2026.
Information you provide through the contact form
The contact form asks for your name, work email, the type of technology problem and a message. Company and role are optional. The message guidance asks for enough context to understand the situation, such as business impact, systems or teams involved, urgency and the decision you need to make.
The form deliberately does not ask for passwords, payment details, customer records, access tokens or private incident evidence. Please do not include those in an initial enquiry.
What happens when you submit an enquiry
Your form submission is sent to the ASKWHYWEB contact endpoint for validation. The current website code checks required fields and message limits before the enquiry is accepted.
Cloudflare Turnstile is used to distinguish legitimate submissions from automated abuse. The verification token is checked server-side and the requesting IP address may be supplied to Cloudflare as part of that verification process.
After successful verification, the enquiry fields are sent through Resend so the message can reach the configured ASKWHYWEB email recipients. The current website application does not write contact-form submissions into its own application database.
Why the information is used
- To understand the technology problem or decision described in your enquiry.
- To decide whether the enquiry is a sensible fit for ASKWHYWEB and what kind of conversation may be useful.
- To reply to you and manage relevant follow-up.
- To protect the contact route from automated or abusive submissions.
- To maintain ordinary business records if a discussion progresses.
ASKWHYWEB does not sell contact-form information and the current site does not use it to build advertising audiences.
Analytics, cookies and technical information
The current website application does not include optional advertising trackers or optional analytics scripts. Cloudflare Turnstile may use technical signals required to perform security verification. Hosting, network and security providers may also process ordinary request information needed to serve and protect the website.
If the website later introduces additional analytics or marketing technologies, this policy should be updated before those changes are treated as part of the normal site experience.
Services involved in processing
Cloudflare Turnstile is used for contact-form security verification. Resend is used to deliver a validated enquiry by email. The website's hosting and network providers necessarily process technical requests required to make the site available.
Those providers operate under their own service and privacy terms. Processing may occur outside your own country depending on the infrastructure used by those providers.
Retention
The website does not publish a fixed retention period for enquiries. A successfully delivered enquiry may remain in the relevant email accounts or email-delivery records while it is reasonably needed to respond, manage a discussion, maintain business records or meet an applicable obligation.
If a formal advisory engagement begins, the handling and retention of engagement records may be governed by the agreement for that work rather than by this website policy alone.
Confidential, customer or security-sensitive information
An initial enquiry should describe the problem without attaching secrets or production evidence. Do not send credentials, API keys, payment information, customer datasets, private logs, unpublished vulnerability details or material you are not authorised to disclose.
If a useful review requires sensitive evidence, agree the appropriate confidentiality, access and information-sharing arrangements first. The contact page is intended to start that conversation, not to act as a secure evidence repository.
Access, correction and deletion requests
If you want to ask what enquiry information ASKWHYWEB holds about you, correct something you submitted or request deletion where applicable, use the contact page. Include enough detail to identify the original enquiry without sending additional sensitive data.
Your legal rights can depend on where you are located and the circumstances in which information is handled. This page describes the website's current handling rather than attempting to replace rights provided by applicable law.
External links and policy changes
The website links to third-party destinations such as LinkedIn. Once you follow an external link, that provider's own privacy practices apply.
This policy should be updated when the website's collection, analytics, contact delivery or material third-party processing changes. The date above indicates the version currently published.
Related
Useful next pages
Contact ASKWHYWEB
Start with the business problem and avoid sending sensitive technical evidence until the right handling route is agreed.
Book a consultationTerms of use
Understand the difference between public website guidance, an enquiry and a separately agreed advisory engagement.
Read the termsAbout Farhan Islam
See the lead advisor, professional background and the operating areas behind ASKWHYWEB.
About the advisor