Privacy & data

Understand what the website and app collect, which provider receives a session, what each privacy tier means, and what Cloaky stores on your device.

Cloaky is a coding-agent workbench that names the provider and privacy tier on every session. Cloaky Base has one provider: every session runs on Venice under your Venice key, on the model and privacy tier you pick. Cloaky Pro adds local models, direct providers and other routes, and it is in a private build; this page describes those routes too, so a Base user knows what Pro changes.

Effective date: October 24, 2026. This page explains the current data practices for cloaky.dev and the Cloaky Base and Cloaky Pro desktop apps. It is a practical notice, not a promise that a provider or tool will never retain or disclose data. The route, provider terms, approved tools, device, and your settings all matter.

What we collect directly

Website signup

The signup form on this site collects the email address you submit, the time it was added, and which of the two signups you chose. We do not ask for a name or phone number, and we do not use the address for a newsletter or a follow-up sequence.

Get the next Base release. You get one email confirming the signup, and one email when the next Cloaky Base release is published. Nothing between, nothing after.

I want Cloaky Pro. You get one email asking what you would do with Cloaky Pro; your reply to it is the application, and a person reads and answers it. We use the address for that correspondence and nothing else.

Either way the address is stored in our Upstash Redis account. The follow-up email, and an alert to us naming your address and signup kind, are sent through Resend. Replies to hello@cloaky.dev pass through our domain’s email forwarding (Squarespace).

Addresses from the earlier beta list are kept separately and may receive one email when Cloaky Pro launches.

You can ask us to remove or correct a signup address by emailing privacy@cloaky.dev from that address. We keep it until the follow-up is complete, you ask us to delete it, or a longer period is required for legal, security, or record-keeping reasons. Operational backups and provider logs may take longer to clear.

The site also receives ordinary technical information needed to deliver and protect a web request, such as request time, URL, browser/device information, and network information in hosting or security logs. We use it to operate the site, prevent abuse, debug failures, and understand aggregate traffic.

The site currently does not use advertising cookies or an account login. Your browser’s local storage keeps your theme, the Base/Pro view you chose, and dismissed notices. The interactive product demo runs a copy of the app on demo data in your browser: it registers a service worker to serve that data and stores its own interface state (layout, drafts, what’s new) in local and session storage. None of it leaves your browser; clearing site data removes it.

Vercel Web Analytics is enabled for aggregate page-view measurement; Vercel says its Web Analytics uses anonymized data and does not use cookies. Vercel Speed Insights measures performance and Core Web Vitals. Both are third-party services under their own privacy terms, and both load regardless of Do Not Track.

Download links fetch the app from GitHub Releases (github.com/cloakydev/cloaky); GitHub receives that request under its own terms.

Separately, the site counts a small set of named actions itself: download clicks, product-demo tab switches, views of the Cloaky Pro section, clicks on the Pro email link, presses of the signup and feedback submit buttons, blog reads, GitHub link clicks, and install-guide views. Each is stored as a daily total in our Upstash Redis account, sometimes with a short label such as which tab or which download. No identifier, IP address, user agent, or cookie is stored with these counts, and two actions by the same person are simply two counts. Browsers with Do Not Track turned on send none of these counts.

App and support

The app keeps its working state on your device: settings (with your Venice key, sealed by the system keychain in the desktop app), session transcripts, per-turn snapshots of project files for Undo, attachments and generated media, memory, cost records, command audit logs, drafts, and in-app browser cookies. Each engine also keeps its own transcripts. None of it is sent to us. Your Venice key stays on the device, is sent only to Venice, and is never handed to the app’s interface.

The app has no telemetry, analytics or crash reporting, and sends nothing to the Cloaky project.

If you contact us, we receive the information you choose to include, such as your email address, app version, screenshots, logs, and the description of a problem. Do not send secrets or sensitive project content in a support request.

Feedback submissions

The feedback form collects the category, note, optional expected outcome, provider or route, Cloaky version, and optional follow-up email you submit. It is stored in our Upstash Redis account for human review, with a reference number, the time it was sent, and a title taken from the first line of your note. The current form does not upload files and does not send your submission to a model or automatic summarizer. If you email a screenshot or log to feedback@cloaky.dev, that message and attachment are handled through our email system instead.

Do not include passwords, API keys, private keys, confidential client data, or other sensitive information. We use feedback to understand problems, respond when you ask for follow-up, and improve Cloaky. We may retain submissions as long as reasonably needed for those purposes, security, and record-keeping; ask privacy@cloaky.dev if you need a submission removed.

Cloaky is not your inference provider. Data handling follows the route you enable: Venice receives the account and operational metadata it needs, Venice can separate your identity from an upstream provider, and in Cloaky Pro a local model involves no inference provider at all. The session badge makes that route explicit before work begins.

Routes in Cloaky Base

Base has one inference destination. Every engine — Claude Code, OpenCode, Codex, Kimi Code, Grok Build — runs its loop on your machine and sends its model calls to Venice under your Venice key. No other provider account is involved. An engine’s CLI may still make non-inference requests of its own, such as an update check.

Routes in Cloaky Pro

