Data Processing
Last reviewed July 21, 2026
This notice explains how Nyrus Corp. processes data through CATO, how service providers support that processing, and how operational records and agent trajectories are used. It supplements the Privacy Policy and Terms of Service. If this notice conflicts with either document, the Terms of Service and Privacy Policy control.
Standard CATO accounts are currently offered only to users in the United States and may not be used for Protected Health Information or other identifiable consumer health, genetic, biometric, or patient-level data.
CATO's Role
Standard accounts
For standard accounts, Nyrus determines why and how account, product, safety, and service data is processed. Nyrus acts as the business or controller for that processing. Individual users are governed by the Terms of Service, Privacy Policy, and this notice rather than a separate data processing agreement.
Institutional and enterprise accounts
When an organization determines the purposes of processing personal data and instructs CATO to process it on the organization's behalf, Nyrus may act as a processor or service provider. Those deployments require an appropriate customer agreement and, where applicable, a CATO data processing addendum. A vendor DPA between Nyrus and a service provider does not replace the agreement between Nyrus and its customer.
What CATO Processes
- Account, identity, contact, subscription, and billing records.
- Prompts, responses, uploaded files, datasets, project artifacts, memories, and feedback.
- Generated code, execution results, citations, literature records, and reviewer findings.
- Tool calls and results, model and workflow metadata, token usage, timing, and reliability data.
- Security signals, policy classifications, authentication events, and records needed to investigate misuse.
CATO limits each service provider to the data needed for its function. The current provider list, data categories, retention posture, and contractual references appear on the Subprocessors and Service Providers page.
Agent Trajectories
CATO records agent trajectories during and after the beta period. A trajectory may include prompts, responses, tool calls and results, generated code, citations, reviewer findings, execution metadata, model selections, safety signals, provider-returned reasoning content where available, and User Content surfaced during the workflow. Uploading a file does not, by itself, copy the full raw file into a trajectory. File excerpts, selected rows, summaries, tool results, generated outputs, or other content surfaced to the agent may be recorded.
Operations, security, and misuse prevention
Nyrus uses trajectories and related service records to operate and restore workflows, diagnose errors, prevent fraud and abuse, enforce the Usage Policy, investigate security events, resolve disputes, and improve the safety and reliability of CATO. Records relevant to abuse, fraud, security, or legal obligations may be retained for longer than ordinary product records when reasonably necessary for those purposes.
Evaluation and improvement
Nyrus also uses trajectories to evaluate scientific performance, curate evaluation and training datasets, and improve or train CATO models, reviewers, routing systems, and agent workflows. This use continues after the beta period. We take steps to minimize direct identifiers in curated datasets and limit access to personnel and systems that need it.
Nyrus does not authorize third-party model providers to train their shared models on CATO User Content. This restriction does not prevent Nyrus from using CATO records to improve its own offerings as described here.
Operational and training-approved stores
CATO keeps operational trajectories and training-approved trajectories in separate Google Cloud storage boundaries. The production trajectory writer is create-only: it cannot list, read, overwrite, or delete operational records. Training systems have no access to that operational store.
A separately authorized cleaning and approval pipeline must read an operational record, apply the applicable review, minimization, and approval controls, and create a distinct copy in the training-approved store. The training identity can read only that approved store. An operational record is therefore not available to training merely because production created it.
Deletion and Future Training
Deleting a conversation, project, or file removes its primary application copy. It may not immediately remove related records from backups, security systems, diagnostic records, or trajectory storage. Verified deletion requests are processed subject to legal, security, fraud-prevention, dispute, and technical-retention requirements.
You may contact contact@nyrus.ai to request deletion of identifiable trajectory records or to request that identifiable records no longer be selected for future model-improvement datasets. A prospective restriction does not require Nyrus to undo processing completed before the request.
Service Providers
Nyrus uses contracted providers for application hosting, model inference, sandbox execution, monitoring, payment processing, and email delivery. When a provider processes personal data on Nyrus's behalf, its applicable agreement includes data-processing terms addressing the provider's permitted purpose, confidentiality, security, subprocessors, incidents, deletion, and assistance with applicable privacy requests.
Those agreements are between Nyrus and the provider. They do not make an individual user a party to the vendor agreement, guarantee that no provider receives data, establish zero retention for every service, or authorize the processing of PHI. Users exercise their rights through Nyrus.
Public Research Services
Literature, patent, trial, protein, pathway, chemical, and other public scientific services are not ordinary CATO subprocessors. CATO sends only the search terms, public identifiers, sequences, structures, filters, or other query elements needed for the requested operation. Their own terms and logging practices apply.
Do not place personal information, identifiable health information, confidential participant narratives, unpublished invention disclosures, or credentials in a public-service query.
Security and Requests
CATO uses authentication-gated access, encrypted connections, isolated execution environments, credential controls, monitoring, and restrictions on access to internal cloud networks. A trusted controller stages required inputs into a temporary sandbox workspace and retrieves validated outputs. Sandbox pods receive no cloud-storage credentials, application secrets, or mounted object storage, and staged copies are removed when the sandbox pod or session is cleaned up. No security measure eliminates all risk.
To request access, correction, export, or deletion of personal data, or to ask about future model-improvement use, contact contact@nyrus.ai. We may need to verify your identity before completing a request.