Security

​

Overview

Macro is built with best-in-class security practices to keep your work safe and secure at every layer. This includes state-of-the-art encryption, safe and reliable infrastructure partners, and independently verified security controls. Macro is also open source under the AGPLv3. The code that runs the hosted product is on GitHub. To request a Data Processing Agreement (DPA) with specific details, contact us at support@macro.com.

​

Shared responsibility

Under our shared responsibility model, Macro secures the components that we control, including the application layer, underlying platform, and cloud infrastructure. This includes protecting against threats targeting these components through security controls, monitoring, and incident response. Customers are responsible for how they use Macro. This includes configuring team access and roles, determining what data they share into which channels, deciding which documents have public links enabled, managing the agents and MCP clients they connect, and maintaining the security settings on the Google account they sign in with.

​

Certifications

Macro is compliant with GDPR, SOC 2 Type II, ISO 27001, and HIPAA. Our certifications cover the hosted product at macro.com. For HIPAA compliance, we offer a Business Associate Agreement (BAA) to customers handling protected health information. Please contact us at support@macro.com for more information. To request other security and compliance documents for Macro — audit reports, our subprocessor list, or a completed security questionnaire — please email security@macro.com. If you have further questions about any of our certifications, please let us know at support@macro.com.

​

Data regions

You have the option to select the region where you want your data to be stored. The available options are:

• United States
• European Union

Most of the data associated with the workspace — including email, messages, documents, tasks, call recordings, and CRM records — will only be stored in the selected region, across three systems inside it:

• Postgres for blocks and the relationships between them
• S3 for files, attachments, images, and call recordings
• OpenSearch for the index that powers Search

​

Access control

Access in Macro is derived from channel-based sharing rather than per-file permission dialogs. That model is the security boundary:

• Mentioning a block in a channel shares it with every member of that channel. Removing someone from the channel revokes what was shared there.
• Teams set the defaults for some block types. Tasks are visible to the team, calls are shared to team memory unless a call is opted out, and emails flow into the CRM when Email Sync is enabled for that company.
• Team roles are Member, Admin, and Owner. Only owners can invite and remove members.
• Auto-join on domain, when an admin enables it, adds anyone who signs up with an email on the owner’s domain to the team.
• Public links make a document readable by anyone with the URL, including people without a Macro account.

Macro does not store passwords. You sign in with Google, with Apple on iOS, or with a one-time link sent to your email. Signing in with Google means your Google Workspace policies — two-factor authentication, session length, and device restrictions — apply to Macro. Revoking Macro’s access from your Google account, or disconnecting it in Settings → Connections, ends email sync.

​

Agents and your data

Agents operate on your workspace data under the following guarantees: Macro routes requests to model providers including Anthropic and OpenAI, depending on the task. Data you send to a third-party MCP server that you connect yourself is governed by that provider’s terms, not ours.

​

Retention and deletion

• Deleting a block moves it to trash first, so it can be recovered.
• Deleting your account is permanent. Settings → Account → Delete account removes your account and its associated data after a confirmation step.
• Organizations can set a retention window that deletes documents and chats which haven’t been accessed within a set number of days. Contact support@macro.com to configure one for your organization.

Disconnecting a Gmail account stops future sync but doesn’t delete mail that has already synced.

​

Report a vulnerability

Send suspected security issues to security@macro.com. We pay bounties in accordance with the severity and impact of the finding. Please include steps to reproduce, the affected surface (web, iOS, API, or MCP), and any accounts involved, and give us a chance to ship a fix before disclosing publicly. Because the codebase is open source, you can reference specific files or commits.

​

FAQ