Terms of service — TripCount
Last updated: 2026-06-03Terms of service for using TripCount — the EU-hosted, end-to-end encrypted group trip expense splitter.
What it does
Free AI receipt OCR with a per-user quota, automatic debt simplification (algorithm reduces N people to at most N−1 transfers — same as Splitwise/Tricount), multi-currency with live FX captured per expense from open.er-api.com, end-to-end encryption.
Privacy by default
Expenses encrypted client-side with per-trip AES-GCM envelope keys, stored at rest as opaque ciphertext. EU hosting (Hetzner). The integration test suite asserts on every CI run that no plaintext media bytes appear in any stored artifact. Zero-knowledge — where no escrowed key sits on the server — is on the roadmap.
Payouts and currencies
One-tap settle-up via Bizum, Revolut and PayPal — each owed transfer renders as a deep link pre-filled with amount and recipient. Multi-currency trips capture each expense's FX rate at the moment of entry, so the final settlement reflects actual rates, not an averaged guess.
50 languages including regional EU
50 languages shipped today, including 11 regional/minority European languages (Catalan, Basque, Galician, Asturian, Occitan, Breton, Scottish Gaelic, Welsh, Frisian, Faroese, Romansh) — first-class, not Google-Translate; the Valencian and Balearic variants are derived from Catalan and being refined. The locale matrix and translations live in the open-source repo at frontend/src/locales.
