Privacy policy
Last updated November 12, 2026.
ArcherMCP (the "Service"), at https://archermcp.com, is operated by 21 Arrows ("we"). This page says what we collect, why, where it is kept and for how long, who can see it, and what you can do about it. It covers the ArcherMCP portal, the ArcherMCP gateway that your AI client connects to, the Gmail, Google Calendar and Google Drive connections that use Google's APIs, Personal Gmail connections that sign in to Gmail with a Google app password, the GitHub connections that use GitHub's API, the Slack connections that use Slack's API, files your company uploads, and S3 buckets your company connects. Where this page and our terms of service say different things, this page governs for privacy.
1. What ArcherMCP does
ArcherMCP sits between the AI client a person uses (Claude, ChatGPT, Cursor, VS Code, Codex and other MCP clients) and the systems their company connects: MCP services, files the company uploads, S3 buckets the company owns, and, optionally, the person's own Gmail, Google Calendar, Google Drive, GitHub and Slack accounts. When the AI asks a connected system a question, ArcherMCP fetches the result, holds any large result in memory, computes figures over it in code when the AI asks, and returns a card that shows what was computed and from what. Every call and computed answer gets a signed receipt.
ArcherMCP is a business tool. Companies sign up, invite their people, and decide which connections those people may use.
2. What we collect and why
| Data | Why | Where and how long |
|---|---|---|
| Account: your email address, password (held by Supabase Auth, never seen by us), second-factor enrollment, single sign-on identity | To sign you in and to know which company you belong to | Supabase Auth and our PostgreSQL database, until your account or company is deleted |
| Mobile number and text message consent: your number, whether, when and how you agreed to receive texts from ArcherMCP, and texts we sent you | To send the account and service texts you agreed to, and to honour STOP | PostgreSQL and Twilio, our SMS provider. Never shared for marketing. See section 7 |
| Company: name, logo, members, roles, teams, invitations, settings and controls | To run the company's workspace and enforce who may use what | PostgreSQL, until the company is deleted |
| Connections: names, URLs and settings of connected MCP services and S3 buckets; API keys, sign-ins to MCP services (OAuth tokens), S3 access keys, Google refresh tokens, GitHub tokens and Slack tokens | To reach the systems you connected, as you | PostgreSQL. Keys and tokens are encrypted (AES-256-GCM) under a master key that exists only in the gateway's environment, bound to the connection and its owner. They are never shown, exported or returned by any API. Kept until you remove them, the connection is deleted, or you leave the company |
| Files your company uploads, and for each one its name, size, type, SHA-256 fingerprint, who uploaded it and when | So your company's AI can read them, and so a figure can name the exact file version it came from | File contents in our object storage, encrypted at rest; the details beside them in PostgreSQL. Every upload is kept as its own version until a company admin deletes the file or the connection, or the company is deleted. See section 6 |
| Install tokens for AI clients | To recognise your AI client | SHA-256 hash only, until revoked or you leave |
| Changes waiting for your approval: the tool, the exact arguments your AI sent (for example a message it wants to send), a one-line summary, and once you decide, the service's answer | So nothing is sent or changed until you approve it, and so your AI can learn the outcome | PostgreSQL. The arguments and the answer are encrypted like keys; only you see the arguments, on the approval page. The arguments are deleted once you deny the change, it is made, or it expires (after an hour); the answer once your AI has read it. The summary, the first 500 characters of the answer, and your decision are kept while the company exists. The summary is also in your approval email, and in the text if you turned approval texts on |
| Results from connected systems, including Gmail, Google Calendar, Google Drive, GitHub, Slack, name.com, Alpaca, Cursor, Twilio, uploaded files read by your AI and files in S3 buckets | To answer the question your AI asked | Memory of one gateway process, for up to 45 minutes or until the process stops. Never written to disk, to the database, to logs or to receipts. See section 3 for Google data, section 4 for GitHub data, section 5 for Slack data and section 6 for files |
| Saved reports: each report's name, its recipe (which tools it calls, on which connections, with which arguments, and the calculations that turn their results into its panels), its schedule, who it is shared with, who opened it and when, and its last 30 snapshots of panel outputs: the computed figures and the columns its owner chose to list, never the rows they were computed from | So the person who saved a report, and the colleagues in the same company they share it with, see the same figures without asking an AI again | PostgreSQL. The recipe and the snapshots are encrypted (AES-256-GCM) under the gateway's master key. Deleted when the report is deleted (by its owner, or by a company admin once the owner has left), or when the company is deleted |
| Texts received on a company's Twilio numbers, once whoever manages the Twilio connection turns receiving on: the sender's number, the number it was sent to, when, the text, how many attachments it had, what happened to each, and who it is for. Photos and documents attached to a text for one person are saved as files in that person's My Files | So the person who holds the number, and their AI, can read texts and documents sent to it | PostgreSQL, until the connection is deleted or the company is; saved attachments are kept like other uploaded files, until the person deletes them. When the person a text was for leaves the company, it is for the company's admins instead. See section 6 |
| Your mobile number for approval texts, if you turn them on: the number, which Twilio connection and sender texts it, when you confirmed it, and why the last text failed, if one did | To text you the link to each change waiting for your approval, as well as emailing it | PostgreSQL, until you turn approval texts off or leave the company. The confirmation code is kept only as a hash, for ten minutes. Company admins see in the activity log that you turned texts on or off and the last four digits, not the number. See section 6 |
| Field names in results: for each tool, the names of the fields its results contain, their types and lengths, how often a value had the format of a card number, Social Security number, bank account number or password, and which fields an admin or a suggestion blocked. Never the values themselves | So your company can choose which fields never reach any AI (data protection), and see what was removed | PostgreSQL, while the company exists. Values that data protection removes are replaced before ArcherMCP holds, hashes, logs or returns a result, so they appear nowhere in ArcherMCP |
| Activity log and receipts: who called which tool when, hashes of inputs and results, row counts, the derivation the AI asked for and the computed result (totals, counts, group labels), admin actions | So your company can see what happened and prove it; so we can operate and secure the Service | PostgreSQL. Kept while the company exists. Receipts are hash-chained, so they cannot be edited or deleted one at a time; see section 12 |
| Operational logs: request times, status codes, error messages, IP addresses | To run and secure the Service | Server logs, rotated; no fixed retention beyond what operating the Service needs |
A group label or a filter value is part of a derivation, so it appears in the log and the receipt. If someone asks for "messages per sender", the sender addresses are in the computed result and therefore in the log. That is by design (a receipt has to show what was computed), and it means the log is not free of business data.
Saved reports are the one place ArcherMCP writes computed results to the database. Where this page says results are held only in memory, that is about the results your AI asks for; a saved report's panel outputs are kept as the table above describes. A report refreshes on the schedule its owner chose (or when they refresh it), by calling the tools in its recipe as its owner, with no AI involved, under the same controls, data protection, activity log and receipts as any call. People a report is shared with see its snapshots and never reach its sources. Reports built from Google, GitHub, Slack or Microsoft 365 data can be kept and opened by their owner only; they cannot be shared.
We do not store your prompts to your AI, your AI's answers, or the credentials your AI client holds for its own provider.
3. Google user data (Gmail, Google Calendar and Google Drive connections)
A Gmail connection lets a person link one or more of their own Google accounts so that their AI can search and read that mail through ArcherMCP. A Google Calendar connection does the same for calendars and events, and a Google Drive connection for files in Drive. The three are separate: an account linked to one grants nothing to the others. This section describes exactly how ArcherMCP accesses, uses, stores and shares Google user data. ArcherMCP'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.
What we ask Google for
openidandemail: to know which Google account you linked and to show you its address.https://www.googleapis.com/auth/gmail.readonly, for Gmail connections only: to search and read mail, labels and attachment names in that account. This scope cannot send, delete, modify or label mail, and ArcherMCP has no tool that tries.https://www.googleapis.com/auth/calendar.readonly, for Google Calendar connections only: to list the calendars in that account and read their events (times, titles, locations, descriptions, attendees and their responses, conference links) and busy times. This scope cannot create, change, delete or respond to events, and ArcherMCP has no tool that tries.https://www.googleapis.com/auth/drive.readonly, for Google Drive connections only: to search, list and read the files in that account and shared drives it can reach (names, folders, metadata, who a file is shared with, and the contents of a file when your AI reads one). This scope cannot create, change, share, move, trash or delete files, and ArcherMCP has no tool that tries.
Each connection asks for openid, email and its own scope, nothing more. These read-only scopes are what a company's Google app asks for at the read-only level described next.
Your company's own Google app
ArcherMCP does not link Google accounts through an app of its own. A company that wants Gmail or Calendar connections creates its own Google OAuth client, in its own Google Cloud project, and gives it to ArcherMCP under Company settings. Its people link their accounts through the company's app: Google's consent screen shows the company's app, and the company decides what it may ask for. Until a company adds one, nobody in it can link a Google account. A company admin chooses one of two levels:
- Read-only: the two read-only scopes above.
- Full access:
https://www.googleapis.com/auth/gmail.modifyfor Gmail, to also send mail and replies, create, send and delete drafts, add and remove labels (which is how mail is archived or marked read), create labels, and move mail to and from Trash. It cannot delete mail permanently.https://www.googleapis.com/auth/calendarfor Calendar, to also create, change and delete events and answer invitations. Andhttps://www.googleapis.com/auth/drivefor Drive, to also create files and folders, edit, rename and move files, share files with people and remove their access, and move files to and from the Trash. It cannot delete a file permanently. ArcherMCP makes such a change only when your AI calls the tool that makes it, on your behalf, and records it in your company's activity log. A company admin can hold those tools for approval or turn on read-only mode under Controls.
The company's client secret is encrypted like the keys in section 2 and used only to sign that company's people in and refresh their tokens. When the company replaces or removes its app, ArcherMCP deletes the accounts linked through the old one and asks Google to revoke them. If ArcherMCP adds another Google service, this page will name its scopes before the connection is offered, and Google will ask you for consent again.
How we access it
You link an account from a connection page in the portal. Google shows its consent screen; you may decline. If you grant access, Google gives ArcherMCP a refresh token, which ArcherMCP encrypts and stores as described in section 2. ArcherMCP uses it to obtain short-lived access tokens, held in memory, only when your AI calls a Gmail, Calendar or Drive tool. ArcherMCP never accesses your mail, calendars or files on a schedule, in the background, or for any purpose other than answering a request your AI made on your behalf. Every such request is recorded in your company's activity log under your name.
How we use it
- To return search results, messages, threads and labels, or calendars, events and busy times, or Drive files and their contents, to your own AI client, in response to a question you asked it.
- Where your company gave full access: to send, draft, label, archive or trash mail, create, change, delete or answer events, or create, edit, move, share or trash Drive files, as you, when your AI asks to.
- To compute over those results in code when your AI asks (for example, count messages per account or per sender, add up meeting hours per calendar, or total a spreadsheet read from Drive) and to return the computed figures.
- Nothing else. We do not use Google user data for advertising, for profiling, to train or improve machine-learning or AI models, to build or sell datasets, or for any purpose unrelated to the feature you are using.
Where it goes (sharing)
- Your AI client and its model provider. Mail or calendar data that answers your question, or a small sample of a large result, is returned to the AI client you installed ArcherMCP in. That client sends it to its model provider (for example Anthropic or OpenAI) under that provider's terms. You choose the client; ArcherMCP sends Google data nowhere else. This is the only transfer of Google user data ArcherMCP makes, and it exists solely to provide the feature you asked for.
- Your company's activity log. Only what section 2 describes: hashes, row counts, the derivation and the computed result. Never message bodies, event details or file contents, and never the raw result rows. Company admins and managers can see the log for the whole company; users see only their own.
- Your approval email. When approval by email is on and your AI asks to send mail, change an event, or create, change, share or trash a Drive file, ArcherMCP emails you, and only you, a one-line summary: the recipients and subject, the event's title, time and invitees, or the file's name and the person and role a share is for. Never a message body, event description or file contents. The full call is shown only on the approval page, after you sign in.
- Our infrastructure providers (section 9) process data on our behalf as described there. Google user data held in gateway memory is on a server we rent; the refresh token is in the database in encrypted form.
- We do not sell Google user data, and we do not share it with anyone else, except if the law requires it or to investigate abuse or a security incident.
How long we keep it
- Mail, calendar and Drive file content: in the memory of one gateway process, for up to 45 minutes after it was fetched, or until the process stops, whichever is first. It is never written to disk, the database, logs or receipts.
- Refresh token, account email and Google account id: until you remove the account, the connection is deleted, or you leave the company.
- Access tokens: in memory, until they expire (about an hour).
Human access
No person at 21 Arrows reads your mail, calendars or files. We do not have a tool that displays Google user data, and refresh tokens are unreadable without the gateway's master key. We will only read Google user data with your explicit consent (for example, to help with a problem you report), when necessary for security or to investigate abuse, to comply with law, or after it has been aggregated so it does not identify anyone.
Removing access
- On the connection page, remove a Google account. ArcherMCP deletes the stored token immediately and asks Google to revoke its grant.
- Or revoke ArcherMCP at myaccount.google.com/permissions. ArcherMCP will then fail to reach that account and will tell you to reconnect or remove it.
- Leaving a company removes every Google account you linked under it.
4. GitHub data (GitHub connections)
A GitHub connection lets a person link one or more of their own GitHub accounts so that their AI can read repositories, issues, pull requests, commits and files, propose changes to them, create new repositories, and merge, close or reopen a pull request once you approve it, through ArcherMCP. It is handled the same way as Google data in section 3, with these differences.
What we ask GitHub for
ArcherMCP signs you in through a GitHub App. The app is registered with read and write access to repository contents, issues and pull requests, read and write access to repository administration (so it can create new repositories), and read access to metadata, and it works only on the accounts and organizations that installed it, on the repositories they chose. You also see and change only what your own GitHub account can already see and change; GitHub's branch protection and organization rules apply as they would to you. ArcherMCP never gets access to any other user's repositories through your link, and nobody else's link reaches yours.
What your AI can change is limited to proposals made as you, creating new repositories, and merging, closing or reopening a pull request: creating a branch, committing to a branch other than the repository's default branch, opening or editing a pull request, requesting reviewers, opening an issue, adding a comment, creating a new repository (private unless you ask for a public one) under your account or an organization you belong to, and merging, closing or reopening a pull request. A merge, close or reopen runs only after you approve that exact action by email, and only within GitHub's own rules (branch protection, required reviews and checks, and what your account may do). ArcherMCP has no tool that commits to the default branch, bypasses branch protection, deletes a branch, or that deletes, renames, archives, transfers, changes the visibility of, or changes the settings of a repository that already exists. Company admins can require approval before any of these run, or switch them off with read-only mode. The content your AI writes is sent to GitHub, recorded by GitHub under your account, and is not kept by ArcherMCP beyond the hash of the call in the activity log.
How we access, use, share and keep it
- You link an account from a connection page. GitHub shows its authorization screen; you may decline. If you authorize, GitHub gives ArcherMCP an access token and, for apps that issue them, a refresh token. Both are encrypted and stored as described in section 2, and rewritten each time GitHub rotates them.
- ArcherMCP calls GitHub only when your AI calls a GitHub tool, never on a schedule or in the background, and records every such call in your company's activity log under your name.
- Repository data is used only to answer your AI's request and to compute over the rows it asked for (for example, open issues per repository or commits per author), and is returned only to your own AI client. It is held in the memory of one gateway process for up to 45 minutes and is never written to disk, the database, logs or receipts. It is not used for advertising, profiling or training models, and it is not sold or shared with anyone else, except if the law requires it or to investigate abuse or a security incident.
- Tokens, your GitHub login and account id are kept until you remove the account, the connection is deleted, or you leave the company. Removing an account deletes the tokens immediately and asks GitHub to revoke the grant; you can also revoke ArcherMCP under your GitHub account's Applications settings, after which ArcherMCP will tell you to reconnect or remove it.
- No person at 21 Arrows reads your repositories through the Service, and tokens are unreadable without the gateway's master key.
5. Slack data (Slack connections)
A Slack connection lets a person link one or more of their own Slack workspaces so that their AI can read the channels, messages, threads and people they can already see there, and post, edit, delete and react as that person, through ArcherMCP. It is handled the same way as Google data in section 3, with these differences.
What we ask Slack for
ArcherMCP signs you in through a Slack app and asks only for user-token scopes, never a bot. To read: channels:read, channels:history, groups:read, groups:history, im:read, im:history, mpim:read, mpim:history, users:read, and for search search:read.public, search:read.private, search:read.im and search:read.mpim, which you may decline. To act: chat:write (post messages and replies, and edit or delete your own), reactions:write (add reactions) and im:write (open a direct message with someone). Everything your AI posts appears under your name, only when your AI calls one of those tools, and is held for approval wherever your company requires approval for changes. ArcherMCP has no tool that uploads files, joins or leaves a channel, invites anyone, or edits or deletes another person's message. The text your AI sends is passed to Slack; the activity log keeps only a fingerprint (a hash) of it, not the text. A post waiting for approval is kept with its exact text, as the table in section 2 describes for changes waiting for approval. A workspace linked before these scopes were offered keeps reading and cannot post until you link it again. Because the token is yours, it reaches only the public channels of your workspace and the private channels, direct messages and group messages you are already a member of. Workspace admins who require approval for apps approve ArcherMCP before a link completes.
How we access, use, share and keep it
- You link a workspace from a connection page. Slack shows its authorization screen; you may decline. If you authorize, Slack gives ArcherMCP an access token and, if the app uses token rotation, a refresh token. Both are encrypted and stored as described in section 2, and rewritten each time Slack rotates them.
- ArcherMCP calls Slack only when your AI calls a Slack tool, never on a schedule or in the background, and records every such call in your company's activity log under your name.
- Messages and member details are used only to answer your AI's request and to compute over the rows it asked for (for example, messages per channel or per person), and are returned only to your own AI client. They are held in the memory of one gateway process for up to 45 minutes and are never written to disk, the database, logs or receipts. They are not used for advertising, profiling or training models, and are not sold or shared with anyone else, except if the law requires it or to investigate abuse or a security incident.
- Tokens, the workspace's name, domain and id, and your Slack user id and name are kept until you remove the workspace, the connection is deleted, or you leave the company. Removing a workspace deletes the tokens immediately and asks Slack to revoke them; you can also remove ArcherMCP from your workspace's app settings, after which ArcherMCP will tell you to reconnect or remove it.
- No person at 21 Arrows reads your Slack messages through the Service, and tokens are unreadable without the gateway's master key.
5a. Microsoft 365 data (Outlook mail and calendar connections)
An Outlook connection lets a person link one or more of their own Microsoft accounts (Microsoft 365 work or school accounts, and personal Outlook.com accounts) so that their AI can read and, if the connection allows it, act on their mail or calendar through ArcherMCP. It is handled the same way as Google data in section 3, with these differences.
What we ask Microsoft for
ArcherMCP signs you in through its Microsoft Entra app with delegated permissions only, so it can never reach more than your own account can. To identify the account: openid, profile, email, User.Read and offline_access. For Outlook mail: Mail.ReadWrite and Mail.Send, to search, read, draft, send, move and mark mail when your AI asks. For Outlook calendar: Calendars.ReadWrite, to read events and create, change, delete and answer them when your AI asks. If the gateway is set to read-only, it asks only for Mail.Read or Calendars.Read. It asks for no application permissions and cannot reach other people's mailboxes. Organizations that let only admins approve apps approve ArcherMCP before a link completes.
How we access, use, share and keep it
- You link an account from a connection page. Microsoft shows its consent screen; you may decline. If you accept, Microsoft gives ArcherMCP an access token and a refresh token. Both are encrypted and stored as described in section 2, and rewritten each time Microsoft renews them.
- ArcherMCP calls Microsoft Graph only when your AI calls an Outlook tool, never on a schedule or in the background, and records every such call in your company's activity log under your name. Sending mail and changing events can be held for your approval under Controls.
- Mail and calendar data is used only to answer your AI's request and to compute over the rows it asked for, and is returned only to your own AI client. It is held in the memory of one gateway process for up to 45 minutes and is never written to disk, the database, logs or receipts. It is not used for advertising, profiling or training models, and is not sold or shared with anyone else, except if the law requires it or to investigate abuse or a security incident.
- Tokens, the account's email address and name, its Microsoft user id and its tenant id are kept until you remove the account, the connection is deleted, or you leave the company. Removing an account deletes the tokens immediately. Microsoft has no way for an app to give up one person's grant itself, so to end it at Microsoft too, remove ArcherMCP at https://myapps.microsoft.com (work or school) or https://account.live.com/consent/Manage (personal); ArcherMCP then tells you to reconnect or remove the account.
- No person at 21 Arrows reads your mail or calendar through the Service, and tokens are unreadable without the gateway's master key.
5b. QuickBooks data (QuickBooks Online connections)
A QuickBooks connection lets a person link one or more QuickBooks Online companies they can already open, so that their AI can read and, if the connection allows it, record in their books through ArcherMCP. It is offered only to companies ArcherMCP has switched it on for, and is handled the same way as Google data in section 3, with these differences.
What we ask Intuit for
ArcherMCP signs you in through its Intuit app and asks for one permission, com.intuit.quickbooks.accounting, for the one company you pick on Intuit's screen. It acts as your QuickBooks user, so it can never reach more than you can in QuickBooks. Intuit does not offer a read-only permission; ArcherMCP serves only read tools unless it has been set to allow changes, and changes can be held for your approval under Controls. ArcherMCP does not ask for payments or payroll access.
How we access, use, share and keep it
- You link a company from a connection page. Intuit shows its consent screen; you may decline. If you accept, Intuit gives ArcherMCP an access token and a refresh token for that company. Both are encrypted and stored as described in section 2, and rewritten each time Intuit renews them.
- ArcherMCP calls QuickBooks only when your AI calls a QuickBooks tool, never on a schedule or in the background, and records every such call in your company's activity log under your name.
- Accounting data is used only to answer your AI's request and to compute over the rows it asked for, and is returned only to your own AI client. It is held in the memory of one gateway process for up to 45 minutes and is never written to disk, the database, logs or receipts. Reports built from it cannot be shared with other people. It is not used for advertising, profiling or training models, and is not sold or shared with anyone else, except if the law requires it or to investigate abuse or a security incident.
- Tokens, the company's name, its QuickBooks company id (realm id) and its country are kept until you remove the company, the connection is deleted, or you leave the company in ArcherMCP. Removing it deletes the tokens immediately and asks Intuit to disconnect ArcherMCP from that company. You can also disconnect ArcherMCP from within QuickBooks, under Apps; ArcherMCP then tells you to reconnect or remove it.
- No person at 21 Arrows reads your books through the Service, and tokens are unreadable without the gateway's master key.
6. Files you upload, S3 buckets, and name.com, Alpaca, Cursor and Twilio accounts you connect
A file connection gives your company's AI a set of files: either files a company admin uploads in the portal, or files in an S3 bucket (or S3-compatible store) your company owns. When the AI reads a table from one of them, ArcherMCP reads the rows, computes figures over them in code, and the card names the exact file, version and SHA-256 fingerprint the figures came from.
Files you upload
- Only a company admin (or, for a personal connection, its owner) can upload or delete files. Everyone who gets the connection can have their AI list, read and search them; nobody can change or delete a file from an AI client.
- Uploaded files are stored in object storage we operate with Amazon Web Services, encrypted at rest, under a location unique to your company and connection. Uploading a file with the same name adds a new version and keeps the earlier one, so figures computed from it can be traced to the bytes they came from.
- We keep each file until a company admin deletes it (which deletes every version), the connection is deleted, or the company is deleted. When a connection is deleted, its files are removed from storage within minutes. The fingerprint, name and size of a file may remain in your company's receipts, which are kept as section 12 describes; the contents do not.
- When your AI reads a file, its contents are handled like any other result: held in the memory of one gateway process for up to 45 minutes and never written to the database, logs or receipts.
- Through Agent Exchange your AI can attach files from your My Files or Company Files to a question it asks someone (PDF, images, CSV, Excel and MP3, WAV or M4A recordings). No copy is made: the person asked, and their AI, may open exactly the versions you attached, including across companies, until you delete the file or the question is deleted, and may save a copy into their own My Files, which is then theirs. A short text extract of each file (at most 4,000 characters a question) is given to their company's AI model to write the reply. A recording is transcribed once, through the AI model key of the asked person's company (or, where that company uses models ArcherMCP provides, ArcherMCP's own OpenAI key), and the transcript is kept beside the recording and deleted with it. A company admin can turn attachments off for questions asked of their company's people.
S3 buckets you connect
- A company admin chooses the bucket and the folders ArcherMCP may read, and gives access either through a role ArcherMCP assumes (with an external id unique to that connection) or through an access key, which is encrypted as section 2 describes. We recommend a role, and a role or key that can only list and read unless your company turns on uploads from AI clients (below).
- ArcherMCP reads the bucket only when someone's AI calls a file tool, and only under the chosen folders. It keeps no copy: file contents are held in memory for the answer, as above.
- ArcherMCP never moves, replaces or deletes your files. It writes to the bucket only if whoever manages the connection turns on uploads from AI clients, which is off by default and needs your company to grant write access to the role or key. While it is on, a person's AI can add new files inside the chosen folders, never over an existing file. Each upload is recorded under that person's name and, where approval applies, waits for their approval. Until an upload is finished its bytes wait in a
.archermcp-uploads/folder in your bucket, which ArcherMCP deletes once the upload is finished, refused or abandoned. The bytes go straight to your bucket and are not stored by ArcherMCP.
name.com accounts you connect
- A Name.com connection lets your AI read the domains, DNS records, forwarding, orders and transfers in a name.com account, check availability and pricing, and change DNS records, nameservers, auto-renew, the transfer lock and WHOIS privacy. It has no tool that can buy, renew or transfer a domain, change contacts or spend money.
- A company admin (for a shared account) or each person (for their own) enters the account's API username and token in the portal. ArcherMCP checks them against name.com once, then encrypts them together as section 2 describes; nobody can read them back. A username ending in
-testis sent to name.com's sandbox instead of the live service. - ArcherMCP calls name.com only when your AI calls a Name.com tool, never on a schedule, and records every call in your company's activity log. Results are held in memory for the answer, as above, and never stored. The username and token are kept until the key is removed, the connection is deleted, or the person leaves the company; name.com's own privacy policy applies to the account.
Alpaca accounts you connect
- An Alpaca connection lets your AI read an Alpaca brokerage account's balances, positions, orders, portfolio history and activity, and market data (quotes, trades, bars, snapshots, news), and place, replace and cancel orders and close positions. It has no tool that can deposit, withdraw or transfer money, change account settings or read account documents.
- A company admin (for a shared account) or each person (for their own) enters the account's API key ID and secret key in the portal. ArcherMCP checks them against Alpaca once, then encrypts them together as section 2 describes; nobody can read them back. A key ID starting with
PKis sent to Alpaca's paper-trading environment, where no real money is traded; one starting withAKis sent to the live environment. - ArcherMCP calls Alpaca only when your AI calls an Alpaca tool, never on a schedule, and records every call in your company's activity log. Results are held in memory for the answer, as above, and never stored. The key pair is kept until the key is removed, the connection is deleted, or the person leaves the company; Alpaca's own privacy policy and customer agreement apply to the account.
Cursor accounts you connect
- A Cursor connection lets your AI list a Cursor account's Cloud Agents, their runs, results, branches, pull requests and token usage, and start agents on repositories, send them follow-ups, cancel runs and archive agents. Prompts your AI writes are sent to Cursor, and the agents work on your repositories under the key owner's Cursor account. It has no tool that can delete an agent, change Cursor environments or secrets, or give an agent secrets.
- A company admin (for a shared key) or each person (for their own) enters a Cursor API key in the portal. ArcherMCP checks it against Cursor once, then encrypts it as section 2 describes; nobody can read it back.
- ArcherMCP calls Cursor only when your AI calls a Cursor tool, never on a schedule, and records every call in your company's activity log. Results are held in memory for the answer, as above, and never stored. The key is kept until it is removed, the connection is deleted, or the person leaves the company; Cursor's own privacy policy and terms apply to the account and to the agents' work.
Twilio accounts you connect
- A Twilio connection lets your AI read a Twilio account's name, status and balance, its phone numbers and Messaging Services, and the text messages it sent and received (who, when, the text itself, delivery status and price), and send a text message to one phone number at a time. The recipient's number and the text your AI writes are sent to Twilio, which delivers it and bills the account. It has no tool that can buy or release numbers, change the account's settings or webhooks, place calls, delete messages or text a list of people at once.
- A company admin (for a shared account) or each person (for their own) enters the account's Account SID and Auth Token in the portal. ArcherMCP checks them against Twilio once, then encrypts them together as section 2 describes; nobody can read them back.
- ArcherMCP calls Twilio when your AI calls a Twilio tool, never on a schedule, and records every call in your company's activity log; the one other time is the approval texts below. Unless the person turns it off, a text waits for their approval by email before it is sent. Results, including message history, are held in memory for the answer, as above, and never stored. The pair is kept until it is removed, the connection is deleted, or the person leaves the company; Twilio's own privacy policy and terms apply to the account and to the messages.
- Whoever manages a Twilio connection can turn on receiving texts. Twilio then sends each text that arrives on the account's numbers to ArcherMCP, signed with the Auth Token; anything unsigned is refused. ArcherMCP stores the sender's number, the number it was sent to, the time, the text and the number of attachments until the connection or the company is deleted. Photos and PDF, Word, Excel, CSV and plain text documents attached to a text for one person are downloaded from Twilio and saved in that person's My Files, under Texts/, as files uploaded in their name; they are kept and deleted like any other uploaded file. If the text is for everyone who gets the connection, or the person has no My Files, the attachments are not downloaded and stay only in Twilio. Video, audio and other attachments are never downloaded. A company admin can assign a number to one person: its texts are then theirs and the company's admins' to read, and other people at the company cannot read them or send from that number. Texts on numbers nobody holds are for everyone who gets the connection. A personal connection's texts are only its owner's. Your AI reads them only when it calls list_inbox. When someone leaves the company, their numbers go back to everyone and the texts they received go to the company's admins.
Personal Gmail accounts you connect
- A Personal Gmail connection lets your AI search and read the mail in a personal @gmail.com account (messages, threads, attachments' names and sizes, labels and drafts), send and reply, create, send and delete drafts, add and remove labels, archive, mark read, star, move mail to Spam and to and out of Trash, and create labels. Mail your AI writes, and any of your uploaded files it attaches, are sent through Gmail to the recipients. It has no tool that deletes mail permanently.
- Each person enters their own Gmail address and a Google app password in the portal; there is never a shared one. ArcherMCP signs in to Gmail with them once to check them, then encrypts them together as section 2 describes; nobody can read them back. An app password reaches the whole mailbox: Google does not let it be limited to reading or to some labels, which is why the change tools wait for approval unless the person turns that off.
- ArcherMCP reaches Gmail over IMAP and SMTP, encrypted, only when your AI calls a Personal Gmail tool, never on a schedule, and records every call in your company's activity log. It keeps a sign-in to Gmail open for up to a minute after a call so the next one is quick. Mail is held in memory for the answer, as above, and never stored, used for advertising or used to train models. The address and app password are kept until the person removes them, the connection is deleted, or the person leaves the company. Revoking the app password at myaccount.google.com/apppasswords cuts ArcherMCP off at once; so does changing the Google account password. Google's own privacy policy and terms apply to the account.
AI model keys you connect (OpenAI, Anthropic, Google Gemini, Amazon Bedrock)
- A model connection lets your company's AI clients call that vendor's models through ArcherMCP's /v1 endpoint with your company's own key. The prompts, documents and images a client sends, and the model's answer, pass through ArcherMCP to the vendor and back. ArcherMCP does not store them: it keeps who called, which model, the token counts, an estimated cost, timings, whether the prose check changed the answer, and SHA-256 fingerprints of the request and response, in your activity log and receipts.
- A company admin (for a shared key) or each person (for their own) enters the key in the portal; for Bedrock, an AWS region and a Bedrock API key or IAM access key. ArcherMCP checks it against the vendor once, then encrypts it as section 2 describes; nobody can read it back, and AI clients never see it.
- When an answer follows ArcherMCP cards in the same conversation, ArcherMCP compares its figures with the cards in memory, as the model proxy does, and may annotate or block it as your company chose. The vendor bills your company for the tokens under your agreement with it; its own privacy policy and terms apply to what it receives. The key is kept until it is removed, the connection is deleted, or the person leaves the company.
Use and human access
Files are used only to answer your company's AI requests. They are not used for advertising, profiling or training models, and are not sold or shared with anyone else, except if the law requires it or to investigate abuse or a security incident. No person at 21 Arrows opens your files except with your company's explicit consent (for example, to help with a problem you report), when necessary for security or to investigate abuse, or to comply with law.
7. Text messages (SMS) from ArcherMCP
ArcherMCP sends text messages only to people who give us a mobile number and agree to receive them. The program, what it sends, how often, and how to stop are in our SMS terms.
- What we keep: your mobile number, whether you agreed to receive texts, and when and how you agreed (the date, the page or form, and the IP address), so we can prove consent and honour opt-outs. We also keep the messages we sent you and their delivery status, for up to 12 months.
- How we use it: only to send the account and service messages described in the SMS terms, such as approval requests, security and sign-in alerts and problems with your connections. Never for advertising, and never to train models.
- No sharing for marketing: we do not sell, rent or share your mobile number, your SMS opt-in or consent information, or the contents of the texts we send you with any third party or affiliate for their marketing or promotional purposes. Text messaging originator opt-in data and consent are not shared with any third parties.
- Who handles it: Twilio, our SMS provider, receives your number and each message only to deliver it, and our hosting and database providers (section 9) store it for us. They may not use it for anything else.
- Stopping: reply STOP to any text to stop all texts at once, or HELP for help. You can also email matt@techvalidus.com. After you opt out we keep only the record of your opt-out, so we do not text you again. Message and data rates may apply.
This section is about texts ArcherMCP sends to you. Texts your company's AI sends through your company's own Twilio connection are covered in section 6 and by your company's own SMS program.
8. How companies are kept apart
Every dataset, log row, receipt, connection and control is owned by one company. The portal's tables are under row level security and the gateway checks the company on every request, so no company can read another's data. Companies share our gateway processes and one database; the separation is logical and tested, not physical. Our security page, in the project documentation, describes this in more detail.
9. Who processes data for us
- Supabase: authentication (passwords, second factors, single sign-on) and the PostgreSQL database that holds companies, connections, encrypted keys and tokens, the activity log and receipts.
- Our hosting provider: the virtual server that runs the portal and the gateway, where results are held in memory.
- Amazon Web Services: object storage for the files your company uploads, encrypted at rest. When your company connects its own S3 bucket, ArcherMCP reads it, and adds files to it where your company has turned that on, through AWS under your company's agreement with AWS.
- Google: when you link a Google account to a Gmail or Calendar connection, ArcherMCP calls Google's APIs as you. Google's own privacy policy applies to that account.
- GitHub: when you link a GitHub account to a GitHub connection, ArcherMCP calls GitHub's API as you. GitHub's own privacy statement applies to that account.
- Slack: when you link a Slack workspace to a Slack connection, ArcherMCP calls Slack's API as you. Slack's own privacy policy and your workspace's agreement with Slack apply to that workspace.
- name.com: when your company enters a name.com API username and token in a Name.com connection, ArcherMCP calls name.com's API with them. name.com's own privacy policy and your agreement with name.com apply to that account.
- Alpaca: when your company enters an Alpaca API key ID and secret key in an Alpaca connection, ArcherMCP calls Alpaca's Trading API and Market Data API with them. Alpaca's own privacy policy and your customer agreement with Alpaca Securities apply to that account.
- Cursor: when your company enters a Cursor API key in a Cursor connection, ArcherMCP calls Cursor's Cloud Agents API with it, including the prompts your AI writes. Cursor's own privacy policy and your agreement with Cursor apply to that account.
- Twilio: when your company enters a Twilio Account SID and Auth Token in a Twilio connection, ArcherMCP calls Twilio's REST and Messaging APIs with them, including the phone numbers and texts your AI sends. Twilio's own privacy policy and your agreement with Twilio apply to that account.
- Amazon Web Services (Amazon Bedrock): when your company leaves field suggestions on, ArcherMCP sends an AI model on Amazon Bedrock a tool's name and description and the names, types, lengths and matched formats of the fields its results contain, to suggest which fields to block. Never the values in them, and nothing at all from Google connections. Amazon does not use Bedrock inputs to train models. A company admin can switch suggestions off under Controls.
- Twilio (ArcherMCP's own texts): delivers the text messages ArcherMCP sends to people who agreed to receive them, described in section 7. Twilio receives the mobile number and the message only to deliver it.
- Resend: delivers the portal's email, such as invitations and the approval emails described in sections 2 and 3, to your address.
- Your AI client's provider: chosen and installed by you; receives what ArcherMCP returns to that client.
We do not use advertising or analytics trackers on the portal.
11. Security
Connections to ArcherMCP use TLS. Keys, sign-ins to MCP services and Google, GitHub and Slack tokens are encrypted at rest with AES-256-GCM under a master key kept only in the gateway's environment, bound to their owner so a sealed value cannot be moved to another connection or person. Fetched results never leave process memory. Uploaded files are encrypted at rest in object storage, and each file's SHA-256 fingerprint is checked every time it is read, so a stored file that changed is refused rather than used. Two-step sign-in is available to everyone and a company admin can require it. Every administrative action is recorded before it takes effect. No outside security review has been completed yet; we say so plainly in our security documentation.
12. Your choices and rights
- See and export: download a copy of the data ArcherMCP holds about you, as a JSON file, under Settings, Your account. It leaves out keys, passwords and stored sign-ins, which are never exported. Your company's activity and receipts are available in the portal to your company's admins and, for your own activity, to you.
- Remove: remove a Google account, a GitHub account, a Slack workspace, an API key, a sign-in to an MCP service, an S3 access key or an uploaded file at any time from the connection page. Signing out of an MCP service also asks that service to end the sign-in, where it supports that. Leave a company from your company's People page (an admin can also remove you). A company admin can delete connections and the company.
- Delete your account: under Settings, Your account. The account is deleted seven days after you ask, and you can cancel until then, from the link we email you or by signing in; in that time we may hold the request to check it came from you, but never past 30 days. We sign you out everywhere straight away. On the day, we delete the account, its membership, every key and Google, GitHub and Slack token it held, and its personal connections and entries, and revoke the Google, GitHub and Slack grants. If you were the only member of your company, the company is deleted too; otherwise shared items you made stay with the company. You can also email us at matt@techvalidus.com from the address on the account, and we do the same within 30 days.
- Receipts: log rows and receipts your actions created are part of a hash chain your company relies on for evidence, so we do not edit or delete individual entries. They contain no message, event or file content; they contain your user id, the tool names, hashes, and the derivations and computed results described in section 2.
- Access, correction, portability and objection: where the law gives you these rights, write to us and we will respond within 30 days.
13. Children
ArcherMCP is for businesses and is not directed at anyone under 16. We do not knowingly collect data from children.
14. Changes to this policy
If we change how we handle Google user data, GitHub data, Slack data, files or anything else material, we will update this page, change the date at the top, and tell company admins by email before the change takes effect. Continued use after that date means you accept the updated policy.
15. Contact
21 Arrows, operator of ArcherMCP. Privacy and security questions: matt@techvalidus.com.