Zero Ad Network por Zero Ad Network
Browse & support partnered Web without Ads, Paywalls or additional Subscriptions.
Algunas características pueden ser de pagoAlgunas características pueden ser de pago
No hay usuariosNo hay usuarios
Metadata de la extensión
Sobre esta extensión
Browse & support partnered Web without Ads, Paywalls or additional Subscriptions.
Zero Ad Network consists of two parts: authority web services (our web backend) and Chrome browser extension. The logged in Zero Ad Network users install the extension, subscribe to one of 3 subscription plans.
Upon a successful subscription our backend generates a special, signed by us, token that is synced with the browser extension along with some other relevant payloads, such as internal authorization token to communicate with our backend services.
This special user token is then injected into each HTML page request as a Request Header, ie { 'X-Better-Web-Hello': 'AftrITJpRwOwAw==.iLTmRJVx6AiWLU9J/xKiK2c8usAEP0b+SDmRxHOOZQKwBkV+UQuyv0KStC8fdlRwkUIjznxBoKqx0Dh6bM+IDg==' }.
Then we have another Zero Ad Network user type - publisher. Anyone who has a website can sign up with us to participate in our monetization program. A website owner can either add 1) add an additional server HTTP Response Header, ie. { 'X-Better-Web-Welcome': 'AZqjLpZqfVKXvP25ojq9vg^1^1' } or 2) add a HTML META tag like
A partnering site using our backend modules (to be published very soon) is then able to determine if the request to their site came from our browser extension user. They then are able to extract web user's subscription plan and check if hasn't expired yet. The token is signed using our private encryption key. Partnering site, using our backend module, that contains our public key, checks if the token data hasn't been tampered with.
Upon a successful, unexpired token validation completion the partnering site backend has to 1) disable every ad on their server-side rendered page 2) disable 3rd party non-functional cookie trackers 3) based on user's subscription plan, the partnering site might choose to turn off any content paywalls they might have 4) based on user's subscription plan they can allow access to their Basic or next level, otherwise paid subscription, functionality (such as SaaS service, video streaming subscription, and more).
Our browser extension notices that the server is responding with our proprietary server header (participating in our program) and starts tracking how much time the user (with the active subscription) spent on the site and how many views (page loads) there were.
This aggregated data (collected against our partnering sites only) is then periodically (daily) sent to our authority services as a telemetry data. The telemetry data includes partner site UUID, total duration spent and total amount of views. Along with that, the user identifying token is attached too.
At the end of the month, our Zero Ad Network web services calculate what partner sites a user visited and how much time proportionally they spend comparing to each visited partnering site. Based on this information, a major part of user's monthly subscription money paid is then divided to each partnering site publisher accordingly.
This incentivizes publishers to provide unobstructed, higher quality level content, otherwise paywalled content and services they might be offering. A website can participate in our program even if they have no ads, paywalls. If our platform user is using their site, by the end of the month they will get their cut of the pie, so to speak.
Ultimately - our users can enjoy clean web experience without needing to use ad-blockers, DNS blockers and similar ad suppression mechanisms. They also don't need to have to pay for multiple subscriptions, scattered across various websites. Instead - they pay once to a centralized authority (Zero Ad Network) and the money is then fairly re-distributed to each partnering site publisher based on user's individual usage patterns.
Zero Ad Network consists of two parts: authority web services (our web backend) and Chrome browser extension. The logged in Zero Ad Network users install the extension, subscribe to one of 3 subscription plans.
Upon a successful subscription our backend generates a special, signed by us, token that is synced with the browser extension along with some other relevant payloads, such as internal authorization token to communicate with our backend services.
This special user token is then injected into each HTML page request as a Request Header, ie { 'X-Better-Web-Hello': 'AftrITJpRwOwAw==.iLTmRJVx6AiWLU9J/xKiK2c8usAEP0b+SDmRxHOOZQKwBkV+UQuyv0KStC8fdlRwkUIjznxBoKqx0Dh6bM+IDg==' }.
Then we have another Zero Ad Network user type - publisher. Anyone who has a website can sign up with us to participate in our monetization program. A website owner can either add 1) add an additional server HTTP Response Header, ie. { 'X-Better-Web-Welcome': 'AZqjLpZqfVKXvP25ojq9vg^1^1' } or 2) add a HTML META tag like
<meta name="X-Better-Web-Welcome" content="AZqjLpZqfVKXvP25ojq9vg^1^1" /> to their rendered HTML document.A partnering site using our backend modules (to be published very soon) is then able to determine if the request to their site came from our browser extension user. They then are able to extract web user's subscription plan and check if hasn't expired yet. The token is signed using our private encryption key. Partnering site, using our backend module, that contains our public key, checks if the token data hasn't been tampered with.
Upon a successful, unexpired token validation completion the partnering site backend has to 1) disable every ad on their server-side rendered page 2) disable 3rd party non-functional cookie trackers 3) based on user's subscription plan, the partnering site might choose to turn off any content paywalls they might have 4) based on user's subscription plan they can allow access to their Basic or next level, otherwise paid subscription, functionality (such as SaaS service, video streaming subscription, and more).
Our browser extension notices that the server is responding with our proprietary server header (participating in our program) and starts tracking how much time the user (with the active subscription) spent on the site and how many views (page loads) there were.
This aggregated data (collected against our partnering sites only) is then periodically (daily) sent to our authority services as a telemetry data. The telemetry data includes partner site UUID, total duration spent and total amount of views. Along with that, the user identifying token is attached too.
At the end of the month, our Zero Ad Network web services calculate what partner sites a user visited and how much time proportionally they spend comparing to each visited partnering site. Based on this information, a major part of user's monthly subscription money paid is then divided to each partnering site publisher accordingly.
This incentivizes publishers to provide unobstructed, higher quality level content, otherwise paywalled content and services they might be offering. A website can participate in our program even if they have no ads, paywalls. If our platform user is using their site, by the end of the month they will get their cut of the pie, so to speak.
Ultimately - our users can enjoy clean web experience without needing to use ad-blockers, DNS blockers and similar ad suppression mechanisms. They also don't need to have to pay for multiple subscriptions, scattered across various websites. Instead - they pay once to a centralized authority (Zero Ad Network) and the money is then fairly re-distributed to each partnering site publisher based on user's individual usage patterns.
Calificado 0 por 0 revisores
Permisos y datos
Permisos requeridos:
- Bloquear contenido en cualquier página
Permisos opcionales:
- Acceder a tus datos para todos los sitios web
Recolección de datos requerida, según el desarrollador:
- Información de autenticación
- Actividad de navegación
- Ubicación
- Información de identificación personal
- Contenido del sitio web
Más información
- Enlaces del complemento
- Versión
- 0.8.2
- Tamaño
- 54,7 KB
- Última actualización
- hace 12 días (30 de nov. de 2025)
- Categorías relacionadas
- Licencia
- Licencia Apache 2.0
- Política de privacidad
- Leer la política de privacidad de este complemento
- Historial de versiones
- Añadir a la colección