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.

You can also join a Circle, a group of members who share their machines with each other. In a Circle two things become possible.

When your own machine cannot serve something, another member’s machine can serve it for you (you are acting as a Guest). That happens by default, and section 3 is about exactly what it means.

Separately, if you choose to, you can share your own GPU so it serves other members’ requests while it is idle (you are acting as a Host). Hosting never starts by itself. Joining a Circle does not turn your machine into a Host; running saylek host does.

That reciprocity is the whole product. You contribute capacity, and you draw on capacity.

When your own device cannot serve a request, your request leaves your device and runs on another member’s machine. This is on by default once you join a Circle.

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 that member. Their 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 a member of a Circle you belong to. Who is in your Circle is the real protection here, so be precise about what that gives you. On an invite-only Circle, which is the default, members are admitted by the Circle’s owner or an admin, so unless you own it someone else chose them. A Circle can also be set to open-join, in which case members join without an invite and may be strangers to you. Check which kind you are in, and choose accordingly.

It passes through us on the way. Your request reaches that member 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.

They do not learn your name or email from it. Your machine identifies itself with a key fingerprint, not your identity. That fingerprint is stable, though, so a Host can tell that many requests came from the same member even without knowing which member.

Joining a Circle is how you consent to this. If you do not want it, you have two options and both are real: do not join a Circle, since a solo install does not route your requests to anyone; or 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 another member. If your machine cannot serve one, it fails instead of leaving. That is a refusal, not a fallback.

Two limits on that, so you are not relying on something broader than we built. Neither control overrides 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. And leaving a Circle takes a few minutes to take effect, because your machine caches what it knows about your memberships. The egress page sets both out in full.

If you share your machine, you are running other members’ requests 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. Members joined a Circle with you on that understanding.

You decide when. Pausing, stopping, or uninstalling is always yours to do, at any time, for any reason. You do not owe the pool 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 guests’ work on your machine.

Nothing here involves payment. Saylek does not sell anything, you are not buying anything, and nothing you contribute converts into money, credit, or any entitlement to be paid.

What you get back is reciprocity: contribute capacity, and you can draw on the pool’s capacity. That balance is a social record among members, not a currency and not a debt. It has no cash value and we do not redeem it.

If that ever changes, it changes with new terms you would have to accept, not quietly under these.

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

Do not use the pool for anything illegal, or to attack, overload, or interfere with other members’ machines. Do not try to deanonymise, track, or profile other members from what passes through your machine.

Keep your invite honest. Invite people you actually know and would vouch for. The pool’s safety is exactly the quality of who is in it.

Your keys are yours to keep. If your machine is compromised, tell your Circle.

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 member 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 a Host, it is on their machine, and we have no ability to reach in and remove it.

Stop hosting any time with saylek host pause, or stop the daemon. Leave a Circle any time; note that requests stop leaving your device only once you hold no live membership at all, since any remaining Circle still serves you. 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 remove you from the pool if you break section 6, most likely by asking your Circle first, because that is who vouched for you.

Requests you already sent, and receipts other members already hold, do not disappear when you leave. We cannot reach into other members’ 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 sign in, the version of these terms in force at that moment is recorded against your account, along with the date. That is what lets us keep the promise in section 9: if we publish a materially different version, your recorded acceptance no longer matches the current one, and we ask you again rather than assuming.

Two honest limits on that. Accounts created before 2026-07-24 pre-date the recording and carry no stored acceptance, so we cannot show you a date for them. And acceptance is expressed by signing in after being shown the notice, 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.