Legal
Terms of Service
The agreement between you and the operator of PlanRelay: what the service is, what it is not, your responsibilities, and the Founding Developer terms.
Effective
PlanRelay is operated by Rytela Inc..
1.About these terms
These terms govern your use of PlanRelay (planrelay.io). PlanRelay is operated by Rytela Inc. ("PlanRelay", "we", "us"). By creating an account, signing in or using the service you agree to them.
Two other documents describe how information is handled and are part of how the service works: the Privacy Policy and the Data Policy.
2.The service
PlanRelay is a coordination and record-keeping service for people who build software with AI coding agents. You create a "Relay", connect your own agents, and PlanRelay:
- relays structured messages between your agents and records them;
- records decisions, disagreements, findings and technical contracts and their revisions;
- records the evidence, test results and build results your agents report;
- records your approvals and authorizations;
- generates checksummed documents from that record.
PlanRelay does not read or access your repositories, write code, run your tests or builds, or deploy anything. Section 10 says more about what the service does and does not do.
The service is in early access. We may add, change or remove features.
3.Your account
Sign-in. PlanRelay has no passwords. You sign in with a single-use link sent to your email address. The link works once and expires after 10 minutes. Anyone who controls your email account can sign in as you, so you are responsible for keeping that email account secure.
Sessions. A signed-in session lasts up to 14 days and is renewed while you use the service. Sign out on devices you do not control.
Your details. Use an email address you control. An account is for one person.
Availability of sign-up. We may limit new sign-ups to invited email addresses at any time.
4.Plans and prices
| Plan | Price | Includes |
|---|---|---|
| Starter | $0 | 10 new Relays per calendar month, counted in UTC, with two builder agents per Relay. Relays you already have keep working after the allowance is used. |
| Developer | Listed at $19 per month. Paid billing is not enabled, so the plan cannot currently be bought. | Unlimited Relays, subject to reasonable abuse safeguards; one connected moderator per Relay; saved templates; agent presets; workspace settings. |
While paid billing is not enabled, Developer access is available only through a Founding Developer membership (section 5) or by invitation (section 6). We do not collect payment details today.
We may change plan features, limits and listed prices. Billing terms will be added to these terms before paid billing is enabled.
5.Founding Developer membership
Founding Developer membership is offered on these terms.
- Who. The first 100 verified developers who claim a seat through PlanRelay's public founding enrollment while it is open. "Verified" currently means that the account's email address has been confirmed. One seat per account.
- What. The Developer plan at no charge for the life of the account, covering the V1 Developer feature set: unlimited Relays (subject to reasonable abuse safeguards), one connected moderator per Relay, saved templates, agent presets and workspace settings.
- What is not included. Features introduced later, such as premium capabilities or hosted AI inference, may be priced separately.
- Not transferable. A seat belongs to the account that claimed it. It cannot be sold, assigned or moved to another account or person.
- Seats are never reused. A seat that ends is not given to anyone else.
- Enrollment. Enrollment may be opened or closed by the operator; the pricing page shows whether it is open and how many spots remain. Seeing the offer does not reserve a seat.
- Ending a membership. We may end a Founding Developer membership for a legitimate policy or security reason, including a breach of these terms.
Developer access given by invitation (section 6) is separate. It is not a Founding seat and does not carry these terms.
6.Developer access by invitation
During early access we may give Developer access to an invited email address. This access is separate from Founding Developer membership: it never takes a Founding seat, it does not carry the terms in section 5, and we may change or withdraw it.
7.Your content
Ownership. You keep all rights in the content you and your agents submit to a Relay ("Relay content"). We claim no ownership of it.
Permission to operate the service. You give us permission to host, store, process, display and transmit Relay content only as needed to provide the service to you, including making it available to the agents and the moderator you connect.
Who can access it. You; the agents and the moderator you connect, each limited to that Relay; and Rytela Inc. as the operator of the service. The Data Policy sets out exactly who can see what, including what our staff can see.
Your responsibility. You confirm that you have the right to submit your Relay content and that submitting it does not breach anyone else's rights or a confidentiality obligation you owe.
8.Connected agents and credentials
Your agents run in your environments. The agents and the moderator in a Relay run in AI clients that you choose, in your own environments. PlanRelay does not supply, operate or control them. You are responsible for:
- which AI clients you connect and how they are configured;
- everything your connected agents and moderator do and submit, as if you had done it yourself;
- the access those clients have to your repositories, systems and environments;
- keeping to the terms of the providers of those AI clients.
Content your AI clients read from or send to PlanRelay is also processed by those clients and their providers, under their terms. That is outside PlanRelay's control.
Credentials are yours to protect. Invitation codes and agent tokens give access to a Relay. Invitation codes expire within 60 minutes and work once. Tokens expire after 24 hours and you can revoke them. Keep them secret. A connector address that contains a token is itself a secret. If a code, token or address may have been exposed, revoke it or issue a new invitation immediately. You are responsible for activity carried out with your credentials until you revoke them.
9.Agent-provided evidence; no secrets
Reported, not checked by PlanRelay. Evidence, test results, build results, log excerpts, commit identifiers, findings and activity reports are supplied by your agents. PlanRelay records and displays what it receives. It does not check that a reported test ran, that a reported build succeeded or that reported evidence is true.
Do not submit
- secrets, credentials, API keys, tokens, private keys or the contents of environment files;
- production credentials or connection strings;
- personal data about other people.
The secret check is not a guarantee. PlanRelay rejects some submissions that match common credential patterns. The check applies to certain kinds of submission only, cannot detect every secret and does not detect personal data. You remain responsible for what you and your agents submit. If a secret is submitted, treat it as exposed and rotate it.
10.What PlanRelay does and does not do
Coordination and record-keeping only. PlanRelay coordinates your agents and keeps the record. It does not read repositories, write code, review code, run tests, build or deploy.
What "verified" means. Where PlanRelay shows a scenario, a build or a Relay as "verified", "passed" or "certified", it means only this: the listed checks were reported by your agents as passing, in a test environment, on the listed commits, and the other agent confirmed that report. It is not a guarantee that the software is correct, secure, complete or fit for production. It says nothing about any commit, environment or behaviour that is not listed.
Authorizations are your decisions. An approval or authorization recorded in PlanRelay, for example to implement, configure, deploy or activate, is a record of your own decision. PlanRelay does not make that decision, does not advise you to make it and does not act on it.
No deployment. PlanRelay makes no change to your repositories, systems or environments. Anything that happens there is done by you or by tools you control.
AI output. Agents can be wrong. You are responsible for reviewing what your agents produce before relying on it.
11.Acceptable use
You must not, and must not allow your agents to:
- use the service unlawfully or to infringe anyone's rights;
- submit secrets, production credentials or other people's personal data (section 9);
- submit malicious code, or content intended to attack or manipulate other people's systems or agents;
- try to access another account's Relays, or use a credential outside the Relay and role it was issued for;
- probe, scan or test the vulnerability of the service, or bypass rate limits, plan limits or seat limits, without our written permission;
- create accounts by automated means, or create several accounts to avoid plan limits or to claim more than one Founding seat;
- share, sell or transfer account access, tokens or a Founding seat;
- interfere with the service or place unreasonable load on it;
- misrepresent a PlanRelay record, for example by presenting a "verified" status as a guarantee by PlanRelay.
12.Suspension and closing your account
We may suspend or close an account that breaches these terms or presents a security risk. A suspended account cannot sign in, its sessions end and its Relays' agent credentials are revoked. Suspension does not delete Relay content.
You may stop using the service at any time. There is currently no self-service account deletion and no self-service way to download a copy of your whole account. You can ask us to close your account or delete a Relay; we handle such requests manually, and some records, such as audit entries, may be retained. The Data Policy describes this.
13.Data, retention and privacy
The Privacy Policy explains what personal information we collect. The Data Policy explains how Relay content is handled. In summary: sign-in links, sessions, invitation codes and agent tokens stop working when they expire; your account and Relay content are kept until they are deleted; ending, closing or archiving a Relay does not delete it.
14.Publication and case studies
Private Relay information is not published without the owner's explicit authorization. We will not name you or your organisation as a customer without your explicit authorization either. Authorization given for one publication does not extend to another.
The case study on this site describes the operator's own integration work and was published with the founder's explicit authorization.
15.Our service and intellectual property
The service, its software and its documentation belong to Rytela Inc.. These terms give you a right to use the service while they apply, not ownership of it.
16.Disclaimer
The service is in early access and is provided "as is" and "as available". To the extent permitted by law, we give no warranty of any kind, express or implied, including that the service will be uninterrupted or error-free, that records, evidence or a "verified" status are accurate, or that software coordinated through PlanRelay is correct, secure or fit for any purpose.
We offer no service level today. Keep your own copies of anything you cannot afford to lose.
17.Limitation of liability
To the extent permitted by law, Rytela Inc. is not liable for indirect, incidental, special or consequential loss, or for loss of profits, revenue, data or goodwill, arising from your use of the service or from the acts of the agents and AI clients you connect.
Nothing in these terms excludes or limits a liability that cannot be excluded or limited by law, and nothing in them removes rights you have under laws that cannot be waived.
18.Changes to these terms
We may update these terms. We will post the updated version on this page with a new effective date. Continuing to use the service after an update takes effect means you accept it.
19.Contact
PlanRelay is operated by Rytela Inc..
A contact address for Rytela Inc. has not been published yet. When it is available it will appear here and, for account holders, in Settings. Until then we cannot receive requests through this page.
See also: Privacy Policy · Data Policy