Terms of Service.

Saylek is operated by Saylek LLC, a Washington limited liability company organized under the Washington Limited Liability Company Act (RCW 25.15), with a Certificate of Formation filed with the Washington Secretary of State. Its registered agent is Northwest Registered Agent, Spokane, Washington.

In these terms, “Saylek”, “we” and “us” mean Saylek LLC. Notices to us can be sent to Contact.

You install Saylek on your own machine. It runs AI models for you locally.

Someone can also share their machines with you, and you can share yours. Sharing goes one way: accepting someone’s invitation lets your requests reach their machines and gives them nothing of yours, and inviting someone gives you nothing of theirs. In this document, the people who share with you are those whose invitation you accepted, and the people you share with are those who accepted yours. The app shows both under Sharing.

When your own machine cannot serve something, another machine can serve it for you: another machine of your own, or one belonging to someone who shares with you. That happens by default, and section 3 is about exactly what it means.

Separately, if you choose to, you can share your own machine so it serves the requests of the people you share with while it is idle. Sharing your machine never starts by itself. Accepting someone’s invitation does not turn your machine into one that serves other people; setting it up with saylek host wizard and switching sharing on does.

When your own device cannot serve a request, your request leaves your device and runs on another machine. That can be another machine of your own, or one belonging to someone who shares with you. This is on by default.

Concretely, and without softening it:

Your prompt leaves your machine. Not a summary of it, not a hash of it. The text itself, and your uploads too if there are any.

It is not encrypted from the machine that serves it. That machine has to read your prompt in order to run it. There is no end-to-end encryption, no secure enclave, and no technical measure that prevents the person operating that machine from seeing it. We are not going to tell you otherwise.

It is your machine, or the machine of someone whose invitation you accepted. Who you accept is the real protection here, so be precise about what that gives you. Saylek does not offer groups. If you have joined one of an older kind that still exists, one that admits people without an invitation or one set up for an organization, anyone in it can serve you too, and they may be strangers to you. Check who shares with you under Sharing, and any such group you are in with saylek circles list, and choose accordingly.

It passes through us on the way. Your request reaches that machine via our registry, which routes it, so we handle your prompt too and it sits in our routing queue. We do not read it and we do not train on it, but we are not going to let you believe it goes straight from your machine to theirs. The Privacy Notice says exactly how long it can sit there, and the answer is not a comfortable one.

It is not anonymous. Someone who shares with you already knows you by the name you set in your account. On their machine’s page, its owner can see each of your requests it served in the last 7 days, with its model, tokens, time, outcome and measured speed, under your display name, or under “Member · ” and the first 4 characters of your account id once that machine is no longer shared with you or you have no display name. The list never shows your prompt or reply, though their machine still reads each prompt it serves, and its own records of those requests can be matched to the list. Not using that person’s machines is the only way to stay off it.

Accepting someone’s invitation is how you consent to your requests reaching their machine. Your own other machines need no invitation. If you do not want your requests to leave the machine you send them from, turn on local-only mode by setting local_only = true under [federation] in ~/.saylek/config.toml. With that on, we will not route your request to any other machine. If your machine cannot serve one, it fails instead of leaving. That is a refusal, not a fallback. Having nobody share with you is not the same thing, because your own other machines can still serve you. And local-only covers only requests that go through your machine: a request an application sends straight to our hosted API with an application key never touches it, and is routed as this section describes.

One limit on that, so you are not relying on something broader than we built. Local-only does not override a destination you configured yourself: if you have registered your own proxy upstream and call a model that resolves to it, the request goes there. The egress page sets this out in full, including what happens when you stop using someone’s machines.

If you share your machine, you are running the requests of the people you share with on your own hardware. Then:

You will be able to read what you run. Their prompts pass through your machine in the clear. Treat what you see as theirs, not yours: do not collect it, do not publish it, do not go looking. They accepted your invitation on that understanding.

You decide who and when. Who you share with, pausing or removing any one of them, and pausing, stopping, or uninstalling are always yours to do, at any time, for any reason. You do not owe anyone an explanation or a notice period.

Serving costs you real things: electricity, wear, heat, and a GPU that is busy when you might want it. That is yours to weigh. Your own work takes priority over other people’s work on your machine.

