Privacy policy

Last updated: 17 October 2026

FiscaLLM helps app developers ("customers") compare the AI cost of each of their users with the subscription revenue from that user. This policy explains what we collect, why, and what you can do about it. Questions: theaicommit@gmail.com.

Data about customers

• Your email address, to sign you in and to contact you about your account.
• The apps you create, their settings, and hashed ingest keys.

Data our customers send about their users

Customers' backends and RevenueCat send us, for each of the customer's end users:

• A user identifier chosen by the customer, normally their RevenueCat app user ID, and the aliases RevenueCat reports for it.
• AI usage: time, provider, model, token counts, an optional cost and an optional feature label.
• Subscription events from RevenueCat: product, price, tax and store commission, store, purchase and expiry dates, and the raw event as RevenueCat sends it.

We never receive prompts, AI responses or message content. The SDK sends token counts only. We do not ask for names, emails or other contact details of end users; customers should not send them as user identifiers.

For this data, the customer decides what is collected and why, and we process it on their behalf to provide the service. End users with questions should contact the app developer, who can ask us to delete their data.

How we use it

• To calculate and show cost, revenue and margin to the customer who sent it.
• To operate, secure and fix the service.

We do not sell data, use it for advertising, or share one customer's data with another.

Retention and deletion

• Raw AI usage events are deleted after 90 days. Daily cost totals per user and subscription events are kept while the app exists.
• Customers can delete all data of an app, or the app itself, at any time from its Settings page. Deletion is immediate.
• To delete your account, email us.

Service providers

• Supabase: database and sign-in.
• Vercel: hosting.

Data may be processed in the United States.

Security

Data is encrypted in transit. Ingest keys are stored only as hashes. Access to an app's data requires signing in as its owner.

Changes

We will post changes here and update the date above. For significant changes we will email customers.