Privacy

AI Cost Map stores as little personal data as possible. We store no name, email or password. Only an anonymous account ID from the provider.

What we store

An anonymous account ID from your sign-in provider

You sign in with Google, GitHub or X. We keep the provider name and the account ID that the provider gives us, so that you can sign in again. Each provider that you link adds one ID.

Organization and project data

Organization, project and environment names, your role, the date that you joined, API key hashes, budget alerts and billing state.

Token counts and labels

Provider, model, token counts, feature, environment, your tags and an optional customer ID that you choose. See what the SDK sends.

Only what you type, by choice

An optional display name in Settings, and the email addresses or Slack webhook that you type into a budget alert. They are stored only on your profile or on that alert.

What we never store

• Your name, email address or profile picture from Google, GitHub or X. We ask for the smallest scopes, and we replace these values before anything is saved.
• A password. There is no email and password sign-in and no magic link.
• OAuth access, refresh or ID tokens. We do not call the provider APIs after the sign-in.
• The IP address or the browser (user agent) of a session.
• Your prompts or the outputs of your models. They never leave your servers.

Cookies

• A session cookie keeps you signed in. It holds a random session token.
• acm_last_provider remembers which provider this browser used last (google, github or twitter), so the sign-in page can highlight it. It is a first-party cookie for 1 year. It is stored only in your browser, never in our database.
• Two cookies remember the project and environment that you selected in the dashboard.

Billing

When you choose a paid plan, Stripe Checkout asks for your billing email and payment details. Stripe keeps them. We do not send Stripe an email address, and we keep only the Stripe customer and subscription IDs.