Skip to main content

Privacy Policy

Effective November 21, 2026

This policy explains what personal data Megido collects about the people who use the MCP server and its HTTP API, the customer portal and this website, why, and what rights they have. The operator of the service, which runs it under the Megido brand, is the controller of this data. Contact: [email protected].

1. What we collect​

Your account. Your email address and name, your second-factor secret if you set one up (stored encrypted), the organizations you belong to and your role in each, and when you accepted the Terms of Service and this policy. When you register, also the organization name you gave, if any, and what you told us you want to research, if anything. When you sign up we record where you came from: a label in the link that brought you, if it had one, your answer to "Where did you find Megido?", if you give one, and the name of the chat app you first connect. An account made without registration has no email address or name until you register it.

Signing in. The IP address and time of each sign-in attempt and of each session, and the expiry of your sessions. Session and access tokens are stored only as hashes. A registration link for an account without registration is stored only as a hash and expires after 30 minutes. Successful sign-ins, access resets, confirmations of sensitive actions and other security events are also recorded, with their IP address, in the security log of your account. To limit how many accounts are made from one network, we count the accounts made without registration and the registrations completed from each IP address; each count expires after a day.

Signing in with Google. When you continue with Google, Google tells us the email address of your Google account, whether Google has confirmed it, the Google Workspace domain of the account if it has one, your name and the identifier of your Google account. We use the address and the name as if you had typed them: the address signs you in to its Megido account, and a new account takes the name. Google also sends a link to your profile picture and your first and last names separately, which we do not keep. Google never gives us your password or access to your Google account. For an address outside Gmail and Google Workspace we first send a code to the address; once you enter it, we keep the identifier of that Google account with your account, so that the next sign-in with it needs no code.

Email. We send you the emails the service needs: codes that sign you in, confirm your address or confirm a sensitive action; invitations; a welcome email once your registration is complete; emails about the tasks you gave to Megido's agents, such as an agent's question or a delivered result; and security notices, such as a reset of your access or a newly connected chat app. Codes are stored only as hashes and are kept until used, or up to 30 minutes. For each email we keep its kind, the address and when it was sent; its content is deleted once it is sent.

Using the service. Each call your organization makes: which tool, when, its status, its price, which API key or chat app made it and for whom, and whether it came through MCP or the HTTP API. The estimates behind paid calls, with their parameters. The full responses of paid calls. The projects your organization revealed and the profile parts it bought. A log of changes to accounts, keys, connections and organization settings, with who made them.

Purchases. When an owner buys credits, we keep a record of the purchase: the package, its credits and price, who bought it and when, its status and any refund, and the identifiers the payment provider gives the checkout and the payment. The payment provider takes the payment on its own page: it receives your email address and collects your card or other payment details itself. We never see or store card details.

Feedback. The messages your agents or your software send us with the feedback tool, the projects or niches they name, who sent them and through which API key or chat app, and our progress on them. A message may contain whatever the agent or you wrote into it.

Chat apps. When you connect a chat app, its name and address, and the authorizations you gave it.

The Megido chat. If your organization has the chat (Research in the portal), your dialogs with it: your messages, the model's answers, the tool calls it made for you with their responses, the notes of the news of the tasks given from them, and the names of your dialogs. For each turn, the model it used, the tokens it took and the credits it cost. For each message, the result of the automatic check described below. A message may contain whatever you write into it.

Tasks for Megido's agents. If your organization has them (Agents in the portal), the tasks its people give the agents: the brief and the files attached to it, the messages of the task between its people, the agent and us, the agent's questions and the answers to them, the versions of the result, requests for revisions and decisions on price offers. The agent's work on the task: the AI model's messages, the tool calls it made with their responses, and what they cost. For each task, who gave it and through what (the portal, the chat, a chat app, or an API key through MCP or the HTTP API), when its status changed, and the result of the automatic check of its brief and messages. A brief, a message or a file may contain whatever was put into it.

