Privacy Policy

1. Introduction

MarketCore LLC, doing business as Marcora ("Marcora," "we," "us," or "our"), is committed to protecting your privacy. This Privacy Policy explains how we collect, use, disclose, and safeguard your information when you use our website at marcora.ai and our software-as-a-service platform (collectively, the "Service").

By using our Service, you consent to the data practices described in this Privacy Policy. If you do not agree with this Privacy Policy, please do not use our Service.

2. Information We Collect

2.1 Information You Provide Directly

We collect information you provide directly to us, including:

Account Information:

Payment Information:

Content and Communications:

2.2 Information We Collect Automatically

When you use our Service, we automatically collect certain information:

Usage Information:

Technical Information:

Cookies and Similar Technologies:

2.3 Information from Third Parties

We may collect information from third-party services:

Sign in with Google or Microsoft. If you choose to sign in with Google or Microsoft, we receive your name, your email address, your profile picture if you have one and, for a Microsoft work or school account, your organization's name from that provider. We use them to create your Marcora account, confirm it's you and sign you in. They then become part of your account information and are handled as this policy describes: for example, PostHog receives your name and email address, and your name and picture can appear in session recordings (see Analytics Services below). We don't use them for advertising, and we don't sell them or share them with anyone other than the service providers that help us run Marcora (Section 4.1).

Analytics Services:

We use PostHog to understand how our Service is used, to improve it and to find and fix problems. PostHog links what it collects to your Marcora account, including your name, email address, team and role.

On our website, PostHog records your visit, including the pages you view and what you click, and it can link those visits to your Marcora account once you sign in.

In the Marcora web app, PostHog receives:

Recordings, usage events and error reports from the app leave out:

Errors from those conversations and from payments are reported with fixed wording only. App recordings don't include your browser's network requests or console. For our AI requests, PostHog receives usage metrics such as cost, token counts and timing, not the text of the prompts or answers (Section 2.4). Documents, drafts and other content you create with Marcora's AI appear in recordings like any other content on your screen.

Notifications:

Integration Services:

2.4 Marcora in Slack, Google Chat, Microsoft Teams and Buzz

If your team adds Marcora to Slack, Google Chat, Microsoft Teams or Buzz, this section explains what we receive from that platform, what we do with it and who else receives it. In Slack, Google Chat and Microsoft Teams, and in their app directories, our app is called "Marcora Marketing Agent".

What we receive

Marcora can't see channels, spaces or chats it hasn't been added to. Where it has been added, we receive:

In those messages, Marcora reads only the text you write. If a message in Slack, Google Chat or Microsoft Teams includes a file, the platform may also send us the file's name and link. We keep only the fact that a file was attached, discard the rest, and never open or download files or attachments. Buzz shares a file as a link inside the message text, so in Buzz that link reaches us and is kept with the conversation, like any other link. Marcora may try to open it, as it can any link, but Buzz shows files only to signed-in members of the workspace, so Marcora doesn't get the file. Links in your messages come through as plain text.

Account details we keep

We use these to connect your chat account to your Marcora account and to deliver Marcora's replies:

We don't keep your email address or display name from Slack, Google Chat, Microsoft Teams or Buzz, and Marcora never reads people's Buzz profiles.

How we use it

To reply to you, to do the work you ask for using your team's Marcora context, and to run and troubleshoot the service. Content Marcora creates for you is saved to your team's Marcora workspace and handled like any other content under this policy. We use the feedback and reports you send from Teams to review and improve Marcora's answers, not to train AI models. We don't sell data from chat platforms or use it for advertising.

AI processing

Anthropic runs the agent. It receives each message with a short note about the platform it came from, which for Slack, Google Chat and Buzz names your workspace. It also receives your team's Marcora context, which includes your name and role and your teammates' names and titles, your saved memories (Section 2.5), and everything the agent does to answer, such as its searches and tool results.

OpenRouter receives the first 500 characters of a conversation's first message and of Marcora's reply, to write the conversation's title. When the agent uses Marcora's own tools, for example to draft content, answer from your library or save context, the text it sends them can also go through OpenRouter to the AI model providers it routes to. Content the agent saves can later be processed the same way, for search embeddings and Context Intelligence. When memory is on, the messages you write to Marcora in Slack direct messages and in one-on-one chats in Google Chat and Microsoft Teams also go through OpenRouter to decide what to save (Section 2.5).

