Subprocessors
This page lists the main third-party providers used to run the service. It is intended as an operational overview, not as a marketing page.
Last updated: August 4, 2026
The service is operated by DPmedia in Poland, European Union. Providers may change over time as the product evolves, but this list is kept in the public trust docs so users and reviewers can see the current stack.
Current providers
Vercel
Category: Hosting and edge infrastructure
Purpose: Runs the web application, API routes, and edge delivery.
Data handled: Application requests and the data needed to serve the product.
Notes: Primary hosting provider for the website and app.
Turso
Category: Database hosting
Purpose: Stores structured analysis results and account-related application data.
Data handled: Extracted transaction data and product metadata needed to display results.
Notes: Uploaded source files are not stored as raw PDFs or images.
Google Gemini API
Category: AI processing
Purpose: Helps categorize transactions and power AI-assisted analysis features.
Data handled: Relevant structured text needed for categorization and analysis prompts.
Notes: Used through API-based processing, not via bank-account connectivity.
Google Cloud Vision
Category: OCR
Purpose: Extracts text from scanned or image-based statements.
Data handled: Images or scanned statement content that requires OCR.
Notes: Used only when OCR is needed for the upload.
Polar
Category: Payments
Purpose: Billing provider for subscriptions, one-time purchases, checkout, and customer portal flows.
Data handled: Payment and billing information needed for subscriptions.
Notes: Card details go directly from the browser to Polar.
Tawk.to
Category: Customer support chat
Purpose: Offers live chat across both public and app pages.
Data handled: Messages and basic session context provided during support conversations.
Notes: Available across both public and app pages.
PostHog
Category: Product analytics and session replay
Purpose: Measures traffic, product funnels, conversion, and aggregated product usage.
Data handled: Page paths, product events, attribution metadata, and masked interaction recordings.
Notes: Input values are masked. Session replay is disabled on results, dashboard, settings, and claim pages.