The website and the portal. If you accept analytics in the cookie banner, the website and the portal measure their use with Google Analytics: the pages you open, the page you came from, your approximate location (country and city), your device, browser, operating system and language, and when you visit. In the portal, Google gets the kind of page you open, not its address: the ids of your organization, dialogs and tasks, the tokens of links and the details of a chat app's request to connect are left out. The portal also tells Google when you sign up, continue without registration, register an account made without registration, sign in, create an API key, copy a chat app's setup or open its one-click install, start a dialog in the chat, give a task to an agent and pay for a credit package, with its price and currency; these events carry no names, email addresses, ids or text you wrote. Google Analytics does not store your IP address. Until you accept, neither the website nor the portal loads analytics, and neither runs advertising. Your browser may store your choice of color theme locally. Our servers record each request to the website, the portal, the MCP server and its HTTP API, with its IP address, the page, the page you came from and your browser, in technical logs. These logs are limited by size, not by time: new requests overwrite the oldest, so how long a request stays in them depends on traffic and can be months.

We do not collect payment card details.

2. Why we use it​

  • To provide the service under our agreement with your organization: accounts, sign-in, calls, billing in credits, purchases of credit packages, reveals and purchases of profile parts. Legal basis: performance of a contract.
  • To answer your questions in the chat with an AI model that calls the service's tools for you, to tell you in a dialog of the news of the tasks given from it, and to keep your dialogs. Legal basis: performance of a contract.
  • To work on the tasks you give the agents with an AI model that calls the service's tools for them, to review results before they are delivered, to keep the tasks and their results, to answer your messages in a task and to send emails about it. Legal basis: performance of a contract.
  • To check each chat message, each brief and each message to an agent automatically before the model reads it, and to answer one that tries to misuse the service with a fixed reply or a refusal. This check makes no decision with legal or similarly significant effects on you. Legal basis: our legitimate interests in securing the service and its data.
  • To limit how many accounts are made from one network. Legal basis: our legitimate interests in securing the service.
  • To send the emails described above. Legal basis: performance of a contract, and our legitimate interest in keeping accounts secure.
  • To keep the service and its data secure: detecting abuse, fraud, automated extraction and unauthorized access. Legal basis: our legitimate interests.
  • To understand demand and improve the service, including by reading and answering feedback. Legal basis: our legitimate interests.
  • To understand how the website and the portal are used and improve them, with Google Analytics. Legal basis: your consent, which you can withdraw at any time.
  • To keep records the law requires, such as accounting records. Legal basis: legal obligation.

We do not sell personal data and do not use it for advertising.

3. Cookies​

The portal uses two strictly necessary cookies that keep you signed in: an access cookie and a refresh cookie. They hold random tokens, are not readable by scripts, and are not used for tracking.

The cookie banner keeps your choice in a strictly necessary cookie for six months. The cookie belongs to megido.io and its subdomains, so the website and the portal share one choice. Only if you accept analytics does Google Analytics set its cookies, _ga and one whose name starts with _ga_, also for megido.io and its subdomains; they tell repeat visits apart, on the website and in the portal alike, and expire after 13 months. In Safari, and in every browser on iPhone and iPad, cookies set by a page's scripts last 7 days at most: there the banner asks again after a week, and the analytics cookies expire after a week. Our network provider may set a strictly necessary cookie when it needs to tell people from automated traffic. To change your choice, open Cookie settings at the bottom of any page of the website, on the portal's sign-in pages or in the portal's account menu; if you withdraw consent, the analytics cookies are deleted.

4. Who sees it​

  • Your organization. Every member of an organization sees its calls and feedback, including who made each call, its parameters and the responses, and our progress on the feedback. The calls the chat makes for you are among them. Your chat dialogs themselves are seen only by you; other members see what the chat cost. Every member also sees the organization's tasks for Megido's agents, with their briefs, files, messages and results, and who gave each. The AI model's own messages on a task are not shown, but the tool calls it makes for a task are among the organization's calls, with the agent and who gave the task. Owners also see the members, their keys and connected chat apps, and the log of changes to the organization.
  • The people who run the service. They can read chat dialogs, to secure the service, to settle disputes about charges, to tune the automatic check of messages and to improve the chat. They also read tasks for Megido's agents, with their files, messages and the agent's work on them, to review results before they are delivered, to answer your messages, to secure the service, to settle disputes about charges and to improve the agents. Each time one of them opens a dialog, a task or a file of a task, this is recorded.
  • Our service providers. Hosting, infrastructure and email delivery providers process data for us under contracts that bind them to our instructions.
  • Our payment provider. It takes payments for credit packages under its own privacy policy, and gets from us the buyer's email address and what is being bought.
  • AI model providers. To answer in the chat, to work on tasks and to check messages, the text of the dialog or of the task, with your messages, the brief, the files attached to it and the responses of earlier calls, is sent to the providers that run the AI models, through a service that routes requests to them. We send it only to providers that do not keep it after answering and do not use it to train models.
  • Google. Google processes the analytics data of the website and the portal for us as our processor. We have turned off Google signals, advertising features and the sharing of this data with Google for its own purposes. When you continue with Google, Google signs you in under its own privacy policy and knows that you use Megido.
  • Authorities and successors. We disclose data when the law requires it, and to a successor if the service changes hands.

