The essentials
- The inquiry form validates required fields and only reports success after the delivery service accepts a message.
- Product security depends on the actual release, configuration, and deployment.
- This site does not claim certifications, independent audits, or a guaranteed response time.
Website inquiry safeguards
The default inquiry flow prepares a draft in your own email app and requires you to send it there. When website delivery is configured, the contact endpoint checks field types and length limits, email format, privacy consent, and a bot-trap field. Requests declaring a different origin are rejected and server-side delivery uses HTTPS.
Delivery credentials stay on the server. If delivery is unavailable or fails, the form does not claim that a message was delivered. These application checks are not a security certification.
Evaluate a deployment, not an illustration
Before using a product for business transactions or source code, discuss the exact release and environment. A diagram or feature description cannot confirm an implementation's security properties.
Ask who operates the service, who can access its data, how changes are applied, and what responsibilities remain with your team.
Questions to cover before production
Discuss authentication, authorization, user roles, encryption, storage location, backups, recovery, update delivery, logging, supported integrations, and data export or deletion.
For Quantum Lite, include devices and payment handling in the review. For Terminus, include filesystem permissions, process execution, extension access, and any model or network service used by intelligence features.
Reporting a potential vulnerability
Email apexsupportcenter@gmail.com with a subject identifying a security concern and the affected page or product. Give a concise description, observed impact, and safe reproduction steps.
Do not include credentials, exploit payloads containing sensitive information, customer data, or private source code in the initial inquiry. Ask the team to agree on a suitable channel before sharing sensitive evidence.
Responsible testing boundaries
Only assess systems you have permission to test. Avoid accessing another person's information, disrupting availability, changing live records, or continuing beyond what is necessary to report the observation.
Submitting a report does not authorize additional testing or imply participation in a bounty program. A public bounty program and response schedule have not been announced here.
Documentation and follow-up
Ask for current, product-specific security documentation during evaluation. This website does not claim a security certification, compliance approval, or independent audit for the company or its products.
The company support email is available through the contact page for initial reports. A dedicated emergency reporting service or guaranteed security response schedule has not been published on this website.
Need a little more clarity?
Explore the related notices or ask the team about the specific product and deployment you are considering.
Contact Apex Tech Labs