Outside ad selection
Source code
Project files and source code are not used to decide which sponsored placement appears.
Trust & security
AdFrolic is designed around a simple boundary: sponsored placements should work without needing the substance of what you are building.
Outside ad selection
Project files and source code are not used to decide which sponsored placement appears.
Outside ad targeting
Prompt and conversation contents are not used as advertising targeting signals.
Outside personalisation
Commands and terminal output are not passed into AdFrolic to personalise sponsored placements.
The data boundary
Only the context needed to decide whether a sponsored placement is eligible to appear.
The environment and eligible surface where an advert may appear.
Signals such as region or language where relevant to campaign eligibility.
Validated creative, campaign settings and destination information.
For the exact data fields AdFrolic collects, why they are used and how long they are retained, see the Privacy Policy.
How a placement moves
VS Code or Claude Code reaches a point where a sponsored placement may be shown.
Campaign eligibility and constrained context determine which structured advert can be returned.
The integration displays the returned advert in its dedicated placement surface.
Creative safety
Advertisers provide validated creative fields rather than raw HTML or JavaScript.
Campaign destination URLs are validated so dangerous URL schemes are not accepted as advert destinations.
Advertiser-controlled strings are escaped before they reach the editor surface.
If a required fraud, database or payment check fails, the affected operation stops rather than treating an unknown result as permission to continue.
Public traffic
Cloudflare provides managed web application firewall rules, DDoS protection, TLS enforcement and endpoint-specific rate limiting around the public service.
Privacy
See exactly what AdFrolic collects, why it is collected and how long it is kept.
Read the Privacy Policy →