Support

Route the issue to the boundary that owns it.

Veklom spans runtime, identity, authority, connection, evidence and recovery. Support is clearer when the report names the failing boundary instead of collapsing the entire stack into one generic 'site issue'.

Product & account

Include the affected route, approximate time and browser/device context. Do not include passwords, bearer tokens, refresh tokens or private keys.

Security

Credential exposure, webhook abuse, suspected authorization bypass, evidence tampering or security vulnerabilities: [email protected]

Use /.well-known/security.txt for the canonical public security-contact surface.

Runtime diagnostics

For service/runtime issues, include the affected Veklom plane when known: BYOS, LockerPhycer, CAPPO, cAPI, PGL/Gnomledger, VLink, VNP or Guardian. Health/reachability information is visible on the public status/proof surfaces without exposing internal credentials.

Evidence

When reporting an execution or recovery discrepancy, provide non-secret execution IDs, receipt/event IDs, timestamps and the expected vs observed outcome. Avoid copying full request bodies or sensitive provider data unless explicitly requested through a secure support channel.

Truth boundary

Support will never ask you to paste private keys, OAuth client secrets, bearer tokens or production credentials into a public issue, screenshot or chat.

Security Support Documentation →