Identify
We may ask for the email, company, or request context needed to locate the relevant record safely.
Route preparation
Preparing a stable QENVEX surface
Checking the localized route and preparing only the surface needed for this request.
Route preparation
Checking the localized route and preparing only the surface needed for this request.
Last updated May 13, 2026
QENVEX handles personal data to answer project enquiries, prepare proposals, operate the authorised internal enquiry admin, and protect the public website.
Plain-language summary
This page explains the data QENVEX handles to answer enquiries, operate the protected internal admin, and protect the public site.
Each data flow is tied to a practical purpose.
Enquiry records are handled through authorised internal access.
Privacy requests follow an identification, review, and response path.
Clear purpose for each public workflow
Supabase stores authorised enquiry data
Email notifications support enquiry follow-up
Contact and commercial details submitted through the contact form, email, WhatsApp, a meeting, or another direct project enquiry.
Information needed by authorised QENVEX staff to qualify and operate an enquiry, such as name, company, role, preferred language, and delivery status.
Technical data needed to operate the site and protect it from abuse, including request metadata, security logs, and anti-spam verification signals.
To respond to enquiries, prepare proposals, clarify project scope, and communicate about a potential engagement.
To operate, secure, debug, and improve the public site, protected enquiry flow, and authorised internal admin.
To send enquiry acknowledgements, internal alerts, and commercial follow-up connected to a submitted request.
QENVEX uses hosted providers for application delivery, authentication, database operations, email delivery, and anti-abuse protection.
QENVEX uses Cloudflare for delivery and form protection, Supabase for authorised internal administration and data, and Resend for email notifications.
Providers process data only for operational purposes connected to the QENVEX website, enquiry flow, and agreed delivery work.
QENVEX keeps enquiry and operational records only as needed to respond, provide agreed services, protect legitimate business interests, and meet applicable obligations.
You can request access, correction, restriction, or deletion of your personal data where applicable. Some records may need to be retained for legal, accounting, security, or contractual reasons.
Privacy requests can be sent to contact@qenvex.com with enough context to identify the relevant enquiry or communication safely.
Requests are handled through a controlled review path so QENVEX can protect the requestor, active engagements, and operational records.
We may ask for the email, company, or request context needed to locate the relevant record safely.
QENVEX checks the request against active delivery, contractual, accounting, security, and legitimate operational obligations before acting.
Where applicable, QENVEX provides the requested response through an appropriate contact channel.
These commitments describe the current lean QENVEX product: public enquiries, protected internal administration, and deliberate provider changes.
Authorised internal access is limited to operating project enquiries and their delivery state.
The public website does not provide a client file portal or accept project file uploads.
Service-role credentials, provider tokens, and deployment secrets remain on trusted server or runtime surfaces rather than browser clients.
Material provider or data-flow changes are reviewed deliberately before they are introduced.
Contact QENVEX with the email or enquiry context connected to your request.
Contact us