Skip to content

Data Handling

How data moves through CyrailsAI, what has been verified, what is not established, and how to handle sensitive security work.

Last updated 16 November 2026Version 1.0
01

Purpose and scope

This page summarizes how the CyrailsAI workspace and API handle data. It is an operational overview, not a replacement for the Privacy Policy or the Terms of Service.

Personal data is governed by the Privacy Policy. Contractual terms are governed by the Terms of Service.

02

Data categories and flows

Account

Examples

Name, email, organization, account settings, authentication data.

Purpose

Account access, support, security, and billing.

Retention position

While the account is active and for a reasonable period afterward.

Workspace

Examples

Prompts, messages, files, logs, notes, and saved conversations.

Purpose

Provide the workspace and preserve investigations you choose to save.

Retention position

Until you delete the content or close the account, subject to backups.

API

Examples

Prompts, outputs, model, timestamps, key identifiers, and usage metadata.

Purpose

Process requests, meter credits, and secure the API.

Retention position

Operational and security period. Confirm current terms.

Billing

Examples

Credits, transactions, invoices, payment status, tax records.

Purpose

Meter usage, process payments, and meet accounting obligations.

Retention position

As required for billing, tax, and legal records.

Technical

Examples

IP address, device and browser data, security events.

Purpose

Security, abuse prevention, reliability, and diagnostics.

Retention position

Operational and security period.

Inference

Examples

Prompts, outputs, and related metadata sent to third-party providers.

Purpose

Run the selected model and return output.

Retention position

Governed by provider terms. Zero retention is not established.

This table is a summary. Provider practices can change, and specific retention periods are not currently published.

03

Inference providers and third-party clients

Requests may be processed by third-party inference providers and model providers, including the providers behind GLM 5.3, GLM 5.3 Flash, and DeepSeek V4.1 Flash. These providers may log or retain data under their own terms.

If you connect the API to Claude Code, Codex, or another client, that client may send, store, or log prompts and outputs. Review its settings and terms before using it with sensitive material.

A current list of material subprocessors is available on request. Confirm provider handling before starting an engagement that involves confidential data.

04

Retention and deletion

  • Deleting a conversation or closing an account removes active access, subject to backup, security, billing, and legal retention.
  • Backups and security logs may persist for a limited period after deletion.
  • Provider retention is outside our direct control. Deleting content in the workspace may not delete provider copies.
  • We may retain data where required by law or needed to establish, exercise, or defend legal claims.

Do not assume zero retention

Zero data retention is not established. Specific provider retention periods are not currently published. Confirm current handling before uploading personal, client, or regulated data.

05

Security controls

We use measures such as access controls, least privilege, encryption in transit, monitoring, security logging, vendor review, and incident response procedures.

No system is completely secure. Report suspected exposure or unauthorized access promptly so we can investigate.

06

Assurance status

Current status

SOC 2 status is unverified. Zero data retention is not established. No independent certification is currently published for the Service.

Confirm current assurance and data-handling details with the team before relying on them for a client engagement, regulated data, or a contractual commitment.

08

Your controls

  • Manage saved conversations and workspace files from your account.
  • Rotate and revoke API keys when access changes.
  • Contact us to request access, correction, or deletion of personal data where applicable.
  • Review third-party client settings before connecting them to the API.
09

Incident reporting

Report suspected data exposure, credential compromise, or unauthorized access to contact@cyrails.com.

Include the affected account, the time observed, and a brief description. Do not include live credentials or sensitive evidence in the first message.

11

Contact

Data-handling questions can be sent to contact@cyrails.com.

Formal entity details and a registered address are available on request. An enterprise data processing agreement is available by agreement.