A1 AI engineering company GitHub

Privacy policy

Effective date: 30 August 2026. Русская версия.

This policy covers the open-source MCP servers published by A1 (the A1-x-Tech organization on GitHub and the corresponding npm packages) and the a1x.tech website. The short version: A1 servers run entirely on your device, your credentials and your content never pass through A1 infrastructure, and A1 has no access to your accounts.

How A1 MCP servers work

Every A1 MCP server is an open-source program that you install and run locally — inside your AI client (Claude, Cursor, Codex and others). The server talks directly from your device to the platform API you connect it to (Google, Yandex, Avito, VK, Shopify or Yango). There is no A1 backend in this path: no proxy, no relay, no server-side storage. What the server does is visible in its source code.

Google user data

Servers of the mcp-google-* line access Google user data through official Google APIs, with your explicit OAuth consent, and only within the scopes you approve — for example calendar events, tasks, contacts, form responses, spreadsheet or document content, depending on the server you install.

  • What is accessed. Only the data needed to execute the request you make in your AI client, at the moment you make it. Servers request the minimum OAuth scopes their tools need; the scopes are listed in each server's README.
  • How it is used. Solely to perform your requests. Data returned by a tool becomes part of your conversation with the AI assistant you connected the server to — that assistant is chosen and configured by you and is governed by its own privacy terms. A1 does not see this data.
  • Where it is stored. OAuth tokens are stored in a local file in your user profile, readable only by your account. Google content itself is not persisted by the server; it exists only in memory while a request is being processed and in your AI client's conversation.
  • What is shared. Nothing. A1 does not receive, store, transfer, sell or share your Google user data. Human beings at A1 cannot read it — technically there is no channel through which it could reach us.
  • AI/ML training. A1 does not use any data obtained through Google APIs to develop, improve or train generalized artificial intelligence or machine learning models.
  • Limited Use. A1'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.

Data of other platforms

Servers for Yandex, Avito, VK, Shopify and Yango follow the same principles: API credentials live only on your device, requests go directly to the platform, and A1 has no access to your accounts or data.

Revoking access and deleting data

You stay in control at all times:

  • disconnect a server in your AI client — it stops running entirely;
  • revoke a server's Google access at myaccount.google.com/permissions (or the equivalent page of the platform), or use the server's logout tool where available — it revokes the token at the platform and deletes the local token file;
  • delete the local configuration files of a server at any time — they are plain files in your user profile.

Since A1 stores nothing, there is nothing else to delete on our side.

Anonymous usage telemetry

A1 servers send anonymous technical events (server start, tool name called) to count active installations and understand which tools matter. An event carries only impersonal fields: a random installation id, package version, the AI client's name and version, the Node.js version and the OS. Credentials, account identifiers, tool arguments, file contents, messages and any other user data are never sent. Telemetry can be disabled for all A1 servers at once with the environment variable ASKADS_TELEMETRY=0; details are in each server's README.

The a1x.tech website

This website uses Yandex Metrica to understand how visitors use it, including session replay (Webvisor), click maps and link tracking. Metrica sets cookies and processes visit data under Yandex's privacy policy. The website has no accounts, forms or databases of its own and collects nothing else.

Changes to this policy

If this policy changes, the new version is published on this page with an updated effective date. The page history is available in the website's public repositories.

Contact

Questions about this policy: Telegram or an issue in the relevant repository of the A1-x-Tech organization.