Built to measure attention, never your work.
RuntimeAds runs inside the same editor as your code and your AI agent, so we hold ourselves to one rule: collect the operational signals needed to pay you and keep the marketplace honest, and nothing about what you’re actually building. Here’s exactly where that line is, and how you can verify it yourself.
What we collect
Operational signals only.
- ✓ Your Google email and account ID, and a random, pseudonymous install ID
- ✓ IP-derived country (and timezone) at signup and install, for fraud review only, never to block access
- ✓ Attention timing (when your agent starts, waits, or resumes) as a hashed session ID plus a coarse activity category
- ✓ Render telemetry (which ad showed, on which surface, and impression/click events) to verify and pay you
- ✓ Runtime health counters (queue/cache sizes, heartbeat timestamps) and the campaign content advertisers submit
What we never touch
It never leaves your machine.
- ✕ Your prompts and the AI’s responses
- ✕ Source code, file contents, and file paths
- ✕ Repository and branch names
- ✕ Terminal output
- ✕ Environment variables, secrets, and clipboard
- ✕ The names of the tools your agent runs, collapsed to a category on your machine, never sent
Don’t take our word for it.
Privacy promises are only as good as the code behind them. Three things make ours verifiable rather than aspirational.
Stripped on your machine
Before anything is sent, an allowlist keeps just four fields from each AI hook event: the event name, a session ID, a source, and a tool category. Every other field in the raw payload (prompt text, tool inputs, file paths) is discarded locally, never read.
Pseudonymous by default
Your session ID is one-way hashed (SHA-256) before it ever leaves your machine, and your install ID is random. We attribute earnings to an install, not an identity, and not your work.
Source-available
The extension client is open for inspection. Read the exact function that does the stripping, terminal-hook-mapper.ts and confirm every claim on this page for yourself.
Uninstall leaves nothing behind.
Tools that reach into your editor have a habit of digging in and staying. RuntimeAds is built to do the opposite. Remove it, restart your editor, and everything is exactly as it was: no ad code, no tracking, no leftover files, and nothing changed in your other extensions.
- ✓ Every change is backed up and put back, so your Claude Code and Codex panels return to exactly how they were
- ✓ Its whole footprint is one folder that gets deleted. Nothing lingers in your home directory
- ✓ Your login never touches disk. It stays in your editor’s secure storage
The whole client is open, so you can confirm this yourself instead of taking our word for it. A full restart of your editor finishes the cleanup.
You’re paid for verified attention, and never charged.
Earnings come from impressions our server-side measurement confirms actually rendered to a human during active coding. Builders are never billed for anything; advertisers pay only for verified, fraud-screened impressions. The exact definition of a verified impression is in the FAQ.
Fraud screening that protects everyone, without punishing honest devs.
Automated systems and human reviewers screen activity in both directions, adaptively and around the clock. The specific signals and thresholds stay undisclosed by design. That’s what keeps them effective. The thing to know: builders coding normally are never affected, and established accounts are reviewed by a person before any action sticks. The ground rules and appeal path are in the FAQ.
Read it in full.
This page is the overview. The legally binding detail (retention, third parties, your data-access and deletion rights) lives in the Privacy Policy.