Service Providers & Data Transfers
This register describes integrations found in the current LifeOrg product. The operator must complete contract, hosting-region and transfer-mechanism fields before enabling public registration.
Current integrations
- Google Gemini API — optional AI generation and image/text recognition; receives the minimized prompt, submitted image and selected feature context. Production must use a paid account and approved data-governance terms.
- DigitalOcean Spaces — object storage for uploaded images and files; configured region and access controls must be recorded in the internal vendor register.
- Map / geocoding providers (MapTiler tiles, Geoapify geocoding, optional Google fallback) — receive the search text and, when enabled, approximate proximity coordinates.
- Telegram — delivery channel for the public support form; receives the name, email and message only when the visitor submits that form. The form must clearly disclose this before submission.
- Identity service, PostgreSQL, Redis, ClickHouse, Grafana and OpenTelemetry — currently operated as LifeOrg infrastructure; the underlying hosting company and regions must be disclosed once the production deployment is selected.
Change notice
This page will be updated before a new provider begins processing personal data. Contractual safeguards do not replace data minimization or user controls. A provider that cannot meet the required health-data and transfer safeguards must not receive sensitive production data.