Legal

Subprocessors

We keep this list short on purpose and update it before adding anyone new.

Effective: 16 August 2026 · Version 1.1 · PractiCura™ · LIVISOMA GmbH · The German version is the legally authoritative one.

ProviderPurposeDataLocationTransfer basis
Lovable Cloud (Supabase infrastructure)Application hosting, database, file storage, authenticationAll account and plan dataEUEEA / adequacy
OpenAISpeech-to-text transcription of dictationsAudio submitted for transcriptionUSAEU SCCs + Swiss addendum
Google (via the AI gateway)Structuring text into plan items, optional interpretation viewsPlan text submitted for structuringUSA / EUEU SCCs + Swiss addendum
StripeSubscription payments and invoicesBilling contact and payment metadata (no card data reaches us)USA / EUEU SCCs + Swiss addendum
Email deliverySending check-in reminders and account emails. Clinics may configure their own mail server, in which case no third party of ours is involvedRecipient address, message contentEU / clinic's own providerEEA / clinic's own contract
Telegram (Telegram FZ-LLC)Delivering the daily check-in reminder to clients who have linked their own Telegram chat. Practices may run their own Telegram bot insteadTelegram chat identifier, first name, reminder message content (plan title, practitioner name, check-in link)InternationalClient's own use of Telegram; EU SCCs / Art. 49 FADP where applicable

Changes

We announce new or replaced subprocessors on this page at least 30 days before they go live. Professional customers may object on reasonable data protection grounds by writing to info@livisoma.ch.

Where a practice connects its own Telegram bot, that bot is the practice’s own channel rather than a subprocessor of ours; Telegram itself remains the transport network in both cases. WhatsApp messages are transported by UnificationEngine (UIB).

Questions? Write to info@livisoma.ch.

PractiCura was invented withInnoIP