Privacy information for website visitors and enquiries

Information we may collect

• Contact details you submit through email, booking forms, or direct enquiries
• Business information you choose to share during a consultation or discovery call
• Basic website usage information such as page visits and interaction data

How information is used

• To respond to your enquiry or schedule a consultation
• To understand your workflow and propose suitable services
• To improve the website and communication process over time

Data handling

Information may be processed through the tools used to run the website, communication channels, scheduling, CRM workflows, and operational systems.

If you need a service-specific or region-specific privacy clarification, contact Qanvex directly so the latest details can be shared with you.

Cookies and analytics (high level)

Like most marketing sites, Qanvex may use basic analytics to understand which pages are useful and where visitors drop off. This is used to improve content, navigation, and enquiry flow.

If you have a strict privacy requirement (for example, a regulated industry policy), mention it before onboarding and we will adapt the approach where possible.

• Traffic and page usage patterns (which pages are viewed, what content is popular)
• Performance signals (slow pages, broken links, or UX issues)
• Attribution context (which channel brought the visit, when available)

Third-party tools

Qanvex is an implementation partner. Many projects involve third-party platforms such as CRMs, booking tools, email providers, WhatsApp tooling, invoicing tools, or analytics providers. Those services have their own privacy practices and terms.

• You remain the owner of your accounts and subscriptions
• Access is requested only when needed for implementation
• If you want a processor list for your specific engagement, request it during onboarding

Data minimisation (practical approach)

You do not need to share sensitive customer records to start a workflow review. In early conversations we can work from process descriptions and tool lists. When real implementation begins, we confirm what data is actually required and keep it as lean as possible.

• Share workflow steps and tool names first, not private client datasets
• Use sample records when possible for testing and configuration
• Limit permissions to what is required for the agreed scope

Practical note for SMEs

Most Qanvex engagements involve workflow and systems discussions. If you share operational details during a consultation (lead sources, CRM setup, quoting flow), the information is used to scope the work and recommend the right next step.

If you need a specific clarification about what data is required for a service setup, ask during the call and we will explain it in plain terms.

If you want to limit what you share

You can start with a high-level description of your workflow without sharing sensitive client data. The goal of early conversations is to understand the bottleneck and recommend the right starting point.

• Describe your lead sources and response flow at a process level
• Share tool names and handoff steps, not private customer records
• Confirm any specific privacy requirement before onboarding begins