Terms of Service

Wayvian reads the website and the source repository you connect, extracts the promises your public pages make, and checks each one against your code. It returns a verdict per claim with a quote from the material that justified it.

Wayvian uses one GitHub App installation in selected-repositories mode. Read operations mint short-lived, read-downscoped installation tokens limited to the repositories needed for that operation. The crawler fetches pages the way a visitor would and is capped per run. Wayvian never deploys anything and never changes your website.

Two details about the crawler are stated precisely in section 03 of the Privacy Policy and we will not summarise them into something rounder here: the page you connect is fetched before robots.txt is read, so disallow rules govern the pages discovered afterwards rather than that first URL; and the crawler follows redirects, so the site it crawls is the origin your URL resolves to, which is not always the origin you typed.

The same GitHub App can open a pull request only after you explicitly approve that specific correction. Each approved correction uses a new short-lived, write-downscoped installation token limited to that one repository, with contents: write and pull_requests: write. Wayvian never merges the pull request, never pushes to your default branch, and discards each per-operation token after use. The connect-time installation token is stored encrypted and typically expires after about one hour.

A verdict is a language model's judgment about whether a piece of code supports a claim, presented with the quote it was based on so you can check the reasoning yourself. That is the entire design: we show the receipt because the judgment can be wrong.

Verdicts go stale. Code and copy both move, and a result reflects the state of the material at the time it was read. The product labels freshness for exactly this reason; do not treat an old verdict as a current statement of fact.

You need an account to use Wayvian, and you must give a real email address you control. You are responsible for your credentials and for activity under your account.

A workspace has an owner and can have admins, editors, and viewers. Anyone you add to a workspace can see the content in it, including the artifacts read from your connected sources. Only owners and admins can connect sources or manage credentials. Add people accordingly.

Do not create an account if you are under 16.

By connecting a source, you confirm that:

• you own the website and the repository, or you are authorized by whoever does to let Wayvian read them;
• you are allowed to send that material to a third-party model provider, and doing so does not breach an agreement you have with a customer, an employer, or a licensor;
• the GitHub installation and any other credentials you provide are yours to grant, and you select only repositories you are authorized to let Wayvian read and, after a specific correction approval, write to through a pull request;
• you will not point the crawler at a site you do not control in order to read it through us.

If you configure custom request headers so the crawler can reach a protected deployment, you are choosing to grant that access and you own that decision.

Do not use Wayvian to:

• read a site or repository you have no right to read;
• upload material you are not permitted to share, including secrets belonging to someone else;
• probe, overload, or work around the crawl limits, rate limits, or usage ceilings;
• resell or expose the engine as your own service, or use the product to build a competing verification engine;
• break the law with it.

Every workspace has a monthly ceiling on model calls, counted per UTC calendar month and per pipeline. On the free plan the ceilings are 1,000 promise extraction calls, 600 verification calls, and 150 Ian calls. Once a pipeline cannot admit another provider call, that provider-backed step waits until the next calendar month.

Read the verification number carefully, because it is not a count of claims. Verifying one claim spends several of those calls — a query expansion, a separate call for each batch of code we re-rank, and the verdict itself — and a claim that keeps failing to resolve can be retried on later runs. So 600 is worth far fewer than 600 verified promises, and a busy workspace can plausibly reach it. It is a cost circuit breaker, and we would rather give you the number than a reassuring adjective we cannot support.

Verification separates permission to process work from permission to spend a model call. Immediately before each verification provider request, Wayvian atomically reserves one call against the monthly ceiling. At the ceiling it sends no new verification request, but it may still finish zero-cost work from previously paid caches and stored fences. Any unfinished model work waits for the next UTC month; verification does not intentionally overshoot its ceiling. Other pipelines can have different call shapes, but they remain subject to their own monthly ceilings above.

There is also an operational suspension lever we can apply to a workspace that is abusing the engine; if we use it, we will tell you why.

Wayvian does not currently charge for anything. There is no payment processor connected to this product, no subscription, and no invoice. Workspaces carry a plan label and per-plan usage ceilings, but no plan costs money today.

If and when we introduce paid plans, we will publish the pricing and the billing terms before charging anyone, and we will not convert an existing free workspace into a paid one without your explicit agreement.

Wayvian is early software. It will have outages, the read worker will sometimes fail a job, and features will change or be removed. We do not offer a service level agreement, and we do not promise a support response time — we answer [email protected] as fast as a small team can.

We depend on services we do not operate — Supabase, Vercel, Fly.io, Anthropic, GitHub — and when they are down, we are degraded.

Everything Wayvian reads from your sources and everything you put into a workspace stays yours. You grant us only the permission needed to run the product for you: to fetch, store, process, and send that material to the model provider described in the Privacy Policy so we can produce verdicts and show them back to you.

We do not train models on your content — we do not have our own models. We do not sell your content. We do not share your workspace with other customers.

The Wayvian software, interface, and brand remain ours. Nothing here transfers them to you.

You can stop at any time: uninstall the GitHub App, disconnect your sources, or email us to delete the workspace. There is no self-serve delete button yet — deletion is done by hand on request, as described in the Privacy Policy.

We may suspend or close an account that is breaking section 05, that is being used to read material its operator has no right to read, or that we are legally required to close. Except where we cannot, we will say why and give you a chance to get your data out first.

Wayvian is provided as-is, without warranties of any kind. To the fullest extent the law allows, we are not liable for indirect or consequential losses, lost revenue, or lost data arising from your use of the product — including a decision you made because of a verdict that turned out to be wrong. Where liability cannot be excluded, it is limited to the amount you have paid us, which today is nothing.

Nothing in this section limits liability that cannot lawfully be limited.

We will update these terms as the product changes, and move the date at the top when we do. If a change materially reduces your rights or expands what we do with your content, we will notify account holders by email. Continuing to use Wayvian after a change means you accept it; if you do not, close the workspace.

Wayvian does not publish a registered entity or a postal address here, because we are not going to invent one. Contact is by email: [email protected] for anything, and [email protected] for vulnerability reports.