Data Policy

This policy explains how PlanRelay handles the engineering information in a Relay: the session itself, agent conversations, technical contracts, evidence, generated documents, and any future community contributions. PlanRelay is operated by Rytela Inc..

Personal information about you as an account holder is covered by the Privacy Policy. Your responsibilities are in the Terms of Service.

PlanRelay coordinates and records. It does not read repositories, write code, run tests, build or deploy. Everything in a Relay was typed by its owner or submitted by an agent or moderator the owner connected.

A Relay is a private working session that belongs to the account that created it. PlanRelay stores, for each Relay:

• its title, objective, guardrails and the questions to settle;
• the display names you give your agents and the repository names you enter. These are names only: PlanRelay holds no access to a repository;
• its status, stage and the release gates you have approved or authorized, with the reasons you record;
• an event stream and an audit trail of who did what and when.

A Relay is private by default and there is no setting that makes it public. There is no feature for sharing a Relay with another PlanRelay account or by public link.

On the Developer plan PlanRelay also stores your saved templates, agent presets and workspace settings.

Connected AI agents operate in their respective environments: each runs in an AI client you chose, on your side. PlanRelay receives only what an agent submits through its Relay token, and stores it in that Relay:

• the turns your agents take, and the decisions and disagreements recorded from them;
• your questions and directives, and the agents' answers;
• a connected moderator's questions, directives, findings and holds, and the observations it records after an approval;
• findings a builder reports after an approval, and your decision on each;
• activity notes and heartbeats: what an agent says it is doing, and when it last called. These are the agent's own reports.

Conversation text is free-form. PlanRelay does not review it and stores it as submitted.

Agents write technical contracts into a structured form. PlanRelay stores every revision, the reviews of each exact revision, and your approval.

An approved revision is immutable. Once you approve a revision it is not edited. A correction goes into a new revision, which is reviewed and approved in the ordinary way, and the earlier revision stays in the record.

When a revision is approved, PlanRelay freezes its documents once and records a SHA-256 checksum for each, so anyone holding a document can tell whether it matches the record.

Evidence in a Relay is reported by your agents. PlanRelay stores it and shows it; it does not run anything and does not check that a reported result is true. Stored items include:

• test scope and scenarios, the commit identifiers your agents declare, and reported results;
• evidence summaries and assertions, and the other agent's verification notes;
• production build records: repository name, commit, build command, environment, exit code and a log excerpt of up to 8,000 characters, with a checksum of the full log. The full log is not stored;
• stage reports, defects, and the findings and amendments recorded after an approval;
• each certified state of a test board, kept as a numbered certification, and later amendments kept as supplements.

"Verified" means the listed checks were reported as passing in a test environment on the listed commits and confirmed by the other agent. It is not a guarantee of correctness, security or fitness for any purpose.

Secrets do not belong in a Relay

Do not submit secrets, production credentials or other people's personal data, and instruct your agents not to. PlanRelay checks some submissions, including verification evidence, build records, activity notes and stage reports, against common credential patterns and rejects a match. The check does not cover every kind of submission or every kind of secret, and it does not detect personal data. It is a safeguard, not a guarantee. If a secret reaches a Relay, treat it as exposed and rotate it.

From an approved contract PlanRelay generates a fixed set of seven documents with checksums: a handoff for each builder and shared files for both. Each agent can read its own handoff and the shared files, not the other agent's handoff.

The owner can download a Relay's documents as one package. The package's cover page is generated at download time from the Relay's current state and is not one of the frozen documents.

That per-Relay download is the export that exists today. There is no account-wide download and no download of a Relay's complete record as data.

What our staff can see, stated plainly. The administrator tools are limited to metadata. A Relay title is text you write, and it is part of that metadata, so do not put confidential names in titles.

Separately, Rytela Inc. operates the database and infrastructure the service runs on. That database-level access is not limited by the administrator tools' metadata-only rule, and PlanRelay does not add its own encryption layer to Relay contents, so it technically reaches stored content. We use it as needed to run the service; we do not claim that nobody at the operator could ever access content.

Existing authorization boundaries stay in force for private engineering sessions, repository references, contracts, evidence, credentials and customer information: an agent's token reaches one Relay only, and nothing in a Relay is exposed to another account.

Private Relay information is not published without the owner's explicit authorization. That covers transcripts, contracts, evidence, documents, repository references and the names of customers. Authorization for one publication does not extend to another.

The case study on this site describes the operator's own integration work. It was published with the founder's explicit authorization.

We do not use private Relay contents to train commercial AI models or build training datasets. This is a commitment by Rytela Inc..

PlanRelay does not itself run AI models over Relay contents today. Any future hosted AI processing would be described in this policy before it is enabled.

The AI providers you connect are a different matter. Your agents and your moderator run in AI clients you chose. Whatever those clients read from a Relay or send to it is processed by their providers under those providers' own terms, which may differ from ours. PlanRelay does not control that; check those terms before you connect a client.

PlanRelay has no community library, shared knowledge base or "Case Law" collection today. Nothing from a Relay is contributed anywhere.

If we introduce one:

• contributing will be explicitly opt-in;
• each contribution will be separately authorized by the owner, one contribution at a time;
• nothing private will become public by default;
• this policy will describe it before it is switched on.

This is how the service behaves today.

• Relay contents are kept until they are deleted. Ending, closing or archiving a Relay does not delete it. We have not set fixed retention periods.
• Nothing is purged on a schedule. The only things that expire by themselves are the short-lived credentials below, and the stored record of an expired credential may remain.
• There is no self-service deletion of an account or a Relay. You can delete saved templates and agent presets yourself.
• You can ask us to delete your account or a Relay. We handle requests manually.
• Some records may be retained. The platform audit log is append-only. Usage records are kept after a Relay is deleted. 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.

Relay contents are stored and processed on infrastructure run by other companies, who process data on our behalf so that the service can work. This is the list at the effective date above.

The email provider receives sign-in and invitation messages only. Relay contents are not sent by email.

We may update this policy. We will post the updated version on this page with a new effective date. Publishing private Relay information always needs the owner's explicit authorization; a new version of this page does not give it.

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.