Privacy policy

Information you provide

If you contact ASKWHYWEB, the information you provide may include your name, email address, organisation, role, and details about the technology problem you want to discuss. This information is used to respond to your enquiry and understand whether ASKWHYWEB can help.

How information is used

Enquiry information is used for communication, scoping, advisory discussion, and follow-up related to your request. ASKWHYWEB does not sell personal information. Sensitive technology, delivery, vendor, or operational details should be shared only through appropriate confidential channels once an engagement is agreed.

Website analytics and cookies

The website may use basic analytics or server logs to understand page usage, performance, and technical issues. If additional analytics, advertising, or tracking tools are introduced, this policy should be updated to describe them clearly.

Questions

For privacy questions, contact ASKWHYWEB through the contact page. This policy is informational and should be reviewed with legal advice if the business requires formal compliance coverage for a specific jurisdiction.

Contact form handling

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

The first form message should not include passwords, access tokens, private customer records, confidential documents, or production secrets. If an engagement requires sensitive technical evidence, that material should be shared later through agreed confidential channels. The form is for initial triage, not for transferring sensitive operational data.

Security and anti-spam protection

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

Email delivery is designed to use 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. Real credentials are configured through environment variables and should never be committed to the repository.

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

ASKWHYWEB does not sell submitted enquiry information. Initial contact is handled as a professional advisory or service enquiry. Information is used to evaluate fit, respond to questions, prepare for discussions, and support legitimate business communication.

This policy may be updated as the site, analytics, contact tooling, or operational needs change. Any future use of additional tracking, advertising, CRM, analytics, or automation tools should be reflected here so visitors understand how their information is handled.

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.

Third-party services used by the website

The website is designed to use Cloudflare Turnstile for bot protection and Resend for email delivery from the contact form. These services may process technical information, message content, metadata, IP-related signals, or delivery information as needed to provide their services. Their own privacy and security practices apply to the parts of the workflow they operate.

ASKWHYWEB uses these services for practical reasons: to reduce automated abuse and to ensure genuine enquiries can reach the configured recipient inbox. The site does not need visitors to create accounts, 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. Where a request involves legal rights, compliance duties, or jurisdiction-specific requirements, the business should take appropriate legal advice. This website policy is written to explain the intended handling of enquiries, not to replace formal legal documentation for every possible jurisdiction.