Technology

The AdWizz extension engine.

A shared engine underpins our extension experiences – designed for remote control, signal-based decisions and a privacy-conscious architecture. It is the backbone that allows us to move quickly without compromising stability.

Developer working with code on multiple screens

Remote configuration

Behaviour is driven by server-side configuration so we can respond quickly to emerging patterns, partner needs and policy changes without resubmitting the extension for every adjustment.

  • Per-domain, per-market and per-product rule sets.
  • Feature flags and controlled rollouts for new capabilities.
  • Safe fallback defaults to maintain a predictable baseline.
Team discussing data and product behaviour

Signal-based decision layer

Rather than heavy user profiling, we rely on patterns and signals observed in aggregate to guide decisions like when to protect, when to ease off and how to respond to complex layouts.

  • Detection of popups, overlays and autoplay behaviour.
  • Heuristics tuned to avoid breaking legitimate site flows.
  • Models designed to evolve as the web and policies change.
We treat the engine as a standalone product: it has its own roadmap, observability, internal SLAs and security reviews. Individual extensions plug into this engine, inheriting its capabilities instead of re-implementing core logic.
Architecture

How our engine integrates with browser extensions.

Client-side components

  • Manifest v3 service workers for background processing and event handling.
  • Content scripts for precise, DOM-level interactions on pages.
  • Lightweight messaging between popup UIs, options pages and engine rules.

Server-side components

  • Configuration APIs for rules, overrides and feature toggles.
  • Aggregated signal collection to understand performance and quality.
  • Partner integration modules for search feeds and commerce flows.
Security & privacy

Built with user trust and platform rules in mind.

We recognise that extensions sit very close to the user. Our technology choices reflect that responsibility.

Privacy-aware by design

We design flows to minimise data collection. Where we use analytics, they are aggregated and focused on performance and quality, not individual profiling.

Policy-aligned behaviours

We architect experiences to stay aligned with browser store policies and partner requirements, avoiding ad injection, deceptive prompts or misleading UX.