5. International transfers​

When data is processed outside the United Kingdom or the European Economic Area, we rely on adequacy decisions or on standard contractual safeguards.

6. How long we keep it​

  • Full responses of paid calls: while your organization's account exists. We keep them to secure the service, to settle disputes about charges and to improve the service.
  • Chat dialogs: while your organization's account exists, including after your own account is deleted. You cannot delete a dialog yourself; you can rename it or archive it, and an archived dialog is kept. You can ask us at [email protected] to delete one.
  • Tasks for Megido's agents, with their briefs, files, messages, results and the agent's work on them: while your organization's account exists, including after your own account is deleted.
  • Files uploaded for a task that was never given: one day.
  • Sessions: until you sign out, or 30 days at most.
  • Sign-in attempts: a short time, for security.
  • Technical logs of requests, with IP addresses: until newer requests overwrite them. The logs are limited by size, not by time, so at low traffic a request can stay in them for months.
  • Analytics of the website and the portal: Google keeps the records of visits for 2 months; reports keep only totals.
  • Your choice in the cookie banner of the website and the portal: 6 months (7 days in Safari and on iPhone and iPad), then the banner asks again.
  • A registration whose address was never confirmed: 72 hours, then it is deleted with its account.
  • An account made without registration: deleted with its organization, its call records and its chat app connections after 30 days without use, unless you register it; the IP addresses in its security log are removed then too.
  • Codes sent by email: until used, or up to 30 minutes.
  • The identifier of a Google account kept for your address: until we reset your access, or your account is disabled or deleted.
  • Records of the emails we sent: 30 days.
  • A request for access we declined before registration opened: kept with your account.
  • Counts of accounts and registrations per IP address: one day.
  • The security log of your account, with the IP addresses of its sign-ins: while your account exists.
  • Records of purchases of credit packages: as long as accounting law requires, which may be longer than your account exists.
  • Your account, your organization's call records, feedback, reveals, purchases and change log: while your account exists. Afterwards we delete or anonymize them within a reasonable period, unless the law requires us to keep them longer.

7. Security​

Second-factor secrets are encrypted, and codes, session tokens and API keys are stored only as hashes. Files attached to tasks are kept in a private store on the servers that run the service. Access to the systems is restricted to the people who run the service.

8. Your rights​

Depending on where you are, you may have the right to access your personal data, to correct it, to have it deleted, to restrict or object to its processing, and to receive it in a portable form. To exercise them, write to [email protected]. You may also complain to a data protection authority; in the United Kingdom, this is the Information Commissioner's Office.

Deleting your account. Write to [email protected] from the address of your account. We disable the account, revoke its API keys and chat apps, and remove its email address, name, second factor, sessions, codes, invitation links, sign-in attempts and records of emails, and the email and IP addresses in its security log. The records your organization keeps of the calls and feedback made through the account stay, linked to an anonymous account, and so do the full responses of those calls, your chat dialogs and the tasks you gave to Megido's agents, which no longer name you.

9. The market data​

The data the service returns describes websites, not the people who use Megido. If you believe it includes personal data about you, write to [email protected].

10. Children​

The service is for businesses and is not meant for anyone under 18.

11. Changes​

We may update this policy. Each version shows its effective date at the top, and the portal asks you to accept a new version before you continue using the service.