Privacy Policy

Who we are

"TryCase", "we", and "us" refer to the TryCase service available at trycase.dev and through the TryCase CLI. You can contact us at ben@trycase.dev.

Information we collect

• Account information, such as your name, email address, sign-in identity, and workspace membership.
• Workspace and project information, such as project names, runtime settings, billing tier, credit usage, and environment history.
• Code and files you upload directly into TryCase environments.
• Environment data, including commands, terminal output, logs, browser console output, network logs, screenshots, recordings, traces, metrics, and artifacts.
• Project secrets you choose to store, such as development API keys or test environment variables.
• Operational data, such as IP address, user agent, timestamps, authentication events, error reports, and service logs.

What happens to your code

TryCase packages the files you select, transfers them to the service, and extracts them inside the target environment.

Running environment disks are disposable. When an environment is stopped, destroyed, failed, or expired, TryCase is designed to clean up the runtime process, networking, and writable disk for that run. Artifacts, logs, screenshots, recordings, upload metadata, project settings, and audit records may remain in the control plane so you can review proof, debug failures, and see usage history.

TryCase does not sell your code and does not use your code to train AI models. If you ask an external AI product or coding agent to use TryCase, that product may process prompts, code, screenshots, recordings, or logs under its own terms and privacy policy.

Secrets and sensitive data

Project secret values are encrypted before storage and are write-only in the product UI and CLI. TryCase sends secrets to the environment only when needed for the project configuration. Known secret values are redacted from TryCase-managed logs and command output where possible.

Redaction is a safety layer, not a guarantee. Your application, browser pages, screenshots, recordings, generated artifacts, third-party tools, or custom scripts can still expose secrets if they print or display them. Use development credentials where possible, rotate secrets if you suspect exposure, and avoid putting production secrets into disposable test environments unless you have decided the risk is acceptable.

How we use information

• Provide the service, authenticate users, manage workspaces, and run disposable environments.
• Transfer uploaded code, execute commands, capture evidence, and return artifacts to your workspace.
• Track billing credits, active environment time, resource usage, and plan status.
• Detect abuse, debug reliability issues, protect the service, and improve product quality.
• Respond to support requests and communicate service changes.

Service providers

TryCase uses third-party providers to operate the service. These may include Clerk for authentication and billing flows, Convex for the application backend, AWS for compute and storage, and payment infrastructure connected through Clerk. These providers process data only as needed to provide their services to TryCase.

Sharing

We do not sell personal information. We share information only when needed to provide the service, comply with law, protect TryCase or users, complete a business transaction such as a merger or acquisition, or with your direction, such as when you ask an agent to upload code.

Retention and deletion

Disposable runtime resources are intended to be removed when environments stop, expire, or are destroyed. Control-plane records, artifacts, uploaded archives, logs, billing records, and audit records may be retained for product, security, billing, and support needs unless deleted or expired by service retention processes. To ask for deletion or export of personal data, email ben@trycase.dev.

Security

We use technical and organizational safeguards appropriate for an early cloud developer tool, including authentication, workspace access checks, encrypted project secrets, isolated runtime environments, and cleanup of disposable runtimes. No system is perfectly secure. Please report security concerns to ben@trycase.dev.

Changes

We may update this policy as TryCase changes. We will update the effective date when we make material changes. Continued use of TryCase after a change means the updated policy applies.