Trust Center – FAQ

Last updated: 16 April 2026

This Trust Center explains how Razer QA Companion‑AI handles security, data protection, confidentiality, and AI usage. Information provided in this Trust Center is for general informational purposes only.

It is intended to provide transparency for customers evaluating or using the service.

  1. 1. What is Razer QA Companion‑AI?

    Key capabilities include:

    1. Performance tracking (FPS, CPU, GPU, memory)
    2. AI‑generated test case suggestions
    3. Vision‑based bug detection from gameplay footage
    4. AI‑assisted bug reporting with Jira integration

    Razer QA Companion‑AI augments human QA but does not replace human review or decision‑making. Outputs are probabilistic and should be reviewed by qualified personnel.

  2. 2. What data does Razer QA Companion‑AI process?

    For the purposes of this Trust Center, "Customer Data" means gameplay footage, telemetry, QA artifacts, and configuration data processed within a customer’s Razer QA Companion‑AI environment.

    Depending on configuration, this may include:

    1. Gameplay videos and screenshots
    2. Studio‑defined telemetry and test events
    3. Optional design documentation used for testing rules
    4. Limited operational diagnostics for service reliability

    Razer QA Companion‑AI is not designed to process player or consumer personal data or live player accounts.

  3. 3. How is customer data isolated and protected?

    Key protections include:

    1. Private tenant isolation designed to prevent cross-customer access or data mixing
    2. Encryption in transit and at rest
    3. Role‑based access controls and least‑privilege access
    4. Audit logging of access and administrative actions

    Unreleased game builds and assets are treated as confidential and protected accordingly.

  4. 4. Who can access customer data?

    Access to Customer Data is restricted to authorized systems and, when required, authorized Razer personnel.

    Employee access is:

    1. Role‑based and restricted to certain job functions only
    2. Authenticated with SSO and multi‑factor authentication
    3. Logged and monitored
    4. Permitted only for support or operational reliability

    There is no routine or unrestricted access to Customer Data.

  5. 5. How long is customer data retained?

    Razer QA Companion‑AI is designed to minimize data retention while supporting service operation.

    1. Frontend processing: Gameplay footage processed through the frontend is handled transiently for analysis and review and is typically deleted within 24 hours.
    2. Backend data: Gameplay footage, processed QA artifacts, telemetry, and configuration data may be retained for a limited period, up to 90 days by default, to support service reliability.
    3. Operational logs: Limited metadata and logs may be retained for security monitoring and system integrity, but do not include reusable gameplay footage.
    4. Deletion: Customers may request earlier deletion of backend Customer Data, subject to technical and/or legal requirements.
  6. 6. How is customer data used, including for AI?

    Customer Data is not shared across customers.

    Depending on configuration, certain data may be used within a customer’s private tenant environment to support service functionality or limited model improvement. Any such use does not transfer control of Customer Data to Razer.

    Where available, customers may opt out of specific data uses related to model improvement.

  7. 7. Are third parties or integrations involved?

    Razer uses third‑party infrastructure providers solely to operate the service. These providers do not independently analyze or access Customer Data.

    Jira Integration

    1. Uses scoped permissions aligned with enabled features
    2. Supports Jira Cloud and Jira Data Center
    3. Designed to operate on QA artifacts, not player personal data
  8. 8. How do you handle security incidents?

    Razer maintains an incident response process covering:

    1. Detection and containment
    2. Investigation and recovery
    3. Notifications aligned with applicable obligations

    Razer also implements preventive controls (encryption, isolation, access controls, logging) to help reduce incident risk.

  9. 9. What control do customers have over their data?

    Customers retain control over their Customer Data, including:

    1. Requesting deletion
    2. Managing retention (where configurable)
    3. Selecting available data‑use controls by tier or configuration

    This Trust Center will be updated from time to time as practices and capabilities evolve.

  10. 10. Do you have security certifications?

    Razer QA Companion‑AI does not currently maintain formal third‑party security certifications. However, controls are designed and periodically reviewed to align with enterprise security standards. The pursuit of certifications is part of the roadmap.

  11. Contact

    For trust, security, or data‑related questions:

    qac-support@razer.com