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.
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.
| Category | Examples | Purpose | Retention position |
|---|---|---|---|
| Account | Name, email, organization, account settings, authentication data. | Account access, support, security, and billing. | While the account is active and for a reasonable period afterward. |
| Workspace | Prompts, messages, files, logs, notes, and saved conversations. | Provide the workspace and preserve investigations you choose to save. | Until you delete the content or close the account, subject to backups. |
| API | Prompts, outputs, model, timestamps, key identifiers, and usage metadata. | Process requests, meter credits, and secure the API. | Operational and security period. Confirm current terms. |
| Billing | Credits, transactions, invoices, payment status, tax records. | Meter usage, process payments, and meet accounting obligations. | As required for billing, tax, and legal records. |
| Technical | IP address, device and browser data, security events. | Security, abuse prevention, reliability, and diagnostics. | Operational and security period. |
| Inference | Prompts, outputs, and related metadata sent to third-party providers. | Run the selected model and return output. | 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.
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.
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.
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.
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.
Recommended handling
For authorized security work, use the minimum data needed to complete the task:
- Use test accounts, owned systems, and synthetic data whenever possible.
- Redact secrets, tokens, personal data, client identifiers, and live credentials before upload.
- Do not upload live victim data, regulated data, or third-party confidential material without confirming handling.
- Keep written authorization, scope, and rules of engagement outside the workspace where appropriate.
- Delete conversations and files after the engagement unless you need them for the report.
- Confirm provider retention before working with sensitive evidence.
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.
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.
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.
