Privacy

Effective November 2, 2026

Vizcoder is a desktop app for Mac and Windows, and vizcoder.com is its website. Both are run by Athletes Department LLC, doing business as Vizcoder ("we"). Questions or requests: vizcoder.com/contact.

The short version

• Your code, files, chats and prompts stay on your computer. We never receive them, except a dashboard's Stage you choose to share by link.
• The app talks to us for six things only: update checks, a one-time count of your first build, from version 0.1.35 a one-time note of each setup step it reaches, license checks (with vizcoder.com), support tickets you choose to send, and Stage links you choose to share.
• This website has no analytics tools, ad trackers or cookies. It only counts visits that come through our own ?ref= links, described below.
• We don't sell your information or share it for advertising.

What this website collects

• Visits. The site is hosted by Cloudflare, which, like any web host, processes your IP address and browser details to deliver the page and protect it from abuse. We don't use analytics tools, ad trackers or cookies.
• Our own links. When you arrive through one of our own links (an ad or video link, or the “Made with Vizcoder” link on a page someone shared: an address ending in ?ref= and a short name like fb1, yt, tt or made), the site adds one to that link's count for the day, and one more if you press Download (Mac or Windows). No cookie, no ID and nothing about you: the link name is kept only in that browser tab until you close it. Your IP address is kept for up to 2 days to stop abuse.
• Downloads. We count how many times each installer is downloaded. The count isn't linked to you.
• Contact form. What you write, the email you give us for a reply, and your country (from Cloudflare), to answer you.
• Our earlier email list. If you joined the beta list, we keep that email address and the date you joined, to send you news about Vizcoder. Every email has a way to unsubscribe, and you can remove yourself below.

What the app sends us, and why

• Update checks, about once an hour while the app is open: a request for our version file, which tells the app about updates and whether paid plans are open. We don't store these requests.
• Your first build, once: a random install ID made on your computer and nothing else, so each install is counted once. We keep the ID and the date; your IP address is kept for 2 days to stop abuse.
• Setup steps, once each (from version 0.1.35): which of five steps this copy has reached (opened, found Claude Code or Codex, signed in, made a first chat, sent a first message), with the app's version and whether it's a Mac or Windows. No install ID and nothing about you; we only add one to a count. Your IP address is kept for up to 2 days to stop abuse.
• Support tickets, only when you send one: your message, your email if you give it, the app version, your operating system, which AI engine you use, part of the install ID and your country. Recent app logs are attached only if you tick the box; in Vizcoder 0.1.22 and later they show your home folder as ~, hide anything that looks like a key or token, and you can read them before sending. Logs can still include file and folder names. We delete tickets after 90 days.
• Shared links, only when you press Share on a dashboard's Stage or on a page you built: a copy of that Stage's files (pictures, videos, PDFs, text files and pages) or of that one page, their titles and captions, the dashboard's or page's name and the install ID. Anyone with the link can see them and leave a comment under the name they type; comments are kept with the link and shown to you in the app, and your chat gets only the ones you send it. Everything is deleted 30 days after you first share, or at once when you press Stop sharing. IP addresses of people who share or comment are kept for up to 2 days to stop abuse.

Apart from a Stage you share by link, we never receive your code, files, chats, prompts, passwords, or your Claude or ChatGPT sign-in tokens. When Vizcoder looks at a project's .env file it keeps only the variable names, never the values, and that stays on your computer.

Payments and licenses

Paid plans are sold through Link, Stripe's merchant-of-record service. You pay on Stripe's own checkout page: Stripe and Link receive your email, your card or other payment method (such as Link, Apple Pay or Cash App Pay) and your billing address for tax, under their own privacy policies. We never see your card. Receipts come from Link.

When a payment goes through, vizcoder.com makes your license key. We keep a scrambled (SHA-256) form of the key, never the key itself, with your Stripe subscription and customer IDs, the plan, its status and renewal date, and up to 3 computers that use it, each a random ID and a label like "Vizcoder on Mac · 1a2b", not your computer's name. The copy of Vizcoder that pressed Buy picks up its key once, using a random install ID (kept at most 7 days if it isn't picked up), and the thank-you page shows the key for 24 hours so you can paste it on another computer.

