Privacy
Effective 6 September 2026. Operated by ETOT (Eric Frye, Minneapolis, USA). Questions: hello@etot.design — we reply within two working days.
This page covers the ETOT website and the Motif tools: the Figma/FigJam plugin, the hosted engine behind it, and the MCP server. It is written to be read, not skimmed; the short version is first.
The short version
- Your interview transcripts are processed for one run and then deleted. We don't keep them.
- Your Anthropic API key stays on your device. It passes through our server only for the length of a request, is never written to disk or logs, and is never used for anything but your run.
- We don't have accounts, we don't run analytics on the site or the plugin, and we don't sell or share anything.
- The plugin and the engine are open source: github.com/sleepycobalt/motif. What this page says can be checked against the code.
- The model calls go to Anthropic under your key and your agreement with them, not ours.
What the plugin sends, and where
When you run a synthesis or a check in the plugin, it extracts the text of your transcripts on your computer (for .docx files the paragraphs are read inside the plugin, so the file itself is never uploaded) and sends that text, your research question, and your API key over HTTPS to our hosted engine at motif-hosted.fly.dev, which runs on Fly.io in Chicago, USA. The engine forwards the transcripts and the model prompts to Anthropic's API using your key, and streams the results back to the plugin. Nothing goes anywhere else.
Uploads are capped at 12 MB per file and 64 MB per run.
Your API key
The plugin stores your key in Figma's client storage on your device. It is sent to our engine in a request header for each run and held in memory only while that run's requests to Anthropic are in flight. It is not written to disk, not logged, and not visible to us after the request ends. If you change or remove the key in the plugin, it is gone from your device; we never had a copy.
On the free tier every run uses your key. ETOT's own key is never used for a free run.
What the engine keeps, and for how long
For each run the engine keeps a working copy of your transcripts and the run's output (the report with its receipts) on the server while the run is in progress and for about one hour afterwards, so the plugin can fetch the result, receipts, and board layout if you closed the window. A scheduled sweep then deletes the working copy and the run's output. This behaviour is covered by an automated test in the public repo, and we checked it by hand on the live server on 5 September 2026.
The engine keeps a redacted log of each run for diagnostics: the run's settings, token counts, timings, cost, the critic's verdicts, and a cryptographic digest (a hash and a character count) of each prompt and response — not their text. Transcript text does not appear in these logs; a test asserts that, and it caught one case where it did before launch, which was fixed before the plugin shipped. These redacted records are deleted 30 days after the run.
Fly.io, like any host, records connection metadata (IP address, time, request path) in its platform logs under its own policy. We use the IP address only to rate-limit concurrent runs from one source.
What Anthropic receives
Your transcripts and the synthesis prompts are sent to Anthropic's API under your key. How Anthropic handles that data — retention, training, region — is governed by your agreement with Anthropic, not by us; their API data policies are at anthropic.com. We cannot see, change, or delete anything on their side. If your transcripts are sensitive, read their policy before running.
The MCP server and the command line
If you run Motif locally (pip install etot-motif, the CLI or the MCP server in local mode), nothing leaves your machine except the model calls to Anthropic under your key. Runs, logs, and transcript copies are stored on your own disk in the run folder. In remote mode the MCP server uses the hosted engine and the sections above apply.
The website
etot.design is a static site on Netlify. It sets no cookies, runs no analytics, and has no accounts. Netlify records connection metadata under its own policy. Email to hello@etot.design is forwarded by ImprovMX to a Gmail mailbox and kept as ordinary correspondence.
What we don't do
We don't store your transcripts beyond the run. We don't read them. We don't use them to train anything. We don't sell, share, or pass any of it to third parties beyond the hosting and model providers named above. We don't have user accounts, tracking pixels, or advertising.
Paid tier
When prepaid credits become available, payments will be handled by Stripe; card details go to Stripe and never to us. We will keep a record of your purchases and remaining balance, and this page will be updated before that tier opens.
Your choices
Stop using the plugin and the hosted engine at any time; there is nothing on our side to delete beyond the hour-long working copies described above. Remove your key from the plugin's settings to delete it from your device. Email hello@etot.design for anything else, including a request to confirm that no run data of yours remains.
Changes
Changes to this page are dated at the top, and the page's history is in our website repository.