Privacy Policy
Last updated: September 2026
ABMeter is a feature-flag and experimentation platform, currently in beta.
This policy describes what we collect, why, and who else can see it.
-
What we collect.
When you sign in with GitHub or Google, we receive your email address, name, and the
provider's account id. We store the resources you create - spaces, experiments, feature
flags, parameters, and audiences - along with the events and exposures your SDKs send us.
Those are keyed by user identifiers you choose, so you decide whether they
identify a real person. We also store the API keys and access tokens your SDKs and MCP
clients authenticate with.
-
How we use and store it.
We use your data to run the service: assign users to variants, evaluate flags, and
compute experiment results. Data is held by third-party cloud providers. The database
is encrypted at rest and in transit, and so is traffic between you and ABMeter. We do
not sell it, use it for advertising, or run analytics or tracking software against it.
-
Third-party sharing.
Our hosting and database providers process data on our behalf. GitHub and Google see
only your sign-in. If you connect an MCP client such as Claude, it receives the data
your own prompts ask for, and nothing else. We share your data with no one else.
-
Retention.
How long we keep events and exposures depends on your plan; beta accounts are limited
to 90 days. We may purge data older than your plan's
retention period. Your current limits are shown on your
Usage page.
-
Contact.
To ask what we hold about you, or to have your account and its data deleted, email
[email protected].