Privacy-first by architecture

Start without handing over the keys to your AI stack. These are the V0.1 boundaries — not stronger claims than the architecture supports.

1. 01

   No provider credentials

   V0.1 does not require an OpenAI, Anthropic, or other provider admin API key.

2. 02

   No bank or accounting connection

   There is no Plaid, bank feed, QuickBooks, or Xero integration in this product version.

3. 03

   No code changes

   AI Billback does not sit in your application runtime or proxy LLM traffic.

4. 04

   Browser-side parsing

   Raw CSV and billing export files are parsed locally in the browser. They are not uploaded to object storage.

5. 05

   Normalized rows only

   When you intentionally save a workspace, only normalized cost information is stored — not the original file.

6. 06

   Deletion

   You can permanently delete your saved AI Billback workspace data from Workspace settings. An active, canceling, or payment-issue Pro subscription is canceled immediately first. Stripe keeps its own billing records. Your Clerk sign-in, trial window, and founding-offer eligibility stay with your account.

7. 07

   Stripe billing boundary

   When you continue Pro, Stripe receives your workspace and account identifiers and email if available. Cost amounts, client names, and cost descriptions are not sent in Stripe metadata.

Questions: hello@aibillback.com