Skip to content
aucert.ai
  • Product
  • Platform
  • ROI
  • Team
  • Contact
  • Product
  • Platform
  • ROI
  • Team
  • Contact
Book time with the foundersBook time

Legal

  • Terms of Service
  • Privacy Policy
  • Acceptable use
  • Data processing agreement
  • Subprocessors
  • Security
Legal

Security

Version 2026-10-19 · Effective 19 October 2026

Draft. Under review by counsel and not yet in force.

Aucert runs your apps, sees their screens and holds your test credentials. This page says exactly how that data is protected today. Every statement here describes a control that exists now, not one that is planned. Where something is not yet in place, it says so.

Where your data lives

  • One cloud, one region. The Product runs on Amazon Web Services in us-west-2 (Oregon). An organisation-level policy denies every other region, so data cannot be created or stored elsewhere by mistake.
  • Separate production account. Production and development run in separate AWS accounts under one organisation. Nothing in production is shared with development.
  • No public entry points. The console, API and device relay are reached only through a Cloudflare tunnel. There is no public load balancer and no public IP address. The database is not reachable from the internet.
  • Devices stay with you. Emulators, simulators and physical phones run on hardware you control, driven by the Aucert desktop application. Live device video passes through the relay and is not stored.

Encryption

  • In transit. All traffic between you and the Product, and between the Product and its providers, is encrypted with TLS. Database connections require TLS.
  • At rest. The database, its backups and Kubernetes secrets are encrypted with a customer-managed AWS KMS key owned by Aucert. Object storage (builds, screenshots, scan evidence) is encrypted with AES-256. Public access to object storage is blocked at the account level.
  • Test credentials. Credentials you give us for your app are stored in AWS Secrets Manager under a dedicated, access-restricted path. The database holds only an opaque reference. A plain-text reveal requires an explicit per-person allow-list (empty by default) and writes an audit record. Payment-type secrets can never be revealed.

Tenant isolation

  • Enforced by the database. Every table that holds customer data has PostgreSQL row-level security enabled and forced. A query without the right tenant context returns nothing. The application’s database role cannot bypass it.
  • Checked on every change. A conformance check runs on every schema change in our pipeline and fails the change if any tenant table lacks the policy.
  • Your knowledge graph is yours. The knowledge the agents build about your app is scoped to your organisation and never shared with another customer.

Access by Aucert staff

  • Single sign-on only. There are no IAM users and no long-lived access keys. Staff sign in through AWS Identity Center. Production access is limited to one named group; builders have development access only.
  • Internal tools behind identity. Logs, traces and admin tools sit behind Cloudflare Access, restricted to Aucert staff accounts.
  • Automation without stored keys. Continuous integration authenticates to AWS with short-lived OIDC tokens. No cloud credentials are stored in the repository.
  • Guardrails. Organisation policies prevent disabling audit logging or threat detection, acting as root, leaving the organisation, or using another region.

Logging and audit

  • Audit trails. Every table a person can change has a companion audit table holding the previous version of each row. Credential reveals write their own append-only audit record.
  • No hard deletes. The application cannot delete rows; deletion is a status change. Erasure on request is performed by an operator under a separate role.
  • Redacted logs. Authorization headers, cookies, API keys, tokens and AI prompt and response bodies are stripped before logs are stored. Our AI gateway does not log prompts or completions. Logs are kept for 30 days.

Backups and recovery

  • Automated database backups are kept for 30 days, with an independent daily copy kept for 35 days and encrypted with Aucert’s key.
  • Deleted secrets remain recoverable for 30 days before they are destroyed.

AI providers

The agents send screenshots, UI hierarchies and on-screen text to the AI providers listed on the Subprocessors page, with the data-use terms each operates under. Your Aucert account data, the contents of the credential vault and your billing data are never inputs to these requests. A screenshot shows whatever the app displayed, so what reaches a provider is bounded by what you let the app show during a test; redaction of screen content before it leaves Aucert is not yet in place (see below). See Section B.3 of the Terms of Service for the commitments by account type.

Reporting a vulnerability

Email security@aucert.ai. We acknowledge reports within two business days and keep you informed until the issue is resolved. Please do not test against other customers’ data; use your own organisation.

Not yet in place

  • Certifications. Aucert does not yet hold SOC 2, ISO 27001 or any other certification, and has not yet commissioned an external penetration test. Both are planned; this page will say so when they exist.
  • Encryption inside the cluster. Traffic between services inside the production cluster is not yet mutually authenticated with TLS. Encryption in transit applies to every hop over a public network.
  • Automatic retention. Customer Content is kept until you delete it or close the organisation. Scheduled retention limits are planned.
  • Screen-content redaction. Screenshots and UI hierarchies are sent to AI providers as captured. Masking of personal data in screen content before it leaves Aucert is planned.
  • Independent audit report. No third-party audit Report exists yet, so Section 5.2 of the Data Processing Agreement is replaced by its Section 5.1 and 5.3 until one does.

Versions

  • 2026-10-19, version 1. First publication.

(Au)tomated (Cert)ification Software

©2026 Aucert Inc. All rights reserved.

Sitemap

  • Home
  • ROI calculator
  • Team
  • Contact

Legal

  • Terms of Service
  • Privacy Policy
  • Acceptable use
  • Data processing agreement
  • Subprocessors
  • Security

For agents

  • [Human] [Agent]
  • llms.txt
  • llms-full.txt