Security at the core!

Transparency Builds Trust

Trust is at the heart of every strong relationship, and we believe transparency is its foundation. That's why we've crafted this document with simplicity and clarity, avoiding unnecessary jargon. Our goal is to make it easy for you to understand how we operate so you can feel confident in trusting us with your business.

We use network segmentation, tenant isolation, and encryption to safeguard all data. All data in transit is sent over TLS/HTTPS and all data at rest, including backups, is encrypted with FIPS-compliant AES-256 encryption. We enforce strict tenant isolation via Azure Active Directory and subscriptions so no customer can access another's data. Azure Role-Based Access Control (RBAC) is used internally to give each team member the minimum permissions needed for their job. Multi-factor authentication (MFA) is required for all administrative access.

Architecture Diagram

The diagram below shows how the Panto AI QA Agent connects test flows, device execution, integrations, and external tools with security boundaries at every interface.

Panto AI QA Agent - security boundary, data flows, and integration points.

Data Collected & Purpose

Panto Mobile QA securely handles all data required to execute tests and generate reports. Each category is collected solely for the purpose of running tests on real devices, enabling debugging, reporting, and on-demand analysis.

• Application Artifacts — Customer APK files and build metadata such as version, app name, and package name.
• Test Execution Data — Test run identifiers, configurations, device details, execution steps, and outcomes.
• Logs & Metrics — App logs, device logs, network logs, crash logs, session logs, and performance metrics such as CPU, memory, battery, temperature, and frame rate.
• Media Captures — Screenshots, screen recordings, or video streams captured during tests, if enabled.
• Workflow Context — Chat or command prompts, responses, environment variables, memory, and state information generated during interactive or automated workflows.
• Integrations & Metadata — Secrets and configuration for connected systems, plus team, workspace, identity, and role metadata.
• Historical Reports — Aggregated reports and analytics computed from past test runs or user activity.

Trusted Execution Partners

To run tests on a wide range of real mobile devices, Panto AI Mobile QA utilises external device farms. We do not name them publicly, but they are carefully chosen partners.

When a test run is executed, the customer's APK and the test instructions are securely transmitted to the device farm over encrypted channels. The device farm runs the application and returns execution logs and metrics to our platform. These partners act solely as service providers under our direction and are subject to strict mutual confidentiality agreements; they are not permitted to retain or reuse customer APKs or data beyond the test execution.

Shared-Responsibility Model

As with any cloud or service integration, security is a partnership. Microsoft secures the underlying infrastructure, and Panto secures how we use it and our own software. We ensure that any data sent to device partners or cloud services is encrypted in transit and at rest and limited to what is absolutely needed for test execution.

Integrations & Connected Systems

Panto Mobile QA can integrate with many external tools. Examples include Slack channels, GitHub/GitLab repositories or CI systems, generic APIs and databases, SSO identity providers, and environment-variable stores.

• We store only the necessary credentials or tokens in encrypted form, for example via Azure Key Vault or an equivalent.
• Tokens and secrets are scoped with least-privilege permissions and encrypted at rest; all API calls are made over HTTPS. GitHub tokens, for example, are stored as secrets and never logged.
• Access to these systems is only for the duration of the workflow, and only with the customer's consent. Customers can connect or revoke integrations at any time.
• Logs of integration actions are recorded in the customer's test context but are treated as customer data subject to encryption and privacy controls.
• By default, integrations do not push data back into customer systems unless explicitly configured. Customers must supply credentials and should follow best practices such as using least-privilege scopes and key rotation.

Access Control & Auditability

All internal access to production systems is tightly controlled. Only authorised Panto staff with specific roles can access the system, and they do so with MFA and role-based restrictions. All administrative actions are logged.

Data Retention & Deletion

We strive to give customers control over their data. Key points:

• Backup Encryption: All backups, including database snapshots and storage backups, are encrypted by Azure's platform using AES-256 bit keys.
• Retention Policies: By default, we retain backup copies and system logs per Azure's standard retention settings. Customers can also configure retention durations for test data and reports within the application.
• Secure Deletion: Customers may request immediate deletion of their data at any time by contacting support. Upon deletion request, we permanently erase all customer data from our systems, including backups, within 48 business hours.
• Tenant Isolation: Each customer's data is stored logically isolated in separate storage containers or databases. There is no shared database or commingled storage between tenants.
• Cross-Region / Data Localisation: Data is stored in the Azure region selected by the customer. We comply with data localisation requests; if required, data can be kept within specified geographic boundaries.

Compliance and Certifications

Panto AI is certified ISO/IEC 27001:2022, reflecting our comprehensive Information Security Management System. We also meet cloud industry compliance standards, including regular audits.

Incident Response

We maintain an incident response plan following industry best practices based on NIST SP 800-61 and Azure guidelines. We practice regular security drills and keep communication channels ready with 24/7 support contacts.

Customer Responsibilities

To complement our security measures, customers should follow these guidelines:

• Authorized Builds: Only upload APKs that you have permission to test.
• Secrets Management: Do not hardcode passwords or secrets in your APKs. When configuring integrations, use secure environment variables or Azure Key Vault to inject credentials.
• Review Permissions: Regularly review which team members, Slack channels, Git repos, and API connections have access to your Panto workspace.
• SSO and Accounts: If you enable SSO/SAML with your identity provider, ensure your provider enforces MFA and reviews enterprise trust settings.
• Data Usage: Remember that any data or APK you upload will be fully visible to you and our support team if we need to troubleshoot, so handle sensitive data accordingly.

Data & Model Usage

We do not use customer applications, logs, screenshots, or any test data for training machine learning models.