Privacy Policy

ABMeter is a free feature-flag and experimentation platform. This policy describes what ABMeter collects, why, and who else can see it.

• What ABMeter collects. When you sign in with GitHub or Google, ABMeter receives your email address, name, and the provider's account id. It stores the resources you create - spaces, experiments, feature flags, parameters, and audiences - along with the events and exposures your SDKs send. Those are keyed by user identifiers you choose, so you decide whether they identify a real person. It also stores the API keys and access tokens your SDKs and MCP clients authenticate with.
• How ABMeter uses and stores it. ABMeter uses 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 the service. ABMeter does not sell your data, use it for advertising, or run analytics or tracking software against it.
• Page counts. ABMeter counts visits to public pages, such as the statistics page: which page, the site that linked to it, and the time. It stores no IP address and sets no extra cookie. If you then sign up, your account keeps the first of those pages you read and the site that linked to it. Until then, they are held in the session cookie this site already uses for signing in.
• Third-party sharing. Hosting and database providers process data on ABMeter's 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. Your data is shared with no one else.
• Retention. ABMeter deletes events and exposures older than 90 days. The deletion runs once a day.
• Contact. To ask what ABMeter holds about you, or to have your account and its data deleted, email [email protected].