← Back to home

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: March 29, 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: Primary billing provider for new subscriptions, checkout, and customer portal flows.

Data handled: Payment and billing information needed for subscriptions.

Notes: Card details go directly from the browser to Polar.

Stripe

Category: Payments

Purpose: Handles billing and customer portal flows for legacy subscriptions.

Data handled: Payment and billing information needed for legacy subscriptions.

Notes: Card details go directly from the browser to Stripe.

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.

Simple Analytics

Category: Marketing analytics

Purpose: Measures visits and page usage on selected marketing and pricing pages.

Data handled: High-level page visit and interaction data on allowed public pages.

Notes: Not loaded on upload, results, dashboard, settings, login, or signup pages.

Google Analytics

Category: Marketing analytics

Purpose: Measures marketing-site traffic and conversion paths on selected pages.

Data handled: Page views and interaction data on allowed marketing and pricing pages.

Notes: Not loaded on upload, results, dashboard, settings, login, or signup pages.

Datafa.st

Category: Marketing analytics

Purpose: Tracks high-level traffic and funnel performance on selected public pages.

Data handled: Page visits and interaction data on allowed marketing and pricing pages.

Notes: Not loaded on upload, results, dashboard, settings, login, or signup pages.

Sourcebeam

Category: Analytics and attribution

Purpose: Measures page views and attribution on marketing and checkout flows.

Data handled: Pageview and attribution metadata on allowed public and checkout pages.

Notes: Not loaded on results, dashboard, settings, login, or signup pages outside checkout.