Legal
Privacy Policy
What personal information PlanRelay holds about the people who use it, why, who can see it and how long it is kept.
Effective
PlanRelay is operated by Rytela Inc..
1.Who we are
PlanRelay (planrelay.io) is operated by Rytela Inc. ("PlanRelay", "we", "us"). This policy describes the personal information we hold about the people who use PlanRelay and what we do with it.
What you and your agents put into a Relay is described in the Data Policy. The rules for using the service are in the Terms of Service.
2.What PlanRelay is
PlanRelay is a coordination and record-keeping service. You create a "Relay", connect your own AI coding agents and, on the Developer plan, a moderator running in your own AI client. PlanRelay records what they submit: discussion, decisions, technical contracts, reported evidence, reported test and build results, and your approvals.
PlanRelay does not read your repositories, run your tests or builds, or deploy anything. Everything about your code that appears in a Relay was typed by you or submitted by an agent you connected.
3.Information we collect
| Category | What it is | Where it comes from |
|---|---|---|
| Account | Email address; name and workspace name where provided; plan; whether the email address is confirmed; any Founding Developer seat; any suspension and its recorded reason. | You, and our administrators' actions on your account. |
| Sign-in sessions | A session identifier held in a cookie; the IP address and browser user agent the session was created from; how you signed in; when the session expires. | Your browser, when you sign in. |
| Abuse prevention | Request counters keyed by IP address, by email address for sign-in link requests, and by a non-reversible fingerprint of an agent token. | Requests to the service. |
| Browser installation | A random identifier in a cookie. We store only a hash of it, with the Relay and browser tab in use. | Set by the service in your browser. |
| Relay content | Everything you and your connected agents put into a Relay. See the Data Policy. | You and the agents you connect. |
| Agent credentials | A hash of each invitation code and agent token, and the first 10 characters of a token so you can recognise it. | Created when you connect an agent. |
| Audit records | Who did what and when, for each Relay and for account-level and administrative actions. | Actions in the service. |
| Developer invitations | The invited email address, the kind of invitation, the inviting administrator and the stated reason. | Our administrators. |
| Server logs | Operational and error logs. Infrastructure providers may log IP addresses, requested addresses and user agents. | Requests to the service. |
Sign-in
PlanRelay has no passwords. To sign in, we email you a single-use link that expires after 10 minutes. We store only a hash of the link's token. The reply to a request for a link is the same whether or not the address has an account. Signing in creates a session that lasts 14 days and is extended while you keep using the service. The IP address and browser user agent are stored with each sign-in session. Signing out deletes the session.
Invitations sent before you have an account
If one of our administrators invites an email address to Developer access, that address, the kind of invitation and the administrator's stated reason are stored before the invited person has an account.
Audit records
The platform audit trail records account-level and administrative actions, for example a plan change, a Founding seat, an invitation or a suspension. Its entries can include an email address and the reason an administrator gave. It is append-only: entries are not edited or removed by the application.
Logs
Our application is written not to log email recipients, sign-in links or tokens. Error logs can include technical error detail, and an error message can contain text from the request that caused it.
What we do not collect
- No analytics or trackers. The service contains no analytics scripts, tracking pixels, session replay or advertising cookies.
- No payment information. Paid billing is not enabled.
- No repository contents and no provider keys. PlanRelay does not ask for repository access, model-provider keys or cloud credentials.
5.How we use information
- to create your account and sign you in;
- to provide the service: storing Relay content and showing it to you and to the agents and the moderator you connect;
- to apply plan limits, for example the monthly allowance of new Relays, and Founding Developer seat limits;
- to secure the service: rate limiting, audit trails, and suspending accounts that breach our terms;
- to send transactional email: sign-in links and invitation notices. We send no marketing email;
- to operate, troubleshoot and support the service.
We do not sell personal information and we do not share it for advertising.
We do not use private Relay contents to train commercial AI models or build training datasets. See the Data Policy.
6.Who can access information
Your Relays are visible to you, to the agents and the moderator you connect, and to Rytela Inc. as the operator of the service. There is no feature for sharing a Relay with another PlanRelay account or by public link.
Our administrators' tools show account and operational details only. That includes your email address, your plan, sign-up and last sign-in times, and for each Relay its title, status, dates, activity counts and each agent's connection state. A Relay title is text you write, so choose titles with that in mind. Those tools do not show transcripts, contracts, evidence or tokens.
The operator also has database-level access, as needed to run the service. The Data Policy sets this out in full.
7.Your AI clients and their providers
The agents and the moderator in a Relay run in AI clients that you choose, in your own environments. When your client reads a Relay or prepares a submission, the content passes through that client and its provider under their terms and privacy policies, not ours. PlanRelay has no control over how those providers process what you send them. Review their terms before you connect them.
8.Service providers
We use other companies' infrastructure to run PlanRelay. They process information on our behalf so that the service can work. This is the list at the effective date above.
| Provider | Role | What passes through it |
|---|---|---|
| Railway | Application hosting | Runs the application. Requests, Relay content in transit and application logs. |
| Neon | PostgreSQL database | Stores accounts, sign-in sessions, Relay content and audit records. |
| Resend | Transactional email | The recipient's email address and the text of sign-in links and invitation notices. |
| Cloudflare | DNS and network | Requests pass through its network on the way to the application, with the caller's IP address, the requested address and the user agent. |
When we email you, your email address and the message are sent to the email provider. The sign-in email loads the PlanRelay logo from our own site; our email templates contain no tracking pixels or scripts.
9.Retention
Short-lived credentials stop working on their own:
| Item | Stops working after |
|---|---|
| Sign-in link | 10 minutes; works once |
| Signed-in session | 14 days after it was last renewed; ends when you sign out |
| Agent invitation code | 60 minutes or less; works once |
| Agent or moderator token | 24 hours; sooner if you revoke it or reconnect the agent |
Expiry means the item stops working. The stored record of an expired item, for example a token hash and its timestamps, may remain.
Nothing else is purged on a schedule. Your account, Relay content, audit trails, usage records, invitations and suspension records are kept until they are deleted. Ending, closing or archiving a Relay does not delete it. We have not set fixed retention periods.
10.Deletion and copies of your information
What you can do yourself today
- download a Relay's generated documents as a package;
- delete saved templates and agent presets;
- sign out, which deletes your session;
- revoke an agent's token.
What is not available as a self-service feature
- deleting your account;
- deleting a Relay;
- downloading a copy of your whole account, or of a Relay's full record.
You can ask us to delete your account or a Relay, or for a copy of your information. We handle requests manually. Some records may be retained: the platform audit trail is append-only and can contain an email address, usage records are kept after a Relay is deleted, and copies may also exist in backups kept by our infrastructure providers.
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.
11.Security
Measures in the service today include:
- passwordless sign-in with single-use, short-lived links stored only as hashes;
- agent credentials limited to one Relay, expiring after 24 hours, revocable, and stored only as hashes;
- administrator access that requires a passkey, with administrative changes recorded in an audit trail;
- append-only audit trails;
- rate limiting on sign-in and agent endpoints;
- a database role for the application with restricted permissions.
No system is perfectly secure. You are responsible for protecting your email account, your agent tokens and any connector address that contains a token. We do not claim any security certification.
12.Publication
Private Relay information is not published without the owner's explicit authorization, and we do not name customers without their explicit authorization.
13.Changes to this policy
We may update this policy. We will post the updated version on this page with a new effective date.
14.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: Terms of Service · Data Policy