Privacy
Last updated: May 1, 2025
Information we handle
MeshMetrics processes the account information needed to provide the subscription service, such as your name, email address, selected country, plan information, and operational preferences. Monitoring configuration can include endpoint addresses, check settings, status-page configuration, and alert destinations you choose to provide.
Monitoring information
A monitor is a configured endpoint that the service checks. Event records may contain a timestamp, endpoint identifier, check result, response timing, and configuration context. We do not ask you to provide unrelated personal data as part of configuring a standard monitor.
How information is used
Information is used to provide the service, deliver activation details, maintain account access, calculate subscription status, respond to support requests, and improve reliability and clarity. The service is designed around operational monitoring rather than collecting unrelated content.
Security
Traffic to the service is designed to use encrypted connections, and stored application data is protected with access controls appropriate to the service. No online system should be described as risk-free, so the site uses concrete security language rather than absolute claims.
Retention
Operational records follow the retention window attached to the plan selected. When an account is cancelled or a retention window expires, records may be removed from active systems according to ordinary service processes and applicable legal requirements.
Your choices
You can request access to or correction of account information through the support route shown on the website. You can also cancel the subscription through account settings without a cancellation fee.
Updates
This policy may be revised when product behavior, legal requirements, or service architecture changes. The date at the top identifies the version presented on the site.
Service providers
MeshMetrics may rely on carefully selected infrastructure providers to host application components, send transactional messages, or maintain service operations. When a provider processes information for the service, the relevant access should be limited to the information required for that operational purpose. The static site does not name production vendors because this package is a front-end demo and the final production configuration may use different services.
International considerations
A visitor may access MeshMetrics from a country different from the service operator or infrastructure location. When information crosses borders, the production service owner should configure appropriate contractual and technical safeguards. This page describes the intended categories of data and the product workflow rather than promising a particular physical storage location.
Data access and correction
Where the production service offers account controls or a support channel, you may ask to review or correct information associated with the account. Requests should identify the relevant account without sending unnecessary sensitive information. Operational logs may have technical integrity requirements that limit edits to individual event records.
Legal requirements
MeshMetrics may retain or disclose information when reasonably necessary to comply with a legal obligation, respond to a valid request, protect the service from abuse, or preserve records needed for a dispute. Any such handling should be limited to the relevant purpose and should not be interpreted as a general license to collect unrelated information.