Zolado

Privacy

DRAFT, last updated 2026-10-31 (DRAFT). Not published. Markers like [OWNER: ...] must be resolved before it goes live.

In short

  • We store your name and email, the Salesforce and MuleSoft connections you make (their keys are encrypted), your chats, and a record of what you approved.
  • Your messages, and what your chat reads from your tools, are sent to one AI provider, Anthropic, to write the answers.
  • Your data is kept until you delete it or delete your account. Deleting your account removes your data.
  • We use no advertising or analytics trackers. Sign-in uses a cookie from Clerk.
  • Questions or requests: support@zolado.io.

Who this covers

This page explains how Zolado ("we") handles personal data in Cockpit, the web app at app.zolado.io, and on the Zolado website at zolado.io. [OWNER: name the legal operator and address here, or keep the person-named operator as in the Cockpit terms ("run by Sivaji Nandimandalam, San Ramon, California")]

Cockpit is for professional developers. It is not for anyone under 18, and we do not knowingly collect data from children. If you think a child has given us data, write to us and we will delete it.

What we store

  • Account. You sign in with Google or with your email through Clerk. Cockpit needs your name and email to open an account. Your data is filed under your Clerk user id.
  • Access requests and invitations. The email, name, company and purpose you type on the request form, the time, and whether the request was approved or declined.
  • Waitlist. What you give when you join the waitlist: your name, work email, the time you joined and which form you used, and, if you choose, your company, what you would connect first and a note. We also keep a scrambled code made from your network address, used only to spot abuse. We read the list ourselves to decide who to invite. You can ask us to remove your details at any time by writing to support@zolado.io. [OWNER: if waitlist or invitation emails are sent at launch, name the mail provider here (ZeptoMail once the adapter ships); if no email is sent, say so]
  • Connections. For each tool you connect (Salesforce, MuleSoft), the access token or key, and details such as the address of your Salesforce instance, the scopes granted and a label. Tokens, keys and any app secret you save are stored encrypted. The keys that unlock them are held in AWS KMS.
  • Chats. Each chat thread and its messages: what you write, the Copilot's answers, and the tool requests and results kept with them. For long chats we also keep a short summary of the older messages. If you attach a connection to a chat, we keep which one, and a short description of it.
  • Code the Copilot writes for you, when you ask for code.
  • Runs, approvals and audit. Each message starts a run; we keep its steps. We keep every approval card, what it asked for, and whether you approved or denied it, plus an audit record of those decisions and of each change of Sandbox or Production mode.
  • Usage. How many tokens each request used and what it cost, your monthly AI spend counters, and, if you use a Workstation, how long it ran.
  • Workstation and runner. If you use a Workstation, the machine record (name, size, state, region), runner tokens, one-time enrollment codes and task records, and the files of the projects you build on it for as long as the machine exists.
  • Consent. That you agreed to the AI provider, which version of the list you agreed to, when, and from which app.
  • Short-lived operating data. A scrambled code made from the network address of a public form submission (request access or waitlist), kept one hour, to limit abuse. Server logs, kept 90 days in production.

We take no payments today, so we hold no card or bank details.

Error reports. [OWNER: keep the Sentry sentence only if Sentry is set up for Zolado; the launch environment has no Sentry DSN, so by default this sentence is removed] The server keeps logs (see How long we keep it).

Where your data lives and who handles it

  • Cockpit's server runs on Amazon Web Services in the us-west-2 (Oregon) region, in an AWS account that belongs to Zolado.
  • The database is a Neon Postgres database in AWS us-west-2. Neon keeps point-in-time history for [OWNER: the Neon plan's history window in days] days; removed data can remain in that history until it expires.
  • Encryption keys for stored connections are held in AWS KMS in us-west-2.
  • The web app is hosted on Vercel.
  • Sign-in is handled by Clerk (with Google or email as the sign-in method).
  • Chat answers are written by Anthropic. See the next section.

Each tool you connect (Salesforce, MuleSoft) also has its own terms and privacy policy. What Cockpit reads from and writes to them is governed by those too.

We do not sell your personal data.

The AI provider

Cockpit uses one AI provider: Anthropic, which makes Claude. There is no other.

To answer you, Cockpit sends Anthropic your messages, the conversation so far, and the results of the tools the Copilot reads for you. That can include the data a chat reads from your Salesforce or MuleSoft. When you ask for code, the request and the context it needs are sent too.

This is not filtered for secrets: what you type, and what Salesforce or MuleSoft return, go as they are. Do not put passwords or keys in a chat.

You agree to this before your first chat. You can withdraw on the Account page at any time. Chat stops until you agree again, and your threads stay. If the provider list ever changes, we ask you to agree again.

What Anthropic does with data after it receives it is set by Anthropic's own terms and privacy policy, not by this page.

Cookies and trackers

We use the cookies Clerk sets to keep you signed in. We use no advertising or analytics trackers on the web app or on the Zolado website, and the website loads nothing from other sites.

The chat screen remembers in your own browser whether the side panels are open or closed. That stays on your device.

How long we keep it

  • Chat history. Kept until you delete it or delete your account. We have no timer that removes old chats.
  • A chat you delete is hidden at once. Its messages, plans, approvals, runs and stored code are removed for good after 30 days. Audit records of decisions stay until you delete your account.
  • Account, connections, access request, waitlist entry and the rest of the list above: kept until you delete your account or ask us to remove them.
  • Database history: kept for the window named under Where your data lives, then expires.
  • Server logs: 90 days in production.

Delete your account

On the Account page, choose Delete account and type DELETE. It takes effect straight away and cannot be undone.

First, Cockpit asks each connected provider to revoke its access, where the provider allows it (Salesforce). MuleSoft keys cannot be revoked by us, so we delete our copy and you can rotate them in Anypoint.

Then we delete, in one step: your threads and messages, approvals and runs, stored code, connections and encrypted tokens, saved app secrets, usage and budget records, Workstations and runners, Sandbox and Production mode settings and their log, AI consent, your trial record, your access request and waitlist entry, and audit records about you. Last, we delete your Clerk sign-in account.

We keep one record that an account was deleted. It carries no name, email or user id, only counts of rows and the result of each revocation. Database history expires on its normal cycle.

If the last step fails, your data is already gone and your sign-in remains. Try again; it is safe to repeat.

Your choices and requests

You can delete chats and your account in the app, and withdraw AI consent on the Account page. There is no download button for your data yet. To get a copy of what we hold about you, to correct it, or to have your waitlist or access-request entry removed, write to support@zolado.io from the address on your account. We send a copy of what we hold within 30 days of a request.

Changes to this page

When we change this page we change the date at the top. For a change that matters, such as a new AI provider, we tell you in the app and ask you to agree again before you chat.

Contact

Write to support@zolado.io. More help is on the support page. The rules for using Cockpit are in the terms.