Macro is a unified workspace for teams: email, chat, docs, tasks, agents, calls, and CRM — @-linked together with shared AI memory.
TypeScript agentaiai-agentsall-in-onecrmcrm-systememaillinearmcpmessagingnotesnotionofficerustslackslack-alternativestartupstartup-toolstypescriptworkspace
Security documentation page (#5213)
Jacob Beckerman1a567e46ea87
diff --git a/apps/docs/account/teams.mdx b/apps/docs/account/teams.mdxindex d0ed86bfa9..0fa37ae038 100644--- a/apps/docs/account/teams.mdx+++ b/apps/docs/account/teams.mdx@@ -45,4 +45,6 @@ See [Permissions](/permissions) for the full sharing model.## Sign-in and enterprise-Macro signs in with your Google account, the same one your Gmail or Google Workspace email syncs from. For enterprise requirements like HIPAA, FedRAMP, or running Macro on your own infrastructure, contact [[email protected]](mailto:[email protected]).\ No newline at end of file+Macro signs in with your Google account, the same one your Gmail or Google Workspace email syncs from. For a GDPR data processing agreement, a HIPAA Business Associate Agreement, or EU hosting, contact [[email protected]](mailto:[email protected]). For FedRAMP or running Macro on your own infrastructure, contact [[email protected]](mailto:[email protected]).++[Security](/security) covers encryption, certifications, retention, and how agents handle team data.\ No newline at end of filediff --git a/apps/docs/docs.json b/apps/docs/docs.jsonindex 268578fd78..ee0c045272 100644--- a/apps/docs/docs.json+++ b/apps/docs/docs.json@@ -98,7 +98,8 @@"group": "Account","pages": ["account/teams",- "account/billing"+ "account/billing",+ "security"]},"support",diff --git a/apps/docs/faq.mdx b/apps/docs/faq.mdxindex a8e6fd33d7..8d34f290a0 100644--- a/apps/docs/faq.mdx+++ b/apps/docs/faq.mdx@@ -48,7 +48,7 @@ description: "How Macro compares to Notion, Superhuman, and Slack, plus licensinThe hosted version is the one that works with the iOS app and has necessary Apple approval, Google Mail approval, and GitHub approval to integrate your PRs. We're hosted on AWS and maintain a SOC 2 Type II audit. We sublicense LiveKit for video calls, FusionAuth for authentication, PostHog for analytics, and so on, so you'd have to maintain licenses to those services or disable them.- Our main focus right now is on making Macro great, but we also want to make it easier to self-host. We hope to turn our attention to this later this year (2026). For HIPAA-compliant, FEDRAMP and other clients, please contact [[email protected]](mailto:[email protected]) and we can work with you to get Macro running on your own infrastructure.+ Our main focus right now is on making Macro great, but we also want to make it easier to self-host. We hope to turn our attention to this later this year (2026). For FedRAMP and other clients who need Macro on their own infrastructure, please contact [[email protected]](mailto:[email protected]) and we can work with you to get it running. Note that self-hosting isn't a prerequisite for HIPAA or EU data residency — we sign BAAs and host in the EU on the managed version too, see [Security](/security).</Accordion><Accordion title="Are you open to contributions?">@@ -65,7 +65,7 @@ description: "How Macro compares to Notion, Superhuman, and Slack, plus licensin</Accordion><Accordion title="How do you use my data?">- We are in the business of making a good product and charging you money for our hosted version of that product. We are not interested in your data. See our privacy policy and terms of service for full information.+ We are in the business of making a good product and charging you money for our hosted version of that product. We are not interested in your data. We don't train models on your content, and we hold zero-retention agreements with the model providers we route to. [Security](/security) covers encryption, certifications, and retention in detail; see our privacy policy and terms of service for full information.</Accordion><Accordion title='How do teams work in Macro? Do I need a "team"?'>diff --git a/apps/docs/permissions.mdx b/apps/docs/permissions.mdxindex b2d2b28ad6..dea094461c 100644--- a/apps/docs/permissions.mdx+++ b/apps/docs/permissions.mdx@@ -27,7 +27,7 @@ Users need to have a file shared with them in order to receive an inbox notificaNotifications only appear after a doc is explicitly shared with a person. @mentioning someone in the doc **body** does _not_ notify them but @mentioning in a **comment** does (lands in their inbox notifications).-Public sharing works for users without Macro. Share by using an email address or enable the **Public Link** in the Share menu.+Public sharing works for users without Macro. Share by using an email address or enable the **Public Link** in the Share menu. Anyone with a public link can read the doc, so check the Share menu on anything sensitive — see [Security](/security).### Tasksdiff --git a/apps/docs/security.mdx b/apps/docs/security.mdxnew file mode 100644index 0000000000..eaab4abcc3--- /dev/null+++ b/apps/docs/security.mdx@@ -0,0 +1,142 @@+---+title: "Security"+icon: "shield-check"+description: "How Macro protects your data: encryption, certifications, access control, agent data handling, and how to report a vulnerability."+---++Macro holds a lot of your work in one place — email, messages, docs, tasks, calls, and CRM records — so we treat security as a product requirement rather than a checklist. Data is encrypted in transit and at rest, access is derived from the same sharing model you see in the app, and our controls are audited by a third party.++Macro is also fully open source under the AGPLv3, so you don't have to take our word for how any of this works. The code that runs the hosted product is on [GitHub](https://github.com/macro-inc/macro).++## Shared responsibility++Security is a split between what we run and what you configure.++| We handle | You handle |+| --- | --- |+| Application and infrastructure security, encryption, patching, monitoring | Who is on your team, and which role each member has |+| Third-party audits and compliance programs | What gets shared into which channel |+| Isolation between workspaces | Whether a public link is enabled on a doc |+| Availability, backups, and durability | Which agents and MCP clients you connect |+| Vetting and monitoring our subprocessors | Your Google account's own security settings, including 2FA |++## Certifications++Macro maintains a **SOC 2 Type II** audit and an **ISO 27001** certification, covering the hosted product at `macro.com`.++A few things we set up per customer rather than by default. Email [[email protected]](mailto:[email protected]) for any of them:++- **GDPR** — a data processing agreement and the accompanying subprocessor list+- **HIPAA** — a Business Associate Agreement, for teams handling protected health information+- **EU hosting** — see [Data storage and regions](#data-storage-and-regions)++For audit reports or a security questionnaire as part of a vendor review, email [[email protected]](mailto:[email protected]).++<Note>+ FedRAMP, or anything else that needs Macro running inside your own infrastructure, is a different conversation — contact [[email protected]](mailto:[email protected]). Self-hosting under the AGPLv3 is covered in the [FAQ](/faq).+</Note>++## Data storage and regions++By default, the hosted version of Macro runs on **AWS in the United States**. **EU hosting is available on request** — email [[email protected]](mailto:[email protected]) and we'll set your workspace up in an EU region.++Whichever region your workspace lives in, your data is stored across a few systems inside it:++- **Postgres** for blocks and their relationships — docs, emails, tasks, channels, messages, calls, CRM records+- **S3** for files, attachments, images, and call recordings+- **OpenSearch** for the search index that powers [Search](/product/search)++## Encryption++- **In transit:** all traffic between your client and Macro, and between Macro's own services, uses TLS.+- **At rest:** databases, file storage, and backups are encrypted with AES-256 using AWS KMS-managed keys.++## Access control++Access in Macro comes from [channel-based sharing](/permissions) rather than per-file permission dialogs. That model is the security boundary, so it's worth understanding:++- Mentioning something in a channel shares it with every member of that channel. Removing someone from the channel revokes what was shared there.+- [Teams](/account/teams) change the defaults for a few block types — tasks are team-visible, calls are shared to team memory unless you opt a call out, and emails flow into the CRM when Email Sync is on for that company.+- Team roles are **Member**, **Admin**, and **Owner**. Only owners can invite and remove members.+- **Auto-join on domain**, if an admin turns it on, adds anyone who signs up with an email on the owner's domain to the team automatically. Leave it off if you'd rather approve each member.+- **Public links** make a doc readable by anyone with the URL, including people without a Macro account. Check the Share menu of anything sensitive.++Macro never stores a password for you. You sign in with Google, with Apple on iOS, or with a one-time link sent to your email. Most people sign in with Google, which means your Google Workspace security policies — 2FA, session length, device restrictions — apply to Macro too. Revoking Macro's access from your Google account, or disconnecting it in **Settings → Connections**, cuts off email sync.++## Agents and your data++Agents are the part of Macro people ask about most, so the guarantees are explicit:++<CardGroup cols={2}>+ <Card title="No training on your data" icon="ban">+ Your content is never used to train models, ours or anyone else's.+ </Card>++ <Card title="Zero data retention" icon="clock-rotate-left">+ We run zero-retention agreements with our model providers, so prompts and content aren't retained on their side.+ </Card>++ <Card title="Agents inherit your permissions" icon="user-lock">+ An agent can only reach what you can reach. If a doc isn't shared with you, it isn't in your agent's context.+ </Card>++ <Card title="You choose the connections" icon="plug">+ Connectors and MCP clients are opt-in per workspace from **Settings → Connections**.+ </Card>+</CardGroup>++Macro routes requests to model providers including Anthropic and OpenAI depending on the task. When you connect an outside MCP server yourself, whatever you send to it is governed by that provider's terms, not ours — so treat third-party connectors as a decision about where your data goes.++## Retention and deletion++- **Trash is reversible.** Deleting a block moves it to trash first, so an accidental delete is recoverable.+- **Deleting your account is not.** **Settings → Account → Delete account** permanently removes your account and its associated data, after a confirmation step.+- **Organizations can set a retention window.** Macro can enforce an org-wide policy that deletes documents and chats which haven't been accessed within a set number of days. Contact [[email protected]](mailto:[email protected]) to configure one for your organization.++Disconnecting a Gmail account stops future sync but doesn't delete already-synced mail; delete the account or the individual threads if you want that data gone.++## Report a vulnerability++Send security reports to [[email protected]](mailto:[email protected]). 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. Give us a chance to ship a fix before disclosing publicly. Since the codebase is open source, feel free to point at specific files or commits — it speeds things up considerably.++<Warning>+ Don't file security issues on the public GitHub tracker. Use [[email protected]](mailto:[email protected]) so a report isn't visible before there's a fix.+</Warning>++## FAQ++<AccordionGroup>+ <Accordion title="Is my data encrypted?">+ Yes. TLS in transit, AES-256 at rest for databases, file storage, and backups.+ </Accordion>++ <Accordion title="Do you train models on my data?">+ No. We don't train on customer content, and we hold zero-retention agreements with the model providers we route to, so they don't retain it either.+ </Accordion>++ <Accordion title="Can I keep my data in the EU?">+ Yes, on request. The default is AWS in the US; email [[email protected]](mailto:[email protected]) and we'll host your workspace in an EU region instead.+ </Accordion>++ <Accordion title="Can you sign a DPA or a BAA?">+ Yes to both. Email [[email protected]](mailto:[email protected]) for a data processing agreement under GDPR, or a Business Associate Agreement if you're handling protected health information.+ </Accordion>++ <Accordion title="Who at Macro can see my workspace?">+ Access to production data is restricted to the engineers who need it to operate the service, and infrastructure access is logged and monitored. We don't browse customer content, and support will ask before looking at anything specific to debug an issue.+ </Accordion>++ <Accordion title="How do I export or delete my data?">+ Delete your account and its data from **Settings → Account → Delete account**. For a bulk export, or deletion scoped to part of your workspace, email [[email protected]](mailto:[email protected]).+ </Accordion>++ <Accordion title="Which subprocessors does Macro use?">+ The hosted product runs on AWS, and we sublicense LiveKit for video calls, FusionAuth for authentication, and PostHog for product analytics, alongside the model providers described above. Email [[email protected]](mailto:[email protected]) for the current list as part of a vendor review.+ </Accordion>++ <Accordion title="Does Macro support SAML or SCIM?">+ Not yet. Sign-in today is Google, Apple on iOS, or a one-time email link — so Google Workspace policies are the practical enforcement point. If you need SAML or SCIM, let us know at [[email protected]](mailto:[email protected]) — demand shapes what we build next.+ </Accordion>+</AccordionGroup>diff --git a/apps/docs/support.mdx b/apps/docs/support.mdxindex 4abd33c5dc..03235fda23 100644--- a/apps/docs/support.mdx+++ b/apps/docs/support.mdx@@ -24,7 +24,7 @@ description: "How to get help with Macro, and fixes for the most common issues."</Card></CardGroup>-For specific topics: [[email protected]](mailto:[email protected]) for commercial licensing, [[email protected]](mailto:[email protected]) for HIPAA/FedRAMP and self-hosted deployments, and [[email protected]](mailto:[email protected]) if you want to contribute but aren't sure where to start.+For specific topics: [[email protected]](mailto:[email protected]) for commercial licensing, [[email protected]](mailto:[email protected]) for a DPA, a HIPAA BAA, or EU hosting, [[email protected]](mailto:[email protected]) for FedRAMP and self-hosted deployments, [[email protected]](mailto:[email protected]) for vulnerability reports and vendor security reviews (see [Security](/security)), and [[email protected]](mailto:[email protected]) if you want to contribute but aren't sure where to start.## Common issues