Agents: this page is also Markdown; every page is in llms.txt.

Privacy and data

Your Tasks are yours. Facet uses what you put in only to build, check and serve your Tasks, never to improve anything for anyone else. The full terms are in the privacy policy; this page is the short version for builders.

What Facet keeps

What Kept For how long
Your Task: description, Instructions, Expectations, examples, versions Yes While the Task exists; unused versions move to cold storage, so you can roll back
Calls to a Task: the messages and the answer Not by Facet. They pass through to answer the call; Modal, which runs it, holds them briefly Up to 7 days at Modal, then deleted
Calls to a Task: version, key, token counts, latency, request ID Yes, to bill you and show usage 90 days
Examples sent to the open models that write and check examples No: only hosts that keep nothing once they answer Not kept

Who sees it

Hidden examples

When you add examples, some are hidden. Once hidden, an example is read only by Facet's checks: not by you, not by Facet's agent, and never used to build a version. That's what makes a green check honest: no version can learn its own test. Exports leave hidden examples out for the same reason.

Keys

API keys start with fct_. Facet stores only a hash of each key, so a lost key can't be shown again; make a new one and revoke the old one under Settings, Keys. A key can be limited to one Task, and a viewer key only reads.

Delete

Next steps