Privacy Policy

doo.mcp is operated by TraceNcode (“we”, “us”, or “our”). The service hosts AI agents, chat channels, and MCP tools for a workspace you create.

If you connect the service to a store, an Odoo database, WhatsApp, Twilio, or Google Calendar, you are responsible for the customer and employee information those systems already hold.

We collect what the product needs to create the account and run the agents you turn on.

• Account. Name, work email, and password. If you sign up with Google, we receive the name and email Google shares for that sign-in.
• Workspace. Which agents you subscribe to, each agent's plan and usage meters, API keys, and the website widget key.
• Content you add. Pages, text, and files you train; talk tracks; and meeting caption text when you start notes.
• Conversations. Messages sent through the widget, mobile chat, WhatsApp, and staff agents, including images when image search is used. Conversation media may be stored so those channels can run and show history.
• Connections. Odoo credentials and WhatsApp tokens, stored encrypted and decrypted only when a tool has to call that system. Calling uses the Twilio number you connect. Calendar booking uses the Google Calendar you connect.
• Billing. Each paid agent is its own subscription. We store the plan and invoice status Stripe sends us for that agent. Card details are collected by Stripe, not stored by us.
• Cookies and local storage. See cookies below.

The browser stores a small set of values so the product can run. Session tokens keep you signed in. The cookie banner remembers whether you accepted all cookies or necessary ones only.

• Necessary. Sign-in, security, and remembering this cookie choice. The site cannot work without these.
• Optional. Used only if you choose Accept all. You can change that anytime from Cookie settings in the footer. If you accept all, the website assistant also remembers a random visitor id so we can tell a return visit from a new one.

The assistant on doomcp.com answers questions about the platform. We keep what you ask and what it replies, so we can improve the answers and the site.

• What we record. Your questions and the replies, the page you were on, the site you came from, a coarse device description (such as mobile, Chrome, macOS), your country when the network provides it, and a random id the browser creates.
• Your address is masked. We store only part of your IP address (the last part is removed), never the full address, and we do not ask for your name or email in the assistant.
• Please do not share secrets. Do not type passwords, card numbers, or other sensitive details into the assistant.
• Who can read it. Only the doo.mcp team. To have your conversations deleted, write to us from the contact page and include the time you chatted.

• Create and secure the workspace, and sign people in.
• Run the agents, tools, and channels you enable.
• Meter each agent on its own allowance: AI responses for Chatbot Agent, eCommerce Agent, and Odoo Agent, and calling minutes for Lead Agent. Notetaker does not draw on the Chatbot or eCommerce allowances.
• Bill each agent subscription separately and show invoices.
• Detect abuse, debug failures, and reply to support requests.

Built-in chat channels may send the prompt for a reply to a model provider we operate through. We use workspace content to provide the service. We do not sell it.

• Model providers such as OpenAI, Anthropic, or Gemini, when a doo.mcp channel writes a reply. The prompt for that reply is sent so the answer can be generated.
• Stripe for each agent subscription you pay for.
• Meta when you connect WhatsApp.
• Twilio when Lead Agent places a call on your number.
• Google when you sign in with Google or book on Google Calendar.
• Your Odoo for catalog, cart, CRM, and staff tools. The agent uses the connection you configured.

If your team connects Claude or Cursor over MCP, that client uses its own model. We authenticate the key and run the tools. We do not bill you for that model.

If you choose to connect a Google account, doo.mcp asks Google for the access below. We ask only when you click Connect, and only for the scopes the feature needs.

• Email address and basic profile (openid, userinfo.email). Used to show which Google account is connected and to sign you in.
• Calendar events, read and write (calendar.events). Used by Lead Agent to create a meeting on your primary calendar, with a Google Meet link, when a lead books a time, and to send the invite.

What we store. The connected account’s email address and the OAuth tokens Google issues, encrypted at rest. We do not copy your calendar into our database beyond what a booking you create needs to show its time and link.

Limited Use. doo.mcp’s use and transfer to any other app of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements. We use Google user data only to provide the features described here. We do not sell it, use it for advertising, or use it to train generalized AI models, and humans do not read it except with your consent, to investigate abuse, or to meet legal requirements.

Disconnect and delete. A workspace owner can disconnect Google from Dashboard → Accounts at any time. We then ask Google to revoke the token and delete the stored connection. You can also remove access from your Google Account permissions page. Deleting the workspace removes the connection as well.

• Shoppers’ card numbers. Checkout and payment stay on your store or your payment provider.
• Meeting audio or video. Notetaker reads captions in the tab you already have open.
• A copy of your whole Odoo database.
• Another customer’s workspace.

People you invite to the workspace can see the agents, conversations, and settings that workspace holds, according to the role you give them.

We share information with the processors in section 4 so the feature you turned on can run, and when the law requires it. We do not sell personal information.

We keep account and usage records for as long as the workspace is active, and afterward as needed for billing, security, and legal compliance.

A workspace owner can delete the account from the dashboard. That removes the workspace, keys, and chat history on doo.mcp. Your Odoo database is not deleted. Stripe may keep invoice records under its own policy.

Each workspace is a separate tenant. Connector secrets are encrypted at rest. How a request is allowed to touch your systems is described on the security page.

We may update this policy. The effective date at the top of this page will change when we do. Continued use of the service after that date is acceptance of the update.

Privacy questions: contact us, or tracencode.com. The rules for billing and acceptable use are in the Terms of Use.