Metrimble / Privacy

Privacy notice

This notice describes information handling that can be verified in the current app code.

Browser-based calculators

The percentage, loan repayment, unit conversion, BMI, and IPv4 subnet calculators keep their inputs and results in browser component state and calculate in the browser. These calculators do not call an app API.

Google AdSense

The site loads the configured Google AdSense script from pagead2.googlesyndication.com. The app code does not specify what the script collects, how the data is used, or how long it is retained.

Analytics, when configured

On deployments where POLSIA_ANALYTICS_SLUG is set, the app makes a best-effort analytics pixel request when it loads. The browser reuses the random UUID stored in local storage under polsia_vid, or creates and stores one if none exists. The page-load pixel request includes the deployment slug and identifier and goes to POLSIA_API_BASE_URL, which defaults to https://polsia.com. If the slug is not set, this beacon is not mounted. The app does not specify the receiving service’s later use or retention, or how the provider handles request logs.

Theme preference

The light and dark theme control uses next-themes. When you select a theme, that preference is stored in browser local storage under the key theme. The initial theme follows your system preference when no saved choice is present.

Public example form

The /example demo sends the name you submit to /api/example through the app API helper. With the default same-origin API configuration, the local handler validates the name and returns it with a generated ID. Its database read and write code is commented out, so it does not currently persist the submitted record in the app database. If a deployment sets NEXT_PUBLIC_API_URL, the request goes to that configured API origin instead; this app’s code does not specify how that service handles or stores the submission.

Privacy contact

For privacy questions, email metrimble@polsia.app.