01
GitHub
Used for source control and, when enabled by the operator, GitHub App/OAuth installation and identity flows. The specific repository/account data available to Veklom depends on the permissions and repositories selected during installation.
Enterprise trust
Disclose the services that actually participate.
Veklom's architecture is intentionally local/private-first, but some product functions can involve third-party infrastructure. This list is conservative: source-code support for a vendor does not automatically make that vendor an active subprocessor.
02
Cloudflare
Used for public DNS/edge routing and Cloudflare Tunnel in the current public-site deployment profile. Cloudflare participation is an ingress/network role; it should not be described as receiving application data that the configured route does not send through it.
03
Optional integrations
The codebase contains optional provider integrations for models, payments, storage and other services. An optional connector becomes relevant to the subprocessor analysis only when it is actually enabled for a deployment and processes customer personal data in a subprocessor role.
04
Change discipline
New production third parties that process customer personal data should be added to this disclosure before or when they enter the applicable production data flow, subject to the notice requirements of the governing agreement.
Truth boundary
This list is not a catalog of every package, API or provider Veklom can technically connect to. It is intended to describe third parties that actually participate in the relevant service/data-processing path.