From version 0.1.35 the app checks the key with vizcoder.com when you activate it and then about once a day (it keeps working offline for 14 days), sending only the key, that computer's random ID and its label. Repeated wrong keys from one IP address are slowed down with counters that last an hour.

Claude Code, Codex and your AI accounts

Vizcoder runs Claude Code (by Anthropic) or Codex (by OpenAI), installed with their makers' own installers. You sign in on Anthropic's or OpenAI's own page; Vizcoder never sees your password or sign-in token. Everything you send to a chat, including a screenshot you share with Point & Tell, goes to Anthropic or OpenAI under their terms and privacy policies, not ours. Vizcoder asks Codex which ChatGPT account and plan you're signed in with and how much of it you've used, to show that in the app; it stays on your computer.

What the app can do on your computer

You decide how much the AI chats may do (Settings › Permissions; the app also asks you the first time):

• Claude chats run in auto mode unless you choose "Ask before every command": routine steps such as reading and editing files and running commands go ahead, and risky ones stop and ask.
• Codex chats have full access to your computer and the internet, and ask you when Codex wants your OK.
• Full Disk Access (Mac, optional) lets chats reach files anywhere on your Mac, such as Documents or Desktop.
• On Mac, Vizcoder can open Terminal and type setup steps you start.

These are powerful. Review what chats change, save versions, and keep backups of anything important.

What the app keeps on your computer

None of this is sent to us.

• Vizcoder's own folder, ~/Library/Application Support/Vizcoder on Mac or %APPDATA%\Vizcoder on Windows: your canvases and how you arranged them, your notes, the chats it started, each canvas's Run command, your settings and license status, a private key only your user account can read, logs of the app's own errors and background installs, and pictures you paste into a chat (deleted after 30 days). On Mac the engine's log is in ~/Library/Logs/Vizcoder.
• Claude Code's files in ~/.claude: Vizcoder reads chat transcripts and usage records to show your chats and usage. When you add a canvas in a folder you allowed, it marks that folder as allowed in ~/.claude.json, the same way Claude Code's own question would. Each canvas gets a .claude/settings.local.json (git is told to ignore it). If you turn on "Show plan limits", it adds a small status-line step to ~/.claude/settings.json; turning it off puts yours back.
• Codex's files in ~/.codex: read to show your Codex chats.
• Your canvases are ordinary folders in ~/Vizcoder.

Links Vizcoder opens for you open in Google Chrome when it's installed, otherwise in your default browser.

Who we share information with

Only these service providers, and only to run Vizcoder: Cloudflare (website hosting, our records and shared links), Resend (delivers support messages to our inbox) and Stripe and Link (payments, as merchant of record). We may disclose information if the law requires it. When you share or publish a canvas, Vizcoder uses your own GitHub account through GitHub's tools; shared copies are created as private repositories, and nothing passes through us.

Your choices and rights

• Access or deletion: ask through vizcoder.com/contact for a copy of what we hold about you, or to have it deleted. We answer within 30 days.
• California: we don't sell or share personal information as California law defines it. We don't track you across other sites, so we treat browsers' "Do Not Track" signals the same as any visit.
• EU and UK: we use your information to provide what you asked for (contract), to keep the service secure (legitimate interest), and for the email list with your consent. You can ask to access, correct, delete or restrict it, or object, and you can complain to your data protection authority. Our providers may process data in the United States.

Children

Vizcoder isn't meant for children under 13 (under 16 in the EU), and we don't knowingly collect their information.

Security

The app's local server answers only Vizcoder's own window, updates are checked for our signature before they install, and we keep as little as we can. To report a security problem, use vizcoder.com/contact (see also security.txt).

Removing Vizcoder

Turn off "Show plan limits" if you turned it on, quit Vizcoder, then delete the app and its folder (above). Your canvases in ~/Vizcoder stay where they are.

Taking your email off the list

Enter the email you signed up with and it's deleted from the list right away. This also stops every email from us.

Changes

If this policy changes, we'll update this page and its date. If a change affects how we use your email, we'll email you first.