Privacy Policy

The meeting clock can accept a meeting name, attendee count, average annual salary, optional individual attendee names and salary estimates, expected duration, working hours and weeks, and an employment-cost multiplier. While a meeting is running, it also keeps the start time, pauses, and elapsed time needed to calculate the estimate.

When you end a meeting, the app can save a local history record with the meeting name, date, duration, attendee count, estimated cost, cost-per-minute, annualized estimate, employee-hours estimate, and any “was it worth it?” response. Individual attendee names and salary estimates are not included in the saved history record.

The current Meeting Meter code stores the active meeting and meeting history in your browser's local storage. It does not send meeting names, attendee counts, salary estimates, duration inputs, or meeting history to a Meeting Meter server, and it does not share those inputs with third parties through the app.

The app also saves your light or dark display preference in local storage. The repository contains a legacy storefront helper that can save supported campaign parameters in session storage when mounted; the current root layout does not mount that helper. Those parameters are separate from meeting data.

You do not need an account to use the meeting clock, local history, receipt, or recurring meeting calculator. If you choose to create an account, the sign-up form sends the name you provide, email address, and password to the app's Convex authentication service. Those account credentials and related workspace information are handled separately from meeting-clock data.

The current app does not offer a self-service account-deletion control. To ask about an account or any information you send us in an email, contact us at team@meeting-meter.madethis.app. Sending an email is your choice; its contents are not submitted through a Meeting Meter web form.

We did not find an active analytics or error-reporting provider mounted in the current Meeting Meter deployment. The project contains legacy PostHog-related code, but no active PostHog provider is mounted in the app. We also found no public-page cookie set by the deployed home page.

The app uses Convex for optional authentication and account features. Its authentication tools may use technical authentication storage when you sign in. Separately, the administrative area can set a secure, HTTP-only admin_token cookie for up to one hour after an administrator opens a valid admin link. That cookie is limited to the/admin path and is not used by the public meeting clock or this policy page.

Meeting Meter is hosted on Vercel. We did not find custom application request logging in this codebase or a source-defined hosting-log retention setting. Like other web hosts, Vercel necessarily handles requests needed to serve the site; this policy does not make a claim about Vercel's independent operational-log retention.

Browser-local meeting data remains on your device until you delete it, your browser clears site data, or the browser removes it. Use theClear history control in Meeting Meter to remove saved meeting-history records. To remove an active meeting, saved display preference, and any other Meeting Meter local storage, clear this site's browser data through your browser settings.

Because meeting data is not sent to our server by the clock, clearing it from your browser removes the app's local copy. For optional account information or support email, we have not published a specific retention period in the app; contact us at team@meeting-meter.madethis.app to ask about deletion or retention.

We may update this policy if the app's data practices change. We will post the revised policy at this URL and update the effective date at the top. If a change requires a different kind of notice, we will provide it where appropriate.

Questions about this policy or privacy can be sent to team@meeting-meter.madethis.app.