Terms of Service
Draft terms for the local-first Project Relay software and any future optional services.
This is a working draft, not a final contract.
It is published to make the intended boundaries visible while Relay is being built. It has not been reviewed by a lawyer and does not create paid-service terms at this stage. The owner must approve and replace this draft before accepting subscriptions, hosted accounts, or consequential customer commitments.
What these terms cover
These draft terms describe use of Project Relay, a provider-neutral coordination, archive, and review tool. "Relay", "we", and "the project" mean the Project Relay software and its project-maintained public documentation. The current public offering is a local application and CLI; future hosted or paid services may have additional terms presented before they are enabled.
Use, licence, and responsibility
The open-source Relay components are provided under the Apache License 2.0, subject to the licence text and third-party notices shipped with the relevant release. That licence governs copying, modification, and redistribution of those components. You are responsible for installing the software in a suitable environment, reviewing changes before applying them, and keeping your own backups and credentials safe.
Any future proprietary feature, hosted service, support plan, or commercial connector will be separately identified and governed by terms that are published before use. Paying for convenience or support does not remove the rights granted by the Apache-licensed components.
Archives, prompts, and outputs stay yours
You retain your rights in transcripts, prompts, files, evidence, and other material you bring into Relay. You confirm that you have the rights and permissions needed to process that material and to connect any provider, repository, workspace, or control room you select.
Relay is local-first: the local archive is stored under your control and is not uploaded to this public Pages site by default. If you enable a connector or hosted service, data is sent to that destination according to the configuration and terms shown for that service. Review destinations, access scopes, retention, and export settings before enabling them.
What you agree not to do
- Use Relay to break the law, violate another person's rights, or bypass a provider's terms or access controls.
- Upload secrets, private transcripts, or regulated information to an unapproved destination.
- Present a model suggestion, comparison, hash, or receipt as human approval or proof of truth.
- Let an automated worker make a consequential human decision, merge protected code, or publish private material without the required approval.
- Interfere with the software, connectors, safeguards, rate limits, or audit records.
Relay remains advisory
Relay can normalize contributions, preserve provenance, identify agreement or conflict, and suggest a next step. It does not guarantee that any answer is correct, safe, complete, independent, or suitable for a particular purpose. Models and connectors cannot create or grant human authority through Relay. You remain responsible for reviewing evidence and making decisions.
Third-party services are separate
Model providers, MCP servers, GitHub, Notion, Slack, payment processors, operating systems, and other third-party services have their own terms, privacy practices, availability, and charges. Relay does not control those services. You are responsible for selecting them, authorizing access, and checking their current terms and costs.
Future commercial terms will be explicit
No Relay subscription, hosted account, or automatic charge is enabled by this draft. If paid plans are introduced, the checkout flow will state the price, billing interval, renewal, cancellation, refund, taxes, support scope, and any usage limits before payment. Those terms may supplement or replace this section after legal review. Voluntary creator support is not a purchase of premium functionality.
Draft clauses requiring legal review
The final version must set the governing law, venue, warranty disclaimer, liability limits, indemnity, suspension, termination, export, and dispute process for the applicable product and jurisdiction. Those clauses are intentionally not invented here. Until counsel approves them, do not treat this page as a complete or enforceable commercial agreement.
Before this becomes final
- Confirm the legal entity or trading name used for customer-facing services.
- Choose and document the governing jurisdiction with qualified legal advice.
- Publish matching privacy, refund, acceptable-use, and data-retention terms for any hosted or paid tier.
- Version the final terms and require affirmative acceptance where the law or product flow requires it.