HTTPS production site
The production service is delivered over HTTPS. Authenticated session cookies are configured as HTTP-only and secure in production.
CashCatalyst asks you to upload financial records, so the data flow should be understandable. This page describes the current product without claiming certifications the service has not independently obtained.
The production service is delivered over HTTPS. Authenticated session cookies are configured as HTTP-only and secure in production.
Cash records are queried by organization. Team administration and invitations are restricted to eligible plans and administrator actions.
State-changing application forms use CSRF protection, and sensitive authentication routes have rate limits.
The current workflow uses uploaded statement exports. CashCatalyst does not ask for your online-banking username or password.
The application accepts supported CSV, Excel, and standard PDF statement exports.
CSV and Excel data are parsed from their columns. PDF content and transaction text requiring AI classification may be sent to Anthropic as an AI service provider.
Pending rows do not become organization transactions until a user confirms the import.
Position, forecast, signals, insights, reports, and grounded assistant answers use organization-scoped records.
| Provider | Purpose | What CashCatalyst does not store |
|---|---|---|
| Anthropic | Supported PDF extraction, classification, daily brief, and assistant responses | Not applicable; financial content needed for the requested AI operation may be processed |
| Stripe | Paid-plan checkout and subscription billing | CashCatalyst does not receive or store full payment-card details |
| Email provider | Account verification, invitations, password reset, and service notifications | Payment-card and bank-login details are not needed for these messages |
| Sentry, when enabled | Application error monitoring | It is not used as the cash ledger or statement store |
Contact [email protected]. We may need to verify the requester before acting on organization data.
Do not attach unredacted bank statements, passwords, payment-card details, or API keys to support messages.