Privacy policy

Information you share with ASKWHYWEB

When you contact ASKWHYWEB, you may share your name, email address, organisation, role, problem type, and a short description of the technology situation you want to discuss. That information is used to understand your enquiry, respond to you, and decide whether ASKWHYWEB is a useful fit for the problem.

How your enquiry is used

Your enquiry is used for communication, scoping, advisory discussion, and relevant follow-up. ASKWHYWEB does not sell personal information. If the situation involves sensitive delivery, vendor, architecture, security, customer, or operational detail, share only enough in the first message to explain the problem. Deeper evidence should wait until suitable confidential channels and engagement terms are agreed.

Analytics and contact-funnel measurement

ASKWHYWEB uses Google Analytics 4 to understand which advisory topics, service pages, FAQs, navigation paths, and calls to action help prospective clients reach the right next step. Analytics also measures the contact-form funnel so ASKWHYWEB can see whether people find the form, start it, encounter validation errors, submit it successfully, or hit a submission problem.

Contact-form analytics are limited to funnel events such as form view, form start, validation error field names, submit attempt, successful lead confirmation, or submit error. ASKWHYWEB does not send form field values, names, email addresses, company names, role text, problem descriptions, or message content to Google Analytics.

Privacy questions before you share context

If your organisation needs to clarify privacy, confidentiality, procurement, or information-handling expectations before sharing context, use the contact page and keep the first message high level. Ask the question directly and avoid including credentials, customer records, incident exports, private documents, or other sensitive material.

Contact form handling

The contact form is for business enquiries about technology advisory, delivery recovery, eCommerce stability, DevOps operations, architecture, and related leadership problems. It may ask for name, email address, company, role, problem type, and a written message so ASKWHYWEB can understand the enquiry and respond appropriately.

Use the first message for triage, not for transferring sensitive operational data. A useful first enquiry can describe that checkout fails during campaigns, a programme keeps slipping, release ownership is unclear, or architecture decisions are blocked without attaching logs, credentials, customer data, confidential reports, or private incident records.

Security and anti-spam protection

The contact form uses Cloudflare Turnstile to reduce automated spam and abuse. Turnstile may process technical signals needed to verify that a form submission is legitimate. Server-side validation and a hidden honeypot field also help reject obvious automated submissions.

Email delivery uses Resend. Form data is sent to the configured ASKWHYWEB recipient addresses so the enquiry can be reviewed. Delivery providers may process message metadata and content as needed to provide the email service.

Retention and deletion

Enquiry messages may be retained for as long as needed to respond, manage follow-up, understand the history of a discussion, or support a potential engagement. If a conversation does not continue, unnecessary enquiry information should not be kept longer than useful for normal business administration.

If you want to ask about information you submitted, use the contact page and include enough context to identify the enquiry. ASKWHYWEB will make a reasonable effort to review and respond to privacy-related requests.

Practical privacy expectations

You should expect the first contact to be handled as a professional advisory or service enquiry. ASKWHYWEB uses the information to evaluate fit, respond to questions, prepare for a useful discussion, and support legitimate business communication connected to your request.

You should also expect the first exchange to stay proportionate. The right first message gives enough business context to start the conversation without exposing unnecessary sensitive material. If deeper review is needed, information handling, confidentiality, access, evidence sharing, and responsibilities should be agreed before detailed material is exchanged.

Information shared during advisory discussions

Initial advisory discussions may include descriptions of delivery problems, production incidents, vendor relationships, eCommerce platform issues, architecture constraints, and operating model concerns. These details can be commercially sensitive even when they are not personal data. ASKWHYWEB treats that context as business enquiry information and uses it only to understand the situation, prepare a response, and discuss relevant next steps.

If a deeper engagement proceeds, confidentiality, information handling, access, documentation, and evidence sharing should be addressed in the relevant agreement or working arrangement. This is important because recovery work can involve incident reports, delivery plans, technical diagrams, vendor communications, system screenshots, and other material that should not be handled through casual channels.

Data minimisation in first contact

The best first enquiry provides enough context to understand the business problem without exposing unnecessary sensitive detail. For example, it is useful to explain that checkout fails during campaigns, a delivery programme is delayed, or DevOps ownership is unclear. It is not necessary to include credentials, full customer records, private incident documents, or system access details.

This approach protects both the person making the enquiry and the business they represent. It also helps ASKWHYWEB respond faster, because the first review can focus on fit, urgency, and the next sensible discussion rather than managing sensitive material that should have been shared through a more controlled process.

Services involved in the enquiry path

Cloudflare Turnstile supports bot protection, Resend supports email delivery from the contact form, and Google Analytics 4 supports page and event analytics. These services may process technical information, usage events, device or browser details, IP-related signals, message content where relevant to email delivery, metadata, or delivery information as needed to provide their services.

ASKWHYWEB uses these services to reduce automated abuse, ensure genuine enquiries can reach the right inbox, and understand whether prospective clients can find relevant advisory information. You do not need to create an account, submit payment data, or provide unnecessary personal information to read content or make an initial enquiry.

Confidentiality and access expectations

Privacy and confidentiality are related but not identical. A business enquiry may include personal contact information, but it may also include commercially sensitive context about delivery delays, platform instability, incidents, vendors, architecture weaknesses, or technology leadership pressure. ASKWHYWEB treats that context carefully because it can affect the organisation even when no personal data is involved.

If an engagement requires system access, documentation, incident evidence, logs, screenshots, architecture diagrams, vendor correspondence, or delivery records, access should be agreed deliberately. That agreement should define what is needed, who provides it, how it is shared, how long it is useful, and what should happen when the work ends. This keeps the advisory process controlled and avoids unnecessary exposure of sensitive operational material.

How privacy questions are handled

Privacy questions should be sent through the contact page with enough context to identify the relevant enquiry. If you are asking about information submitted through the form, include the email address, approximate date, and the nature of the request. Do not include secrets or unnecessary system details in a privacy request.

ASKWHYWEB will make a reasonable effort to respond to privacy-related questions in a practical way. If your request involves legal rights, compliance duties, procurement requirements, or jurisdiction-specific obligations, your organisation should take appropriate legal advice before sharing sensitive material or starting a formal engagement.