Aura by OmniConflux
Earn transparency
Exactly what Aura does on your device, what leaves it, and how views are counted. Revenue share is announced at launch.
What leaves your device
OmniConflux classifies your session on your own machine into a fixed list of topic tags, such as a language, a framework or a kind of task. Tags are recomputed per session window, not per keystroke. Only those tags, and at most one short summary built from them, are sent to choose an ad. Your tag history stays on your device.
What never leaves your device
- Your code and file contents
- File paths and project names
- Your prompts and your agents' replies
Where ads can appear
Ads appear only on OmniConflux-owned surfaces. Every ad has a visible Sponsored label.
- Idle status line
- One short line in genuinely idle space. Never replaces usage, limit or error indicators.
- Working line
- Replaces only the waiting text while an agent works. Hidden the moment real status appears.
- Reply footer
- One labeled line below a finished reply, styled apart from the agent's answer.
- No ads
- Voice, anything you share with clients, and automated server sessions never show ads.
How views are counted
- Rendered: the ad was drawn on screen.
- Viewable: the ad was visible in a focused window.
- View threshold met: the ad stayed visible and focused for a continuous period. Only this counts as a paid view.
- Click: you opened the ad's link.
Each event carries a one-time code, so the same view is never counted twice.
Fraud controls
- Views require a focused window and normal human input patterns.
- Each seat has caps on how many views it can earn.
- Traffic from hosting, proxy and automation networks is excluded before any ad is chosen.
- Clicks on your own ads earn no credit.
Consent and controls
- Off by default. You opt in explicitly.
- One toggle turns everything off.
- Per-placement toggles and advertiser category blocks.
- Global Privacy Control signals are honored.
See the Earn FAQ and the advertising policies.