Every claim backed by evidence. Every control mapped to status. This page exists so your InfoSec team does not have to ask twice — complete due diligence documentation in one place.
We distinguish three tiers of evidence. Public evidence is available to anyone. NDA evidence is provided to qualified prospects after signing. Planned evidence is not yet available.
Infrastructure-level and application-level security controls active in production across all K0nsult deployments.
Current posture against major regulatory and certification frameworks. Honest status — no greenwashing.
| Framework | Status | Details |
|---|---|---|
| GDPR | Compliant | EU hosting only (Frankfurt + Amsterdam). DPA available on request. No tracking cookies. Server-side request logs only for service improvement — no third-party analytics tools, no analytics cookies, no tracking pixels. DSAR process implemented. Art. 17 erasure and Art. 20 portability endpoints live. No cross-border transfers outside EU. |
| EU AI Act | In Progress | AI system inventory registered (2,000+ agent profiles). Risk classification framework: prohibited / high-risk / limited / minimal. Human oversight controls implemented. Compliance tooling actively built. Target: Article 9 conformance by Q4 2026. |
| SOC 2 Type II | Planned Q3 2026 | Controls mapped to Trust Service Criteria (TSC). Evidence collection system active. Audit trail, access control, change management, and incident response procedures documented and operational. Audit engagement in preparation. |
| ISO 27001 | Planned Q4 2026 | Information Security Management System (ISMS) framework defined. Risk register maintained. Control objectives aligned to Annex A. Gap assessment complete. Certification audit planned Q4 2026. |
| ISO 42001 | Planned Q4 2026 | AI Management System requirements aligned. AI governance engine, policy engine, bias monitoring, and human oversight controls are foundational elements. Certification planned alongside ISO 27001 engagement. |
Summary of key DPA terms. Full DPA template available on request via contact form or security@k0nsult.cloud.
K0nsult acts as a Data Processor when processing personal data on behalf of enterprise customers. Enterprise customers are the Data Controllers responsible for determining purposes and means of processing. For K0nsult's own operational data, K0nsult is the Data Controller.
trust-dpa or email security@k0nsult.cloud. We respond within 2 business days.
Answers to the most common InfoSec due diligence questions. Click any question to expand.
All customer data is stored exclusively in the European Union. Primary datacenter is Frankfurt, Germany (Fly.io eu-central region). Failover capacity is available in Amsterdam, Netherlands (Fly.io eu-west region). No data is transferred or replicated outside the EEA. PostgreSQL databases run on encrypted volumes with AES-256 at rest. Data residency is guaranteed at the contractual level in our DPA.
In transit: TLS 1.3 is enforced on all connections. TLS 1.0 and 1.1 are disabled. Certificates are issued by Let's Encrypt with automatic renewal. HSTS is enforced (max-age 1 year, includeSubDomains).
At rest: PostgreSQL data volumes are encrypted using AES-256. Fly.io machine volumes use encrypted block storage. Database credentials and application secrets are stored as Fly.io secrets (never in source code or config files).
Not yet. SOC 2 Type II certification is planned for Q3 2026. We are transparent about this. In the meantime:
To request our current security posture documentation, contact security@k0nsult.cloud.
K0nsult follows a 5-phase Incident Response procedure:
Affected data controllers are notified within 72 hours of a confirmed breach, meeting GDPR Art. 33 obligations. Response SLAs: Critical <1h, High <4h, Medium <24h, Low <72h.
Annual third-party penetration testing is planned as part of the SOC 2 preparation program. Current security testing includes:
Results of penetration testing will be shared under NDA with enterprise customers upon request.
All secrets are managed following a zero-secrets-in-code policy:
Database backups are automated and tested:
Full backup and restore documentation is available at /governance/backup-restore.html.
Google OAuth2 and SAML 2.0 are live on all plans. SCIM provisioning is planned for Q2 2026:
Contact kontakt@k0nsult.cloud to configure your identity provider integration.
SLA targets by plan:
Aktualny status platformy dostepny na /status.html. Endpoint /health zwraca minimalny status: {ok: true, status: 'healthy'}. Infrastruktura na 3 maszynach w 2 centrach danych EU z auto-failover. Scheduled maintenance windows are announced 48 hours in advance via email and status page.
Yes. K0nsult can complete standard vendor security questionnaires including:
Please submit your questionnaire template via the contact form with reference trust-security or email security@k0nsult.cloud. Typical turnaround is 5 business days.
Specific controls for AI systems operated on K0nsult. Relevant for EU AI Act compliance, enterprise AI procurement, and internal AI governance reviews.
K0nsult maintains an AI system inventory with risk classification aligned to the EU AI Act framework:
All 2,000+ registered agent profiles include a risk classification field in the Agent Registry. Risk classification is reviewed and updated as EU AI Act guidance is published.
Human oversight is enforced through a multi-level approval workflow system:
Break-glass procedures allow emergency override with mandatory post-incident review and audit record. All overrides are logged with actor identity, timestamp, and justification.
K0nsult maintains a comprehensive, tamper-evident audit trail for all AI agent actions:
Evidence packs are suitable for regulatory submission and compliance audits. Retention: 7 years by default.
Agent permissions are enforced at multiple layers:
Yes. K0nsult maintains a comprehensive AI System Inventory (Agent Registry) containing:
The registry is accessible via API (GET /api/agents) for enterprise tenants. A human-readable directory is available at /docs/agents_all.html.
Bias and fairness controls are integrated into the governance engine:
K0nsult does not operate its own foundation models. For third-party model integrations (Claude, GPT, etc.), we rely on provider bias controls and supplement with application-layer monitoring.
K0nsult builds transparency into every layer of AI governance:
Yes. K0nsult supports enterprise AI literacy and compliance programs through:
Enterprise customers can request bespoke AI governance training materials tailored to their sector. Contact kontakt@k0nsult.cloud.
Every major claim on this site mapped to its status, evidence type, and availability. Updated: April 2026.
| Claim | Status | Evidence type | Availability |
|---|---|---|---|
| Policy engine enforces rules before execution | ● LIVE | Code + API demo | Public / on request |
| Immutable audit trail with SHA-256 evidence export | ● LIVE | API response + export demo | Public / demo session |
| Multi-level approval queue with SLA tracking | ● LIVE | API + workflow demo | Public / demo session |
| RBAC with 6 roles, per-endpoint enforcement | ● LIVE | Code + API docs | Public |
| Google OAuth SSO + TOTP 2FA | ● LIVE | Auth flow demo | Public / demo session |
| EU hosting — Frankfurt / Warsaw region | ● LIVE | Fly.io region config | Public |
| Daily encrypted backups, 30-day retention | ● LIVE | Restore test report | NDA |
| Incident response — 72h GDPR Art.33 notification | ● LIVE (process) | Policy doc | Public (this page) |
| TLS 1.3 encryption in transit | ● LIVE | SSL Labs / headers | Public (verifiable) |
| AES-256 encryption at rest | ● LIVE | Infra config | NDA |
| SAML 2.0 SSO | ⚡ Enterprise plan | Config on request | Enterprise only |
| SCIM automated provisioning | 🔜 Planned Q3 2026 | — | Not yet available |
| SOC 2 Type II certification | 🔜 Planned Q3 2026 | Controls self-assessment now | NDA (self-assessment) |
| ISO 27001 / ISO 42001 certification | 🔜 Planned Q3–Q4 2026 | — | Not yet available |
| Third-party penetration test | 🔜 Scheduled Q2 2026 | Report post-test | NDA post-test |
Mapping of all active security and governance controls to their evidence source and current operational status.
| Control Area | Control | Evidence | Status |
|---|---|---|---|
| Access Control | JWT + RBAC (6-role hierarchy) | Auth logs, role assignment records, per-endpoint permission matrix | Active |
| Encryption | TLS 1.3 in transit + AES-256 at rest | Certificate records (Let's Encrypt), encrypted volume configuration | Active |
| Logging | Centralized audit trail, SHA-256 integrity | Log exports via /api/audit, event replays, SIEM-ready JSON format | Active |
| Change Management | Versioned deployments, tagged releases | Git commit history, Fly.io deploy logs, release tags | Active |
| Incident Response | 5-phase IR procedure documented | Incident records, severity classification, SLA tracking, post-mortems | Active |
| Business Continuity | Primary runtime: Frankfurt (EU-FRA). Failover capacity: Amsterdam (EU-AMS). No contractual multi-region active-active. Auto-failover on health check failure. | Health check (/health — minimalny status), uptime dashboard, failover test logs | Active |
| Data Protection | GDPR controls, Art. 17 erasure, Art. 20 export | Privacy policy, DPA template, deletion SLA records, export endpoint | Active |
| Vulnerability Mgmt | Dependency scanning, SAST in CI/CD | npm audit reports, Snyk scan outputs, CI pipeline logs | Planned (DAST) |
| Agent Governance | Policy engine + evidence packs + AI registry | Governance packs (SHA-256), policy evaluation logs, agent registry exports | Active |
| Third-Party Risk | Sub-processor register, vendor reviews | Sub-processor list (this page), Fly.io + Stripe compliance documentation | Active |
Retention periods by data type, aligned to GDPR storage limitation principle and applicable regulatory obligations.
| Data Type | Retention Period | Legal Basis |
|---|---|---|
| Application logs | 90 days | Operational necessity — diagnostic and security monitoring |
| Audit trail / evidence packs | 7 years | Legal and regulatory obligation — compliance evidence requirement |
| User account data | Account lifetime + 30 days | GDPR Art. 17 — erasure on account closure after 30-day cooling period |
| Incident records | 5 years | Compliance obligation — security incident documentation requirements |
| Automated backups | 30 days rolling | Disaster recovery policy — continuous rolling backup window |
| Session / authentication data | 24 hours | Security policy — short-lived tokens, session binding limits |
| Financial / billing records | 7 years | Tax and accounting regulations (EU member state laws) |
| DSAR request records | 3 years | GDPR accountability principle — demonstration of compliance |
5-phase incident response procedure. Post-mortem required for all Critical and High incidents.
Transparency about what has been tested, how, and when. Updated quarterly.
| Test type | Status | Last run | Frequency | Evidence |
|---|---|---|---|---|
| SAST (Static Analysis) | ● LIVE | Every deploy | CI/CD pipeline | Internal log |
| Dependency vulnerability scan | ● LIVE | Every deploy | CI/CD + npm audit | Internal log |
| Secrets scan (leaked credentials) | ● LIVE | Every commit | Pre-commit hook | Internal log |
| E2E functional tests (Playwright) | ● LIVE | Every deploy | Post-deploy suite | Internal log |
| Backup restore test | ● LIVE | Q1 2026 | Quarterly | Available under NDA |
| DAST (Dynamic Analysis) | ⚡ IN PROGRESS | — | Planned quarterly | — |
| Third-party penetration test | 🔜 SCHEDULED | Scheduled Q2 2026 | Annual | Report under NDA post-test |
| SOC 2 Type II audit | 🔜 PLANNED | Target Q3 2026 | Annual | Certificate post-audit |
Request and data flow from client to data store. Every layer enforces a distinct security boundary.
// ── K0NSULT ARCHITECTURE — SECURITY & GOVERNANCE LAYERS ──────────────────────────────── // // Each layer is a discrete security and governance boundary. // No layer can be bypassed; all paths converge on the audit logger. // [ Client Browser / Enterprise API Consumer / Mobile ] │ │ HTTPS / TLS 1.3 (enforced, no downgrade) ▼ [ Fly.io Edge — Frankfurt (primary) + Amsterdam (failover) ] │ DDoS mitigation, TLS termination, edge routing │ 3 machines, auto-scaling ▼ [ Rate Limiter ] ─────────────────────────────────────────────────── API: 500 req/15min │ Static: 5000/15min │ Auth: 10 req/15min ▼ [ Authentication Gateway ] ─────────────────────────────────────────── JWT validation │ Token expiry check │ TOTP 2FA, Google SSO │ SAML 2.0 (Azure AD, Okta) LIVE ▼ [ RBAC Middleware ] ────────────────────────────────────────────────── 6 roles: Owner→Guest │ Per-endpoint matrix │ Tenant-scoped access ▼ [ Policy Engine ] ──────────────────────────────────────────────────── Pre-execution eval │ block/warn/approve/ │ escalate outcomes │ Configurable per tenant ▼ [ Route Handler / Business Logic ] ─────────────────────────────────── Input validation │ │ Sanitization │ │ ▼ ▼ [ Governance Engine ] [ Agent Registry ] Approval queues 2,000+ profiles Evidence packs Skill marketplace Incident mgmt Capability matching │ │ ▼ ▼ [ Audit Logger ] ──────────────────────────────────────────────────── Append-only log │ actor/action/target/ts │ SHA-256 integrity hash │ 7-year retention ▼ [ PostgreSQL — EU Only ] ───────────────────────────────────────────── AES-256 at rest Row-Level Security (RLS) Per-tenant isolation Frankfurt + Amsterdam // ── SECURITY HEADERS ON ALL RESPONSES ────────────────────────────────────────────────── // // Strict-Transport-Security: max-age=31536000; includeSubDomains // Content-Security-Policy: nonce-based (migration in progress) // X-Frame-Options: DENY // X-Content-Type-Options: nosniff // Referrer-Policy: strict-origin-when-cross-origin // Permissions-Policy: camera=(), microphone=(), geolocation=()
Download the DPA template, request a completed security questionnaire, or schedule a compliance review call with our security team. We respond within 2 business days.
Email: security@k0nsult.cloud | Privacy Policy | Terms of Service