Identify
We may ask for the email, workspace account, company, project, or request context needed to locate the relevant records safely.
Loading secure project, delivery, and launch evidence surfaces.
Loading secure project, delivery, and launch evidence surfaces.
Monthly notes on nearshore engineering teams, CAD and documentation quality, delivery controls, and QENVEX launch updates.
Last updated May 13, 2026
QENVEX handles personal data to answer enquiries, operate the client workspace, deliver digital and technical services, and protect the platform.
Clear purpose for every workflow
Hosted Supabase project data
Transactional email and CRM processing
Contact and commercial details submitted through forms, quote estimates, team configurator requests, email, WhatsApp, or meetings.
Workspace account data such as name, company, role, preferred language, project access, support history, uploaded files, invoices, and notifications.
Technical data needed to operate the site and protect it from abuse, including session cookies, security logs, request metadata, and anti-spam verification signals.
To respond to enquiries, prepare proposals, create project scopes, manage engineering delivery, provide workspace access, and support active clients.
To operate, secure, debug, and improve the QENVEX platform, including authentication, file access, invoice delivery, support requests, and admin workflows.
To send transactional emails, internal alerts, workspace notification emails, project updates, and commercial follow-ups connected to a submitted request or active engagement.
QENVEX uses hosted service providers for secure application delivery, authentication, database operations, file storage, email delivery, CRM handoff, scheduling, and anti-abuse protection.
Current production services include Supabase, Cloudflare, Resend, HubSpot, Cal.com, and related infrastructure providers used to deliver the platform.
Providers process data only for operational purposes connected to the QENVEX platform and client delivery workflows.
We keep lead, project, invoice, support, and workspace records for as long as needed to provide services, maintain audit history, satisfy contractual obligations, and protect legitimate business interests.
You can request access, correction, export, restriction, or deletion of your personal data where applicable. Some records may need to be retained when required for legal, accounting, security, or contractual reasons.
Privacy requests can be sent to contact@qenvex.com with enough context for us to identify the relevant record or workspace account.
Requests are handled through a controlled review path so QENVEX can protect the requestor, active clients, workspace records, and project evidence.
We may ask for the email, workspace account, company, project, or request context needed to locate the relevant records safely.
QENVEX checks the request against active delivery, contractual, accounting, security, and legitimate operational obligations before acting.
When applicable, QENVEX provides access, correction, export, restriction, or deletion response details through an appropriate contact channel.
These operational commitments align the privacy page with the product controls already present in the workspace, admin console, exports, and Trust Center.
Admin exports are protected behind trusted admin access and include evidence manifests so sensitive packages can be handled deliberately.
Workspace and admin file routes re-check access before serving private project and invoice files.
Service-role credentials, provider tokens, and deployment secrets stay on trusted server/runtime surfaces rather than browser clients.
Subprocessor usage is documented in the Trust Center and should be reviewed again before material provider or data-flow changes.
Contact QENVEX with the email or workspace account connected to your request.
Contact us