Privacy Policy
How Quantum QA handles account data, configuration, hosted reporting metadata, and customer evidence links.
Customer policy
Last updated June 29, 2026. Enterprise, regulated, or custom-service work may use additional signed terms.
These policies are provided for transparency and onboarding. They are not a substitute for legal advice, and final commercial agreements may include additional terms for enterprise, regulated, or custom-service engagements.
1. Information We Collect
Quantum QA may collect account information such as name, email address, workspace membership, role, plan status, and authentication metadata.
The product may also collect project and product configuration, selected capabilities, generated Test Pack metadata, reporting summaries, run labels, evidence links, posture scores, release-confidence signals, and integration status.
2. Customer Configuration and Secrets
Customers may configure environment variables, webhook URLs, Xray or Jira settings, CI information, and other integration details. Secrets should be stored only in supported secret-management fields or customer CI secret stores.
Generated tests are designed to sanitize sensitive values in evidence where practical, but customers remain responsible for reviewing generated artifacts, CI logs, and third-party reports before broader distribution.
3. How We Use Information
We use collected information to operate the service, generate frameworks and Test Packs, enforce plan limits, provide reporting dashboards, support customer onboarding, improve product quality, and investigate security or reliability issues.
We may use aggregated or de-identified product usage signals to improve Quantum QA features, reliability, and customer readiness.
4. Third-Party Services
Quantum QA may integrate with providers such as Supabase, Stripe, GitHub, GitLab, Azure DevOps, Slack, Microsoft Teams, Jira, Xray, Allure hosting, and object storage providers selected or configured by the customer.
Information sent to third-party services is subject to those providers' terms and privacy policies. Customers should configure third-party integrations according to their own security and compliance requirements.
5. Hosted Evidence Retention
Quantum QA may retain hosted reporting metadata and evidence links according to the selected plan, trial limits, or customer agreement. Customers can download customer-owned artifacts from their repositories, CI systems, or configured storage providers.
Deleting a workspace, project, or subscription may limit access to hosted reporting history, but external artifacts may remain in customer-controlled systems.
6. Security
We use reasonable administrative and technical controls appropriate for the service and customer agreement. No online service can guarantee absolute security.
Customers should avoid submitting production secrets, protected health information, regulated records, or confidential client data unless a separate agreement and security review authorize that use.
7. Your Choices
Customers may request updates to account information, workspace access, billing status, or onboarding configuration through the product or contact page.
Customers may also request deletion or export of certain hosted metadata, subject to legal, security, billing, and operational retention requirements.
8. Contact
Privacy questions, security concerns, and enterprise data-handling requests can be sent through the Quantum QA contact page.