Data transparency

Processor and service-provider register

This register explains which external services Culinaro uses, when they receive data and for what purpose. A conditional provider receives data only when the related feature is used.

Last reviewed: September 1, 2026

IONOS

Active

Purpose: VPS hosting, API, database and transactional email delivery.
Data categories: Account, profile, content, messages, request, email and security-log data needed to operate Culinaro.
Location and transfer context: Primary infrastructure is configured in the EEA. Contracted location and remote support access remain subject to the controller's vendor review.

Amazon Web Services (S3)

Active

Purpose: Object storage for uploaded recipe and profile media.
Data categories: Uploaded public images, object names and related technical metadata.
Location and transfer context: The bucket is configured in eu-central-1 (Frankfurt). Ancillary access is governed by AWS contractual transfer safeguards.

Google Identity

Feature-dependent

Purpose: Optional sign-in with a Google account.
Data categories: Identity token, email, display name and profile image supplied by Google when the user chooses this method.
Location and transfer context: Google may process data outside the EEA under its applicable transfer safeguards.

Google Analytics

Only with consent

Purpose: Consent-based audience and performance measurement.
Data categories: Cookie identifiers, visited URLs, device and usage metadata; Culinaro blocks Analytics before consent and supports withdrawal.
Location and transfer context: Google may process data in and outside the EEA under its applicable transfer safeguards.

OpenAI API

Feature-dependent

Purpose: Translation of recipes, blog posts and tags, plus assisted SEO and nutrition estimates.
Data categories: Culinary content and task prompts. Verification files, private messages and unnecessary personal data must not be sent.
Location and transfer context: Processing may involve non-EEA locations and is conditional on the controller approving the provider DPA and data-control settings.

Didit

Disabled

Purpose: Optional hosted identity and liveness verification for chefs.
Data categories: Identity-document and liveness data only if the provider is activated and the chef starts verification.
Location and transfer context: Currently disabled. No data is sent until the DPA, subprocessors, locations, deletion terms and biometric roles are approved.

Changes to this register

We update this page when a provider, purpose or transfer arrangement changes. Material changes are communicated through the website or the registered contact channel before they take effect where required.