Privacy Policy

How the Enhancer browser extension handles your data.

Version
1.0.0
Last updated
13 September 2026

Summary

Enhancer is a free browser extension maintained as a hobby project by igorovh in Poland. You do not need to create an Enhancer account or sign in.

For privacy questions or requests, contact privacy@enhancer.at.

Data stored only on your device

The following data is written to your browser's local storage and never leaves it:

This data is stored in the browser databases enhancer_settings and enhancer_watchtime. You can remove it by clearing the corresponding browser data. We cannot restore locally deleted data.

Data sent to Enhancer servers

To show badges and nickname styles in chat, the extension connects to api.enhancer.at over HTTPS and a WebSocket. We and our infrastructure providers process your IP address, the requested resource and technical connection information. Depending on the request, this may include:

How badges are matched

When you open a channel, we send you the list of badges and nickname styles that belong to that channel. Your browser then matches that list against the chat messages on screen.

The browser performs this matching locally; it does not need to upload chat messages to our servers for this purpose.

Connection limits and diagnostics

The API uses IP addresses in memory to enforce connection limits and keep the service available. Error logs may contain request URLs and technical error information. Infrastructure providers also process connection information to deliver and protect the service.

We use aggregated connection metrics, including country, extension version and client source, to monitor service usage and availability.

Image previews in chat

When a chat message contains a link to an image, the extension can show a preview instead of a bare link. Two of our services support this:

These services receive the image address and the IP address of the request. Retrieved images are cached for one hour so the same link does not have to be fetched repeatedly.

Watch time lookups

The watch time feature can look up how long a person has watched a channel. This lookup is answered by a third-party service, xayo.pl, which receives the username being looked up and your IP address. A lookup may run when a channel page opens or when the watch time command is used. This is separate from the watch time recorded locally by the extension.

Custom fonts

If someone in a channel has chosen a custom font for their nickname, your browser loads that font from Google Fonts so the nickname renders correctly. Google receives your IP address and request metadata, which may include referrer information depending on the browser's referrer policy. This can happen because of another person's preference rather than your own.

See Third Party Services for information about the services involved.

People with badges

We obtain public profile information from the Twitch and Kick APIs, including platform identifiers, login names and display names. We also store badge and nickname-style assignments, appearance settings and related timestamps. Public profile information can still be personal data.

Badges and styles may be assigned at your request, at a channel operator's request, or by the project maintainers. The relevant profile identifiers and assignments are made available to other users through the service so the extension can display them.

If you do not want a badge or nickname style, you can contact us to request its removal.

Why we process data

We process this information to deliver badges and nickname styles, maintain and troubleshoot the service, prevent abuse, and respond to messages and privacy requests.

We rely on our legitimate interests in operating and securing the free service and maintaining its community features, taking into account the rights and reasonable expectations of the people concerned. Where processing is necessary to comply with a legal obligation, such as handling applicable data protection requests, we rely on that obligation. These grounds correspond to Article 6(1)(f) and Article 6(1)(c) of the GDPR, respectively.

Access and service providers

Project maintainers access service data for administration, maintenance and support. We use infrastructure providers to run the service and Purelymail to handle email. If you write to us, we receive your email address, message contents and any attachments you send.

We also use third-party AI tools for development and troubleshooting. When these tools are connected to our systems, database records or diagnostic information containing personal data may be sent to their providers.

See Third Party Services for the providers and external features.

How long data is kept

Local extension data remains on your device until it is cleared.

Server-side profile records and badge or style assignments are currently retained without a scheduled deletion period. Disabling an assignment marks it as archived; it does not delete the underlying record. You may separately request erasure of your personal data as described below.

Email correspondence is currently retained without a fixed deletion period. Retrieved preview images are cached for one hour, as described above.

Data we do not collect

Your rights

Depending on the circumstances, you may request access to, correction or erasure of your personal data, restriction of processing, or data portability where applicable. You may object to processing based on legitimate interests.

To exercise your rights, contact privacy@enhancer.at. We may ask for information reasonably necessary to verify that a request concerns your data.

You may lodge a complaint with a data protection authority, including the President of the Personal Data Protection Office (UODO) in Poland.

Children

Enhancer is not directed at children. Twitch and Kick each set their own minimum age, and you should meet the requirement of the platform you use.

Contact

Questions about this policy: privacy@enhancer.at


Changes

We may update this policy as the extension or its supporting services change. The current version and update date are shown on this page. Where required, we will provide additional notice before relevant changes take effect.

Changelog

Version Date Change
1.0.0 13 September 2026 First published version.