Privacy policy

Updated 7 November 2026

ArcRoom keeps a team playbook for you, your team and your agents. This page shows what goes into it, where it lives, and what never leaves your hands.

Stays on your machine

  • Your file contents, tool output and edit diffs, unless your agent saves them to team memory on purpose (a failed command’s error text is sent, redacted)
  • Secrets we detect, removed before anything is sent
  • Your AI provider account and its keys

Reaches ArcRoom

  • Your account: name, email, a hashed password
  • Run metadata from the plugin: prompts, paths, commands, redacted
  • Memory: answers, steps, decisions, failures and their versions

Never happens

  • Sold, rented or used for ads
  • Used to train any AI model
  • Shown to anyone outside your workspace, other than the providers that run ArcRoom for us (listed in section 05)

The data map

WhatExactlyHow long
AccountName, email, password hashUntil you ask us to delete it
Sign-in sessionsA random token; we keep only its hash30 days, or until you sign out
Workspace and teamWorkspace name, members and roles, projectsUntil the owner deletes the workspace
API keysOnly a hash and the first 8 charactersUntil revoked; stops working at once
Run eventsPrompts (first 1,000 characters); tool names with their file paths, search patterns, shell commands (first 1,000 characters), URLs and web queries; machine name and folder; git hashes of touched files; done-check commands and results; token counts; the first 500 characters of a failed command’s error. Never file contents or edit diffs. Redacted on your machine.Your plan’s history (7 days on Free, 90 days on Pro), then deleted
Run summariesPrompt, outcome, timing, token counts and the run reportYour plan’s history (7 days on Free, 90 days on Pro)
Team memoryTask descriptions, answers, steps, decisions, failures, rules, desks, versions, who saved each one, model names, token costWhile the workspace exists; answers stop being reused after your "keep answers for" setting
What ArcRoom told your agentSize of each piece of context it added; the text of hand-overs and the last-run note (up to 2,000 characters)90 days, with run events

01 · Who we are

In short ArcRoom AI runs this website, the app and the API behind the ArcRoom plugin.

This policy covers arcroomai.com, the ArcRoom web app and the ArcRoom API that the plugin on your machine talks to (together, “ArcRoom”). “We” means the team that runs ArcRoom AI.

02 · What we collect

In short Your account, your team’s setup, and the run events and memory the plugin sends. The data map above lists each one.

Account. Your name (optional), your email and a hash of your password. We never store the password itself.

Workspace and team. Workspace names, who is a member and their role, projects and the repo or folder each one belongs to.

Run events. When the plugin is on, ArcRoom sends metadata about a run: your prompt, which tools ran and on which paths, shell commands, URLs and queries, the machine name and folder, done-check results, timing and token counts. They never send your file contents or edit diffs; of tool output, only a failed command’s first 500 characters of error text go, redacted. What your agent saves to team memory on purpose is sent and kept as team memory. What is sent lists every field.

Team memory. When your agent saves a solved subtask, we store the task description, the answer, the steps that produced it, the model that ran it and what it cost in tokens, with every version. When it saves a decision, we store its text, who saved it and when.

Technical. Like every website, our servers see your IP address when you connect. We do not add it to your account or workspace data.

03 · What stays on your machine

In short Your file contents stay with you, unless your agent saves part of one to team memory on purpose. What leaves is metadata, and secrets we can recognise are removed before upload.

The plugin does not upload your repository, file contents, tool output or edit diffs. The exceptions are what you type or paste into a prompt, what your agent saves to team memory on purpose, and the error text of a failed command (first 500 characters). Otherwise it sends run metadata only, and before sending it removes text that looks like keys, tokens and passwords. Detection is pattern based, so it is best effort: please do not paste secrets into prompts.

Events wait in a local queue file on your machine and are sent when you're back online. Your AI provider account and its keys are never sent to us.

04 · How we use it

In short To run ArcRoom for you, and for nothing else.

  • Show your team’s run reports and dashboards;
  • Find and reuse answers your workspace already paid for, and replay their steps;
  • Keep accounts secure and stop abuse;
  • Answer you when you write to us.

Matching by meaning. To match a new task to stored ones, the task text (the first 300 characters of a prompt, with secrets already redacted) and the text of saved answers and decisions are sent to Google's Vertex AI embedding model (gemini-embedding-001), which turns them into numbers we compare. We never use your data to train a model. Your agent itself runs on your own account with your own AI provider.

05 · Who can see it

In short Members of your workspace, and the providers that run ArcRoom for us. Nobody else.

Runs and team memory are visible to the members of the workspace they belong to. Decisions saved as yours, and an answer your agent marked private when it started the task, are visible only to you until you share them. Other workspaces never see your data.

We use providers that run the service for us, bound to use the data only for that:

  • Supabase (database): the Postgres database where ArcRoom’s data is stored;
  • Oracle Cloud (our server): the machines that run the ArcRoom API;
  • Google Cloud (Vertex AI): turns task texts into embeddings for matching, as described above.

We do not sell or rent your data, and we do not share it for anyone’s advertising.

06 · How long we keep it

In short Runs are kept for your plan's history (7 days on Free, 90 days on Pro) and then deleted. Memory lives as long as the workspace; delete the workspace and all of it goes at once.

Runs (the step-by-step trace and the summary of each one) are deleted when they are older than your plan's history: 7 days on Free, 90 days on Pro. Memory is kept while its workspace exists; a failure no agent hits for 30 days is removed. Answers stop being reused once they are older than the workspace’s “keep answers for” setting (1 day unless the owner changes it); the steps that produced them are kept so they can be replayed.

When an owner deletes a workspace, its runs, memory, projects and keys are removed together, immediately. We keep no backups, so they can't be recovered. Sign-in sessions end after 30 days. Your account stays until you ask us to delete it.

07 · How we protect it

In short Hashes instead of secrets, a locked database, and encryption on the way in.

  • Passwords, sign-in tokens and API keys are stored as hashes.
  • The database cannot be reached from the internet directly: every read and write goes through the ArcRoom API, which checks your key or session.
  • Traffic to our hosted service is encrypted (HTTPS).

No system is perfectly secure. If something goes wrong that affects your data, we will tell you.

08 · Your choices and rights

In short Turn things off yourself, or write to us for anything else.

  • Stop sending data: run arcroom off in a repo, take ArcRoom out of a project with arcroom uninstall, or revoke its key in Settings → API keys.
  • Stop a wrong answer being reused: expire it from the Memory page.
  • Delete everything for a team: Settings → Danger zone (workspace owners).
  • See, export, correct or delete your account: email us and we will do it.

09 · Cookies

In short One cookie to keep you signed in. No analytics, no ads.

The details are on Cookie settings.

10 · Children

In short ArcRoom is a tool for teams at work, not for children.

We do not knowingly collect data from anyone under 16. If you think a child has signed up, write to us and we will delete the account.

11 · Changes to this policy

In short We change the date at the top, and tell signed-in users about anything that matters.

If a change affects what we collect or who sees it, we will say so in the app before it takes effect.

12 · Contact

In short One address for anything about your data: sachin.kumar@arcroomai.com.