← Legal

Terms of Service

Your rights and responsibilities when you use Ephyra’s website and the deployments we operate.

Revised · Review copy

Prepared for review, not yet effective. The operator is Keith Abiola Noel, a sole proprietor in Québec, Canada. A public business mailing address, legal review and a French edition must be completed before adoption.

At a glance

This summary is a guide to the full text below.

What these terms cover

These proposed terms govern the Ephyra website, its journal, and any Ephyra service we operate for you, such as a hosted deployment and its sign-in. “Ephyra,” “we,” and “us” refer to Keith Abiola Noel, a sole proprietor in Québec, Canada. Ephyra is a working name. It is not a registered business name or a corporation, and nothing here represents that it is.

They do not govern the Ephyra software when you run it yourself. That is covered by the open-source licence published in its repository. The licence is still being chosen. Whoever operates a self-hosted deployment is responsible for it and for the people who use it.

Once adopted and presented for acceptance, these terms form the agreement for the covered services. This review copy does not itself change an existing agreement.

Accounts and sign-in

Ephyra uses Not Organic accounts. Signing in sends you to Not Organic, which authenticates you under its own Terms of Service and Privacy Policy. Ephyra receives your decentralized identifier (DID), your handle, and tokens that let it act within the scopes you approved.

Use accurate information and protect your sign-in and the CLI credentials file on your computer. Approve a terminal sign-in only when the code in your browser matches the one your terminal shows. Tell us at ephyra@notorganic.info if you believe someone has used your account without permission.

Each deployment decides who may approve quests. Being signed in does not make you an approver. If you act for an organization, you confirm that you can bind it.

What Ephyra does on your behalf

Ephyra reads the production signals you send it and opens quests. It runs code in sandboxes and writes patches. After the approvals your autonomy policy requires, it lands changes on the forges you connect. It acts with the credentials and permissions you give the deployment, and no others.

You set the autonomy policy. It says which areas Ephyra may research or patch, and which changes need a person at checkpoints A, B and C. Approving a checkpoint is your decision to proceed. You are responsible for the changes you approve, and for anything your policy lets land without a person.

Proof, watch windows and rollback reduce risk; they do not remove it. A passing proof can miss a defect, a watch can miss a regression, and a rollback can fail or arrive late. Keep your own review, backups and deploy controls for any system where a bad change could cause harm.

Only connect repositories, forges, telemetry and systems you are authorized to read and change.

Your content and AI output

You keep the rights you hold in your code, signals, quests and other content. You permit us to process, store, transmit and display that content only as needed to provide the features you use, protect the service and meet legal obligations, as the Privacy Policy describes. This permission does not transfer ownership of your work to us.

Models produce Ephyra's patches, plans, summaries and triage decisions. That output can be wrong, incomplete or insecure, and it can resemble code produced for others. It may not qualify for copyright protection. Review it before you rely on it. You are responsible for the licence compliance of code that lands in your repositories.

Ephyra treats signals, logs, stack traces and forge comments as untrusted data. Content from them never grants Ephyra new permissions. No filter is perfect, though, so keep secrets out of production logs.

Model training

We do not use your code, signals, quests or proof to train models, and we do not sell them. The model providers your deployment sends requests to process them under their own terms, and their retention depends on the provider and your agreement with it. The service providers page lists them.

Services from others

Ephyra connects to the services you choose:

Each provider is responsible for its own service under its own terms. Naming one here is not an endorsement. It is also not a promise that the integration is available for your deployment.

Radicle replicates repositories between peers. A patch that lands on a Radicle repository can be copied by seed nodes nobody controls centrally, and it cannot reliably be recalled.

Charges

Ephyra charges nothing today, and running it yourself is free.

Before we charge for any service, checkout will show the price, the seller, taxes, the billing interval and the cancellation terms.

Acceptable use

Follow the Acceptable Use Policy. In short: point Ephyra only at systems you may change, do not use it to attack or deceive anyone, and do not interfere with checkpoints, proof or audit records. Report a suspected security issue as described on the security page.

Preview status and availability

Ephyra is pre-alpha. Features, integrations and model routes can change or stop working. Unless a separate agreement provides one, there is no service-level guarantee. Keep independent copies of anything important. The quest journal lives in your git repository; the inbox and job queue live in the deployment’s database.

If we materially reduce a paid service, we will give the notice and remedies that your purchase agreement and applicable law require.

Suspension, closure and your data

We may restrict access when reasonably necessary to address a security incident, unlawful use, a serious breach or a legal obligation. Where appropriate, we will explain why and give you an opportunity to resolve the problem. We may act without advance notice when notice would compromise security or break the law.

You can stop using a service at any time. To close an account on a deployment we operate, or to request an export first, write to ephyra@notorganic.info. Closure, erasure and the end of a subscription are separate actions. We may keep records needed for legal, fraud-prevention or dispute purposes. Copies already held by forges, seed nodes or other independent services are outside our direct control.

Responsibility and legal rights

We provide the services with the care that applicable law requires. Subject to rights that cannot be excluded, they are provided as available. We do not promise that every output is correct or that access will be uninterrupted.

We do not exclude responsibility that cannot lawfully be excluded, including obligations concerning consumer services, privacy, fraud or deliberate misconduct. These terms do not impose mandatory arbitration, waive class proceedings or set a monetary liability cap.

If you have a disagreement, contact us first at ephyra@notorganic.info and we will try to resolve it. You keep any right to complain to a regulator or to use the courts available to you. Subject to mandatory protections where you live, these terms are governed by the laws of Québec and the applicable federal laws of Canada. That does not restrict any court or complaint process that mandatory law gives you.

Québec and language of contract

For an agreement subject to Québec’s French-language requirements, the complete French version and related documents must be made available as the law requires before you are asked to choose to contract in English. A browser language setting is not that choice. Choosing English must not cost more or reduce the service available in French.

These terms do not waive Québec’s mandatory consumer protections, impose compulsory arbitration on a consumer, or prevent a consumer from using a court or class proceeding.

Changes and contact

We will post changes on this page with a new revision date. For a change that materially affects an active paid service, we will give the notice that the law and your agreement require before it applies to you.

Questions about these terms: ephyra@notorganic.info.