Privacy Policy

Awaitful is built around one rule: it never reads your code, your prompts, your files, or your AI agent's output. This page explains, in plain language, exactly what the Awaitful client and website handle, and what they deliberately do not. Every claim about the client is enforced by code you can read, because the client is open source.

Awaitful LLC (“Awaitful”, “we”) is the company responsible for the information described here - the data controller for the account details you provide and the marketplace records the service creates.

The one rule

Awaitful shows a single sponsored line while your AI coding agent is thinking, and pays you a share of the ad revenue. To do that, the client needs to know only that an agent is thinking and for how long the line was actually visible. It learns this by watching the agent's own thinking indicator, never by reading your editor buffers, your transcripts, or your filesystem.

What the client sends to our server

The client makes a small, fixed set of requests. None of them carries a file, a path, a prompt, or any of your content:

• An ad request with the surface being rendered (for example, the status bar) and, only if you opt in, a coarse hint such as the hour of day. Never content.
• Ad events that record which sponsored line was shown, on which surface, and how many milliseconds it was visible. That visible time is the most specific thing Awaitful ever learns about a session.
• A killswitch check that asks whether ads are paused, with no data attached.
• Patch-health reports (only if you enable a surface that modifies Claude Code) that contain SHA-256 hashes of Claude Code's own shipped files, used to recognize a known-good build. These hashes are of the editor's bytes, not yours, and cannot be reversed into your content.
• Account reads so the panel can show whose account is earning and how much.
• A one-time device link that ties your machine to your account after you sign in.

Requests are authenticated with a single opaque device token sent in the request header. It identifies the device, not you within a session, and you can revoke it from your dashboard at any time. The server honors revocation immediately.

What stays on your machine

The surfaces that render inside Claude Code (the thinking line, the composer banner, and the terminal status line) communicate only with a small Awaitful helper running on 127.0.0.1 on your own machine. Those local messages say only which helper is running, "draw the current line," "the line was drawn, seen or clicked," and - when the spot the line attaches to is missing - "I had a line and could not place it." Nothing from inside your editor reaches our server except the ad events listed above. If a surface preserves your existing status line, it does so locally and restores it when you turn the surface off.

Each editor window, and each copy of the in-editor script, generates a random identifier when it starts. These let a window tell its own script apart from another window's, so one line shown in two editors is not counted as twice the viewing time. They exist only in memory for the length of a session, are never sent to our server or written to disk, and identify a window and a script rather than you, your machine, or your work.

What we deliberately do not do

• We do not read your source files, open buffers, terminal, or clipboard.
• We do not read your prompts or your agent's responses.
• We do not send file names, paths, project names, or repository information.
• We do not fingerprint you across sites. There is no third-party tracker in the client.
• We do not ship ad-rendering code from the server. The code that runs is in the public source tree, and the client verifies it before it changes anything.

Your account and this website

When you create an account for the dashboard, we process the details you provide, such as your name and email address. If you sign in with Google or GitHub, we receive basic profile information from that provider solely to authenticate you and link your account. We keep you signed in with a first-party session cookie. There are no third-party advertising or tracking cookies on this website.

For product analytics we use Umami, which we run on our own server. It is cookieless: it sets no cookies, collects no personal data, does not fingerprint you, and never follows you to any other site. It also honors your browser's Do Not Track setting, so if you have that on, it records nothing. We use it to see which pages and steps people use, and we use its heatmaps and session insights to see where people click, scroll, and get stuck, so we can make those pages better. The content of anything you type or that appears on your screen is masked out of these, so it is never captured. This is on the website only; the extension carries no analytics or tracker of any kind, which the client's public source and the egress test let you confirm.

To run the marketplace, we store the data you create: advertisers' campaigns and creatives, and developers' impression, click, and earnings records. We use this to serve ads, calculate earnings, prevent abuse, and provide support.

Payments

Funding a campaign or receiving a payout involves a payment provider. Where that applies, the limited information needed to process a transaction is handled by that provider. We do not store full card numbers.

Data retention and your choices

• You can revoke a device token from your dashboard at any time.
• You can delete your account from Settings. This erases your login and personal details and switches off every device. We keep only the financial records the law requires us to retain (past earnings and payouts), with your identity removed from them.
• We keep transaction and earnings records for as long as needed to operate the service and meet legal and accounting obligations.

Children

Awaitful is not directed to children and is not intended for anyone under the age required to form a binding agreement in their location.

Changes to this policy

We may update this policy as the product evolves. When we do, we will revise the date at the top of this page.

Verify it yourself

You do not have to take any of this on faith. The client is open source at github.com/Awaitful/awaitful. The exact payload shapes are defined in the shared contract, and a test in that repository fails if a field that could carry your content is ever added. If you find anything in the source that contradicts this page, please open an issue. The code is the source of truth.

Contact

For privacy questions, contact Awaitful LLC at [email protected].