Personal use. Saylek is free for personal use. We aim to keep it that way. If this changes, we will give you ample advance notice and ask you to accept updated terms before any fees apply.

Organizations. Organizations can arrange a one-month free trial with us. We will confirm its start and end dates and notify you before it ends. Starting a trial creates no payment obligation. Any paid continuation begins on the date and at the rates specified in a separate written agreement. Without an agreement, no charges apply when the trial ends.

Sharing. Access to another member’s machines depends on their permission, availability, and sharing settings. Sharing capacity does not create a right to payment, credits, or access to anyone else’s machines.

Do not send other people’s private data through Saylek. Your prompt can land on a real person’s machine. If it is not yours to share, do not share it.

Do not use Saylek for anything illegal, or to attack, overload, or interfere with other people’s machines.

Do not track or profile other members. This rule does not rest on anyone being unknown to you: if you share your machine, its page can show you, under each person’s display name, the requests it served for them (section 3 says what that list holds). Reading that list is not a breach of this rule. What you may not do with it is use it to track or profile anyone: do not collect it, publish it, or pass it on, and do not combine it with your machine’s own records or any other information to build a picture of what someone does. The same goes for anything else that passes through your machine.

Keep your invitations honest. Invite people you actually know and would vouch for. The safety of sharing is exactly the quality of who you share with.

Your keys are yours to keep. If your machine is compromised, tell the people you share with and the people who share with you.

Saylek is early software, run by members on their own hardware. Plainly:

No uptime, no availability, no guarantee anything gets served. The machine that would have served you can be switched off mid-request by someone who is under no obligation to you. That is not a bug, that is the model.

No warranty of any kind, to the fullest extent the law allows. Model output can be wrong, offensive, or made up. Do not rely on it for anything that matters without checking it.

We are not liable for loss arising from your use of Saylek, to the fullest extent the law allows, including anything another person does with a request you sent them. Section 3 is the honest warning; please act on that rather than on this paragraph.

We cannot undo what has left your machine. Once a request has gone to another machine, it is on that machine, and we have no ability to reach in and remove it.

Stop sharing your machine any time with saylek host pause, or stop the daemon. Stop using someone’s machines, or stop sharing yours with someone, any time; note that requests you send through your machine stop leaving it only with local-only mode on, since anyone else who shares with you, any group of the older kind you are in, and your own other machines can still serve you. Requests sent to our hosted API are routed whether or not local-only is on. Delete your account from your account settings, or remove everything locally with saylek wipe, which deletes ~/.saylek entirely: receipts, keys, models, logs, and config.

We may suspend your account or stop routing your requests if you break section 6, most likely after raising it with you and the people involved first.

Requests you already sent, and receipts other machines already hold, do not disappear when you leave. We cannot reach into other people’s machines. See the Privacy Notice.

If we change these terms in a way that affects what happens to your data, we will ask you to accept the new version rather than bury it in a changelog. Everything else, we will date and publish here.

These terms are governed by the laws of the State of Washington, USA, without regard to its conflict-of-laws rules, and the state and federal courts sitting in Washington are the venue for any dispute arising out of them.

If you live somewhere whose law gives you rights that cannot be signed away, nothing here waives them, and this clause does not deprive you of mandatory consumer protections in your country of residence.

Before filing anything, please write to us at Contact. Most things are faster to fix than to litigate.

Two things are not settled, and we would rather name them than print something inaccurate.

A minimum age and the jurisdictions that rule has to satisfy are still being decided. Saylek is not intended for children, and the figure will appear here before Saylek opens publicly.

How your acceptance is recorded. When you create your account, the version of these terms in force at that moment is recorded against it, along with the date. If we later publish a materially different version, we ask you to review and accept it before continuing, and record that acceptance too. That is what lets us keep the promise in section 9.

Two honest limits on that. Accounts created before 2026-07-24 pre-date the recording, so they carry no stored acceptance until their owner accepts the current version, which we ask for the next time they sign in. And when you create an account, acceptance is expressed by continuing past a notice that links these terms, rather than by ticking a box; if that turns out to be the wrong form, we will change it and ask you again.

This text is grounded against the running code rather than against intention, but it has not been reviewed by a lawyer. Questions go to Contact.