Skip to content
ArchFoundry Docs Open the canvas

Your data and privacy

Updated October 19, 2026Plans: Free, Pro, Enterprise

Overview

ArchFoundry is built so that the most sensitive things you work with never reach it. Terraform state is read in your browser and never uploaded. AWS access keys are refused. This guide lists what is kept, where, and what you can switch off. The full legal terms are in the privacy policy.

Prerequisites

  • None. This applies to every ArchFoundry account.

Steps

  1. In the workspace sidebar, click Settings, then the Data & privacy tab, to read What leaves this browser.
  2. Under Sharing diagrams with the copilot, see whether you have allowed diagrams that came from an import or a connected account to be sent to Archie's AI provider.
  3. To be asked again before such a diagram is sent, click Ask me again next time.
  4. To stop Archie using ArchFoundry's AI provider, give it your organization's own key. See Use your own AI key for Archie.
  5. To revoke what you connected, remove it where you added it: Remove under Cloud accounts, Disconnect under Repositories, Revoke under Coding agents.

Example

What happens to each thing you give ArchFoundry:

text
Terraform state or plan JSON   parsed in your browser; never uploaded, not kept after the import
AWS access                     a role ARN and an external id; access keys are refused
AWS reads                      temporary sessions, never stored; only when you ask, no background polling
Repository token               sealed with AES-256-GCM, never shown again; the GitHub App leaves none
Repository contents            read when you ask; names from example env files, never a .env file
Agent token                    stored as a hash; nobody can read it back, ArchFoundry included
Archie's own AI key            sealed on the server; only its last four characters come back
Diagrams                       saved to your organization when you are signed in
A question to Archie           your message, attached files, and the diagram's card
                               names, types, prices, the lines between cards and
                               network details go to the AI provider. Each message
                               also carries your connected repositories and AWS
                               accounts: their names, branches and environments,
                               whether each is working, and whether it can save
                               changes or deploy. On a diagram linked to a
                               repository, Archie may also read its files and
                               send what it reads, with values that look like
                               credentials masked first; state files, keys and
                               .env files are never read. Account numbers and
                               credentials are never sent.

Verify it worked

  • Sharing diagrams with the copilot reads Not granted after you ask to be asked again.
  • Each connection you removed is gone from its list.

Troubleshooting

Archie asks Before Archie reads this diagram. The diagram came from an import or a connected account, or it is linked to a repository Archie has not been allowed to read yet. The dialog lists what would be sent. Click Allow and send, or Cancel to keep your message without sending it.

A teammate can see your diagrams. Diagrams, connected accounts and deployments belong to the organization, and everyone in it shares them. See Invite your team.

You were removed from an organization. You keep your account and sign-in, with a new organization of your own. You lose access to the old one's diagrams and deployments.

Next steps