Anthropic and the model providers we reach through OpenRouter don't use your inputs or outputs to train their models. Anthropic's commercial terms don't allow it, and every request we send through OpenRouter tells it to use only providers that don't collect request data (Section 4.2).

Other services that receive chat content

Parts of a conversation can also reach these services:

Each of these providers is listed at marcora.ai/security.

Slackbot access

Slackbot, Slack's own AI assistant, can use Marcora's tools. This is optional: it's offered as "Slackbot access" when you install Marcora, and a team that declined can turn it on later from the Slack card in Marcora. Each person signs in to their own Marcora account from Slackbot. Once you've signed in, Slackbot can search your team's context, read your Brand Foundation and create content for you.

Marcora receives only the tool calls Slackbot makes: which tool it uses and the inputs it writes, which can quote your request. We never receive your conversation with Slackbot itself. Results go back to Slack, which handles them under its own terms. Our request logs keep each call's inputs and results as described under Retention, and we keep a record of each call saying who made it, which tool, when, how long it took, whether it worked and which app made it, without its inputs or results. Content created this way is saved to your team's Marcora content like content you create in the app, and the AI requests behind it follow the same no-training rules (Section 4.2).

Buzz workspaces

Marcora connects only to Buzz workspaces hosted by Block, the company behind Buzz. Some workspaces ask everyone who joins to accept a policy, such as terms of use, a privacy policy or an age confirmation. When a Marcora team admin or editor connects one of these, they read and accept its policy on behalf of their team, and Marcora passes that acceptance to Buzz when it joins. Marcora never accepts a policy on its own. We record the version that was accepted in our service logs.

Retention

Removing Marcora

The Slack deletion doesn't reach every copy. It doesn't reach database backups, which expire within 100 days (Section 6); request logs we can't tie to the workspace, whose contents follow the 7-day schedule above and whose entries are kept for 30 days; service and provider logs; or copies that Anthropic, the other AI providers and the services named in this section keep under their own retention terms. For Google Chat, Microsoft Teams and Buzz, removing Marcora doesn't delete data we already hold. Anyone can ask us to delete their own conversations or their account at any time by emailing support@marcora.ai (Section 6). Deleting conversations doesn't delete memories saved from them (Section 2.5).

2.5 Memory

Memory lets the Marcora agent carry useful details between conversations, in your own words. It's on by default for each person in each team; see, edit, delete or turn it off in Memory Settings in your account menu.

When it's on, your messages in private conversations with the agent go through OpenRouter to a TypeSafe model that decides what to save, and Anthropic receives up to 20 of your memories at the start of each new conversation. Section 4.2's no-training rules apply.

Memories are private to you within each team, but replies in shared channels and workflow runs can reflect them, where teammates can see them. They stay until you delete them or ask us to (Section 6). Deleting a conversation or turning memory off doesn't delete them, and neither does removing Marcora from Google Chat or Microsoft Teams. Removing it from Slack deletes memories saved from that workspace within the same 14 business days (Section 2.4), unless you've since edited them. Deleting a memory doesn't change earlier conversations.

3. How We Use Your Information

We use the collected information for the following purposes:

3.1 Service Provision

3.2 Communication

3.3 Business Operations

3.4 Legal and Safety

4. How We Share Your Information

We do not sell, trade, or rent your personal information to third parties. We may share your information in the following circumstances:

4.1 Service Providers

We share information with trusted third-party service providers who assist us in operating our Service:

All service providers are contractually obligated to protect your information and use it only for the specified purposes.

A current list of our subprocessors is maintained at marcora.ai/security.

4.2 AI Service Providers

Marcora generates content using third-party large-language-model providers. Content you create or upload, messages you send Marcora in a chat app (Section 2.4), and your messages and memories when memory is on (Section 2.5), may be transmitted to them to fulfill your requests. Anthropic (Claude) maintains a SOC 2 Type 2 attestation and is called directly under its commercial API terms, which don't allow it to train models on that content. Requests to OpenAI models and a TypeSafe model, and some requests to Claude models, are routed through OpenRouter. Our OpenRouter account settings don't allow paid or free endpoints to train on request data, prompts are never published, and every request we send tells OpenRouter to use only providers that don't collect request data. Your inputs and outputs are not used to train these providers' models.

4.3 Team Members

Within your Marcora team:

4.4 Blueprint Exchange

When you publish blueprints to the Marcora Blueprint Exchange:

