Privacy notice

What we collect

• Your Google account's email address and name, when you sign in with Google. We ask Google only for your basic profile (the openid, email and profile scopes) and never see your Google password.
• The projects you upload: cascodex.yaml, testbenches, netlists and notes, for every revision.
• What the service makes from them: simulation results, logs, waveforms, analyses and proposed changes from the analysis agent, and the share links you create.
• Account settings: your teams and roles, the invites you send (with the invited email address), notification choices, and API keys (we keep only a hash of each key).
• Basic technical records: the IP address and browser (user agent) of each signed-in session, and service logs of each request (time, the kind of request, its result, and your user and organization IDs) for security and debugging.

Why we use it

• To sign you in and keep you signed in.
• To run your simulations and analyses and show you the results.
• To send the emails you expect: run finished, analysis finished and team invites. You can turn run and analysis emails off in Settings.
• To keep the service secure and working: rate limits, abuse prevention and fixing faults.
• To run the service from totals such as the number of users, runs and simulations.

We do not sell your data, use it for advertising, or train AI models on your designs. We share it only with the providers below, to run the service.

Where it is stored and who processes it

• Neon (Postgres, in AWS us-east-1, United States): accounts, projects, results, analyses and sessions.
• Cloudflare: the web app and the API run on Cloudflare Workers and Containers, and uploaded files, logs and waveforms are kept in Cloudflare R2.
• Upstash (Redis, in AWS us-east-1): run queues, live progress, rate limits, short-lived sign-in state and a one-minute cache of session lookups.
• Google: sign-in.
• Resend: delivers our notification emails, once email sending is turned on.
• Anthropic: the AI model behind analyses (next section).

The analysis agent and Anthropic

Nothing is sent to an AI model unless someone in your workspace runs an analysis (Explain on a failing spec). Then the analysis agent sends Anthropic's API (the Claude model) the analyzed revision's project name, cascodex.yaml, testbenches and included netlists, the run's results, and the measurements and simulations it makes while it works, so the model can find the cause of the failure and propose a change. Anthropic processes this data to answer each request, under its terms for API customers.

Cookies

We set two cookies, both needed to sign in, and nothing else:

• The session cookie (__Secure-cdx_session) keeps you signed in. It is HttpOnly, so page scripts cannot read it. A session ends after 7 days without use, 30 days after you sign in, or when you sign out.
• The sign-in cookie (cdx_oauth) exists only while you sign in with Google, for at most 10 minutes, and ties that sign-in to your browser.

There are no advertising or tracking cookies and no third-party analytics. The app keeps a few preferences, such as your theme and the selected organization, in your browser's local storage.

How long we keep it

We keep your account and your data while your account is active. A session is deleted when you sign out, and expired ones the next time you sign in. Sent emails leave our email queue after 30 days, and service logs are kept for about 7 days. Deleted data can remain in database backups until they expire.

Deleting your data

Write to hello@cascodex.com from the email address you sign in with. We will delete your account, your sessions and API keys, and the projects, runs, analyses and files in your personal workspace, and tell you when it is done. Projects in a team stay with the team. You can also ask us for a copy of your data, or to correct it.

Children

Cascodex is a tool for engineers and is not meant for anyone under 16.

Changes to this notice

We will post changes on this page and update the date above. For a significant change we will also tell signed-in users by email or in the app before it takes effect.

Contact

Cascodex, hello@cascodex.com.