Pangea Download Pangea
Trust Center

Your company’s code and data, handled with care.

Teams bring their repositories, cloud accounts and conversations to Pangea. This page lists the security controls the product has today, the companies that process data for us, and where we stand on compliance. It lists only what is built and running.

Last updated: November 14, 2026

Overview

Pangea is a hosted, governed workspace where teams run Claude Code, Codex, Cursor and Antigravity together. Sensitive steps wait for a person, every agent action is recorded, and agents use your own model accounts.

Where it runs

The backend and Pangea Cloud computers run on Fly.io servers in São Paulo, Brazil. Agents can also run on your Mac or a server you control.

Your model accounts

Each agent signs in with your own Claude, ChatGPT, Cursor or Google account. Pangea does not run or resell a model, and does not train models on your content.

Who sees what

Roles, approvals and per-connector access lists decide who can use what. The audit trail records who did what, with which agent, and who approved it.

How to report a vulnerability

Email augusto@pangea.build with what you found, the steps to reproduce it, and what an attacker could do with it. Please do not access, change or delete other people’s data while testing, and give us a reasonable time to fix the issue before you disclose it.

We will confirm that we received your report and keep you posted until it is fixed. Pangea does not run a paid bug bounty program.

Controls

Each control below is in the product or its production configuration today. Anything planned is left off this list.

Infrastructure security

Where Pangea runs and how it is reached.

  • TLS on every endpointThe API, the web app and this website accept HTTPS only. Plain HTTP requests are redirected to HTTPS.
  • Backend hosted in São Pauloapi.pangea.build and app.pangea.build run on Fly.io in its São Paulo (gru) region.
  • One isolated machine per cloud computerEach Pangea Cloud computer is its own Fly Machine with its own encrypted volume. Removing the computer deletes the machine and its volume.
  • Idle cloud computers are stoppedA cloud computer nobody has used for 30 minutes is stopped, and starts again on the next turn. A monthly hours cap stops it between turns when the hours run out.
  • A cloud computer image we build ourselvesPangea builds the image every cloud computer runs. Nothing is downloaded when a computer starts, and the bundled Cursor CLI is a pinned, checksum-verified build.

Product security

How people sign in and how agents are kept in check.

  • Two-factor sign-inWith an authenticator app or a passkey, plus ten single-use recovery codes. The authenticator secret is encrypted, recovery codes are stored only as hashes, and a code is never accepted twice.
  • Re-verification for security changesAdding a passkey or an authenticator, removing a passkey, creating new recovery codes and turning two-factor off each need a fresh code or a recent sign-in.
  • Sign-in optionsA one-time code sent by email, a password stored as an Argon2id hash, Sign in with Google or Sign in with Apple.
  • Session limits and sign-in alertsSessions end after 14 days without use and after 30 days at most. Session tokens are stored only as hashes. You can see and end your sessions, and a sign-in from a new IP address triggers an email.
  • Human approval for agent actionsWhen an agent asks permission to run a tool, the request waits for a person to approve or deny it. If nobody answers in time, it counts as denied. A person can turn on Full Access for a conversation, which lets those requests through without asking.
  • Approval before database changesA database change request runs only after the required number of approvals from teammates other than the requester. Each approval applies to the exact statement, and Viewers cannot approve or run changes.
  • Tamper-evident audit trailEvery agent turn, prompt, tool call and approval is recorded, and each entry is chained by hash to the one before it. Admins can export it as evidence.
  • Computer access historyEach change to who can use a computer is recorded: sharing, invitations, moves, and people leaving or being removed from the team.
  • Secret scan on skills installed from GitHubA team skill installed from a GitHub repository is pinned to a commit and scanned for embedded secrets. If a file appears to contain one, the install is refused.
  • Secrets masked in stored transcriptsWell-known API key formats that an agent prints by mistake are masked before the message is stored.

Data and privacy

How credentials and your content are kept and used.

  • Connector secrets encrypted at restTokens and keys for connected tools, database credentials and two-factor secrets are encrypted with AES-256-GCM. The encryption keys are held as server secrets, outside the database.
  • No long-lived cloud keysAWS, Google Cloud and Azure are reached through OIDC or workload identity federation. Pangea signs a short-lived token for your team, and your cloud’s own trust policy decides what it may do. There is no fallback to stored static keys.
  • Short-lived GitHub tokensThe GitHub connector uses GitHub App installation tokens, which expire within the hour, instead of a stored personal token.
  • Personal Credentials stay personalYour own GitHub, Linear, Gmail and Google Drive connections are used only for your own turns. Gmail and Drive work only in conversations you own. A teammate’s message never uses your credentials, even in a shared session.
  • No training on your contentPangea does not use your content to train AI models, and does not sell personal data or use it for advertising.
  • Card data handled only by StripePayments go through Stripe Checkout and the Stripe customer portal. Card numbers never reach Pangea’s servers.
  • Team data exportA team admin can export the team’s data as a ZIP file. Credentials and sealed secrets are left out of the export.
  • Account deletion in the appDelete your account from the iOS or Android app, confirmed with your password or an email code. Personal Credentials and profile photos are deleted at once, and the rest of the account within 30 days.

Organizational security

