Alkera publishes a detailed security architecture. Its July 29, 2026 security page separates credentials and model access into distinct trust zones, says credentials are not directly exposed to the LLM, classifies tool calls as read, write, destroy or egress, and requires approval above read unless policy is explicitly configured otherwise.3 It also describes OS-level sandbox restrictions, SAML/OIDC, SCIM, MFA, encryption, signed images, SBOM generation and tamper-evident audit logs.3
The same page says SOC 2 Type II, ISO 27001, GDPR and HIPAA work is in process with external auditors; these should not be represented as completed certifications.3 The Privacy Policy, also updated July 29, 2026, contains broad personal-data provisions and states that conversation and personal data may be stored for up to six years unless an account is deleted, after which disposal is described as no longer than 60 days.6 Teams should reconcile that retention language with any zero-data-retention terms offered on eligible plans.1
Alkera and Y Combinator state that Alkera ranked first on UC Berkeley's DataAgentBench with 83.28% Pass@1.14 The independent DataAgentBench project confirms the benchmark's 54-query, multi-database methodology and public submission model, but the crawler-visible current leaderboard did not independently expose that exact Alkera result during this audit.7 AiToolMap therefore preserves the 83.28/#1 figure as a vendor/YC-repeated claim rather than using it as a numeric rating input. The fixed 50-source panel produced no qualifying exact-product evidence, and missing evidence remains neutral under Rating v1.0.