Cloaky Pro adds the routes below. They are not in Base, and Pro is in a private build; this is what Pro changes about where a session goes.

In Pro, a local model keeps inference on your machine when the model is capable enough for the work; a direct provider is for a particular model or an account you already trust.

How to read the privacy labels

Provider choice is fixed when a session starts. Cloaky shows the route that actually reached the model and does not silently move a session to another provider when the selected route is unavailable.

In Base the model picker lists encrypted models first, then private, then anonymized under its own heading. Each tier carries a label:

Encryption and tool use

Venice’s encrypted route does not return the structured tool calls a coding agent needs. Every agent turn offers tools, so agent sessions are never end-to-end encrypted: those turns go to the model unencrypted under the private tier’s zero retention. Plain chats, incognito chats and assists can be encrypted. A turn also goes unencrypted when the enclave fails Cloaky’s check, and the thread warns you. Cloaky reports the route that was used instead of presenting the stronger label when it did not apply.

Attestation is useful but bounded evidence. Cloaky checks that the quote carries its own nonce, binds the enclave key and is not debuggable, and flags an enclave whose measurement changes. It does not verify the quote’s signature or compare the measurement with a published build, so attestation is not presented as cryptographic proof.

Network access beyond inference

Model inference is only one form of network access. Content may also leave the device when you approve or enable:

• WebFetch, WebSearch, MCP servers, or network-capable shell commands;
• a provider’s account, billing, abuse-prevention, or operational systems;
• (Cloaky Pro) the optional local-model gallery, which contacts a model registry when opened;
• the update check, which sends GitHub Releases the app version and platform when you press Check for updates, or at launch and hourly while automatic checks are on (setup offers them, ticked); or
• the website’s aggregate, cookieless analytics, action counts, and performance measurement.

Those actions are not covered by Venice’s inference-retention commitment. Cloaky makes network-capable actions visible and asks for approval where the workbench can intervene. A local session (Cloaky Pro) means model inference is local; it does not automatically make every approved tool action offline.

Cloaky also contacts Venice for its model list (even before you save a key) and your balance (every 60 seconds while a window is open), and npm once a day for the Claude Agent SDK it uses. When you start them, it runs engine installers and update checks, and downloads voice models and the sandbox. The in-app browser loads the pages you open in it, and on Linux the spell checker downloads its dictionary. The app’s Data and privacy notes, linked from Settings → General, list every host and when each is contacted.

We do not sell your prompts, code, or provider credentials. We do not use private app content to train a general-purpose model. However, the selected provider, tool, registry, or account system may process the content you send to it under its own terms. If you use a direct provider (Cloaky Pro) or a network-capable tool, that service is a separate recipient.

Data stored on your device

App and support above lists everything the app keeps.

Settings → Start fresh deletes chats, transcripts, snapshots, generated media, cost records, audit logs and caches (and, if you choose, workflows and schedules). It keeps your key, settings, engine configuration, memory, attachments, logs, Squad teammates and in-app browser sign-ins. It cannot run while a session is working.

Never paste a credential into a prompt, issue, social post, or support reply.

Assists and automations

In Base every assist goes to Venice on your key: commit-message and teammate drafts, side chats, prompt refinement, skill records, memory suggestions (off by default), Cloakster’s checks and scheduled routines. Session headlines are written on your device from the session’s actions, or by Venice’s decision model when Cloakster is on and your session’s model is on the anonymized tier. If an assist cannot reach Venice, it stops and explains the problem; nothing falls back to another provider.

If content should not leave the device, use a local session (Cloaky Pro) and avoid network-capable tools; in Base, every model turn goes to Venice. The provider badge identifies the inference route, and your approvals determine which additional actions run.

Your choices and privacy rights

You can pick the model and its privacy tier per session, turn off Cloakster and Memory, disable network-capable tools, skip the signup list, or ask us to delete information we hold. In Cloaky Pro you can also choose a local route. Depending on where you live, you may also have rights to access, correct, delete, or receive a copy of personal information, object to or restrict certain uses, or complain to a privacy regulator. Send a request to privacy@cloaky.dev. We may need to verify the request and may retain a limited record of it to comply with law and prevent abuse.

We do not currently sell or share personal information for cross-context behavioral advertising. If that changes, this page and any legally required choice mechanism will be updated before the change takes effect.

Security and changes

We use reasonable administrative, technical, and organizational safeguards, but no device, network, provider, or software system is perfectly secure. You are responsible for backups, credential hygiene, permissions, and choosing a route appropriate for the sensitivity of your work.

We may update this page as the products change. The effective date above will change with a material update. If a future feature changes what we collect or where content goes, we will update the relevant disclosure before or when the feature is introduced.

Quick reference

Cloaky Base runs every session on Venice, on the model and privacy tier you pick: enclave-encrypted for tool-free turns, zero-retention private, or anonymized. Cloaky Pro adds local models and direct providers. Cloaky keeps the route visible; the guarantee belongs to the provider.

For the operator’s contract terms, risk allocation, and early-software disclaimer, read the Terms of Use. For practical safeguards, read Safety & responsible use.