Service providers

Why this list exists

KDPika uses infrastructure providers to host the platform, deliver transactional email and handle payments. Their role depends on the data and purpose. This list is a transparent pre-launch inventory, not a claim that every location or contract has already been verified. The Privacy notice covers controller processing and the DPA covers processing on developers' instructions. Contact hi@kdpika.com for the completed annex or a provider-change objection.

Hosting — Hostinger

Purpose: website/application hosting, database and infrastructure operation. Relevant data: account, licensing and operational records hosted by the platform. Status: Hostinger is the configured hosting provider. Before launch: verify the contracting Hostinger entity, legal address and telephone, actual data-centre region, support-access countries, DPA, backup retention and any transfer mechanism from the hosting contract. A French business address does not establish an EU-only data location. The provider's general information is available at https://www.hostinger.com/legal; it does not identify this account's specific region by itself.

Payments — Stripe

Purpose: secure payment fields, authentication, subscription billing, invoices, refunds and payment-related fraud prevention. Relevant information: billing/customer identifiers and payment data supplied directly to Stripe. KDPika's application does not store full card numbers or CVCs. Stripe can act as processor for some activities and independent controller for others. Consult https://stripe.com/privacy and the applicable Stripe service agreement for its roles and safeguards. Before launch: confirm the applicable contracting entity, enabled methods, privacy/transfer terms and invoice settings for this account. Payment-provider processing is not a licence to send unrelated licensing customer data to Stripe.

Transactional email — Brevo or Titan/Hostinger SMTP

Purpose: verification codes and links, password recovery, account/service notices and configured transactional messages. Relevant information: recipient address, message content and delivery metadata. Both Brevo and Titan-compatible SMTP configurations are supported; the administrator's active configuration determines which provider handles a message. This page does not assert that both receive every message or that either uses an unverified EU-only location.

Before launch: record the active provider, exact contracting entity, DPA, processing/support locations, security settings and retention. Confirm the sender domain and authenticated email delivery. If another SMTP provider is configured, update this inventory and complete the required processor/transfer review before sending personal data to it. Provider information: https://www.brevo.com/legal/ and https://titan.email/privacy-policy/.

Developer-configured destinations

Developers can configure their own permitted webhook destinations and application integrations. Those destinations are selected by the developer, not automatically approved KDPika subprocessors. Developers must use lawful recipients, protect secrets and avoid unnecessary personal information in payloads. KDPika's URL and security checks do not replace the developer's recipient and transfer assessment.

Changes and evidence

The completed DPA requires advance notice and an opportunity for a reasoned objection to relevant subprocessor additions or replacements. Contact hi@kdpika.com to request the current provider annex, transfer safeguards and applicable notice. No external webhook-testing service is required for core license validation; authoritative licensing responses come from this KDPika deployment.