Privacy Policy

Who we are

This site is Meet Counter. You can contact us.

What data we collect

When the extension opens the welcome page, your browser stores your serving number on this device. This keeps a refresh from taking another number.

We also run Umami, a self-hosted analytics tool, to see which pages people read. It collects page views, referrer URLs, browsers, operating systems, device types and country of origin. It does not use cookies, does not store IP addresses and does not track you across other websites. It also counts which page sections come into view, how far down the page someone scrolls, presses of install and navigation links, and interactions with page features. It counts the event, not who did it. When we are showing more than one version of the front page, which one you see is worked out from your IP address and your browser, mixed together for that one request and then dropped. Nothing is stored on your device, and no cookie is set.

Your camera and meeting

Meet Counter processes your camera on your device to cut you out and draw a live background. The model, processing code and fonts are bundled with the extension. We do not receive your camera frames, audio or captions. The finished picture is passed to your call app as your camera stream, so the call app and the people in your call receive it as they would your normal camera. Your chosen theme can show meeting costs, titles and counters to those people.

Meet Counter works in Chrome in Google Meet, Zoom, Microsoft Teams and Jitsi Meet. When you install it, Chrome asks you to let it read and change those apps' web pages, so it can replace your camera there. Reload any call tab that was open before you installed it. You can take that access away in Chrome's own site settings. Meet Counter does not ask any call app for an account sign-in or other access.

You set the people count, average annual salary, booked time and counters. Costs are estimates from those settings. Optional experimental readings start off and work only in Google Meet: they can read the participant count and page title from Meet, count selected phrases in visible English captions, and estimate your own microphone level and speaking time from audio already opened by Meet. These readings run locally, can be unavailable or incomplete, and can be turned off in Settings. In Zoom, Teams and Jitsi Meet you set these values yourself. Meet Counter does not identify faces or voices or record your call.

Settings and saved presets stay in this browser through Chrome's local extension storage. Presets can include their name, meeting title and receipt labels. Current meeting state and readings use session storage and are cleared when the meeting tab closes or the browser session ends. Caption text and audio are not saved. You can delete presets in Settings. Meet Counter also remembers where you moved its button on each call app's site. Removing the extension removes its local settings and presets.

Extension usage

We use our self-hosted Umami server to count extension installs and updates, loads on supported call pages, theme choices, background and reader toggles, manual stats resets, manual setting or counter changes, and opening or dismissing the first-use guide. These events include the extension version and fixed labels for the action. They do not include the values you enter.

Meeting URLs, codes, titles, captions, names, participant counts, salaries, costs, counter values, audio and video are not sent to analytics. Meeting processing stays on your device. The analytics server receives your network address and browser headers when it handles a request. We add no installation identifier and do not link extension activity to your email or visits to this site.

We use these counts to maintain and improve the live backgrounds and their controls. Meet Counter follows the Chrome Web Store User Data Policy, including its Limited Use requirements. We do not sell extension data, use it for advertising or credit decisions, or use meeting content to train models. We do not receive meeting content for people to read. The camera output you choose to send through your call app is separate from usage analytics.

Bug reports

Report a bug in the extension's Settings shows you a diagnostic bundle before opening a draft in your mail app. It includes the extension version, build channel, chosen background, browser version, OS family, camera pipeline state and recent fixed error codes. Each preview gets a new report ID. The bundle excludes meeting content, names, titles, captions, salaries, email addresses and persistent install identifiers.

Camera state and error codes stay in browser session storage until the tab closes or the browser session ends, and start fresh when the page reloads. The report controls send no analytics events. You can copy or save the bundle, edit or discard the draft, and choose whether to send it. Opening the draft does not send it. If you send a report, we receive your email address, message and any diagnostics or attachments you choose to include in our support mailbox. We use them to investigate and reply to your report. Avoid adding private meeting details. You can ask us to delete a report through the contact link above.

Why we collect it

We use analytics in aggregate to understand which pages people read, how they move through the page, and how different versions of the page perform.

How we store it

Your serving number stays in your browser's local storage. Analytics data is stored on a server in Germany (EEA). Analytics data is not sold or shared for advertising. Your camera output is shared through your call app as described above.

Your rights

Under UK GDPR, you have the right to:

• Access your data, email us and we will confirm what we have
• Delete your data by contacting us
• Object to anything we do on legitimate interest, which is the analytics and picking which version of the front page you see, email us and we will stop
• Complain to the ICO if you are unhappy with how we have handled your data

Legal basis

For analytics, the legal basis is our legitimate interest in understanding which pages people read and maintaining and improving the extension. Analytics do not use cookies. Network addresses and browser headers are processed when requests reach the analytics server, as described above.

Picking which version of the front page you see runs on the same legitimate interest: we want to know which version of the page works better. Your IP address and browser are read for that one request, mixed together to pick a version, and dropped. Neither is written down, no cookie is set, and nothing is kept that could be traced back to you. You can object to this at any time, as you can to the analytics. Email us and we will stop. Because nothing about the request is kept, there is nothing left to delete afterwards.

Changes

If we make significant changes to this policy, we will note it at the top. The current version was last updated on 16 October 2026.