Access within your organization, and how Pangea ships code.

  • RolesOwner, Admin, Editor and Viewer. Admins manage members, billing and settings. Editors start conversations and work with computers. Viewers read conversations and the audit log.
  • Invite links with a role, a limit and an expiryEach link carries a role (never Admin), a use limit and an expiry of 1 to 30 days, and can be revoked. Only a hash of the link is stored.
  • Company email domainsA team can claim its company domain by proving control with a DNS record. People who sign in with that domain can join with the role the team chose, never Admin. Public email domains cannot be claimed.
  • Per-connector member allow-listAdmins choose which members may use each connected tool. Connectors whose credentials cannot be narrowed on the provider’s side start limited to the person who connected them.
  • Third-party code is reviewedEvery third-party code update is reviewed before release. It is merged on a separate branch, checked for security issues and run through type checks and tests before release.

Subprocessors

These companies process personal data for us to run Pangea. Model providers and the tools you connect are not listed, because you have your own relationship with them. The same list, with more detail, is in our Privacy Policy.

Subprocessor
What it does for Pangea
Data involved
Location
Fly.ioHosting
What it doesHosts the Pangea backend (api.pangea.build and app.pangea.build), runs cloud computers, and serves www.pangea.build and its waitlist form.
DataAll Service data while it is processed; cloud computer disks; waitlist form requests.
LocationServers in São Paulo, Brazil
MongoDB AtlasMongoDB, Inc.
What it doesMain database.
DataAccounts, teams, Customer Content, the audit trail, encrypted credentials.
LocationUnited States (company)
Upstash
What it doesQueues for scheduled agents and webhook-started turns, rate-limit counters.
DataJob references, counters keyed by hashed IP address or account.
LocationUnited States (company)
CloudflareR2 storage
What it doesStores files transferred between you and agents, editable skills and desktop crash reports; serves app downloads at download.pangea.build.
DataFiles, skills, crash reports; the IP address of each download.
LocationUnited States (company)
Resend
What it doesSends email from no-reply@pangea.build.
DataEmail address, name, and the email’s content: sign-in codes, invitations, download links, and sign-in alerts with IP address and approximate location.
LocationUnited States (company)
Stripe
What it doesPayments, invoices and the customer portal.
DataBilling name and email, payment details (held by Stripe only), plan and invoices.
LocationUnited States (company)
Apple
What it doesSign in with Apple; push notifications to iPhone and iPad (APNs).
DataApple account identifier and email; push token and notification text.
LocationUnited States (company)
Google
What it doesSign in with Google; push notifications to Android (Firebase Cloud Messaging); the Gmail and Google Drive APIs when you connect them.
DataGoogle account identifier, email, name and photo; push token and notification text; the Gmail and Drive data your agent works with.
LocationUnited States (company)
Composio
What it doesGmail and Google Drive connections for teams without their own Google OAuth client; the Trello connector.
DataThe OAuth grant, the actions an agent runs and their results.
LocationUnited States (company)
Neon
What it doesDatabase for the waitlist.
DataWaitlist email, company, team size, sign-up page, IP address and user agent.
LocationUnited States (company)
OpenAIOnly when voice input is on
What it doesTurns voice input into text.
DataThe audio you record.
LocationUnited States (company)

“Company” means the country where the provider is based, not where your data is stored. Only the Fly.io servers Pangea uses are confirmed to be in São Paulo. We will update this list before we add a new subprocessor.

Compliance

Where Pangea stands today, stated plainly.

Not certified

SOC 2

Pangea is not yet SOC 2 certified, and holds no other security certification today. A SOC 2 audit is planned.

On request

Security questionnaire

Companies evaluating Pangea can request a completed security questionnaire, or send their own, at augusto@pangea.build.

How we handle personal data, including your rights under the GDPR and Brazil’s LGPD, is in our Privacy Policy. The terms of use are in our Terms of Service.

Questions

What security reviewers usually ask first.

Where does my data live?

The Pangea backend and Pangea Cloud computers run on Fly.io servers in São Paulo, Brazil. The main database is MongoDB Atlas and files are stored on Cloudflare R2; we do not state a region for those here. When an agent runs on your Mac or on a server you control, your code stays on that computer. What appears in the conversation (prompts, replies, tool calls and their results) is stored by Pangea.

Who can see my code and conversations?

Members of your workspace who have access to a conversation, according to their role. Viewers can read but not act. Admins can view and export the workspace’s audit trail. The model provider your agent signs in with receives what the agent sends it. People at Pangea look at the minimum needed, only when you ask for help or to fix a problem.

Does Pangea train AI models on my data?

No. Pangea does not run its own model and does not use your content to train AI models. Agents sign in with your own Claude, ChatGPT, Cursor or Google account, so what the provider does with your prompts is governed by your agreement with that provider.

How do I delete my data?

You can delete your account in the iOS or Android app, under Account, or by email. Your Personal Credentials and profile photos are deleted as soon as you ask, and the rest of your account within 30 days. A workspace owner can delete the workspace, and an admin can first export the team’s data as a ZIP file. Retention details are in the Privacy Policy.

How are cloud credentials handled?

For AWS, Google Cloud and Azure, Pangea stores no long-lived cloud keys. It signs a short-lived token for your team and exchanges it with the cloud provider through OIDC or workload identity federation, and the provider’s own trust policy decides what that token may do. GitHub access uses short-lived GitHub App installation tokens. Other connector secrets are encrypted with AES-256-GCM, and admins can limit each connector to named members.

Is Pangea SOC 2 certified?

Not yet. Pangea holds no security certification today. A SOC 2 audit is planned. Companies evaluating Pangea can request a security questionnaire at augusto@pangea.build.