Short form
During the beta, your prompts are processed on computers in the Feya network, including Macs and PCs run by other Feya members, which can see what you send while they answer it. This is a concession we are making for the beta, so please don’t share anything sensitive. Feya does not store your chat history during the beta: your conversations are not saved on our servers, in your browser, or on the computers that answer them (except that, rarely, part of a conversation can end up in an error log on our servers or on those computers, as the full notice explains).
Long form
What happens to a prompt during the beta
- A beta concession: prompts and responses are processed on member computers. The coordinator sends each request to a computer in the network that serves the model. That may be a Feya-operated machine, or a Mac or PC run by another Feya member, either serving the model on its own or leading a cluster. That computer handles the full prompt and response for the duration of the request.
- When a model is split across several computers, treat every computer in the split as able to see what you send. One computer leads the split and handles the full prompt and response, as above. The others each run some of the model’s layers. The one running the first layers receives your prompt, and the reply as it is written, as numbers that can be turned straight back into the words. The rest receive the model’s intermediate results for your prompt; we have not measured how much of your text can be recovered from those, so do not assume they hide it. Traffic between the computers in a split goes through Feya’s relay, which can read it too; a split set up to connect its computers directly sends it between them unencrypted.
- A small share of requests are checked for honest answers (see the audit bullet below). The request is sent to two computers chosen at random, and to a third if their answers differ. Each of them sees that request. If the check produces no usable answer, the request is then routed the usual way and may reach more computers.
What we protect
- No chat history is stored during the beta. Conversations are not saved on Feya’s servers, not kept in your browser between visits, and not written to disk by the node software on the computers that answer them. One exception: if a request or a reply arrives malformed, or a computer reports an error, part of your prompt or of its reply may be written to a log file, by the node software on that computer or by Feya’s coordinator, which routes it. For rewards Feya records usage: which model, how many tokens, and which computer served the request, never the text itself. The computer that answers also keeps a signed receipt, which it sends to Feya to check. The receipt holds a fingerprint (an unsalted SHA-256 hash) of the model and the whole conversation it was sent, and of the answer. It doesn’t contain the text, but anyone holding it can check whether a guessed conversation or answer matches.
- What our servers log. Like most websites, Feya’s servers record the internet address each connection comes from, the page or API address requested, your browser’s or app’s name, and the time. Some log lines include your email address. One-time sign-in and unsubscribe links are recorded with their codes removed. Our web server deletes its logs after about 11 days. Our application logs are limited by size, not by date; today they reach back about 10 days. We keep a record of the emails we send you (address, kind, time, whether sending succeeded) for 90 days. For each request we also keep, for 30 days, your account, the identifier of the API key used, the model, the computers that answered and the times, never the text. We keep, with no end date for now, the address you signed up and activated from and your browser’s language.
- If you run Feya on a computer, we record the network its address belongs to and a map point: the place you typed when you set it up (which can be a city), or else your country. While it’s online, anyone can see that point, its country and the place name on Feya’s public map. A country-only point is shown at the capital.
- Connections to Feya are encrypted in transit. Feya’s apps and installers connect to Feya over TLS by default, and each computer proves its identity with its own key. Not everything is encrypted, though:
- Feya can also send a request straight to a computer at an address it registered (on the internet, or on a shared local network), instead of over that computer’s own connection to Feya. If that address isn’t https, your request travels to it unencrypted.
- Traffic inside a split goes through Feya’s relay and is not end-to-end encrypted: the relay can read it. A split set up to connect its computers directly sends that traffic between them unencrypted.
- Computation correctness on the standalone path is verified by random audits. Providers caught tampering lose their reputation and network access.
- MAGIC accounting is backed by signed work receipts. The protocol is public, so any provider can verify their balance (see work receipts).
What we do not guarantee
- During the beta, the member computer that answers your request can see your prompt and its response while it works on them; so can the other computers in a split (see above), and Feya’s coordinator and relay, which route it. This is not cryptographically prevented.
- For maximum-sensitivity content, use a local model or our Private Mode product when available.
- Traffic metadata (timing, request size) is visible to intermediate nodes.
- User-provider machines run our signed runtime but are not hardware-attested.
