Privacy policy.

Static pages, and nothing that watches.

evoke.build is a set of static pages. It sets no cookie, runs no analytics and asks you for nothing. The pages, the fonts and the manual are served from this address, so reading here calls no third party.

• The manual remembers your sidebar in your browser's own storage. It stays there, and is sent nowhere.
• A Copy button touches your clipboard only when you press it.
• GitHub hosts these pages. It logs the IP address of each visit, for security, under its privacy statement.
• Installing goes through GitHub and npm. The install script fetches the release from GitHub, and npm fetches the SDK from the npm registry. Each sees that download under its own policy.

Your sentence goes to the classifier. Nothing goes to us.

A reflex is a small program you install and ask for in your words. evoke runs on your computer. It never contacts evoke.build, checks for nothing and reports nothing. There is no server of ours on the way, and no telemetry.

When it decides

• Each decision is one request, through your project's adapter. jev, the default, reaches Jev at TypeSafe AI. openjev reaches Jev through OpenJEV, an independent service that forwards the request. clef and clef_flash reach Clef, another classifier, at Cloudflare. The request carries your sentence and the questions built from the reflexes you installed. Each reflex adds its description, what it is not for, its examples, and each input's question and options. Your vocabulary adds its words, with the meaning you wrote for each.
• A sentence that may hold several steps can make more than one request. Where a word such as and or then, or a comma, could separate two things, one request asks the classifier whether it does. Each step is then decided with a request of its own, and when a sentence has three steps or more, a word such as them can take one more. Each carries only your words and questions built from them and from your reflexes. How a sentence is read →
• A sentence you repeat is answered from a cache on your machine, with no request, as long as your installed reflexes and your own words for them have not changed. The cache →
• Nothing else of yours travels. Never a vocabulary's value, a setting, a key, a file, or anything else on your machine. Your key goes only in that request's header, to the classifier.
• A proxy you name in your environment carries the connection, and sees ciphertext.
• With the openjev adapter, OpenJEV sees the request first. It is an independent service, not TypeSafe AI's. As of the date at the top of this page it publishes no privacy policy and no terms, so nothing states what it keeps. Weigh that before you choose it.
• With the clef or clef_flash adapter, the request goes to Cloudflare instead. Clef is Cloudflare's model, served by its Workers AI, and TypeSafe AI sees nothing of such a request. What Cloudflare does with it is set by its privacy policy and its data usage page for Workers AI. As of the date at the top of this page, that page says your requests are not used to train its models or to improve its services without your consent.
• What TypeSafe AI does with a request to Jev is set by its privacy policy and customer agreement, which you accept when you take a key. As of the date at the top of this page, the customer agreement says your input is not used to train its models without your consent. It also lets TypeSafe AI derive information from your requests, such as logs, metrics and summary statistics, and use it without restriction, including to improve its services.

What stays on your machine

• The log of decisions and the history of the REPL hold what you typed and what a program returned, in ~/.local/state/evoke/. Only you can read them.
• The answer cache and the fetched reflexes live under ~/.cache/evoke/. Delete them any time. The next run rebuilds them.
• Your words, your lessons and your settings are files you own and edit, in ~/.config/evoke/.
• No key is ever written to a file. A secret is only ever a reference to a variable in your environment, and reaches a program for the length of one run.

To forget everything, delete those three directories. Every path is listed on the manual's environment page, and the guarantees around them on its security page.

A reflex is a program. It runs as you.

A reflex runs under your account with the arguments decided, and does what its author wrote: an email drafted, a file saved, a light switched. Where it sends what is the reflex's own doing, and its body is one file you can read before you install it.

• Installing a reflex fetches it from the git host its ref names, with your own git credentials. That host sees the fetch.
• A program runs under a scrubbed environment of five variables, and gets a secret only through its settings, for one run.
• The first-party collection acts on your Mac, and reaches only the addresses you name: a file to download, a site to visit, a mail to start.

Read what you install. add and update are the trust decisions, and the security page says what is guaranteed around them, and what is not.

Inside your application, under its policy.

The SDK runs inside your application and sends the same requests to the adapter your application configures, with your application's key. We receive nothing.

What your application does with its users' sentences, and what it tells them, is your application's responsibility, and belongs in its own privacy policy. The adapters page says exactly what an adapter is given.

The other parties, and what each one sees.

None of them is us. Each sees only what its line names.

• TypeSafe AI sees every request evoke makes through jev, the default adapter, and each one OpenJEV forwards when a project names openjev. Its privacy policy and customer agreement apply.
• OpenJEV sees a decision's request when your project names openjev, and forwards it to Jev. It publishes no privacy policy and no terms, as of the date at the top of this page.
• Cloudflare sees a decision's request when your project names clef or clef_flash. Its privacy policy and its data usage page for Workers AI apply.
• GitHub sees a visit to this site, a download of a release, and a fetch from a repository it hosts. Its privacy statement applies.
• npm sees an install of the SDK. Its privacy policy applies.
• Your git host sees a fetch of a reflex you install from it, under your own account and its terms.

This page is a file in the repository.

Every change to it is a commit anyone can read, with its date, in the repository's history. The date at the top of this page is the last change.

• If a version of evoke or of this site ever sends or keeps something new, this page changes in the same commit, so what the page says is what the tool does.
• Nothing is held by us, so there is nothing we could hand over, correct or delete. What is on your machine, you delete. For what a party above holds, its own policy says how to ask.
• A question is an issue on GitHub. A vulnerability goes through GitHub's private form, never a public issue.

Questions about evoke → What you need to get started →