Security & Trust

Canadian innovation. Clear commitments.

TestLauncher is Canadian-owned. Hosting and data residency are defined for each offering and engagement. We work with innovators whose systems have real-world consequences. Security requirements, data flows, and delivery responsibilities belong in the scope of every custom engagement. bugAgent currently runs production in the US. Canadian production hosting and data residency are planned options for new clients, subject to deployment planning and agreement; they are not active in production today.

Compliance

Certifications & standards

We do not currently claim SOC 2 Type II attestation, ISO/IEC 27001 certification, or ISO 9001 certification. Discuss any required assurance evidence with us before an engagement.

  • SOC 2 Type II Not attested

    TestLauncher does not currently claim a SOC 2 Type II attestation. Discuss your assurance requirements with us.

  • ISO/IEC 27001 Not certified

    TestLauncher does not currently hold ISO/IEC 27001 certification.

  • ISO 9001 Not certified

    TestLauncher does not currently hold ISO 9001 certification.

  • Privacy obligations Engagement-specific

    Applicable privacy requirements, responsibilities, and contractual terms are reviewed for each engagement.

Product readiness matters. bugAgent is our production-ready software quality platform; its conversational capabilities are in active development and are not yet released. Launch, qualThread, ARC, and OQA are in development and are not fully released offerings. manualTesting is an available managed testing service and consultancy, not a software product. Our Canadian operating system and sovereign email initiatives are in research and development. Product plans do not constitute a compliance guarantee. See current product statuses.
Planning your engagement

Security requirements we scope

The controls and evidence needed depend on your use case, deployment, and obligations. These are topics to resolve together during discovery.

Encryption & secrets

Define encryption, key management, and secrets-handling requirements for the systems and data in scope.

Hosting & data residency

Hosting and data residency are defined for each offering and engagement. Agree on deployment locations, data flows, access, retention, and third-party services before onboarding.

Access & accountability

Scope user roles, access boundaries, and review responsibilities around the people and systems involved.

Security testing scope

Agree on testing methods, environments, evidence, and remediation responsibilities as part of the delivery plan.

Third-party dependencies

Identify vendors, integrations, and subprocessors that could affect your security or residency requirements.

Operational readiness

Establish support expectations, incident contacts, recovery requirements, and handover responsibilities before deployment.

Data protection & privacy

Our Privacy Policy describes how this website handles personal information, including third-party services. For customer engagements, discuss data ownership, processing terms, hosting locations, and subprocessors with us so the agreed scope reflects your residency requirements.

Responsible disclosure

Found a vulnerability? Please report it to security@testlauncher.com. Our machine-readable security contact is published at /.well-known/security.txt (RFC 9116). We investigate every good-faith report and will not pursue action against researchers who act responsibly.

Accessibility

We are committed to making testlauncher.com usable by everyone and aim to conform to WCAG 2.2 Level AA. The site uses semantic HTML, keyboard-navigable controls, visible focus states, sufficient color contrast, and respects reduced-motion preferences. If you encounter a barrier, email hello@testlauncher.com and we'll work to fix it.