This explains what ADCode collects, what it does not, and why. It covers the ADCode editor and this website.

The short version

ADCode's advertising, earnings, and analytics services never receive file contents, file paths, or project names.
AI features may send source text and prompts to the provider you select. ADCode explains and limits that separate path below.
Ads are targeted using a fixed list of 45 generic tags describing the language or framework you have open.
You are identified by an anonymous account created automatically, with no email, name, or password, unless you choose to add one.
We do not sell personal data, and there are no third-party advertising trackers in the editor or on this site.

What the editor sends

To serve an ad

A request contains three things: the tags for what you have open, whether your theme is light or dark, and how many cards to return.

Tags come from a closed vocabulary compiled into the editor — values like lang:rust, fw:react, tool:docker, platform:backend. There are 45 of them. The server cannot add to the list, and any tag the editor does not recognise is never sent.

There is no field in this request for a filename, a path, a repository, a symbol, or a line of code.

To record that you saw an ad

A receipt contains an identifier for the card, how long it was on screen, whether you clicked or dismissed it, and your theme. This is what your earnings are calculated from.

When you send feedback

If you use the feedback button, we receive what you typed, the app version, and your operating system name. Nothing else about your machine or your work is attached.

AI features

You choose the AI provider and supply its API key. Chat and agent tools can send your prompt, relevant source text, and tool results to that provider so it can answer or edit an isolated task workspace. Automatic inline completion sends bounded text around the cursor (up to 6,000 characters before it and 2,000 after it), the language, and a small output allowance; it does not send the file path. You can turn inline completion off in Settings.

AI traffic goes directly from the desktop app to the selected provider under that provider's terms and privacy policy, not through ADCode's advertising service. ADCode keeps task sandboxes, rollback checkpoints, schedules, and operational traces locally. Traces describe actions and outcomes rather than storing a provider's private reasoning, and common credential shapes are redacted. ADCode also skips inline completion for common credential files, but you should still review what you ask any AI provider to read.

Identity

On first launch the editor creates an anonymous account through Firebase Authentication. It has no email address, no name, and no password. Its only purpose is to have somewhere to credit your earnings.

If you later choose to withdraw money, you can attach an email address to that same account — an address the provider has confirmed, which is a condition of being paid. Your existing balance carries over because it is the same account, not a new one.

What we store

Your anonymous account identifier, and when it was created.
Your ledger: one row per credit, reversal, adjustment, or withdrawal, with the amount and a short description.
Records of ads served to you, kept briefly, so a receipt can be checked against a real serve.
Feedback you send, if you send any.
If, and only if, you ask to be paid: the payout details you enter — the full name on the receiving account, the country and currency, and either the email address on your Wise account or the bank details you give us. We store them so a person can make the transfer, and a copy is attached to each request so that editing your details later cannot redirect a payment already in progress. You can change or clear them at any time from the Payouts tab.

Cookies and analytics

This website sets no cookies and runs no third-party analytics or advertising scripts. Fonts are served from this site's own domain rather than a font CDN, so loading a page does not disclose your address to another company.

The signed-in areas — the dashboard, advertiser portal, and admin panel — use a session cookie strictly to keep you signed in.

Sharing

We share personal data with nobody for advertising purposes.

Advertisers receive aggregate reporting: how many times their campaign was served, viewed, and clicked. They never receive your identifier, your tags, or anything that identifies you individually.

We use Google Cloud and Firebase to run the service, Dodo Payments to take payment from advertisers, and Wise to send withdrawals. Each receives only what it needs to do its part — Wise receives your payout details and the amount, and nothing about how you earned it.

Your choices

Turn ads off. Settings has a cadence control with an off position. The editor is otherwise identical, with no reduced features and no prompts to turn it back on.
Ask for your data or its deletion. Write to privacy@adcode.bluethenics.com. Deleting your account removes your identifier and your ledger. Records we must keep for accounting are retained where the law requires.

Retention

Ledger rows are kept as long as the account exists, because they are the record of what you were paid. Serve records expire automatically within hours. Feedback is kept until it is resolved.

Children

ADCode is not directed at children under 13, and we do not knowingly create accounts for them.

Changes

If this policy changes in a way that affects what is collected, the date below changes and the change is described in the blog rather than made quietly.