Legal

Privacy Policy

This policy explains what Architect (“we”) collects when you use Architect, how it is used, and the choices you have. We collect what we need to run the product, and we don't sell personal information.

Last updated October 6, 2026

What we collect

  • Account information. Your name, email address and password (stored as a hash by our authentication provider), or your basic Google profile if you sign in with Google.
  • Workspace content. What you and your team put into Architect: your onboarding answers, Blueprint, Entries, Flows, notes, tasks, files, Intents, Playbooks and conversations with Architect.
  • Connected Google data. Only if you connect Gmail, Google Calendar or Google Contacts: the messages, events or contacts Architect needs to show them alongside your Entries. You can disconnect at any time from Settings.
  • Technical information. Basic logs (such as IP address, browser and timestamps) that our infrastructure records to keep the service running and secure.

We don't run advertising or third-party analytics trackers on Architect.

How we use it

  • To provide the product: build and run your workspace, sign you in, and send the emails the product needs, such as team invitations.
  • To answer you when you use Architect's AI features, such as the onboarding interview or Architect chat.
  • To keep the service secure and to investigate problems.

AI features

When you use the onboarding interview or Architect chat, the text you write and the workspace context needed to respond are sent to OpenAI, which generates the response. Architect never changes your workspace on its own: every proposed change waits for your approval. The public demo workspace doesn't use an AI model.

Who processes data for us

We rely on a small number of service providers to run Architect:

  • Supabase for the database, authentication and file storage.
  • OpenAI for the AI features described above.
  • Resend to deliver transactional email, such as invitations.
  • Google, only when you choose to connect a Google account.

They process data on our behalf to provide these services.

Cookies and local storage

Architect uses cookies to keep you signed in, and your browser's local storage for preferences such as the theme. The demo workspace keeps its data in your browser only; nothing you change in the demo is sent to us.

Retention and your choices

Workspace content stays in your workspace until you delete it. You can export Entries to CSV at any time and disconnect Google connections from Settings.

Depending on where you live, you may have the right to access, correct or delete your personal information.

Changes to this policy

If we make material changes, we'll update this page and the date above. See also our Terms of Service and Security page.