Security & trust

Last updated and effective: 28 October 2026.

Built to earn your repo access

Aient reads your production telemetry and your source code to fix bugs — so trust is the product. Here's exactly what we access, where your data lives, and the controls you keep.

The five things that matter

You control the autonomy.

Aient opens a pull request; you merge by default. Merge automation is opt-in and requires approval of the exact PR head.

Organisation-scoped isolation.

Your code and telemetry are separated from other organisations, and every fix runs in an isolated, single-tenant sandbox.

EU primary storage.

Some providers process outside the EEA. Locations and transfer safeguards are described in the DPA and provider list.

Revoke or scope anytime.

Limit Aient to specific repositories at install, and revoke the GitHub App whenever you want.

We never sell your data,

and never share it with model providers for their own training.

Least privilege, by surface

Aient pushes changes to pull-request branches. You control merging, including whether to enable merge automation.

GitHub

Read source and open pull requests, via a scoped GitHub App you install — you pick the repos

Investigate the root cause and open the fix PR

Telemetry (OpenTelemetry)

The traces, logs, and errors you send us

Detect and group production problems

Notifications & collaboration

Post messages and issue updates in the channels you connect — Slack, Microsoft Teams, Linear, Telegram, or email

Triage, notifications, and team collaboration

Where processing happens

Primary EU storage

  • Telemetry — your traces, logs, and errors (EU)
  • Object storage — verification evidence of fixes (EU)
  • Supabase (EU region) — application data, protected with row-level security

Additional processing

  • Sandboxes — Aient-operated EU infrastructure and Modal EU compute; Modal retains logs, images, snapshots and configured secrets in the US
  • OpenAI / Anthropic / Google — relevant code and telemetry context for inference; standard routing is not restricted to the EU
  • Other providers — hosting, email and billing can involve processing outside the EEA; see the provider list

We publish our full subprocessor list and notify on changes — see subprocessors. We do not claim end-to-end EU-only processing.

Repository access and retained copies

Aient fetches your code via your GitHub grant and runs the fixing agent in an isolated sandbox. Workspaces and snapshots may be retained between runs. Revoking GitHub access stops future fetches from GitHub; it does not delete copies already fetched. Retention and deletion follow the Privacy Policy and DPA.

Relevant code and telemetry context is sent to OpenAI, Anthropic or Google for inference, under their contractual terms. Code snippets (e.g. stack-trace context) can appear in retained diagnostics — see how we use your data below.

To make the fixes better

We review agent traces to locate failures and correct prompts and the agent harness. Customer-specific classifiers learn from your telemetry to group related log messages. These uses serve your organisation under the DPA.

Shared improvements. We use reasonable measures to remove personal data before trace material or derived examples are reused across customers. Shared material must not reasonably identify individuals or contain customer Confidential Information. Raw traces and customer-specific classifiers are excluded. Standard plans permit this limited reuse; an Enterprise agreement may exclude it. An exclusion does not itself promise zero retention.

Privacy and retention. Individual rights are free on every plan. Customer data, including customer-specific classifier data, follows the Privacy Policy retention provisions and DPA return and deletion provisions. Separate accounting records follow legal requirements.

Your controls

  • Limit Aient to specific repositories.
  • Revoke the GitHub App at any time.
  • Request a copy or deletion of your data (GDPR DSR).
  • DPA available.

Enterprise

  • Contractual opt-out of shared improvements.
  • Customer-specific requirements and commitments are set out in the service agreement.

Compliance

  • GDPR — primary EU storage, DPA + SCCs, documented ROPA, data-subject requests honored.
  • SOC 2 — programme in progress; no completed report is available.

Found something? Tell us.

Email security@aient.ai with the details and steps to reproduce. We welcome responsible disclosure and aim to acknowledge within five business days. For sensitive reports, encrypt with our PGP key. Our policy is published at /.well-known/security.txt.

Questions, answered

Does Aient merge code on its own?

Not without your approval. Aient opens a pull request; by default you merge it yourself. If you enable merge automation for an environment (off by default), Aient merges only after a human approves the exact PR head and checks pass. Aient pushes its changes to pull-request branches.

Where is my data stored?

Primary storage is in Finland, with disaster-recovery backups in Germany and a Supabase database in Stockholm. Aient operates EU sandboxes and also uses Modal EU compute; Modal keeps logs, images, snapshots, configured secrets and control-plane data in the US. Standard model-provider routing is not restricted to the EU. Other providers, including web hosting and email, may also process outside the EEA. The subprocessor list and DPA describe the applicable locations and transfer safeguards.

Do you train on my code?

We review agent traces to troubleshoot your Services and improve prompts and the harness. Customer-specific classifiers learn from your telemetry to group related log messages. We use reasonable measures to remove personal data before shared reuse. Shared material must not reasonably identify individuals or contain customer Confidential Information; raw traces and customer-specific classifiers are excluded. This permission does not authorise training general-purpose model weights on your personal data. Enterprise agreements may exclude shared improvement use. Individual privacy rights apply on every plan.

Can I limit or revoke Aient's access?

Yes. You install a scoped GitHub App and pick exactly which repositories Aient can see, and you can revoke it at any time — revoking GitHub access stops future fetches from GitHub. Previously fetched copies remain subject to the retention and deletion provisions. You can also request a copy or deletion of your data at any time.

Is Aient SOC 2 certified?

Our SOC 2 programme is in progress. That is not a completed audit report. The DPA describes our controls and how customers can request available security evidence.

Trust, then fixes

Connect a scoped GitHub App and your telemetry, and keep the merge button. You can revoke or narrow access at any time.