Privacy policy

Metrician reads connected providers’ allowance information and stores normalized readings locally in its Chrome extension or Android app. No Metrician account is required.

What Metrician processes

The Chrome extension uses optional Chrome permissions to request allowance information from providers you explicitly connect. It uses the provider session already signed in within your Chrome profile.

• Provider cookies, authorization headers, session-derived tokens, and raw responses remain inside provider and extension contexts.
• Metrician retains normalized allowance windows, reset times, provider status, freshness, settings, and bounded normalized percentage history in local Chrome extension storage.
• History has no fixed age expiry. Recent history retains regular polling detail, samples older than 48 hours compact hourly, and samples older than 30 days compact daily to preserve the maximum useful local range.
• Widget position, theme, hidden sites, alerts, and provider order remain local.
• The extension checks signed collector compatibility files from metrician.io/mobile/specs/ the same way the Android app does: no account, no provider data, at most once per six hours per provider unless a schema failure forces one retry.

Metrician’s use of information received through Chrome permissions complies with the Chrome Web Store User Data Policy, including its Limited Use requirements.

Android app

On Android, provider sign-in occurs inside Metrician’s persistent GeckoView browser profile. Gecko stores that profile locally so sessions can persist. Provider cookies, session-derived tokens, authorization headers, raw responses, and provider page contents remain inside that browser context. They do not enter Metrician’s Flutter/SQLite data, widgets, notifications, or servers.

The Android app stores validated normalized readings, bounded history, preferences, alert state, verified compatibility-spec metadata, widget projections, and a bounded normalized-result inbox in app-private local storage. Android backup and device-transfer extraction are disabled for that data. It automatically checks signed declarative compatibility files from metrician.io/mobile/specs/ during available foreground opportunities. Routine checks are limited to once every six hours per provider; a detected schema change can trigger one immediate check and one collection retry. These requests include no Metrician account, provider data, allowance values, or purpose-built device identifier. As with any HTTPS request, the hosting/CDN can receive ordinary network metadata such as IP address, request time, path, and user agent.

Complete provider or OAuth URLs are not retained in Metrician’s native control state. URLs used for safe state handling are reduced to origin and path, without query strings, fragments, user information, or ports.

Android internet access supports provider pages, normalized provider usage requests, and signed compatibility files. Notification permission is requested only after the first successful provider connect, when you accept Tell me before I run out, on Android 13 or later. Metrician does not request contacts, location, camera, microphone, SMS, broad file access, accessibility, VPN, device-admin, or Android account permissions.

Website measurement

This website uses a first-party measurement service to count anonymous visits, engaged visits, and clicks through to the Chrome Web Store. It records campaign parameters, referring page, a random browser identifier, a random session identifier, basic browser metadata, and a one-way IP hash for attribution, data quality, and abuse prevention.

A standard page-view event and the same named events are sent to BAMBAM LLC’s PostHog project in its EU Cloud region. PostHog receives an anonymous identifier, experiment variant, attribution, event time, the page URL without query parameters, and basic browser metadata. Automatic click capture, heatmaps, session replay, performance capture, and exception capture are disabled.

For visits delivered by a TinyAdz advertising campaign, TinyAdz’s TinyStats service measures click quality and whether the Chrome Web Store button is selected. It receives TinyAdz campaign and click identifiers, the landing-page URL including campaign parameters, referring page, normalized browser language and timezone information, and interaction counts such as active time, pointer or touch movement, scroll depth, page visibility, and URL changes. Metrician configures this integration not to store TinyAdz session data in the browser. This measurement is used for bot detection, campaign cost adjustment, and conversion reporting.

The website does not send provider allowances, extension state, page text, email addresses, or Chrome account details to Validation. Raw anonymous events are retained for 13 months and then reduced to non-identifying daily totals.

What Metrician does not collect

• No Metrician account, email address, or profile is required.
• No browsing history, page text, screenshots, or unrelated response bodies.
• No provider passwords or API keys.
• No behavioral analytics or automatic telemetry from the extension or Android app. Limited website measurement is described above.
• No upload of provider allowances or raw provider data to Metrician.

Diagnostics

Metrician does not gather diagnostics. Opening support loads this website in a normal browser tab; neither product attaches provider readings, browser-session material, local product state, or diagnostics to that address.

Support messages

The extension contains no support form and transmits nothing. Its support buttons open this website in a new browser tab. Android Settings Support and feedback opens the same public support page.

Support messages and enquiry forms on this website are sent to BAMBAM LLC’s support system. Metrician receives the form fields, messages, contact details, attachments, and basic browser metadata you choose to provide.

If you email Metrician’s support address instead — linked from the support page — Metrician receives the address, message, and attachments you choose to send. Support is separate from product runtime; Metrician never sends diagnostics or provider data to support automatically.

Permissions and control

Provider origins are requested one at a time when you choose Connect. All-sites access is separately requested only if you enable the floating widget.

You can disconnect a provider to remove its current reading and revoke access while preserving local usage history for later reconnection. Clear history removes timeline samples and alerts while preserving current connections. Reset & revoke deletes all Metrician state and removes every optional provider and site permission. Chrome also lets you revoke extension permissions at any time.

On Android, Clear history, Disconnect all providers, Clear browser sessions, and Reset all local data are separate controls. Disconnecting stops collection and removes current display state but preserves history and does not claim to sign you out of the provider website. Clearing browser sessions removes Metrician’s Gecko profile. Reset removes normalized app data, native widget/notification state, preferences, verified-spec state, and browser sessions.

Data sharing and sale

Metrician does not sell personal data. Neither product transmits provider data to Metrician or shares it with advertisers, analytics services, or data brokers.

Changes

Material privacy changes will be documented here and in relevant product release notes before release. If Metrician adds a feature that processes data differently, this policy will be updated before that feature is enabled.