PRIVACY / WHAT THE SITE RECORDS
Privacy
Last updated 13 November 2026
Automaton Chandlery is run by Dead Reckoning Foundry. This page describes what the site records, written from how the site works on the date above. It names the other services that see your data and says what it does not cover.
Reading the public pages
The shelf, the packouts, the tools and the agent index need no account.
When you open a public page or use a tracked control, your browser sends our server one small message: the kind of event and the page path or control name. The server adds one to a daily count for that pair. The message has no free-text field, and the server accepts only values from a fixed list. It does not store your network address, your browser string, a referrer, an account or a cookie ID with the count. Some counts are made on the server instead: a try-box result type, a published skill read, an agent index read, a packout page and a loadout copied into a workspace. They hold the same kind of value, such as a skill name or a packout name. To limit abuse, the server also counts requests by address in memory in the same way for the endpoint that receives these messages, and drops them on the same schedule as for the try box below.
The try box
The try box on the shelf, and the address /shelf/match.json that it calls, match your one-line task against the published shelf in the server’s memory. The task line is not stored and is not sent to any other service. Only the kind of result (a match, no match, an invalid request or a rate limit) is added to a daily count. To limit abuse, the server keeps your network address in memory and does not write it to disk, to count your requests over one minute. It is dropped at the first clean-up after that minute ends. Clean-ups run at most once a minute and only when a request arrives, so with steady traffic an address stays 60 to 120 seconds, and with no traffic it stays until the next request or until the server restarts. The web server in front of it also limits request rates by address, and its access log may record your address, and the URL if you call that address yourself with the task in the URL.
Visit count on the home page and two tools
Three pages load a hidden frame from automaton-memory.com, another Dead Reckoning Foundry site: the home page, /tools/astra and /tools/fable. Each sends the frame one message that says the page was viewed. The message holds a fixed type label and a site label. It does not carry the page address, anything from a workspace, who you are or any other property. The frame is loaded without a referrer.
The frame belongs to that other site, and it decides whether to record the view with Google Analytics. A recorded view carries a fixed page address and title for that page and no referrer. Google’s own terms cover what Google receives. Loading the frame is a request to automaton-memory.com, which sees what any web server sees when it is asked for a page.
Accounts and sign-in
Sign-in and sign-up are handled by Clerk. Clerk holds the details you give it when you sign up and the session that keeps you signed in. Chandlery’s own code does not read your email address or your name from Clerk. For each account it stores your Clerk user ID and a fixed placeholder name. Prompts you save in a prompt lab while signed in belong to your account, not to a workspace, and are stored with their name, text, goal, domain and context.
Where sign-in is turned on, the Clerk script loads on every page of this site, public pages included. Chandlery’s own code does not set cookies and does not write to your browser’s local or session storage. Clerk’s script, which this site loads, may do both.
What a workspace holds
An account has one or more workspaces. A workspace holds what you or your agents put in it:
- skills and other items you import or save, their versions and the scan results for them;
- profiles, which are the sets of pinned versions you grant to an agent;
- agent connections, with a label, the connecting client and host, when it was last seen, and a hash of its token where one was minted (the token itself is not kept);
- receipts of some calls a connected agent makes, described below;
- members and their roles, invitations, and an audit log of actions in the workspace;
- text runs you start, with the prompt, the plan and each model’s output.
Only members of a workspace can read it through the site.
OpenRouter keys
You may add an OpenRouter API key to a workspace, as a personal key or one shared with the workspace. The key is encrypted with a key held on the server before it is stored. Keys are decrypted on the server when a run is made. A personal key is used only for runs you start. A key shared with the workspace is used for runs started by any member of it. A run decrypts every key available to it, yours and the workspace’s shared keys, not only the one that makes the call. The workspace screen lists a key by its label, never its value. A text run sends its prompt to OpenRouter using such a key, so OpenRouter’s terms cover what it receives.
Connected agents
An agent connects to /api/v1/mcp only after you approve it in your workspace. Five tools leave a record in your workspace, visible to you. The other calls, which search or list skills and profiles or read the status of a proposal, an outcome or a changelog, write no record.
- a task call (
skills_for_task) stores the task line the agent sent (up to 500 characters) and which skills were picked; - a loadout call (
loadout) stores the same; - a read (
skill_read) stores the skill, its version and the section read; - feedback (
skill_feedback) stores the verdict the agent reported for each skill, specialist or playbook it was given, a note of up to 2000 characters, and any outcome evidence it attached; - a proposal (
skill_propose) stores the full skill text the agent sends (up to 48,000 characters), its name and slug, a rationale of up to 2000 characters, the scan result, and, only when the agent supplies them, a source URL, an author (up to 200 characters, which can be a person’s name), a license (up to 100 characters), a community rating (value, source and date) and the id of the version it would replace. It waits in your review queue and publishes nothing.
To rank skills, and the specialists and playbooks a profile pins, for a task, the server can send the task line and short skill, specialist or playbook descriptions to a ranking or embedding service that Dead Reckoning Foundry runs itself, to a model reached through OpenRouter, or to an OpenAI-compatible service the deployment names for a second opinion on the ranking. Which of these are switched on, and where the last one runs, is a setting of the deployment. Where OpenRouter or another outside provider is used, its terms cover what it receives. The public try box does not use them.
Where the deployment turns on a second scan of imported skill text, the scanner can send that text to a model provider named by its settings. Where one-click approval is switched on, an unapproved agent’s connection attempt leaves a pending request tied to your Clerk user ID and outside any workspace, with the agent’s issuer, credential ID, client ID and name, redirect hosts and scopes. Requests that expire unanswered are swept; decided requests are kept.
Verdicts count toward the evidence for a skill version. The public shelf shows counts from the owner’s dated publication, which do not move between publications. Where live counts are switched on, a version shows them only once at least five different people have reported on it.
What this page does not cover
This page says what the app does. The web server’s access log may record addresses and URLs; this page does not say how long that log is kept. It does not set how long any records are kept, and it does not describe the practices of Clerk, OpenRouter or Google. When the site changes, this page changes and the date at the top changes with it.
Terms →Trust and limits →Questions and requests
Write to drew@automaton-memory.com to ask what a workspace holds, or to have an account and its workspace removed. There is no self-serve delete yet, so removal is done by hand on request.