# AImKeeper Privacy Policy

Last updated September 28, 2026

AImKeeper is a Chrome extension that blocks sites you choose and, if you subscribe, checks pages against a goal you write. This policy explains what AImKeeper collects, why, and who it is shared with.

## What stays on your device

These are stored in Chrome's extension storage on your computer:

- Your Blocks and Monitors: names, site lists, goals, schedules, breaks, locks, and a hashed lock password if you set one.
- Per-site counts of how often AImKeeper allowed or blocked a page, kept for at most 30 days.
- Recent decisions for pages you visited, kept only until Chrome closes.
- Your settings, such as dark mode and the screenshot notice.

None of this is sent to us, except Monitor goals, which are sent as described below.

## What is sent when a Monitor checks a page

Monitors only run if you turn one on, and only on the sites you choose (or on every site, if you turn on "Monitor all sites"). When a Monitor checks a page, AImKeeper sends:

- a screenshot of the visible part of the tab,
- the page address, with tracking parameters removed,
- the page title,
- your goal for that Monitor,
- for YouTube videos, the address of the video's public thumbnail.

The address and title of a page on an active Monitor are sent with the screenshot for the decision. Pages that are not on an active Monitor are not sent.

This goes to the AImKeeper server on Supabase, which forwards it to OpenRouter to get an allow or block decision from an AI model. The AImKeeper server does not save the screenshot, address, title, or goal. Each request is routed only to model providers that do not keep the screenshot, address, title, or goal and do not train on them.

Pages on sites you have not asked AImKeeper to monitor are never captured or sent.

When you save a custom goal, the goal text is sent the same way to check that it is a usable rule.

## Account and payment

Monitoring requires a subscription. You can sign in with Google or with an email and password, through Supabase. Google sign-in stores your Google account's name, email address, and an account ID. Email sign-in sends your email and password to Supabase, which stores the email and a password hash. AImKeeper stores your subscription status, its end date, and your Stripe customer ID linked to that account. A lock password, if you set one, is stored on your device only as a hash.

Payment is handled by Stripe on Stripe's own pages. AImKeeper never sees or stores your card details: [Stripe privacy policy](https://stripe.com/privacy).

Blocks work without an account, and nothing about them is sent anywhere.

## How the information is used

Only to block or allow pages, to check that your goal is usable, and to know whether your subscription is active. AImKeeper does not sell your information, use it for advertising, or use it to decide creditworthiness. It is not shared with anyone except Supabase, OpenRouter and its model providers, Google, and Stripe, as described above.

The use of information received from Chrome APIs adheres to the [Chrome Web Store User Data Policy](https://developer.chrome.com/docs/webstore/program-policies/user-data-faq), including its Limited Use requirements.

## Deleting your data

Uninstalling AImKeeper removes everything stored on your device. To delete your account and subscription record, cancel your subscription from Manage subscription in AImKeeper settings and email the address below. We will delete your account within 30 days.

## Changes

If this policy changes, the new version will be posted at this address with a new effective date.

## Contact

[service@aimkeeper.app](mailto:service@aimkeeper.app)