Last updated: June 24, 2026
Retrace ("we", "us", "our"), operated by Yash Bogam, is committed to protecting your privacy. This Privacy Policy explains how we collect, use, store, and protect your information when you use our execution replay engine for AI agents, including our website, dashboard, SDKs, CLI, API, and related services. By creating an account, signing in, or using the Service, you acknowledge this Privacy Policy.
When you create an account, we receive: name, email address, and (for social sign-in) a profile picture. Retrace is passwordless, we never collect or store passwords. You sign in with a magic link, a passkey, or a supported social login provider.
When you use our SDKs to record agent executions, we collect: function inputs and outputs, LLM prompts and responses, tool call parameters and results, error messages and stack traces, timing data (start time, end time, duration), token counts and cost calculations, model names and provider information. This data is submitted by your code via our SDK, we only collect what your instrumented functions produce. This content is stored (not only as embeddings) so we can display, search, and replay your traces.
We automatically collect: number of traces, spans, tapes, and forks created; API request counts for rate limiting; subscription plan and billing status; IP addresses for rate limiting (not stored long-term).
Payment processing is handled by a third-party payment processor. We do not store credit card numbers, CVVs, or full payment details. We receive only: subscription status, plan type, and transaction history references.
We generate vector embeddings from your trace data using a third-party embedding model to power semantic search. Embeddings are numerical representations stored alongside the underlying text; the original text you submit is also stored so we can display and replay your traces. Embeddings reduce, but do not eliminate, the ability to relate content.
To provide detection, the AI assistant, replay analysis, and related features, we transmit relevant trace content (such as prompts, responses, tool calls, and errors) to a third-party AI provider for processing. We use an API tier that does not use your inputs to train the provider's models. We send only what is needed to deliver the feature you are using.
With your consent, we collect privacy-preserving, anonymous usage analytics to understand which features are most valuable and to improve Retrace. This is strictly limited to a random, browser-generated identifier that is not linked to your name, email, or account, together with the pages and features visited and the time of visit. It never includes trace content, prompts, responses, tool calls, or any personal information.
We ask for your choice through a cookie banner on first visit. Selecting "Reject non-essential" disables all analytics collection; only the strictly necessary cookies required to sign in and operate the Service are used. Selecting "Agree" enables the anonymous analytics described above. Your preference is stored in a first-party cookie so we do not ask again, and you may change it at any time by clearing the rt_consent cookie in your browser. We do not use third-party advertising or cross-site tracking cookies.
To operate, secure, and troubleshoot the Service, we and our infrastructure providers generate operational and diagnostic logs, for example, error reports, request metadata, performance timings, and security events. We use these solely for reliability, security, and abuse prevention. Our logging is designed to minimize personal data: trace content (prompts, responses, and tool calls) is not written to operational logs, IP addresses are not retained in diagnostic logs (they are dropped or truncated), and credentials and tokens are redacted before a log is stored. Operational logs are kept for a limited period and then automatically deleted.
Our SDKs may send anonymous diagnostic telemetry that helps us detect errors and improve reliability, for example, the SDK version, the runtime and operating-system family, and error categories. This telemetry contains no source code, no API keys, no prompts or responses, and no personal information, and it is not linked to your account. It is opt-out: set RETRACE_TELEMETRY=0 in your environment to disable it entirely.
Your content is processed automatically to provide the Service, including detection, semantic search, replay analysis, and the AI assistant, which involves transmitting content to the subprocessors listed in Section 6.
We do NOT:
Database: Your data is stored in a managed relational database with vector-search support for embeddings. All connections use TLS encryption.
API Keys: Hashed with HMAC-SHA256 (keyed with a server-side secret, so a database leak alone cannot brute-force them) before storage, with a legacy plain SHA-256 fallback for keys issued before this migration. The plaintext key is shown only once at creation and never stored.
Encryption: All data is encrypted in transit (TLS 1.3). Data at rest is protected by the disk-level encryption provided by our hosting providers, and sensitive stored secrets (such as third-party provider credentials you supply for replay) are additionally encrypted at the application layer using AES-256-GCM with per-secret derived keys.
Infrastructure: The Service runs on reputable third-party cloud providers, the API and database sit behind a managed network/tunnel layer, the web app is hosted separately, tape snapshots and assets are kept with a third-party object-storage provider, and transactional email is sent through a third-party email provider.
Access Control: All API endpoints require authentication via a signed session token (JWT) or API key. Data is scoped to the authenticated user, you cannot access other users' traces.
| Plan | Retention Period |
|---|---|
| Free | 7 days |
| Pro | 90 days |
| Teams | 1 year |
| Enterprise | Configurable (up to unlimited) |
After the retention period, trace data is automatically and permanently deleted. Account data (email, name) is retained until account deletion. When you delete your account, it is deactivated immediately (sign-in is blocked) and all associated data is permanently purged after a 90-day grace period (which allows recovery from accidental or fraudulent deletion requests). Rate limiting data (IP-based counters) expires after 60 seconds.
Operational and diagnostic logs (Section 2.8) and anonymous telemetry (Section 2.9) are kept only for a limited retention period appropriate to operational and security needs (typically up to 90 days) and are then automatically deleted.
We share data only with the following categories of service providers, solely to operate the Service:
If you configure webhooks (for example, eval-rule notifications), the event data you elect to forward is transmitted to the destination URL you specify; that destination is outside our control and you are responsible for it.
We do not sell, rent, or trade your personal information. We may disclose data if required by law, court order, or to protect our rights and safety. We make a Data Processing Addendum (DPA) available to business and Enterprise customers on request.
When you publish a trace as a tape with "public" or "unlisted" visibility, the trace content becomes accessible to anyone with the URL. This includes all span data, inputs, outputs, and timing information in that trace. You control visibility and can unpublish at any time. We recommend reviewing tape content before sharing to ensure no sensitive data is exposed.
Depending on your jurisdiction, you have the right to:
To exercise any of these rights, contact hello@retraceai.tech. We will respond within 30 days. Where you upload data about third parties, you act as the data controller and we act as your processor; a DPA is available on request.
We use essential authentication cookies that are required for the Service to function. We also use a third-party product-analytics tool, including session-replay sampling, to understand feature usage and improve the product. We do not use advertising trackers, sell behavioral data, or participate in cross-site advertising. If you are in the EU/UK, you may withhold consent to non-essential analytics; contact us at hello@retraceai.tech to opt out.
The Service is not intended for users under 18 years of age. We do not knowingly collect data from minors. If we discover we have collected data from a minor, we will delete it immediately.
Your data may be processed in the United States and other countries where our infrastructure and subprocessors operate. By using the Service, you consent to this transfer. For EU users, transfers are protected by Standard Contractual Clauses (SCCs) implemented by our service providers. Enterprise customers may request data residency in specific regions.
In the event of a data breach affecting your personal information, we will notify affected users and relevant supervisory authorities without undue delay, and within 72 hours of becoming aware where required by applicable law (such as GDPR).
We may update this Privacy Policy periodically. Material changes will be communicated via email at least 14 days before taking effect. The "Last updated" date at the top reflects the most recent revision.
For privacy-related questions, data requests, or concerns:
Email: hello@retraceai.tech
Data Controller: Yash Bogam
Response Time: Within 30 days for all data subject requests