4.5 Legal Requirements

We may disclose your information if required by law or if we believe in good faith that such disclosure is necessary to:

4.6 Business Transfers

In the event of a merger, acquisition, or sale of assets, your information may be transferred to the new entity, subject to this Privacy Policy.

5. Data Security

We implement appropriate technical and organizational security measures to protect your information against unauthorized access, alteration, disclosure, or destruction. Our security measures include:

The certifications above are held by our infrastructure providers; Marcora inherits the controls they cover. Marcora (MarketCore LLC) has not yet completed its own independent SOC 2 or ISO 27001 audit. Details: marcora.ai/security. In the event of a data breach affecting your personal data, we will notify affected users without undue delay, consistent with GDPR and applicable state breach-notification laws.

However, no method of transmission over the internet or electronic storage is 100% secure. While we strive to protect your information, we cannot guarantee absolute security.

6. Data Retention

We retain your information for as long as necessary to provide our Service and fulfill the purposes outlined in this Privacy Policy:

You may request deletion of your account and associated data at any time by emailing support@marcora.ai. We delete it from our live systems within 30 days, except where retention is required by law. Backup copies expire within 100 days.

For Marcora in Slack, Google Chat, Microsoft Teams and Buzz, deletion covers your conversations with Marcora, including the records Anthropic keeps for us, and your chat account links. If you ask us to delete your whole team, it also covers the team's chat-app installations. Chat messages copied into our request logs aren't linked to your account, so they're removed on the 7-day schedule in Section 2.4 rather than by your request. Copies held by the other services listed in Section 2.4 are handled through each service's own deletion process and retention terms.

Deleting your data doesn't remove Marcora from your chat platform, and it doesn't delete messages in your Slack, Google Chat, Microsoft Teams or Buzz workspace, which stay under that workspace's own settings. To remove Marcora, uninstall it there, or for Buzz, remove the workspace in Marcora's integration settings. Removing Marcora from Slack also deletes that workspace's Marcora conversations from our live systems within 14 business days, as described in Section 2.4.

7. Your Privacy Rights

Depending on your location, you may have certain rights regarding your personal information:

7.1 Access and Portability

7.2 Correction and Updates

7.3 Deletion

7.4 Restriction and Objection

7.5 Marketing Communications

To exercise these rights, please contact us at support@marcora.ai. We will respond to your request within a reasonable timeframe as required by applicable law.

8. International Data Transfers

Your information may be transferred to and processed in countries other than your country of residence. These countries may have different data protection laws than your country.

When we transfer information internationally, we ensure appropriate safeguards are in place to protect your information in accordance with this Privacy Policy and applicable law.

Our primary hosting is in the United States: our application backend and database run on Railway's own infrastructure in its US East region, and Google Cloud Storage holds database backups and stored file objects in the US. We don't pin AI requests to a region. OpenRouter chooses among the providers that host each model, and we don't restrict where those providers process requests.

9. Children's Privacy

Our Service is not intended for children under the age of 18. We do not knowingly collect personal information from children under 18. If we become aware that we have collected personal information from a child under 18, we will take steps to delete such information.

10. Third-Party Links and Services

Our Service may contain links to third-party websites or integrate with third-party services. This Privacy Policy does not apply to those third-party services. We encourage you to review the privacy policies of any third-party services you use.

11. Changes to This Privacy Policy

We may update this Privacy Policy from time to time to reflect changes in our practices or applicable law. We will notify you of any material changes by:

Your continued use of our Service after the effective date of the updated Privacy Policy constitutes acceptance of the changes.

12. California Privacy Rights

If you are a California resident, you may have additional rights under the California Consumer Privacy Act (CCPA):

12.1 Categories of Information

We collect the following categories of personal information:

12.2 Sources and Purposes

We collect this information directly from you, automatically through your use of our Service, and from third parties as described in Section 2.

12.3 California Consumer Rights

You have the right to:

To exercise these rights, contact us at support@marcora.ai.

13. European Privacy Rights

If you are located in the European Economic Area (EEA), United Kingdom, or Switzerland, you have additional rights under the General Data Protection Regulation (GDPR):

13.1 Legal Basis for Processing

We process your personal information based on:

13.2 Privacy Contact

For GDPR-related inquiries, you may contact our privacy team at support@marcora.ai.

13.3 Supervisory Authority

You have the right to lodge a complaint with your local data protection supervisory authority.