Back to Matrix QA
Policy / 02

Privacy Policy

A clear map of the information Matrix QA handles — from account identity and test evidence to AI processing, storage, analytics, and deletion.

Effective 1 September 2026
This policy is written for clarity and accountability. If you have a question about how it applies to your account or organization, contact support@trlabs.tech.

Who we are

This Privacy Policy explains how Tr Labs, operating Matrix QA, collects and uses information when you visit the site, create an account, use the console, run an authorized test, receive notifications, or contact support. It applies worldwide, subject to mandatory local law.

OperatorTr Labs
Address15 Marina Road, Lagos Island, Lagos State, Nigeria, 101001
Privacy contactsupport@trlabs.tech
DPOTr Labs has not appointed a Data Protection Officer

Information we collect

We collect account information such as email address, full name, password hash, verification status, account identifiers, organization memberships, and timestamps. We also collect organization, workspace, project, feature, target URL, test mode, mission instructions, access settings, authorization confirmations, run status, timestamps, errors, retries, and metadata.

Runs can generate screenshots, browser events, page URLs, console and network observations, logs, audit logs, test steps, assertions, findings, reports, videos, artifacts, and evidence storage keys. Optional test credentials are stored in encrypted form by the backend when provided. Use dedicated test accounts and avoid production secrets.

We may receive technical information such as IP address, browser and device details, timestamps, API activity, authentication events, security events, rate-limit events, referrer information, and diagnostic logs. If you enable push notifications, we collect the push endpoint, subscription keys, and a shortened user-agent string.

AI and provider processing

Production AI providers are Groq, Ollama, Google Gemini, Z.ai, OpenRouter, and Cloudflare Workers AI. The active provider may vary by task and availability. Selected prompts, test context, page observations, screenshots, and report inputs may be processed for planning, browser decisions, recovery, summarization, or report enrichment.

You can choose whether to allow or prevent AI-provider training use through the setting in Matrix QA Settings or while starting a run. Tr Labs applies your selected choice to the extent supported by the relevant provider and configuration. AI outputs may be wrong or incomplete.

Why we use information

We use information to create and secure accounts, verify email, authenticate users, operate organizations and workspaces, execute authorized tests, generate reports and evidence, send transactional messages and notifications, prevent abuse, troubleshoot, manage provider capacity, calculate usage and Matrix Units, improve reliability, comply with law, and establish or defend legal claims.

We may use aggregated or de-identified information for capacity planning, reliability, quality measurement, product improvement, and business reporting where it cannot reasonably identify you or your organization.

Vendors and disclosures

We share information only as needed to operate the Service, comply with law, or protect users and the Service.

Hosting and databaseRender and Neon
Object storageCloudflare, including R2 where configured
Transactional emailResend
OAuthGoogle and GitHub
AI providersGroq, Ollama, Google Gemini, Z.ai, OpenRouter, Cloudflare Workers AI
AnalyticsGoogle Analytics

Providers may process information in countries other than your own, including Nigeria, the United States, and countries where our providers operate. We use legally required transfer safeguards and can provide further information at support@trlabs.tech.

Cookies and analytics

The frontend uses local storage for authentication and console context and session storage for temporary OAuth flow state. Matrix QA uses Google Analytics. The reviewed frontend did not show a direct first-party cookie assignment or dedicated advertising-cookie SDK, but Google Analytics, OAuth providers, hosting infrastructure, and future deployments may use cookies or similar technologies.

See the Cookie Policy for details and controls.

Retention and deletion

Our proposed default retention schedule is: verification codes until expiry; account and organization data while active and for 30 days after approved deletion; run metadata, reports, screenshots, logs, videos, AI usage, and credit ledgers while needed and for 30 days after approved deletion; support records for 24 months; security logs for 12 months; and encrypted backups for up to 90 days before overwrite or inaccessibility.

Tr Labs will begin approved deletion of active account and associated personal data immediately, subject to technical processing time, legal holds, security records, and backup overwriting. Organization owners control deletion of organization-owned projects, runs, reports, and evidence. Retention may be extended for legal obligations, security investigations, disputes, or backup integrity.

Your rights

Depending on applicable law, you may request access, correction, deletion, restriction, objection, portability, or withdrawal of consent, and you may complain to a supervisory authority. Contact support@trlabs.tech. We may verify your identity and apply lawful exceptions. Organization-owned test content may need to be requested through the organization owner.

The Service is intended for people aged 16 or older. Tr Labs has not appointed a regional privacy representative.