Menu
Sign in Demo

Security

Security, data hosting and evidence

Database and sign-in in Frankfurt. Separation of customers by database rules. No training of a language model on contract content.

No certification. Self-assessment against ISO/IEC 27001:2022 on 16 November 2026.

As of 18 November 2026

Overview

SubjectStatusBasis
Database and sign-inSupabase, Frankfurt (AWS eu-central-1), since 19 September 2026Project configuration
Contract data in the delivered filesnone; the application loads data only after sign-inConfiguration
Encryption in transitHTTPS on all addresses, HSTS valid for one yearMeasured 17 November 2026
Encryption at restby the database providerProvider statement
Separation of customersTenant key and database rule on 39 tablesTest on 22 September 2026 on a copy
Training on contract contentexcludedCommercial terms of the model provider
Two-factor sign-in in CLEVERnot available; sign-in by link or with a Google or Microsoft accountStatus of the application
Certificationnone; no ISO/IEC 27001 certificate, no SOC 2 report—
Reporting of vulnerabilitiesinfo@clever-ai.org, /.well-known/security.txtRFC 9116

Hosting and data storage

Encryption and response headers

Access, roles and tenant separation

Sign-in

Link by e-mail or a Google or Microsoft account. CLEVER stores no password. A new account can be used only after approval. Two-factor sign-in in CLEVER: not available.

Roles

Rights per role, among them Admin, Deal Manager, Risk Manager and Approver. Enforced by database rules per role (Row Level Security), also on direct access to the interface.

Tenants

Tenant key on 39 tables, set by the database; a foreign value sent by the browser is rejected. The members are decided by the tenant’s Admin. The operator creates tenants, adds no members and assigns no roles.

Test of the separation

On 22 September 2026 on a copy of the database schema: 25 of 25 checks without a foreign row, 195 of 195 pairs of role and table unchanged. Internal test, no third-party audit.

Residual risk

One database rule separates the customers of a shared database; an error in it would affect all tenants. An own database per customer is available by agreement.

Log

Deletions, restorations and permanent deletions are recorded in a log that only appends entries. Read access for the Admin only.

Sub-processors

ServicePurposeContract dataLocationEvidence per provider
SupabaseDatabase and sign-inyesFrankfurt (AWS eu-central-1)ISO/IEC 27001:2022, SOC 2 Type 2
NetlifyDelivery of the website and the application, server functionsin transit only, not storedEdge nodes without assured location; server functions USAISO/IEC 27001, SOC 2 Type 2
Anthropic (Anthropic Ireland, Limited)Analysis by the language modelyesoutside the EEASOC 2 Type 2, ISO/IEC 42001
Amazon Web Services (Bedrock)Analysis in the EU, only with the add-on “EU processing”yes, with the add-onFrankfurtISO/IEC 27001, BSI C5
ResendDelivery of notifications and of the sign-in linkpartly: subject, recipient, content of the notificationUSASOC 2 Type 2
GoogleSign-in with a Google account; reading a document selected in Driveonly on selection by the userEU and USAISO/IEC 27001
Microsoft (Microsoft Ireland Operations Ltd.)Sign-in with a Microsoft account (Entra ID)noneEU (EU Data Boundary); USA in individual casesISO/IEC 27001

Without contract data, with personal data: Microsoft 365 (e-mail and appointments); GitHub (source code and automated checks with test accounts and synthetic contracts, started hourly by a server function; in reports on failed analyses a pseudonym of the user instead of the e-mail address); Plausible (visitor statistics of the website, not in the application).

Without personal data: Cloudflare (DNS without routing through Cloudflare); European Central Bank (exchange rates, retrieved by the server).

Independent controller: Paddle (payment processing as reseller; the application loads the Paddle checkout only on purchase).

Evidence as stated by the providers, retrieved on 16 November 2026. Anthropic’s sub-processors are listed at anthropic.com/subprocessors. Legal basis of transfers: privacy notice, section 4.

Language model

Reporting of vulnerabilities

Address

info@clever-ai.org, subject “Security”. Machine-readable at /.well-known/security.txt (RFC 9116).

Content

Affected address or function, steps to reproduce, time, own contact address.

Limits

Tests with an own account only. No access to data of other customers beyond the proof, no modification or deletion of data, no load or denial-of-service attempts, no deception of people.

Response time

First response within 5 business days.

Confidentiality

No publication before the fix.

Rewards

There is no bounty programme.

Security incident

ISO/IEC 27001

Certification

None. No ISO/IEC 27001 certificate, no SOC 2 report, no BSI C5 attestation.

Self-assessment

On 16 November 2026 against ISO/IEC 27001:2022: clauses 4 to 10 and the 93 controls of Annex A, each with evidence or gap. No third-party audit.

Management system

Drafts of 17 November 2026: scope, information security policy, roles, risk assessment method, inventory, access policy, incident policy, endpoint policy. Approval by the management pending.

Audit

No date agreed with a certification body.

Questionnaires and contracts

Supplier questionnaire and data processing agreement on request via info@clever-ai.org.

Documents

Security questions

Supplier questionnaires, data processing and architecture: info@clever-ai.org.