Metricarchy

Privacy Policy

Effective 20 September 2026. Public beta.

What we store

Account data (name, email, organization membership, terms-acceptance version and time). Product metadata (schemas, profiles, ontology mappings, metric definitions, alarm configuration, job history). Encrypted source credentials. Uploaded CSV/JSON files on the operator's staging volume. Alarm delivery attempts and audit events for configuration changes.

What we do not warehouse

Customer business facts stay in your systems. Metricarchy reads them to inspect, sample, and evaluate metrics, then stores the computed metric values and lineage — not a copy of your production tables.

How we use data

To operate the product, authenticate you, send verification/reset/invitation email when SMTP is configured, evaluate metrics, deliver alarms you configure, and keep the deployment secure. We do not sell personal data.

Retention and deletion

This is a public beta: the operator may retain, reset, or delete workspaces. To request deletion of your account and organization metadata, contact the operator of this deployment. Backups, if configured, may retain copies until the backup retention window expires.

Security

Source credentials are encrypted with AES-256-GCM. Production requires HTTPS, unique secrets, and email verification for public signup. Connector hosts that resolve to private or link-local addresses are blocked. No security measure is perfect; report issues to the operator.